Subject: Re: Is this a panic or a break to ddb?
To: None <email@example.com>
From: Mark Cullen <firstname.lastname@example.org>
Date: 08/05/2006 13:31:56
Pavel Cahyna wrote:
> On Wed, Aug 02, 2006 at 04:30:53PM +0100, Mark Cullen wrote:
>> I would think that if I set ddb.fromconsole=0 and ddb.onpanic=0 that sending a
>> break wouldn't drop to ddb anymore, and it will reboot automatically when it
>> panics, right? I've done that now.
>> I'm a little concerned about the 'onpanic' one, as manually typing 'reboot' or
>> 'sync' at ddb just hangs (I mentioned this in another mail regarding RAIDFrame
>> actually). In order for it to work I need... 'reboot 0x104' (as in the
>> RAIDFrame 'testing kernel dumps'. I don't know what the 0x104 means, but is
>> this what a panic() will do if it's not set to drop to ddb?
> I'm afraid not, I think it will do an equivalent of "sync".
> Try sysctl -w ddb.commandonenter="reboot 0x104"
Is that a -current thing only? I don't have that sysctl. Any idea why my
machine might hang in the first place, unless it's a 'reboot 0x104'?
What does the 0x104 actually mean?
Mark Cullen <email@example.com>
BSc (Hons), Computer Science