Date: Sun, 2 May 2010 20:00:15 GMT From: Dominic Fandrey <kamikaze@bsdforen.de> To: freebsd-net@FreeBSD.org Subject: Re: kern/144898: [wpi] [panic] wpi panics system Message-ID: <201005022000.o42K0Fjg019091@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/144898; it has been noted by GNATS. From: Dominic Fandrey <kamikaze@bsdforen.de> To: jeff curry <jeff@degrind.org> Cc: bug-followup@FreeBSD.org Subject: Re: kern/144898: [wpi] [panic] wpi panics system Date: Sun, 02 May 2010 21:55:02 +0200 On 02/05/2010 21:45, jeff curry wrote: > This is happening to me as well, 8.0-release p2, amd64, 4 GB RAM, same > motherboard chipset and graphics card ( Dell D630 ). > > wpi0: device timeout > wpi0: could not set power mode > wpi0: device config failed > > kldunload -> kldload panics the system often but not always. wpi0 device > timeouts happen more often with X/gnome running. wireless will not work > after this until a reboot ( when kldload doesn't cause kernel panics ) I have found a very reliable (as in 100%) way to panic the system. - Turn radio off (via hardware switch) - Load the driver and firmware - Turn radio on (via hardware switch) Voilà, instant panic. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005022000.o42K0Fjg019091>