Re: Kernel 2.6.37-rc5 rc7 Oops

[Gertjan van Wingerde]

On 01/10/11 22:12, David Miller wrote:
> From: Gertjan van Wingerde <gwingerde@xxxxxxxxx>
> Date: Mon, 10 Jan 2011 22:08:32 +0100
> 
>> On 01/10/11 09:06, David Miller wrote:
>>> From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
>>> Date: Wed, 29 Dec 2010 21:02:45 +0100
>>>
>>>> Le mercredi 29 décembre 2010 à 11:23 -0800, Linus Torvalds a écrit :
>>>>> On Wed, Dec 29, 2010 at 4:26 AM, Alex Arnautu <alex.arnautu96@xxxxxxxxx> wrote:
>>>>>>
>>>>>> I get an oops with 2.6.37-rc5 and 2.6.37-rc7-git1.
>>>>>> http://www.fotoshack.us/fotos/19044P271210_15.14_[01].jpg
>>>>>
>>>>> Hmm. Davem added to the list of people involved. This _may_ be fixed
>>>>> by the "always clone skbs" commit in -rc8 (commit 173021072), but
>>>>> David can make a better judgment call.
>>>>>
>>>>
>>>> Very unlikely, as commit 173021072 only fix a bug in case mirred is
>>>> used.
>>>
>>> This should be taken to the wireless list (now CC:'d) as the rt2xxx
>>> driver and the wireless stack are both in that backtrace.
>>
>> Hmmm, the jpg images of the oops don't seem to be available anymore
>> (a 404 not found is returned on the URL.
>> Does anybody still have the backtrace? Otherwise it will be very hard to look
>> into this.
> 
> You must have copy-and-paste'd it wrong, the URL works perfectly fine
> for me.
> 
> I also put up a copy at:
> 
> http://vger.kernel.org/~davem/crash.jpg
> 

OK. Got it now. My Unix/Linux twisted mind took the [01] in the file name as a
slick indication that there were two pictures, one with 0 there and one with 1
there. It never occurred to me that it was literally the file name ;-) :-(

Anyway, I wonder if this particular oops is fixed by commit:

20ed3166c84d145589a89d8cde12aa32cf2d17f4 mac80211/rt2x00: add ieee80211_tx_status_ni()

which got into Linus' tree after 2.6.37-rc7 but is part of 2.6.37 final.

It looks a lot like the symptoms that that patch was fixing.

---
Gertjan.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/