linux-kernel - Re: soft lockup apparently in ath5k_hw_update_mib

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 29 Mar 2009 09:15:24 -0400
From:	Bob Copeland <bcopeland@...il.com>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	Paul Collins <paul@...ly.ondioline.org>,
	Jiri Slaby <jirislaby@...il.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	ath5k-devel@...ts.ath5k.org
Subject: Re: soft lockup apparently in ath5k_hw_update_mib_counters (or 
	ioread32?) with 2.6.29

On Sun, Mar 29, 2009 at 5:37 AM, Michael Tokarev <mjt@....msk.ru> wrote:
> Paul Collins wrote:
>>
>> Jiri Slaby <jirislaby@...il.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
--
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/