Alan DuBoff wrote:
> On Sun, 16 Sep 2007, [EMAIL PROTECTED] wrote:
>
>> I assume you know about the "snooping" flag and deadman timer. This
>> can be
>> useful in getting a dump when the system is "hard" hung (i.e., you may
>> or may not
>> have kmdb loaded, but you can't get in).
>
> Recentely I
Alan DuBoff wrote:
> On Sun, 16 Sep 2007, [EMAIL PROTECTED] wrote:
>
>> Hi All,
>> OK. I figured out how to get my blog stuff working in English, so you
>> can also read about the modified mdb on my blog,
>> http://mbruning.blogspot.com/
>>
>> max
>
> This is very nice! I didn't know you had all t
On Sun, 16 Sep 2007, [EMAIL PROTECTED] wrote:
> I assume you know about the "snooping" flag and deadman timer. This can be
> useful in getting a dump when the system is "hard" hung (i.e., you may
> or may not
> have kmdb loaded, but you can't get in).
Recentely I've had a system that wouldn't co
On Sun, 16 Sep 2007, [EMAIL PROTECTED] wrote:
> Hi All,
> OK. I figured out how to get my blog stuff working in English, so you
> can also read about the modified mdb on my blog,
> http://mbruning.blogspot.com/
>
> max
This is very nice! I didn't know you had all this info, very cool stuff.
--
John Levon <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 16, 2007 at 09:49:27PM +0200, Joerg Schilling wrote:
>
> > > Much better is to add an option to abort_sequence_enter() to panic
> > > instead of
> > > drop into the debugger. That way you wouldn't even need kmdb. Of course,
> > > the
> > > opti
On Sun, Sep 16, 2007 at 09:49:27PM +0200, Joerg Schilling wrote:
> > Much better is to add an option to abort_sequence_enter() to panic instead
> > of
> > drop into the debugger. That way you wouldn't even need kmdb. Of course, the
> > option would imply nopanicdebug=1.
>
> Thank you for this hi
John Levon <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 16, 2007 at 02:26:52PM +0200, Joerg Schilling wrote:
>
> > If you do not own a x86 system that itself implements remote
> > administration, you need to run Solaris x86 permanently under kmdb.
> >
> > This is because the only way to
On Sun, Sep 16, 2007 at 03:14:32PM +0200, [EMAIL PROTECTED] wrote:
> I think better is a flag that says that when the system panics, bypass
> kmdb and go immediately
> to the dump code.
Right.
> And I think this should be the default behaviour. I
> mostly use kmdb > for analyzing hangs, not p
On Sun, Sep 16, 2007 at 02:26:52PM +0200, Joerg Schilling wrote:
> If you do not own a x86 system that itself implements remote
> administration, you need to run Solaris x86 permanently under kmdb.
>
> This is because the only way to abort a hung x86 system is to send
> a
Joerg Schilling wrote:
> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
>
>> Hi All,
>> OK. I figured out how to get my blog stuff working in English, so you
>> can also read about the modified mdb on my blog,
>> http://mbruning.blogspot.com/
>>
>
> Well, let me take your use your work
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Hi All,
> OK. I figured out how to get my blog stuff working in English, so you
> can also read about the modified mdb on my blog,
> http://mbruning.blogspot.com/
Well, let me take your use your work on mdb as a cause for thoughts on kmdb
usabil
Hi All,
OK. I figured out how to get my blog stuff working in English, so you
can also read about the modified mdb on my blog,
http://mbruning.blogspot.com/
max
[EMAIL PROTECTED] wrote:
> Hi All,
> I have modified mdb so that I can use ::print type with a raw disk. You
> can read this: http:
12 matches
Mail list logo
