| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1ba2fa240807231502t1c4ce7d5k9b8acbcaed4d166a@mail.gmail.com> Date: Thu, 24 Jul 2008 01:02:15 +0300 From: "Tomas Winkler" <tomasw@...il.com> To: "Theodore Tso" <tytso@....edu>, yi.zhu@...el.com, reinette.chatre@...el.com, linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Potential iwlwifi locking problem in 2.6.26-git9 On Thu, Jul 24, 2008 at 12:49 AM, Theodore Tso <tytso@....edu> wrote: > On Wed, Jul 23, 2008 at 05:36:30PM -0400, Theodore Ts'o wrote: >> >> Is this a new one? I don't think I've seen this on LKML.... > > The context of this was I had just booted to 2.6.26-git9, noted with > annoyance that that the iwl4965 driver needed a new microcode file, so > I popped in my EVDO card, downloaded the firmware, moved the firmware > into place, and then got the above error message. > > I've since noted that it seems to be utterly refusing to associate > with my wireless access point. This was working just fine with > 2.6.26-git6 kernel, so it looks like a recent regression? I just > noticed someone else had recently complained about a similar "refusal > to associate" with the iwl3945 driver. I'm not sure but this can be connected to what is described in thread: 'New: dhcp doesn't work with iwl4965' Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists