Subject: Re: Qube2 random crash at 3.1
To: Izumi Tsutsui <firstname.lastname@example.org>
From: Andy Ruhl <email@example.com>
Date: 02/27/2007 18:02:47
On 2/23/07, Andy Ruhl <firstname.lastname@example.org> wrote:
> On 2/23/07, Izumi Tsutsui <email@example.com> wrote:
> > Could you post actual panic message which should be shown
> > before the first bt command? Panic after sync on ddb could
> > happen if some kernel structures were corrupted and it isn't
> > a real problem.
> No, I don't leave the serial console session active (hyperterm on a
> windows box usually). I did try to save a crash file but it complained
> about something so I'm guessing it's corrupt. But it did save
> something and I still have it. Would this help?
> I'll see if I can leave the serial console session on for a while to
> see if I can catch it.
> BTW, the way I notice this is my machines on my network can't connect.
> This Qube is my firewall/gateway, so I hit it with hyperterm, and I
> get a db> prompt. I have the sysctl ddb.fromconsole turned off
> (learned that the hard way) so it's probably really panicking.
> I'll try to get you that data. Thanks Izumi.
Well, I've had a hypterterm session active since I wrote that email,
and of course it hasn't crashed yet :)
I'll turn it off and it will crash tonight, so I can then try again :)