Messages in this thread | ![/](/images/icornerl.gif) | | From | "Sergey S. Kostyliov" <> | Subject | Re: eth0: Bus master arbitration failure | Date | Sat, 22 Mar 2003 15:33:06 +0300 |
| |
Hello all,
On Friday 14 March 2003 20:41, latten@austin.ibm.com wrote: > >On Thu, 13 Mar 2003 latten@austin.ibm.com wrote: > > > >> I was wondering if anyone knew if this had been resolved > >> or see this problem too. I am having the same problem. > >> However, I am using 2.5.64 kernel and I have tried > >> both an eepro100 and a 3com-tornado ethernet card. > >> > > > >I think the problem is probably all those "printk()" calls > >within timing-sensitive code (really). A Bus master arbitration > >failure is supposed to result in a retry. It is not supposed to > >be fatal. For kicks, just comment out the printk() and see if > >the box starts to work. If that makes it work, an appropriate > >permanent fix would be to just keep track of the number of > >such failures just like the dropped-packet and collision count. > > > >If removing the printk() doesn't fix it, there may be a retained > >spin-lock on an error exit path. > > > > I did go and take a look at that printk :-) and realized it was in > pcnet32.c and that it was my pcnet32 card complaining and not > my eepro100 or 3com card. Whew! Sorry about that mistake. > I am going to try and install kdb and see if it will help > locate where the lockup is occuring.
I just want to clear things out. This check was in kernels before 2.4.19 too.
if (csr0 & 0x0800) { printk(KERN_ERR "%s: Bus master arbitration failure, status %4.4x.\n", dev->name, csr0); /* unlike for the lance, there is no restart needed */ }
But I've never seen nor this message neither kernel lockups before 2.4.19. And even for kernels > 2.4.19 it seems UP systems are not affected (There are no such problems on my UP Netfinity 5100 so far).
> > Thanks, > Joy
-- Best regards, Sergey S. Kostyliov <rathamahata@php4.ru> Public PGP key: http://sysadminday.org.ru/rathamahata.asc - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |