linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaddy Baddah <shaddy_baddah@hotmail.com>
To: linux-wireless@vger.kernel.org
Cc: jt@hpl.hp.com, Daniel Drake <dsd@gentoo.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	David Miller <davem@davemloft.net>
Subject: Re: zd1211rw (2.6.22 sparc64): unaligned access (do_rx)
Date: Fri, 30 Nov 2007 14:42:37 +1100	[thread overview]
Message-ID: <474F86AD.4040403@hotmail.com> (raw)
In-Reply-To: <20071121184459.GA17199@bougret.hpl.hp.com>

Hi,

First off, sorry for the delay in responding. I am now trying to catch 
up with my backlog on this issue.

Jean Tourrilhes wrote:
> 	The patch from Masakazu Mokuno I was talking about is not in
> your kernel. It defintely would explain why you would get the
> "Encryption key:<too big>". Basically the length of any variable field
> is not properly return to user space. This patch would fix that
> problem.
> 	The patch from Masakazu Mokuno is not in 2.6.22, and it not
> either in 2.6.14. The patch is only included in 2.6.23 and later. I
> would suggest upgrading to 2.6.23 to get that patch. Alternatively,
> I've included the patch as attachement, and you can use it with
> 2.6.22.
> 	I would like you to try that patch and report.

Yes, this solved that problem. Thank you,

>>> 	Can you give me the exact error text as reported by iwconfig ?
>>> I'll probably have to send you a test version to see what's happening
>>> under the cover.
>> Please find this in-lined below (with key protected):
>>
>> # iwconfig eth2
>> eth2      IEEE 802.11b/g  ESSID:off/any  Nickname:"zd1211"
>>           Mode:Managed  Frequency:2.462 GHz  Access Point: Invalid
>>           Bit Rate=1 Mb/s
>>           Encryption key:<too big>
> 
> 	Note that under Wireless Tools 30, you will notice that it
> won't return too bug but will print an absurdly long encryption
> key. Two symptoms of the same bug.
> 
>>> 		o version of Wireless Tools (iwconfig --version).
>>> 	Most likely, you need to upgrade your Wireless Tools to
>>> version 29 which fixes this 32/64 interop problem.
>>> 	With the latest kernel and the latest wireless tools, the only
>>> known bugs are the two ESSID bugs.
>> I think I'm right for version:
>> # iwconfig --version
>> iwconfig  Wireless-Tools version 29
>>           Compatible with Wireless Extension v11 to v22.
>>
>> Kernel    Currently compiled with Wireless Extension v22.
>>
>> eth2      Recommend Wireless Extension v20 or later,
>>           Currently compiled with Wireless Extension v22.
> 
> 	Yep, that's the correct version. I was afraid you were running
> Debian stable. I'll need to dig up a little bit more in this.
> 	Note that the patch above *may* help with this issue as well.

No, it does not seem to have. An iwlist eth2 scanning command still 
lists a single access point, then fails with a bus error.

Thanks for your help,
Shaddy


  reply	other threads:[~2007-11-30  3:45 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  0:56 zd1211rw (2.6.22 sparc64): unaligned access (do_rx) Shaddy Baddah
2007-11-19  8:27 ` 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 [this message]
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=474F86AD.4040403@hotmail.com \
    --to=shaddy_baddah@hotmail.com \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=jt@hpl.hp.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).