linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@hpl.hp.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: David Miller <davem@davemloft.net>,
	shaddy_baddah@hotmail.com, linux-wireless@vger.kernel.org,
	Daniel Drake <dsd@gentoo.org>
Subject: Re: zd1211rw (2.6.22 sparc64): unaligned access (do_rx)
Date: Mon, 19 Nov 2007 10:04:23 -0800	[thread overview]
Message-ID: <20071119180423.GA19250@bougret.hpl.hp.com> (raw)
In-Reply-To: <1195484582.8642.18.camel@johannes.berg>

On Mon, Nov 19, 2007 at 04:03:02PM +0100, Johannes Berg wrote:
> 
> > > 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>".
> > 
> > Likely some wireless ioctl compat layer bug in the kernel.
> 
> Is this 32/64 interop? The kernel has never been fixed and never will
> be. New wireless tools should "support" this, but imnsho you're *much*
> better off compiling 64-bit wireless tools.

	There was a patch for this kind of issue from Masakazu Mokuno
that went in 2.6.22 or 2.6.23 that was touching that part. I don't
think he went in the stable series, but probably should have. There
are other potential cause of problem here, and I suspect he might get
the same error with 64 bits userspace.
	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.

> > > 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.
> > 
> > This is an unaligned data access in the userland tools.
> > Try to catch it with GDB and give us ths backtrace.
> 
> For Jean.

	Definitely, it sounds familiar.
	This is that I need :
		o version of the kernel
		o version of the driver if not stock driver
		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.

	Regards,

	Jean

  reply	other threads:[~2007-11-19 18:06 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 [this message]
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=20071119180423.GA19250@bougret.hpl.hp.com \
    --to=jt@hpl.hp.com \
    --cc=davem@davemloft.net \
    --cc=dsd@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shaddy_baddah@hotmail.com \
    /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).