Date: Mon, 4 Jan 2010 07:50:41 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: freebsd-stable@freebsd.org Subject: Re: 8.0 regression: consecutive panics (iwi / wlan / zfs ?) Message-ID: <20100104155041.GA73184@icarus.home.lan> In-Reply-To: <hht15s$9up$1@ger.gmane.org> References: <hht15s$9up$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 04, 2010 at 04:13:36PM +0100, martinko wrote: > A few hours ago I experienced 3 consecutive panics on this freshly > installed 8.0, the last panic just 28s into boot sequence. It seems > to me that culprit could be iwi/wlan possibly with help from zfs or > others. > More details even with screen-shot of the last panic follow. > > I have used versions 5.3 to 6.4 on this laptop, the last one being > the most stable and smooth. A few weeks ago I moved to 8.0 (fresh > install) and since then I've been experiencing funny issues. > > Last night I was writing an email when I noticed my wi-fi link was > gone. I checked /var/log/messages and saw the following: > > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > wlan0: link state changed to DOWN > wlan0: link state changed to UP > linux: pid 6189 (skype): syscall inotify_init not implemented > ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable, > add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. > ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable > behavior. > Consider tuning vm.kmem_size and vm.kmem_size_max > in /boot/loader.conf. > ZFS filesystem version 13 > ZFS storage pool version 13 > > While wifi weirdness did not impressed me, I was perplexed by ZFS > messages. I checked kldstat and indeed ZFS was loaded. Note that I > have not attached any ZFS storage devices nor I have ever configured > ZFS on this laptop. And before I could investigate any further my > laptop froze and then rebooted. The ZFS messages in question get printed when ZFS initialises (in your case, when the kernel module was loaded). How or why it got loaded is beyond me. In this case would help to post these kinds of kernel messages taken directly from /var/log/messages instead of from dmesg -- the file in question is handled by syslog and will have timestamps. I can't help with the rest of the problems mentioned, sorry. :-( -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100104155041.GA73184>