kern/112654: [pcn] Kernel panic upon if_pcn module load on a
Netfinity 5000
Marius Strobl
marius at alchemy.franken.de
Tue Jan 22 11:50:04 PST 2008
The following reply was made to PR kern/112654; it has been noted by GNATS.
From: Marius Strobl <marius at alchemy.franken.de>
To: bug-followup at freebsd.org
Cc: Andy Farkas <chuzzwassa at gmail.com>, wforms at Safe-mail.net
Subject: Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000
Date: Tue, 22 Jan 2008 20:43:48 +0100
On Tue, Jan 22, 2008 at 07:23:17PM +0100, wforms at Safe-mail.net wrote:
> New test was carried out today using Marius' patch (and not using Andy's patch at the same time).
> The new kernel re-introduces the original problem, loading the if_pcn driver while the RJ45 cable is connected results in a kernel panic and the system reboots. While the cable is disconnected the if_pcn module loads fine, after which the cable can be plugged back and the card can be used as expected.
>
> ### Here is what shows up upon "kldload if_pcn" while the cable is unplugged ###
> pcn0: <AMD PCnet/PCI 10/100BaseTX> port 0x2180-0x219f mem 0xfebff800-0xfebff81f
> irq 17 at device 9.0 on pci0
> pcn0: Chip ID 2624 (Am79C972)
> miibus5: <MII bus> on pcn0
> nsphyter0: <DP83843 10/100 media interface> on miibus5
> nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ukphy0: <Generic IEEE 802.3u media interface> on miibus5
> ukphy0: 10baseT, 10baseT-FDX, auto
> pcn0: Ethernet address: 00:06:29:50:d9:9e
>
> ### At that point ifconfig says: ###
> root at netfinity ~# ifconfig pcn0
> pcn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> ether 00:06:29:50:d9:9e
> media: Ethernet autoselect (none)
> status: no carrier
> ### Then I connect the RJ45 cable coming from the switch and: ###
> root at netfinity ~# ifconfig pcn0
> pcn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> ether 00:06:29:50:d9:9e
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
> root at netfinity ~#
>
>
> ### Now here is what "kldload if_pcn" does while the cable is connected: ###
> pcn0: <AMD PCnet/PCI 10/100BaseTX> port 0x2180-0x219f mem 0xfebff800-0xfebff81f
> irq 17 at device 9.0 on pci0
> pcn0: Chip ID 2624 (Am79C972)
> miibus5: <MII bus> on pcn0
> nsphyter0: <DP83843 10/100 media interface> on miibus5
> nsphyter0: no media present
> ifmedia_set: no match for 0x0/0xfffffff
> panic: ifmedia_set
>
Could you please:
1) try again with the nsphyter patch already in place and
http://people.freebsd.org/~marius/nsphyter.c
copied on top of the existing src/sys/dev/mii/nsphyter.c?
The new one uses the reset function from nsphy(4), which is about
the only thing I can think of making the difference that a nsphy(4)
hacked to attach to the DP83843 doesn't panic.
2) In case it also panics with the nsphyter.c provide a backtrace.
Thanks,
Marius
More information about the freebsd-net
mailing list