Subject: Re: kern/29903 (register data)
To: None <firstname.lastname@example.org>
From: Arto Selonen <email@example.com>
Date: 04/21/2005 13:27:21
On Thu, 21 Apr 2005, Martin Husemann wrote:
> From: Martin Husemann <firstname.lastname@example.org>
> To: Arto Selonen <email@example.com>
> Cc: firstname.lastname@example.org
> Subject: Re: kern/29903 (panic is back; data follows)
> Date: Thu, 21 Apr 2005 12:07:28 +0200
> On Thu, Apr 21, 2005 at 12:54:03PM +0300, Arto Selonen wrote:
> > 2231 m->m_len = len;
> Hmm, can you examine the value of the ebx register at this point?
> (show registers at the db> prompt should do that)
ebx is 0
It has been at least 10 years since I last used any debugger,
and even then it was minimal, so the more detailed your instructions
the better. :) The above is from 'show registers' at the ddb 'db>'
prompt right after the panic, and not from gdb; nor did I do anything
to make it be at "m->m_len = len;"
I am no longer able to make the system panic 100% of the attempts any
more. It did panic after three attempts, and is now sitting in ddb, so
at least at the moment I can provide more data as needed. This is
currently a testbed, so there is no immediate need to reboot it.
I could keep it in ddb for several days, if needed, though I suspect
it should not be too hard to get it panic again. But for the next
few hours/days, I can provide more timely data as needed.
#######======------ http://www.selonen.org/arto/ --------========########
Everstinkuja 5 B 35 Don't mind doing it.
FIN-02600 Espoo email@example.com Don't mind not doing it.
Finland tel +358 50 560 4826 Don't know anything about it.