From: Corey Hickey <bugfood-ml@fatooh.org>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: kernel panic on 2.6.24 with esfq patch applied
Date: Sat, 02 Feb 2008 02:23:36 -0800 [thread overview]
Message-ID: <47A444A8.8020304@fatooh.org> (raw)
In-Reply-To: <20080201131509.M52958@visp.net.lb>
Denys Fedoryshchenko wrote:
> Hi
>
> Probably bug related to ESFQ, now i will unload module and will test more.
> But probably not related, so if not difficult, please take a look.
>
> Feb 1 09:08:50 SERVER [12380.067104] BUG: unable to handle kernel NULL
> pointer dereference
> Feb 1 09:08:50 SERVER at virtual address 00000008
> Feb 1 09:08:50 SERVER [12380.067140] printing eip: c01f10ed
> Feb 1 09:08:50 SERVER *pde = 00000000
> Feb 1 09:08:50 SERVER
> Feb 1 09:08:50 SERVER [12380.067162] Oops: 0000 [#1]
> Feb 1 09:08:50 SERVER SMP
> Feb 1 09:08:50 SERVER
> Feb 1 09:08:50 SERVER [12380.067181] Modules linked in:
> Feb 1 09:08:50 SERVER netconsole
> Feb 1 09:08:50 SERVER configfs
> Feb 1 09:08:50 SERVER iTCO_wdt
> Feb 1 09:08:50 SERVER nf_nat_pptp
> Feb 1 09:08:50 SERVER nf_conntrack_pptp
> Feb 1 09:08:50 SERVER nf_conntrack_proto_gre
> Feb 1 09:08:50 SERVER nf_nat_proto_gre
> Feb 1 09:08:50 SERVER sch_esfq
I'd rather you were using my recent patches to SFQ instead of ESFQ. I
was able to crash a 2.6.24 user-mode Linux with ESFQ as well; I don't
know if that's what you encountered, but the SFQ patches should be
better anyway.
http://fatooh.org/esfq-2.6/sfq-2.6.24.tar.bz2
http://fatooh.org/esfq-2.6/
-Corey
next prev parent reply other threads:[~2008-02-02 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 13:25 kernel panic on 2.6.24 with esfq patch applied Denys Fedoryshchenko
2008-02-02 9:28 ` Jarek Poplawski
2008-02-02 10:23 ` Corey Hickey [this message]
2008-02-02 22:19 ` Jarek Poplawski
2008-02-02 22:53 ` Corey Hickey
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=47A444A8.8020304@fatooh.org \
--to=bugfood-ml@fatooh.org \
--cc=denys@visp.net.lb \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.