Re: iwl4965 oops in 2.6.26-rc5 x86_64

[Thomas Backlund]

Tomas Winkler skrev:
> On Fri, Jun 6, 2008 at 5:51 PM, Thomas Backlund <tmb@xxxxxxxxxxxx> wrote:
> > Tomas Winkler skrev:
> > > On Fri, Jun 6, 2008 at 3:33 PM, Thomas Backlund <tmb@xxxxxxxxxxxx> wrote:
> > > > Thomas Backlund skrev:
> > > > > Tomas Winkler skrev:
> > > > > > On Fri, Jun 6, 2008 at 3:44 AM, Ian Schram <ischram@xxxxxxxxxx> wrote:
> > > > > > > Isn't this the Oops Joonwoo Park wanted to patch with
> > > > > > >
> > > > > > > "[PATCH] iwlwifi: fix oops on wep key insertion" 27/5/2008
> > > > > > >
> > > > > > > invalid length of webkey that would/should be handled in mac80211?
> > > > > > >
> > > > > > > ian
> > > > > > Yes, it looks like.
> > > > > Ummm, what has a wep key to do with me trying to access a WPA2-Personal
> > > > > encrypted net ?
> > > Not sure yet, but mac is trying to assign default/static wep key.
> > >
> > > :iwlcore:iwl_send_static_wepkey_cmd+0xcb/0xd5
> > > :iwlcore:iwl_set_default_wep_key+0xa2/0xbc
> > >
> > > Try to set the encryption explicitly
> > > network={
> > >    psk="*************************"
> > >    scan_ssid=1
> > >    ssid="dlink"
> > >    pairwise=CCMP
> > >   group=CCMP
> > >  }
> > That didn't help at all.
> >
> > What's more it prevented the wifi to work on 2.6.24.7 so I had to remove the
> > lines again...
> So what's your AP configuration TKIP?

I've switched to clean WPA2-AES on the AP, but it does not do any 
difference... I still get the oops...

> Second try also with sw decryption:
>
> in /etc/modprobe.conf
> options iwl4965 swcrypto=1


That works.
I now run a clean 2.6.26-rc5


I also tried to bisect between 2.6.25 and 2.6.26-rc1 and ended up with:

[root@5720g linux-2.6]# git bisect good
8318d78a44d49ac1edf2bdec7299de3617c4232e is first bad commit
commit 8318d78a44d49ac1edf2bdec7299de3617c4232e
Author: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
Date:   Thu Jan 24 19:38:38 2008 +0100

    cfg80211 API for channels/bitrates, mac80211 and driver conversion



Any more I can provide to help finding the bug ?
--
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/