Bug#577747: linux-image-2.6.32-4-686: corrupted SSH connection little time after boot with the atl1e driver on a Eeepc 1002HA
- To: Ben Hutchings <ben@decadent.org.uk>
- Cc: 577747@bugs.debian.org
- Subject: Bug#577747: linux-image-2.6.32-4-686: corrupted SSH connection little time after boot with the atl1e driver on a Eeepc 1002HA
- From: Frédéric Boiteux <fboiteux@calistel.com>
- Date: Wed, 14 Apr 2010 13:00:36 +0200
- Message-id: <20100414130036.0e3cc981@prem6s>
- Reply-to: Frédéric Boiteux <fboiteux@calistel.com>, 577747@bugs.debian.org
- In-reply-to: <1271241145.2243.20.camel@localhost>
- References: <20100414072805.7439.84723.reportbug@prem6s> <1271241145.2243.20.camel@localhost>
Le Wed, 14 Apr 2010 11:32:25 +0100,
Ben Hutchings <ben@decadent.org.uk> a écrit :
> On Wed, 2010-04-14 at 09:28 +0200, Frédéric Boiteux wrote:
> > Package: linux-2.6
> > Version: 2.6.32-11
> > Severity: normal
> > Tags: upstream
> >
> > Some minutes after booting (cold boot, or resume from hibernation,
> > at least before #534422 prevents me to use hibernation), my
> > Iceweasel session launched through a SSH connection always fail
> > with following error message : Corrupted MAC on input.
> > Disconnecting: Packet corrupt Restarting the SSH connection, the
> > problem don't occur anymore before next reboot. I've checked and
> > replaced the ethernet cable, without change. I also tested the
> > memory, seems ok. I thought at start it was a iceweasel or openssh
> > problem, but then found other people have the same problem, like :
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/60764
> > https://bugzilla.kernel.org/show_bug.cgi?id=12282 and perhaps also
> > https://bugzilla.kernel.org/show_bug.cgi?id=13404 The problem is
> > here at least since 2.6.30, and is always present with latest
> > kernel from Sid.
>
> The bug could be at either end of the connection (or between them).
> Is the remote system on the same local network? If so, please can you
> provide the output of these commands on the remote system:
>
> ls -l /sys/class/net/*/device/driver
> grep . /sys/class/net/*/features
I don't think so, because the remote system is on a local network, and
I use same type of ssh connection from other systems without problem.
But here is the output you request (the remote system is an HP
DL380G5) :
$ ls -l /sys/class/net/*/device/driver
lrwxrwxrwx 1 root root 0 avr 14 12:58 /sys/class/net/eth0/device/driver -> ../../../../../bus/pci/drivers/bnx2
lrwxrwxrwx 1 root root 0 avr 14 12:58 /sys/class/net/eth1/device/driver -> ../../../../../bus/pci/drivers/bnx2
$ grep . /sys/class/net/*/features
/sys/class/net/br0/features:0x1000
/sys/class/net/br1/features:0x1000
/sys/class/net/eth0/features:0x909a3
/sys/class/net/eth1/features:0x909a3
/sys/class/net/lo/features:0x13865
/sys/class/net/tap0/features:0x2000
/sys/class/net/tap1/features:0x2000
Fred.
Reply to: