Date: Wed, 22 Oct 1997 10:10:41 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: "Brian N. Handy" <handy@sag.space.lockheed.com> Cc: Nate Williams <nate@mt.sri.com>, Mike Smith <mike@smith.net.au>, mobile@freebsd.org Subject: Re: Patches from -current for -stable I'd like to commit after testing Message-ID: <199710221610.KAA10346@rocky.mt.sri.com> In-Reply-To: <Pine.OSF.3.96.971021224641.5461B-100000@sag.space.lockheed.com> References: <199710220418.WAA08580@rocky.mt.sri.com> <Pine.OSF.3.96.971021224641.5461B-100000@sag.space.lockheed.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> OK, I jumped to conclusions a little too fast... > > My box won't suspend now. When I pull the pccards, invoke 'zzz', and sit > back... the lights blink for a second, the laptop appears to suspend, the > screen goes black and the sounds go away. Then, a second later, it starts > back up again! The error logs say: > > Oct 21 22:49:22 kriek /kernel: sio2: unload,gone > Oct 21 22:49:22 kriek /kernel: Return IRQ=10 > Oct 21 22:49:22 kriek /kernel: Card removed, slot 0 > Oct 21 22:49:22 kriek /kernel: stray irq 10 > > [Now my trusty assistant types 'zzz' at the console] > > Oct 21 22:49:32 kriek /kernel: sio2: suspending This is weird here, since sio2 is already gone. But, I'm seeing this on -current as well, so I'm not sure what's up. I thought it was due to something weird on my box, but it appears that drivers aren't fully unloaded for some reason although they should be. > Oct 21 22:49:32 kriek /kernel: Entire system suspend failure: errcode = 96 > Oct 21 22:49:32 kriek /kernel: calcru: negative time: -804770 usec > Oct 21 22:49:55 kriek /kernel: resumed from suspended mode (slept 00:00:23) > Oct 21 22:50:00 kriek /kernel: Card inserted, slot 0 > Oct 21 22:50:11 kriek /kernel: sio2: type 16550A > > (I included the first part as proof I pulled out the modem first. :-) Hmm, that's no good. > It puzzles me that it also burps up this sio2 error, with the card out. That's very confusing. I'll look into it on my box to see if I can track anything down. > But it does. This with with the sysctls both set and unset. (But not one > or the other.) Sooo...something seems amiss. Can you yank *all* the patches and see if they are making the difference? It's possible the 'low-power' changes may have an adverse affect, since with both sysctl's unset, the only changes are the modem speaker and the power. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710221610.KAA10346>