From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, <hadi@cyberus.ca>
Subject: Re: 2.6.38.x, 2.6.39 sfq? kernel panic in sfq_enqueue
Date: Tue, 24 May 2011 16:26:41 +0300 [thread overview]
Message-ID: <67447e772bb5bcf42dfcdb817c756c74@visp.net.lb> (raw)
In-Reply-To: <1306243069.3026.34.camel@edumazet-laptop>
On Tue, 24 May 2011 15:17:49 +0200, Eric Dumazet wrote:
> Le mardi 24 mai 2011 à 01:35 +0300, Denys Fedoryshchenko a écrit :
>> On Mon, 23 May 2011 17:05:46 +0200, Eric Dumazet wrote:
>> > Le lundi 23 mai 2011 à 17:27 +0300, Denys Fedoryshchenko a écrit :
>> >
>> >> > Thanks !
>> >> By objdump or he must recompile kernel with DEBUG_INFO and use
>> gdb?
>> >>
>> >>
>> >>
>> >
>> >
>> > Just objdump of sch_sfq.o (or sch_sfq.ko) file, (to keep existing
>> > offsets), thanks
>> Sorry for delay, i had to contact person who run that kernel :)
>>
>> www.nuclearcat.com/files/disasm.txt
>> www.nuclearcat.com/files/sch_sfq.ko
>>
>>
>
> Thanks !
>
> BTW, does this person have another bug trace to feed us ?
>
> I tried to reproduce it here but failed.
>
> full dmesg might help too
We can try to compile also kernel with debug info and run gdb on it
maybe, i will ask him about that.
next prev parent reply other threads:[~2011-05-24 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 10:01 2.6.38.x, 2.6.39 sfq? kernel panic in sfq_enqueue Denys Fedoryshchenko
2011-05-23 12:32 ` Eric Dumazet
2011-05-23 12:50 ` Eric Dumazet
2011-05-23 13:23 ` Eric Dumazet
2011-05-23 14:27 ` Denys Fedoryshchenko
2011-05-23 15:05 ` Eric Dumazet
2011-05-23 22:35 ` Denys Fedoryshchenko
2011-05-24 13:17 ` Eric Dumazet
2011-05-24 13:26 ` Denys Fedoryshchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 16:09 Vadym Abramchuk
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=67447e772bb5bcf42dfcdb817c756c74@visp.net.lb \
--to=denys@visp.net.lb \
--cc=eric.dumazet@gmail.com \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.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