From: Shaddy Baddah <shaddy_baddah@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: zd1211rw (2.6.22 sparc64): unaligned access (do_rx)
Date: Mon, 19 Nov 2007 11:56:39 +1100 [thread overview]
Message-ID: <4740DF47.4040206@hotmail.com> (raw)
Hi,
I have successfully built a 2.6.22 kernel for sparc64, by taking the
configuration for the Debian build of this kernel, and additionally
configuring the zd1211rw driver.
I am able to modprobe this module, and the device is correctly detected.
However, beyond that, I am experiencing problems with the device here
and there.
The first noticeable problem is when using iwconfig on the device. I
cannot set a key for the device, and a query of the configuration always
claims that the "<encryption key is too long>".
If I try to scan for APs using iwlist, I get one AP listed, before a bus
error occurs. This of course, does not suggest that the problem is with
the driver, but I mention it for the record.
If I configure my AP for open authentication, I can actually configure
the device, and be assigned an address via DHCP. However, the connection
drops out frequently, and is quite unstable.
Whilst the device is up, I continually get console messages like those I
have inlined below:
Kernel unaligned access at TPC[100ee4d4] do_rx+0x244/0x614 [zd1211rw]
Kernel unaligned access at TPC[100ee4e8] do_rx+0x258/0x614 [zd1211rw]
Kernel unaligned access at TPC[100ee4cc] do_rx+0x23c/0x614 [zd1211rw]
I am supposing that the driver hasn't really been tested extensively on
sparc64 architecture. However, can anyone shed some light on why the
driver wouldn't just work as it (I assume) would do on 386 architecture?
Thanks in advance,
Shaddy
next reply other threads:[~2007-11-19 1:37 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 0:56 Shaddy Baddah [this message]
2007-11-19 8:27 ` zd1211rw (2.6.22 sparc64): unaligned access (do_rx) David Miller
2007-11-19 12:11 ` Shaddy Baddah
2007-11-19 12:19 ` David Miller
2007-11-21 13:08 ` Shaddy Baddah
2007-11-19 15:03 ` Johannes Berg
2007-11-19 18:04 ` Jean Tourrilhes
2007-11-21 13:18 ` Shaddy Baddah
2007-11-21 13:30 ` Shaddy Baddah
2007-11-21 14:23 ` Daniel Drake
2007-11-21 18:05 ` Kyle McMartin
2007-11-30 5:31 ` Shaddy Baddah
2007-11-21 14:33 ` Daniel Drake
2007-11-21 18:44 ` Jean Tourrilhes
2007-11-30 3:42 ` Shaddy Baddah
2007-11-30 20:21 ` Jean Tourrilhes
2007-12-04 0:01 ` Jean Tourrilhes
[not found] ` <4756AABC.3000204@hotmail.com>
[not found] ` <20071205215600.GA28349@bougret.hpl.hp.com>
2007-12-05 23:25 ` Shaddy Baddah
2007-12-05 23:40 ` Jean Tourrilhes
2007-12-06 21:59 ` Jean Tourrilhes
2007-12-06 2:36 ` David Miller
2007-12-06 21:25 ` Jean Tourrilhes
2007-12-06 21:33 ` Michael Buesch
2007-12-06 21:43 ` Jean Tourrilhes
2007-12-07 3:52 ` David Miller
2007-12-07 11:35 ` Michael Buesch
2007-12-07 12:34 ` David Miller
2007-12-07 13:36 ` Michael Buesch
2007-12-07 14:48 ` Daniel Drake
2007-12-08 1:36 ` David Miller
2007-12-08 1:35 ` David Miller
2007-12-08 11:21 ` Michael Buesch
2007-12-08 12:54 ` Daniel Drake
2007-12-07 3:50 ` David Miller
2007-12-07 3:49 ` David Miller
2007-11-19 22:20 ` David Miller
2007-11-19 22:35 ` Jean Tourrilhes
2007-11-20 7:42 ` David Miller
2007-11-20 17:43 ` Jean Tourrilhes
2007-11-20 21:56 ` David Miller
2007-11-20 12:40 ` Johannes Berg
2007-11-20 12:46 ` David Miller
[not found] ` <20071120180016.GC1480@bougret.hpl.hp.com>
2007-11-20 21:58 ` David Miller
2007-11-20 22:08 ` John W. Linville
2007-11-20 22:38 ` David Miller
2007-11-20 22:16 ` Jean Tourrilhes
2007-11-20 22:41 ` David Miller
[not found] ` <20071120180601.GA2019@bougret.hpl.hp.com>
[not found] ` <47443430.3010504@hotmail.com>
2007-11-21 19:06 ` Jean Tourrilhes
2007-11-20 17:38 ` Jean Tourrilhes
2007-11-20 12:34 ` David Miller
2007-11-20 13:15 ` Johannes Berg
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=4740DF47.4040206@hotmail.com \
--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).