Date: Fri, 11 Aug 2000 01:21:35 +0100 From: Josef Karthauser <joe@pavilion.net> To: Brian Somers <brian@Awfulhak.org> Cc: freebsd-bugs@FreeBSD.ORG, sheldonh@FreeBSD.ORG Subject: Re: kern/20375: APM doesn't work properly! Suspend/resume/suspend/hang Message-ID: <20000811012135.A353@pavilion.net> In-Reply-To: <20000810122214.J1050@pavilion.net>; from joe@pavilion.net on Thu, Aug 10, 2000 at 12:22:15PM %2B0100 References: <joe@pavilion.net> <200008101112.MAA03082@hak.lan.Awfulhak.org> <20000810122214.J1050@pavilion.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 10, 2000 at 12:22:15PM +0100, Josef Karthauser wrote: > On Thu, Aug 10, 2000 at 12:12:17PM +0100, Brian Somers wrote: > > > > With the dodgy call to tsleep (passing a NULL as the first arg) I was > > getting a panic in the KASSERT in tsleep(), but once that was fixed > > I'm back where I can suspend, resume then lock up when I try to suspend > > again. > > > > It'd be worth looking at a crash trace if you can get one. > > Mine was working once _until_ the tsleep fix! I'll recompile the > kernel again afresh and check again. My guess is that this tsleep > is independant to my original report. To repeat - even though it looks like the KASSERT in tsleep fixed the ata code for you, it's still broken for me on the head branch. Upon a resume the debugger kicks in at tsleep within atareset. > My original problem is the same as what you report above. I've > tried with a cutdown kernel, to remove the possibility that it's > pcm, etc, but it does appear to be more fundamental than that. I > don't get a crash, just a hang, so no coredump or back trace is > available. :( I've gone back to 1/Aug/2000 for the ata code to get around that local problem which isn't necessarily the direct cause of the suspend/resume hang that you mention, and which appears to be the same as the one that I opened this PR under. My suspicion is that something isn't resuming properly and when asked to suspend a second time it's hanging the system. I wish that I could find our where the hang is occuring. Joe 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?20000811012135.A353>