kern/74635: [panic] vlan over fxp driver IP assignment crash
Fireball
fireball at zerouptime.ch
Mon Dec 13 08:10:31 PST 2004
The following reply was made to PR kern/74635; it has been noted by GNATS.
From: Fireball <fireball at zerouptime.ch>
To: Gleb Smirnoff <glebius at cell.sick.ru>,
FreeBSD-gnats-submit at FreeBSD.org
Cc: freebsd-bugs at FreeBSD.org
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Mon, 13 Dec 2004 16:53:10 +0100
> this problem can be specific to hardware. I can't reproduce it
> on Thinkpad T20 running CURRENT and this card:
Well, I noticed that it requires having IPV6 support compiled in, to
reproduce the bug. If I take a GENERIC kernel and comment 'options INET6',
then the panic is no longer reproducable.
> fxp0: <Intel 82559ER Pro/100 Ethernet> port 0x1800-0x183f mem 0xe8100000-0xe811f
> fff,0xe8120000-0xe8120fff irq 11 at device 3.0 on pci0
>
> How does you card look in dmesg?
fxp0: <Intel 82801DB (ICH4) Pro/100 VE Ethernet> port 0x8000-0x803f mem
0xd0204000-0xd0204fff irq 11 at device 8.0 on pci2 miibus0: <MII bus> on
fxp0
> Can you describe 'panic recipe' as much precisely as possible? And pls
> show output of 'ifconfig fxp0' before starting the recipe.
Lemme type down the panic message/stack trace (I can provide stack
addresses etc. if needed):
Stopped at 0xc0519017 = fxp_mc_setup+0x47: movw $0,0(%eax)
db> trace
fxp_mc_setup(c1ba4000) at 0xc0519017 = fxp_mc_setup+0x47
fxp_ioctl(c1ba4000,80206932,0) at 0xc0518de6 = fxp_ioctl+0x12e
if_delmulti(...) at ...
vlan_setmulti(...) at ...
vlan_ioctl(...) at ...
vlan_ifaddmulti(...) at ...
if_addmulti(...) at ...
in6_addmulti(...) at ...
in6_update_ifa(...) at ...
in6_ifattach_linklocal(...) at ...
in6_ifattach(...)
in6_if_up(...)
if_route(...)
if_up(...)
ifhwioctl(...)
ifioctl(...)
soo_ioctl(...)
iotctl(...)
syscall(2f,2f,2f,3,1) at ... = ...
Xint0x80_syscall() at 0xc07af1cf = ...
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280cc0b7, esp =
0xbfbfebac, ebp = 0xbfbfebf8 ---
--
Jonas Nagel <fireball at zerouptime.ch>
More information about the freebsd-bugs
mailing list