re(4) unaligned panic on -current

[John Baldwin]

On Dec 28, 2005, at 11:35 AM, Bernd Walter wrote:

> The same card works fine on an AS4100 running 5.4-STABLE.
>
> Booting [/boot/kernel/kernel]...
> Entering /boot/kernel/kernel at 0xfffffc000033bf00...
 > ...
> re0: <RealTek 8169S Single-chip Gigabit Ethernet> port  
> 0x11000-0x110ff mem 0x80320000-0x803200ff irq 0 at device 11.0 on pci0
> miibus1: <MII bus> on re0
> rgephy0: <RTL8169S/8110S media interface> on miibus1
> rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,  
> 1000baseTX, 1000baseTX-FDX, auto
> re0: Ethernet address: 00:40:f4:d0:8d:eb
>
> fatal kernel trap:
>
>     trap entry     = 0x4 (unaligned access fault)
>     cpuid          = 0
>     faulting va    = 0xfffffc00008a472b
>     opcode         = 0x28
>     register       = 0x12
>     pc             = 0xfffffc00003b0608
>     ra             = 0xfffffc00003b05cc
>     sp             = 0xfffffc00007339d0
>     usp            = 0x0
>     curthread      = 0xfffffc000068b008
>         pid = 0, comm = swapper
>
> [thread pid 0 tid 0 ]
> Stopped at      re_init_locked+0xd8:    jsr     ra, 
> (pv),re_init_locked+0xdc      
> <ra=0xfffffc00003b05cc,pv=0xfffffc00005d2dd0>
> db> bt
> Tracing pid 0 tid 0 td 0xfffffc000068b008
> re_init_locked() at re_init_locked+0xd8
> re_diag() at re_diag+0x178

My first guess would be Ruslan's IF_LLADDR changes.  If so, you can  
try doing a bcopy to a char array as a workaround similar to the  
recent changes to de(4) and dc(4) to fix similar panics on Alpha.  It  
might be something else though.  If you could pull up gdb on your  
kernel.debug and do 'l *re_init_locked+0xd8' to see what file/line  
that corresponds to that would be helpful.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org