All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaddy Baddah <shaddy_baddah@hotmail.com>
To: linux-wireless@vger.kernel.org, Daniel Drake <dsd@gentoo.org>,
	jt@hpl.hp.com, Johannes Berg <johannes@sipsolutions.net>,
	David Miller <davem@davemloft.net>
Subject: Re: zd1211rw (2.6.22 sparc64): unaligned access (do_rx)
Date: Thu, 22 Nov 2007 00:30:16 +1100	[thread overview]
Message-ID: <474432E8.90304@hotmail.com> (raw)
In-Reply-To: <47443035.1070702@hotmail.com>

Hi,

Shaddy Baddah wrote:
=> 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>
> 
> # iwconfig eth2 essid dixieland key "GGGGGGGGGG"
> # iwconfig eth2
> eth2      IEEE 802.11b/g  ESSID:off/any  Nickname:"zd1211"
>           Mode:Managed  Frequency:2.462 GHz  Access Point: 
> GG:GG:GG:GG:GG:GG
>           Bit Rate=24 Mb/s
>           Encryption key:<too big>
> 
> #
> 


Interestingly, after performing the above actions, I am now getting 
additional log messages:

SoftMAC: Open Authentication completed with GG:GG:GG:GG:GG:GG
Kernel unaligned access at TPC[100df410] 
ieee80211softmac_handle_assoc_response]
Kernel unaligned access at TPC[100df548] 
ieee80211softmac_handle_assoc_response]
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Kernel unaligned access at TPC[100d03ec] ieee80211_copy_snap+0x74/0x78 
[ieee802]
Kernel unaligned access at TPC[100d03ec] ieee80211_copy_snap+0x74/0x78 
[ieee802]
Kernel unaligned access at TPC[100d03ec] ieee80211_copy_snap+0x74/0x78 
[ieee802]
Kernel unaligned access at TPC[100d03ec] ieee80211_copy_snap+0x74/0x78 
[ieee802]
Kernel unaligned access at TPC[100d03ec] ieee80211_copy_snap+0x74/0x78 
[ieee802]
Kernel unaligned access at TPC[100ee624] do_rx+0x394/0x5ec [zd1211rw] 

Kernel unaligned access at TPC[100ee62c] do_rx+0x39c/0x5ec [zd1211rw] 

Kernel unaligned access at TPC[100ee638] do_rx+0x3a8/0x5ec [zd1211rw] 

Kernel unaligned access at TPC[100ee668] do_rx+0x3d8/0x5ec [zd1211rw] 

Kernel unaligned access at TPC[100ee670] do_rx+0x3e0/0x5ec [zd1211rw] 



Hope this helps,
Shaddy

  reply	other threads:[~2007-11-21 13:32 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 [this message]
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=474432E8.90304@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.