Hi Ivaylo,
On Tue, Feb 25, 2014 at 07:56:11AM +, Ivaylo Dimitrov wrote:
> On 14.02.2014 18:24, Will Deacon wrote:
> > You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
> > commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
> > above.
> >
>
> the
On Tue, Feb 25, 2014 at 10:44:44AM +, Pavel Machek wrote:
> > >>You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
> > >>commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
> > >>above.
> > >
> > >This seems to fix the issue too, but I am afraid there
Hi!
> >>You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
> >>commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
> >>above.
> >
> >This seems to fix the issue too, but I am afraid there is more to be
> >done, as I see
> >
> >Feb 14 18:33:46 Nokia-N900
Hi!
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid there is more to be
done, as I see
Feb 14 18:33:46 Nokia-N900 kernel: [ 88.599853]
On Tue, Feb 25, 2014 at 10:44:44AM +, Pavel Machek wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid there is more to be
Hi Ivaylo,
On Tue, Feb 25, 2014 at 07:56:11AM +, Ivaylo Dimitrov wrote:
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
the following patch
Hi,
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
above.
the following patch
diff --git a/drivers/net/wireless/ti/wl1251/rx.c
Will Deacon writes:
> Well, we probably need a bit more to go on, because I doubt that this code
> is to blame. More likely, the issue is in the caller.
> Looking at drivers/net/wireless/ti/wl1251/rx.c:182
>
> /* The actual length doesn't include the target's alignment */
>
Will Deacon will.dea...@arm.com writes:
Well, we probably need a bit more to go on, because I doubt that this code
is to blame. More likely, the issue is in the caller.
Looking at drivers/net/wireless/ti/wl1251/rx.c:182
/* The actual length doesn't include the target's alignment */
Hi,
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
the following patch
diff --git a/drivers/net/wireless/ti/wl1251/rx.c
On 14.02.2014 19:11, Ivaylo Dimitrov wrote:
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid
On 14.02.2014 19:11, Ivaylo Dimitrov wrote:
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid there
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb->len = desc->length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid there is more to be
done, as I see
Feb 14
On Fri, Feb 14, 2014 at 04:12:44PM +, Ivaylo Dimitrov wrote:
> On 13.02.2014 21:29, Will Deacon wrote:
> >
> > Can you try hacking crypto/memneq.c so that it doesn't use
> > CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS please? That would at least point the
> > finger at net/mac80211/rx.c or similar.
On 13.02.2014 21:29, Will Deacon wrote:
Can you try hacking crypto/memneq.c so that it doesn't use
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS please? That would at least point the
finger at net/mac80211/rx.c or similar.
Cheers,
Will
Well, I am lazy so I hacked net/mac80211/rx.c first:
index
On 13.02.2014 21:29, Will Deacon wrote:
Can you try hacking crypto/memneq.c so that it doesn't use
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS please? That would at least point the
finger at net/mac80211/rx.c or similar.
Cheers,
Will
Well, I am lazy so I hacked net/mac80211/rx.c first:
index
On Fri, Feb 14, 2014 at 04:12:44PM +, Ivaylo Dimitrov wrote:
On 13.02.2014 21:29, Will Deacon wrote:
Can you try hacking crypto/memneq.c so that it doesn't use
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS please? That would at least point the
finger at net/mac80211/rx.c or similar.
On 14.02.2014 18:24, Will Deacon wrote:
You could try putting back the UNALIGNED_ACCESS in net/mac80211/rx.c and
commenting out the skb-len = desc-length - PLCP_HEADER_LENGTH; line
above.
This seems to fix the issue too, but I am afraid there is more to be
done, as I see
Feb 14
On Thu, Feb 13, 2014 at 06:43:15PM +, Ivaylo Dimitrov wrote:
>
>
> On 13.02.2014 20:21, Will Deacon wrote:
> >
> > 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.
> >
>
>
On 13.02.2014 20:21, Will Deacon wrote:
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.
Yep, Cortex-A8 and it has no problem to do unaligned memory accesses
AFAIK. I suspect it is
Hi Ivo,
Thanks for bisecting this.
On Thu, Feb 13, 2014 at 06:02:57PM +, 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
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:
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:
Hi Ivo,
Thanks for bisecting this.
On Thu, Feb 13, 2014 at 06:02:57PM +, 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
On 13.02.2014 20:21, Will Deacon wrote:
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.
Yep, Cortex-A8 and it has no problem to do unaligned memory accesses
AFAIK. I suspect it is
On Thu, Feb 13, 2014 at 06:43:15PM +, Ivaylo Dimitrov wrote:
On 13.02.2014 20:21, Will Deacon wrote:
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.
Yep, Cortex-A8
26 matches
Mail list logo
