From: Shaddy Baddah <shaddy_baddah@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: zd1211rw (2.6.26 sparc64): unaligned access (zd_mac_rx)
Date: Sat, 08 Nov 2008 23:45:33 +1100 [thread overview]
Message-ID: <BAY104-DAV4C468E484B2456B3D02B799180@phx.gbl> (raw) (sfid-20081108_135158_067215_F443609D)
Message-ID: <491589ED.4090904@hotmail.com> (raw)
In-Reply-To: <49033782.5040701@hotmail.com>
Hi again,
On 26/10/08 02:13, Shaddy Baddah wrote:
> After applying this patch, things seem better. I can associate to an
> open access point, get an IP address and even ping.
>
> However on association, I am still seeing:
>
>
> [ 179.249516] zd1211rw 4-3:1.0: zd_usb_rfwrite() value 0x01e6666 bits 24
> [ 179.254524] wlan0: Initial auth_alg=0
> [ 179.254549] wlan0: authenticate with AP XX:XX:XX:XX:XX:XX
> [ 179.256215] Kernel unaligned access at TPC[10129b94]
> zd_mac_rx+0x174/0x320 [zd1211rw]
> [ 179.349135] Kernel unaligned access at TPC[10129b9c]
> zd_mac_rx+0x17c/0x320 [zd1211rw]
> [ 179.442852] Kernel unaligned access at TPC[10129ba0]
> zd_mac_rx+0x180/0x320 [zd1211rw]
> [ 179.536579] Kernel unaligned access at TPC[10129ba4]
> zd_mac_rx+0x184/0x320 [zd1211rw]
> [ 179.630306] Kernel unaligned access at TPC[10129ba8]
> zd_mac_rx+0x188/0x320 [zd1211rw]
I'm keen on troubleshooting this myself. Could you please tell me how I
can get a disassembly intermixed with source. An objdump -S ./zd1211rw.o
is not doing the job. I'd rather not re-compile the whole kernel if
possible, because it takes long. Should I rm the file, do a build, take
the command line and substitute -g for any -O option?
TIA,
Shaddy
next prev parent reply other threads:[~2008-11-08 12:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 8:54 zd1211rw (2.6.26 sparc64): unaligned access (zd_mac_rx) Shaddy Baddah
2008-10-25 9:17 ` Johannes Berg
2008-10-25 11:25 ` Sebastian Andrzej Siewior
2008-10-25 12:05 ` Johannes Berg
2008-10-26 22:00 ` Sebastian Andrzej Siewior
2008-10-27 7:00 ` Johannes Berg
2008-10-25 11:21 ` Sebastian Andrzej Siewior
2008-10-25 11:25 ` Michael Buesch
2008-10-25 11:28 ` Sebastian Andrzej Siewior
2008-10-25 11:31 ` Michael Buesch
2008-10-25 11:38 ` Sebastian Andrzej Siewior
2008-10-25 15:13 ` Shaddy Baddah
[not found] ` <491589ED.4090904@hotmail.com>
2008-11-08 12:45 ` Shaddy Baddah [this message]
2008-11-08 13:11 ` Johannes Berg
[not found] ` <491653A6.20705@hotmail.com>
2008-11-09 3:06 ` Shaddy Baddah
[not found] ` <49165436.4040306@hotmail.com>
2008-11-09 3:08 ` Shaddy Baddah
2008-11-09 12:00 ` Michael Buesch
2008-11-09 8:56 ` Johannes Berg
2008-11-09 9:03 ` Johannes Berg
2008-11-09 12:02 ` Michael Buesch
2008-11-09 18:31 ` Johannes Berg
[not found] ` <4916F1C0.1040703@hotmail.com>
2008-11-09 14:20 ` Shaddy Baddah
[not found] ` <49184F82.9070102@hotmail.com>
2008-11-10 15:13 ` Shaddy Baddah
[not found] ` <492F82EA.4030902@hotmail.com>
2008-11-28 5:34 ` Shaddy Baddah
2008-11-28 7:10 ` David Miller
2008-11-28 22:44 ` Michael Buesch
[not found] ` <49310454.60906@hotmail.com>
2008-11-29 8:59 ` Shaddy Baddah
2008-11-29 9:50 ` Johannes Berg
[not found] ` <49313C0E.9030309@hotmail.com>
2008-11-29 12:56 ` Shaddy Baddah
[not found] ` <492F856D.9020200@hotmail.com>
2008-11-28 5:45 ` Shaddy Baddah
2008-11-28 6:47 ` Harvey Harrison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY104-DAV4C468E484B2456B3D02B799180@phx.gbl \
--to=shaddy_baddah@hotmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).