Bug#506419: kernel trace during IPv6 ssh output
On Fri, Nov 21, 2008 at 12:06 PM, martin f krafft <firstname.lastname@example.org>
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).
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.
I cannot reproduce the problem with an IPv4 connection.
I cannot reproduce the problem with an incoming transfer.
Syslog excerpt of the last boot and first trace attached.
Can you reproduce on another version of the kernel or a vanilla?