Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Aug 2007 08:55:48 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        Joshua Isom <jrisom@gmail.com>
Subject:   Re: Debugging problems on amd64-current
Message-ID:  <200708270855.48720.jhb@freebsd.org>
In-Reply-To: <7ed534d5904b6579416f3c1be82c2792@gmail.com>
References:  <7ed534d5904b6579416f3c1be82c2792@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 24 August 2007 03:13:08 am Joshua Isom wrote:
> As some may remember, about a month ago I asked a question about my dvd  
> drive, apparently an sata atapi drive.  Updating to a 7.0-current/amd64  
> kernel did allow it to be recognized and I've been able to use it.  But  
> recently I'd been noticing a kernel crash I could create.  My computer  
> is headless so I didn't get any dump(savecore saved nothing).  If I  
> used gdb and stepped after a segfault, it'd crash the system.  Pressing  
> the power button did nothing, and pressing and holding it was required  
> to get it to do something.  Although I knew there was a problem, I  
> figured I'd update my world to match my kernel(a few apps didn't work  
> with the mismatch but those I needed did).  It went smoothly, until I  
> tried running gdb.

Have you tried breaking into the kernel debugger?  It sounds like you've
hit a deadlock of some sort.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708270855.48720.jhb>