From: Gertjan van Wingerde <gwingerde@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, torvalds@linux-foundation.org,
alex.arnautu96@gmail.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: Kernel 2.6.37-rc5 rc7 Oops
Date: Mon, 10 Jan 2011 22:08:32 +0100 [thread overview]
Message-ID: <4D2B7550.5000008@gmail.com> (raw)
In-Reply-To: <20110110.000650.124002380.davem@davemloft.net>
On 01/10/11 09:06, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> 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@gmail.com> 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.
---
Gertjan.
next prev parent reply other threads:[~2011-01-10 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinCD5Jf-dEUpv7hu4YKrxS0DGqqqBU94iCJ8602@mail.gmail.com>
[not found] ` <AANLkTinJAEW-xAiEKnfxo1+3FiGwFXFii5Rh6d8tAtB-@mail.gmail.com>
[not found] ` <1293652965.7150.13.camel@edumazet-laptop>
2011-01-10 8:06 ` Kernel 2.6.37-rc5 rc7 Oops David Miller
2011-01-10 21:08 ` Gertjan van Wingerde [this message]
2011-01-10 21:12 ` David Miller
2011-01-10 22:55 ` Gertjan van Wingerde
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=4D2B7550.5000008@gmail.com \
--to=gwingerde@gmail.com \
--cc=alex.arnautu96@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).