From owner-freebsd-stable@FreeBSD.ORG Tue Jan 5 22:47:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDC29106566B for ; Tue, 5 Jan 2010 22:47:49 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 633D58FC0A for ; Tue, 5 Jan 2010 22:47:49 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NSIBm-0007uV-Lx for freebsd-stable@freebsd.org; Tue, 05 Jan 2010 23:47:46 +0100 Received: from 200.41.broadband11.iol.cz ([90.178.41.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 23:47:46 +0100 Received: from gamato by 200.41.broadband11.iol.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 23:47:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Tue, 05 Jan 2010 23:47:34 +0100 Lines: 66 Message-ID: References: <20100104155041.GA73184@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 200.41.broadband11.iol.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.6) Gecko/20100102 SeaMonkey/2.0.1 In-Reply-To: <20100104155041.GA73184@icarus.home.lan> Sender: news Subject: Re: 8.0 regression: consecutive panics (iwi / wlan / zfs ?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2010 22:47:50 -0000 Jeremy Chadwick wrote: > 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. :-( > There's nothing else in log regarding ZFS. It sure was loaded as I checked with kldstat. But I have not loaded it nor I have ever had any device with ZFS on it near this laptop. Really strange. This appeared in log shortly before a crash: Jan 4 04:42:24 mb-aw1n-bsd kernel: wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost Jan 4 04:42:24 mb-aw1n-bsd kernel: wlan0: link state changed to UP Jan 4 04:42:24 mb-aw1n-bsd kernel: iwi0: firmware error And then again on subsequent boot. Wi-fi did not work and system panicked again. Then panicked already during boot. A then I switched it off which obviously helped (to restore HW to its defaults?). Hm.. M.