On Thu, Dec 08, 2005 at 07:32:13AM -0500, Sean Davis wrote:
> On Thu, Dec 08, 2005 at 12:12:57PM +0100, Pavel Cahyna wrote:
> > On Thu, Dec 08, 2005 at 01:10:02AM +0000, Sean Davis wrote:
> > >  On Thu, Dec 08, 2005 at 12:40:02AM +0000, Martin Husemann wrote:
> > >  >  Could you try the same on a kernel with options LOCKDEBUG, DEBUG and DIAGNOSTIC
> > >  >  defined?
> > 
> > makeoptions DEBUG="-g" could be also helpful
> > 
> > >  
> > >  I'd be happy to once bin/32267 is resolved - however, due to the issue in
> > >  that PR, I cannot login on console - only through KDM - so I wouldn't be
> > >  able to write down any panic messages if the machine were to deadlock again.
> > 
> > blind type bt/l and then reboot 0x104. If the kernel is really in ddb, it
> > should write a crash dump and then reboot. You can the extract the panic
> > messages with dmesg -M.
> 
> Will this work with a USB keyboard? I remember reading about issues with ddb

Don't know - I never used an USB keyboard. I think that there is some
workaround for this issue (like removing PS/2 keyboard from the kernel?)

Pavel