Re: Trap 0x34 panic on 5.1 on Blade 100

To: Martin Husemann <martin%duskware.de@localhost>
Subject: Re: Trap 0x34 panic on 5.1 on Blade 100
From: George Harvey <fr30%dial.pipex.com@localhost>
Date: Sat, 7 May 2011 23:45:52 +0100

On Sat, 7 May 2011 09:18:26 +0200
Martin Husemann <martin%duskware.de@localhost> wrote:

> On Sat, May 07, 2011 at 12:13:02AM +0100, George Harvey wrote:
> > Are there any kernel debug options I could set to get a more readable
> > traceback?
> 
> If this is not a production server, you probably want ddb.onpanic = 1
> in /etc/sysctl.conf.

Looks like it could be the gem driver, I switched to a 3Com Ethernet
card and it stopped crashing.

George

Follow-Ups:
- Re: Trap 0x34 panic on 5.1 on Blade 100
  - From: George Harvey

References:
- Trap 0x34 panic on 5.1 on Blade 100
  - From: George Harvey
- Re: Trap 0x34 panic on 5.1 on Blade 100
  - From: Martin Husemann

Prev by Date: Re: NetBSD/sparc64 and GbE performance
Next by Date: Re: NetBSD/sparc64 and GbE performance
Previous by Thread: Re: Trap 0x34 panic on 5.1 on Blade 100
Next by Thread: Re: Trap 0x34 panic on 5.1 on Blade 100
Indexes:

Home | Main Index | Thread Index | Old Index