From: Bob Copeland <bcopeland@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Paul Collins <paul@burly.ondioline.org>,
Jiri Slaby <jirislaby@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath5k-devel@venema.h4ckr.net
Subject: Re: soft lockup apparently in ath5k_hw_update_mib_counters (or ioread32?) with 2.6.29
Date: Sun, 29 Mar 2009 09:15:24 -0400 [thread overview]
Message-ID: <b6c5339f0903290615p5d7d7041nd5e5b5a584ef9bae@mail.gmail.com> (raw)
In-Reply-To: <49CF4161.6080401@msgid.tls.msk.ru>
On Sun, Mar 29, 2009 at 5:37 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
> Paul Collins wrote:
>>
>> Jiri Slaby <jirislaby@gmail.com> writes:
>>
>>> On 03/29/2009 08:20 AM, Paul Collins wrote:
>>>>
>>>> After about two days of uptime with 2.6.29 I got this:
>>>>
>>>> BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
>>> Huh. I see no reason for this to happen. I suppose this is a regression,
>>> which kernel worked?
>>
>> I had a previous instance of the problem with v2.6.29-rc8 after about
>> six days of uptime. The kernel before that was 2.6.29-rc7ish, ran OK
>> for a couple of days. But since I don't know how to reproduce it
>> reliably it's hard to say which kernel is truly good.
I think it's just an interrupt storm because we don't reset MIB
interrupts properly (I think not all devices are read-and-clear). I
already have a patch in wireless-testing to turn off MIB interrupts until
ANI is working and I CCed stable on it.
http://marc.info/?l=linux-wireless&m=123725924404147&w=2
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-03-29 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 6:20 Paul Collins
2009-03-29 8:29 ` Jiri Slaby
2009-03-29 9:00 ` Paul Collins
2009-03-29 9:37 ` Michael Tokarev
2009-03-29 13:15 ` Bob Copeland [this message]
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=b6c5339f0903290615p5d7d7041nd5e5b5a584ef9bae@mail.gmail.com \
--to=bcopeland@gmail.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=paul@burly.ondioline.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 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®