From: Abraham van der Merwe <abz@frogfoot.net>
To: kuznet@ms2.inr.ac.ru
Cc: devik@cdi.cz, ahu@ds9a.nl, linux-kernel@vger.kernel.org,
david@uninetwork.co.za, netdev@oss.sgi.com
Subject: Re: kernel panic: bug in sch_sfq.c
Date: Tue, 11 Mar 2003 23:19:02 +0200 [thread overview]
Message-ID: <20030311211902.GA8699@oasis.frogfoot.net> (raw)
In-Reply-To: <200303111608.TAA13074@sex.inr.ac.ru>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
Hi kuznet!
> > Also, if I compile the kernel with all debugging enabled (CONFIG_DEBUG_SLAB,
> > etc) I can reliably trigger the BUG() on line 1263 in mm/slab.c
>
> How does backtrace oops look?
I didn't write down most of the BUG() panics, but here is one (unfortunately
it doesn't have any QoS code in the stack trace):
------------< snip <------< snip <------< snip <------------
root@trillian:~/uni-qos# cat panic.txt
c0192eb1
c0176c8c
c017718c
c0176afa
c010810f
c01082b3
c0105240
c0105240
c0105240
c0105240
c0105263
c01052d2
c0105000
c0105027
0f 0b ef 04 e0 87 1e c0 f7 c5 00 04 00 00 74 36 b8 a5 c2 0f
EIP: 0010:c012642e
ESP: c0221eb4
KERNEL BUG slab.c:1263
root@trillian:~/uni-qos#
------------< snip <------< snip <------< snip <------------
A quick objdump through the kernel's vmlinux image reveals, that the stack
trace above looks as follows:
------------< snip <------< snip <------< snip <------------
c0192eb1 alloc_skb
c0176c8c speedo_refill_rx_buf
c017718c speedo_rx
c0176afa speedo_interrupt
c010810f handle_IRQ_event
c01082b3 do_IRQ
c0105240 default_idle
c0105240 default_idle
c0105240 default_idle
c0105240
c0105263 default_idle
c01052d2 cpu_idle
c0105000 rest_init
c0105027 rest_init
------------< snip <------< snip <------< snip <------------
It crashes when it hits BUG(); in slab.c:
------------< snip <------< snip <------< snip <------------
#if DEBUG
if (cachep->flags & SLAB_POISON)
if (kmem_check_poison_obj(cachep, objp))
BUG();
------------< snip <------< snip <------< snip <------------
--
Regards
Abraham
Nothing is so often irretrievably missed as a daily opportunity.
-- Ebner-Eschenbach
___________________________________________________
Abraham vd Merwe - Frogfoot Networks CC
9 Kinnaird Court, 33 Main Street, Newlands, 7700
Phone: +27 21 686 1674 Cell: +27 82 565 4451
Http: http://www.frogfoot.net/ Email: abz@frogfoot.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-03-11 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030311091409.GA4491@oasis.frogfoot.net>
2003-03-11 9:44 ` kernel panic: bug in sch_sfq.c bert hubert
2003-03-11 11:55 ` devik
2003-03-11 15:54 ` Abraham van der Merwe
2003-03-11 16:08 ` kuznet
2003-03-11 21:19 ` Abraham van der Merwe [this message]
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=20030311211902.GA8699@oasis.frogfoot.net \
--to=abz@frogfoot.net \
--cc=ahu@ds9a.nl \
--cc=david@uninetwork.co.za \
--cc=devik@cdi.cz \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).