Date: Mon, 14 Aug 2000 02:40:02 -0700 (PDT) From: Josef Karthauser <joe@pavilion.net> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/20375: APM doesn't work properly! Suspend/resume/suspend/hang Message-ID: <200008140940.CAA33576@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/20375; it has been noted by GNATS. From: Josef Karthauser <joe@pavilion.net> To: freebsd-bugs@FreeBSD.ORG Cc: Subject: Re: kern/20375: APM doesn't work properly! Suspend/resume/suspend/hang Date: Sat, 12 Aug 2000 17:47:28 +0100 On Fri, Aug 11, 2000 at 05:30:09AM -0700, Josef Karthauser wrote: > > I believe that it broke sometime in the last couple of months. > > If I could get a trace that'd find the culprit, but unfortunately > the machine hangs hard - power reset required. Maybe some debug > output to stderr would catch the problem. Is there somewhere in > the bus code that I can add some debug that'll show each device > being suspended? > Ok, more updates. There _is_ a sysctl (debug.apm_debug) recently added for debugging. Using the kernel debugger I've determined that the freeze is almost definitely in the bios32 call: apm_do_suspend apm_suspend_system apm_bioscall bios32 HANG This happens on the second suspend only, the first time through it succeeds, and returns after a resume event (keypress, etc.). Who's our APM wizard? I've no idea what the bios interaction should be. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008140940.CAA33576>