Date: Fri, 25 Dec 2009 11:31:31 -0800 From: Sam Leffler <sam@errno.com> To: Frank Staals <frank@fstaals.net> Cc: Lars Engels <lars.engels@0x20.net>, freebsd-mobile@freebsd.org Subject: Re: wpi and suspend/resume Message-ID: <4B351313.4000506@errno.com> In-Reply-To: <4B32688A.3030602@fstaals.net> References: <4B30FE4E.9050801@fstaals.net> <20091223115046.cs98224exsgw00ok@0x20.net> <4B32688A.3030602@fstaals.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank Staals wrote: > On 12/23/09 11:50, Lars Engels wrote: >> <snip> >> >> You could try to unload the module before you go to standby and reload >> it after resuming. > Ah I forgot to mention that: I actually also tried that unfortunately > that resulted in wpi completely hanging my system when I try to reload > it after resuming. It again gives a bunch of 'wpi0: could not lock > memory' errors. Then something what I believe to be > initializing/scanning? channels and then: > > wpi0: SKU does support 802.11a > panic: ieee8021_get_ratetable: no rate table for channel: freq 0 flags 0x0 > > > This sounds like wpi didn't read data properly from the eeprom on resume. The panic is because no channels were registered by the driver. There look to be debug msgs in the driver that can help track that issue down. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B351313.4000506>