[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140213182105.GN13576@mudshark.cambridge.arm.com>
Date: Thu, 13 Feb 2014 18:21:06 +0000
From: Will Deacon <will.deacon@....com>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Pavel Machek <pavel@....cz>, Sebastian Reichel <sre@...g0.de>,
Pali Rohár <pali.rohar@...il.com>
Subject: Re: [BISECTED] ssh - Received disconnect from x.x.x.x: 2: Bad packet
length 3149594624
Hi Ivo,
Thanks for bisecting this.
On Thu, Feb 13, 2014 at 06:02:57PM +0000, Ivaylo Dimitrov wrote:
> Since next-21012014 I started to receive "Received disconnect from
> x.x.x.x: 2: Bad packet length 3149594624" errors when trying to
> establish ssh session over wifi to my N900, running Maemo 5. I bisected
> and it turned out that commit dce5c9e35bc4085bd33eccdb8c9ec5a643507a14
> "ARM: 7928/1: kconfig: select HAVE_EFFICIENT_UNALIGNED_ACCESS for CPUv6+
> && MMU" is the first bad. There is nothing related in either dmesg or
> syslog on the device. Reverting that commit on 3.14-rc1 make those
> errors disappear.
That's certainly unexpected. The n900 has (iirc) a Cortex-A8, which as an
ARMv7 core, can perform unaligned accesses to normal, cacheable memory in
hardware.
Can you provide your .config and/or any information about your network chip
please? There's a chance that the driver is doing something odd.
Cheers,
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists