From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: reinette chatre <reinette.chatre@intel.com>,
Lukas Hejtmanek <xhejtman@ics.muni.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: iwlagn driver segfault in 2.6.28-rc3
Date: Wed, 19 Nov 2008 23:29:40 +0100 [thread overview]
Message-ID: <20081119222940.GA30846@localhost.aei.mpg.de> (raw)
In-Reply-To: <1ba2fa240811191406j5a116ad2h91873749cc96ab97@mail.gmail.com>
On Thu 20.Nov'08 at 0:06:05 +0200, Tomas Winkler wrote:
> >
> > I don't if the situation leading to the WARN() in your patch is the same
> > one which used to kill my wireless connection before (with the oops
> > in iwl_eeprom_query16 that started this thread), but the fact is
> > that my wifi is still working.
>
> The second removal of invalid key corrupt the eeprom pointer
> in this line
>
> if (!test_and_clear_bit(priv->stations[sta_id].sta.key.key_offset,
> &priv->ucode_key_table))
>
> as discovered by Yi so this patch also fix the immediate failure
> We are just not sure in what flow the key is removed second time and maybe
> there is an other issue behind it.
Ok, thanks for the explanation!
> The full log will be appreciated but you've already helped a lot
> Thanks for your time
I thank you too for taking care of it, and now at least my wifi does not
die as before.
I uploaded the dmesg here
http://www.aei.mpg.de/~crmafra/dmesg-iwlwifi.txt
it contains the warnings including the first (not tainted),
but the beginning of the log is missing because it was too big I guess.
But the boot messages are probably the same as the other dmesg
I've sent already in this thread.
next prev parent reply other threads:[~2008-11-19 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 14:34 iwlagn driver segfault in 2.6.28-rc3 Lukas Hejtmanek
2008-11-13 7:07 ` reinette chatre
2008-11-16 12:06 ` Carlos R. Mafra
2008-11-16 12:29 ` Tomas Winkler
2008-11-16 12:51 ` Carlos R. Mafra
2008-11-16 23:54 ` Tomas Winkler
2008-11-17 0:39 ` Carlos R. Mafra
2008-11-19 20:45 ` Carlos R. Mafra
2008-11-19 22:06 ` Tomas Winkler
2008-11-19 22:29 ` Carlos R. Mafra [this message]
2008-11-16 17:47 ` reinette chatre
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=20081119222940.GA30846@localhost.aei.mpg.de \
--to=crmafra2@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tomasw@gmail.com \
--cc=xhejtman@ics.muni.cz \
/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).