Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 May 2007 01:20:24 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Nikos Vassiliadis <nvass@teledomenet.gr>
Cc:        freebsd-net@freebsd.org, Robert Watson <rwatson@freebsd.org>
Subject:   debuging a hung kernel
Message-ID:  <465A90C8.8020600@elischer.org>
In-Reply-To: <200705281104.22384.nvass@teledomenet.gr>
References:  <200705221006.49359.nvass@teledomenet.gr>	<200705281033.08968.nvass@teledomenet.gr>	<465A8B7B.7060204@elischer.org> <200705281104.22384.nvass@teledomenet.gr>

next in thread | previous in thread | raw e-mail | index | archive | help
Nikos Vassiliadis wrote:
> On Monday 28 May 2007 10:57, Julian Elischer wrote:
>> Nikos Vassiliadis wrote:
>>> On Tuesday 22 May 2007 10:06, I wrote:
>>>> Hello everybody,
>>>>
>>>>  I just managed to lock my box and I want to report it
>> define "lock"?
>>
>> Does it still respond to <CTL><ALT><ESC> on the keyboard?
> 
> No, but I was trying to break to the debugger with
> <Control><PrintScreen> myself. I assume that it is
> equivalent to the combination you wrote, or not?
> 
>> (Assuming you have the debugger in your kernel?).
> 
> Yes, I have included my kernel configuration, see bellow.
> 
>> Does it still ping?
> 
> no, ARP does not work as well.
> 

nasty.. do you have IPMI?
sometimes that allows you to generate an NMI
that could theoretically be made to drop to the debugger.

I've not had success with that but I have heard others have.




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