RE: [PATCH] fs_enet: Don't call phy_mii_ioctl() in atomic context.

p;fep->lock, flags); > - return rc; > + return phy_mii_ioctl(fep->phydev, mii, cmd); > } > > extern int fs_mii_connect(struct net_device *dev); Acked-by: Rune Torgersen <[EMAIL PROTECTED]> Tested it and it does indeed take care of the bug. -- To unsubscribe fr

RE: WARN_ON() hit in fsl bitbanged phy driver

Scott Wood wrote: > Rune Torgersen wrote: >> I hit the following WARN_ON when using mii-tools agains a ethernet >> interface using a bit-banged mii interface > > It looks like the kernel thinks it's in an interrupt, even though it > clearly isn't from the backtra

WARN_ON() hit in fsl bitbanged phy driver

I hit the following WARN_ON when using mii-tools agains a ethernet interface using a bit-banged mii interface It is only diplayed once, and does not seem to impact usage at all Does somebody know what is wrong, and how to fix it? The PHY is an Intel LXT973 Badness at kernel/softirq.c:139 NIP: c00

RE: Ethernet weirdness on 82xx

> -Original Message- > From: Denys [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 02, 2007 6:12 AM > To: Rune Torgersen; [EMAIL PROTECTED]; > netdev@vger.kernel.org > Subject: Re: Ethernet weirdness on 82xx > > Thats normal. > Check arp_filter sysctl : &g

Ethernet weirdness on 82xx

I'm not sure if this is by design or an actual bug. We have a system witb an 8280 with two active ethernets (fcc2 and fcc3) We are running kernel 2.6.18.1 (and won't be upgrading in a while) out of arch/ppc Eth0 and eth1 are in totally different subnets. We happened to have both ehternets connect