Re: Trap 0x34 panic on 5.1 on Blade 100

[George Harvey <fr30%dial.pipex.com@localhost>]

On Sat, 7 May 2011 23:45:52 +0100
George Harvey <fr30%dial.pipex.com@localhost> wrote:

> 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.

After further testing, it appears that I only get panics when using the
on-board gem interface with a 100Mb half-duplex connection.
Specifically, when connected to a 3Com SuperStack II Dual Speed Hub 500.
With a full-duplex switch connection, or even with an old 10Mb hub, I
don't get any panics. The following backtrace is from a panic caused
by starting xterm over ssh. FTP and NFS also produce similar panics:

blade100# trap type 0x34: cpu 0, pc=137b108 npc=137b10c 
pstate=44800006<PRIV,IE> kernel trap 34: mem address not aligned
Stopped in pid 451.1 (sshd) at  netbsd:m_xhalf+0x8:
 ld [%o0 + 0 x20], %g2
db> bt
bpf_mtap(2ed0e00, c78c0f0, 0, 800, 2, 0) at netbsd:bpf_mtap+0xd4
gem_rint(c78c000, 80000000, 17d8, 1ff00400000, 4, 4000) at
netbsd:gem_rint+0x2cc
gem_intr(0, 0, e0017ed0, 4243ea34, 11a3f20, d36bdc0) at netbsd:gem_intr
+0x144 
sparc_interrupt(c0af558, ffffffffffff7e6c, 90,
fffffffff3f5891c,5ce88622, 42940144) at netbsd:sparc_interrupt+0x1dc
copyout_vmspace(c072b80, c0af044, ffffffffffff7958, 5a8, 0, 0) at
netbsd:copyout _vmspace+0x5c
uiomove(c0af044, 5a8, d36bbf0, 0, 0, 34b0) at netbsd:uiomove+0xa8
soreceive(2f53870, 0, d36bbf0, d2ae460, 0, 5a8) at netbsd:soreceive
+0x7cc 
soo_read(d3df0f0, d3df0f0, d36bbf0, c04bef0, 1, 0) at
netbsd:soo_read+0x1c 
dofileread(16, d3df0f0, ffffffffffff6e08, 4000, 5, 1) at
netbsd:dofileread+0x60 
sys_read(5, d36bdc0, d36be00, 10, 0, 1820eb8) at netbsd:sys_read+0x60
syscall_plain(d36bed0, d36bf58, 4243ea30, 4243ea34, 0, d36bdc0) at
netbsd:syscall_plain+0x138 
?(5, ffffffffffff6e08, 4000, 0, 0, 42940144) at 0x1008c68
db>

George