From: "Chris Friesen" <[EMAIL PROTECTED]>
Date: Mon, 15 Oct 2007 23:16:16 -0600
> Our version of the e1000 passes 200 bytes in the initial chunk, and the
> rest in fragments. tipc currently handles that without any difficulty.
There is no requirement for any bytes to be in the initial skb->data
Stephen Hemminger wrote:
Maybe TIPC can't handle fragmented receive buffers. The sky2 driver
generates skb's with header and multiple pages if MTU is big enough.
For 9K MTU that would be 1K of data + 2 4K pages. The protocols are
supposed to be smart enough to handle this, but TIPC is rarely u
On Mon, 15 Oct 2007 14:17:50 -0600
"Chris Friesen" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We're using Yukon-XL (0xb3) rev 3 hardware with a vendor-supplied
> 2.6.14. BAsed on suggestions here, I backported the sky2 driver (v1.10
> from 2.6.20.6) to 2.6.14.
>
> Unfortunately, when I booted th
Hi,
We're using Yukon-XL (0xb3) rev 3 hardware with a vendor-supplied
2.6.14. BAsed on suggestions here, I backported the sky2 driver (v1.10
from 2.6.20.6) to 2.6.14.
Unfortunately, when I booted this I got the following:
skb_over_panic: text:d00d4e14 len:60 put:60
head:c0026
