On Sun, 2009-01-18 at 02:59 +0100, Hans van Kranenburg wrote:
Some additional info:
I can only reproduce the WARNING: at net/core/dev.c:1457
skb_gso_segment+0x88/0x1af() when directly logging into the dom0 host
using a IPv6 and SSH *before* any domU is started yet :|
net/core/dev.c:1457
Ian, thanks for the reply. Based on your you suggestions, I did some
further research on this issue, as I don't yet know much about the
details of checksum offloading, GSO and other stuff in combination with
bridging.
From dmesg:
[4.069406] eth0: Tigon3 [partno(BCM95704A6) rev 2100
Some additional info:
I can only reproduce the WARNING: at net/core/dev.c:1457
skb_gso_segment+0x88/0x1af() when directly logging into the dom0 host
using a IPv6 and SSH *before* any domU is started yet :|
I also tried copying several test files with scp, to generate network
traffic, but I
Hans van Kranenburg wrote:
Furthermore, when starting a domU (also using 2.6.26-12), SSH-ing into
the domU, whether it's over IPv4 of IPv6, it does not trigger the
warnings again in the domU or dom0 console.
After shutting down the domU no more warnings occur, even when messing
around at
4 matches
Mail list logo
