Re: [PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

Erik Mouw wrote: Hi, Changes in other networking paths uncovered a bug in the xircom_cb driver which made the kernel spew lots of the following error messages: BUG eth1 code -5 qlen 0 It turned out that the driver returned -EIO when there was no descriptor available for sending packets. It

[PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

Hi, Changes in other networking paths uncovered a bug in the xircom_cb driver which made the kernel spew lots of the following error messages: BUG eth1 code -5 qlen 0 It turned out that the driver returned -EIO when there was no descriptor available for sending packets. It should return

Re: [PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

On Mon, Feb 04, 2008 at 06:56:54PM +0100, Erik Mouw wrote: Changes in other networking paths uncovered a bug in the xircom_cb driver which made the kernel spew lots of the following error messages: BUG eth1 code -5 qlen 0 It turned out that the driver returned -EIO when there was no

Re: [PATCH] xircom_cb should return NETDEV_TX_BUSY when there are no descriptors available

Erik Mouw wrote: On Mon, Feb 04, 2008 at 06:56:54PM +0100, Erik Mouw wrote: Changes in other networking paths uncovered a bug in the xircom_cb driver which made the kernel spew lots of the following error messages: BUG eth1 code -5 qlen 0 It turned out that the driver returned -EIO when