[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#506419: kernel trace during IPv6 ssh output

On Fri, 2008-11-21 at 11:06 +0100, martin f krafft wrote:
> Package: linux-image-2.6.26-1-amd64
> Version: 2.6.26-10
> Severity: important
> Tags: ipv6
> This is a lenny system. Important because IPv6 is a release goal.
> When I run dmesg through a (native) IPv6 SSH connection on a new
> server, the kernel spews plenty traces to the console. The first
> trace says the kernel is not tainted, in subsequent traces, the
> taint is claimed to be GW(512). Note below how it is tainted at
> 10:25:50 (second trace), but not at 10:25:49 (first trace).

A WARN or BUG taints the kernel.

> The same problem arises during *outgoing* scp and renders all other
> SSH sessions basically unusable for the duration of the transfer.
> I can reproduce this with an *outgoing* HTTP session too.

This is a warning from the GSO (like TSO) code which only applies to
outgoing traffic.

The warning comes from:
	if (WARN_ON(skb->ip_summed != CHECKSUM_PARTIAL)) {
which means something generated an skb with incorrect flags (GSO depends
on having a partial checksum).

I notice there's bridging code in the call trace, and kvm in the modules
list.  Were you initiating the IPv6 connections from inside a VM?


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: