From: "Andrew Lutomirski" <luto@myrealbox.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: richard@scherping.de, "Frederik Himpe" <fhimpe@telenet.be>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: iwlagn: associating with AP causes kernel hiccup
Date: Sun, 19 Oct 2008 18:52:03 -0400 [thread overview]
Message-ID: <cb0375e10810191552l7541e034l6f1e095c0c268baa@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240810191512i4c6ce748kd13d1671cc2a2ff6@mail.gmail.com>
On Sun, Oct 19, 2008 at 6:12 PM, Tomas Winkler <tomasw@gmail.com> wrote:
> On Sun, Oct 19, 2008 at 5:18 PM, Andy Lutomirski <luto@myrealbox.com> wrote:
>> Richard Scherping wrote:
>>>
>>> Tomas Winkler schrieb:
>
>>
>> Amen.
> Stable doesn't mean all components are stable, citation from Linus blog:
> "It doesn't have to be perfect (and obviously no release ever is), but
> it needs to be in reasonable shape"
>
> The fact is that some critical patches were rejected as not
> regressions in rc cycle and probably need to be pushed to the stable
> version now or distribution will merge them.
> We gave more priority for testing 32 bit version so it is more stable
> then 64 bit which got much less in house testing and we've missed many
> issues there. The driver doesn't get full exposure till it's get to
> the public in stable version therefore no bugs are opened in the rc
> cycle so also are not fixed in the stable version. and unfortunately
> there is no much system testing at all for what get's into merging
> window.
> Second the whole mac80211 stack didn't address fully MQ rewrite so
> it's a bit shaky as well and this will be fact also in 2.6.28.
OK.
>
> This driver has been available and more-or-less working for ages.
>> What kernel am I supposed to run if I just want a stable system? Haven't
>> found one yet, other than distro kernels...
>>
>> In any case, I've seen these complete system hiccups with iwl4965 and iwlagn
>> since at least 2.6.25 and through quite a few wireless-testing versions. I
>> bet that this, along with things like it, is the culprit:
>
> Haven't seen you've filled bug for it.
Fair enough. #1790.
>
> Locking need to be really revised but till now I didn't see show
> stoppers issues so it didn't get priority
>
>> Would I be out of line for wishing the iwlwifi developers
> Patches are always welcome
I can write a patch to add a mutex and change it to:
take mutex
grab_nic
spinlock
but I bet that would break all kinds of things. :)
--Andy
next prev parent reply other threads:[~2008-10-19 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gd5gs4$abi$1@ger.gmane.org>
2008-10-15 20:59 ` reinette chatre
[not found] ` <gd9v3f$3ft$1@ger.gmane.org>
[not found] ` <gd9vpo$5ql$1@ger.gmane.org>
2008-10-17 15:27 ` Richard Scherping
2008-10-17 20:02 ` Tomas Winkler
2008-10-18 16:17 ` Richard Scherping
2008-10-19 15:18 ` Andy Lutomirski
2008-10-19 22:12 ` Tomas Winkler
2008-10-19 22:52 ` Andrew Lutomirski [this message]
2008-10-19 23:12 ` Tomas Winkler
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=cb0375e10810191552l7541e034l6f1e095c0c268baa@mail.gmail.com \
--to=luto@myrealbox.com \
--cc=fhimpe@telenet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=richard@scherping.de \
--cc=tomasw@gmail.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
all inboxes | Powered by JetHome®