netdev - RE: Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 1 Feb 2008 11:07:18 -0800
From:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To:	"Erik Mouw" <mouw@...linux.org>, "jamal" <hadi@...erus.ca>
Cc:	<netdev@...r.kernel.org>
Subject: RE: Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24

> I've changed the -EIO into NETDEV_TX_BUSY and so far I can't 
> trigger the bug anymore. It was quite easy to trigger within 
> minutes with rsync, but I can't trigger it anymore. Should I 
> send a patch, and if
> so: to who? The tulip/xircom_cb driver seems to be orphaned.

Perhaps Jeff Garzik is a good place to start.  He maintains the driver
tree, he either can take the patch or direct you to where it should go.

> No need to test that, it *is* netif_stopped before the return:
> 
>         /* Uh oh... no free descriptor... drop the packet */
>         netif_stop_queue(dev);
>         spin_unlock_irqrestore(&card->lock,flags);
>         trigger_transmit(card);
> 
>         return NETDEV_TX_BUSY;
> 
> trigger_transmit() is a simple function that just writes a 
> single register on the card to trigger a transmit.

Eek!  No need to make this smarter at this point, but this is pretty
basic.

Cheers,

-PJ Waskiewicz
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html