From: Tomasz Wrona <tw@eter.tym.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] oops
Date: Mon, 25 Nov 2002 11:27:16 +0000 [thread overview]
Message-ID: <marc-lartc-103822373129529@msgid-missing> (raw)
Hello,
Does following oops say something ?
I post it to LARTC because I get it when playing with QoS tools.
--
ksymoops 2.4.5 on i686 2.4.18-grsec. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.18-grsec/ (default)
-m /boot/System.map-2.4.18-grsec (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
CPU: 0
EIP: 0010:[<cc097c26>] Not tained
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010283
eax: 9812f7e0 ebx: cc904d28 ecx: 00000006 edx: cc904e60
esi: cc904e48 edi: cc8f5600 ebp: cc904c60 esp: c021fd84
ds: 0018 es: 0018 ss: 0018
Process (pid: 0, stackpage¿21f000)
Stack: d08768a3 cc097bc0 ffffffff 00000000 00000000 cc904c00 cc8f5600
cc8d6e00
00000040 cc904d28 cc904e48 cc8f5600 d0876c2d cc904c60 00000006
00000000
cc904c00 cfe52800 00000000 c01a994c cc904e28 cc904f68 00000001
cc904c60
Call Trace: [<d08768a3>] [<d0876c2d>] [<c01a994c>] [<c019c693>]
[<c0196503>]
[<c01e99dd>] [<c019bec6>] [<c01a6bf0>] [<c01a9932>] [<c01a994c>]
[<c01a6c3a>]
[<c019bec6>] [<c01a6b9b>] [<c01a6bf0>] [<c01a5f79>] [<c01a5db8>]
[<c019bec6>]
[<c01e5c26>] [<c01a5db8>] [<c0196a9d>] [<c011554a>] [<c0107f5d>]
[<c0105150>]
[<c0105150>] [<c010a2d8>] [<c0105150>] [<c0105150>] [<c0105173>]
[<c01051d9>]
[<c0105000>] [<c0105027>]
Code: 00 00 00 20 8e cc 00 00 00 00 03 00 00 00 00 40 89 cc 00 00
>>EIP; cc097c26 <_end+be1ac9e/1058e078> <==
>>eax; 9812f7e0 Before first symbol
>>ebx; cc904d28 <_end+c687da0/1058e078>
>>edx; cc904e60 <_end+c687ed8/1058e078>
>>esi; cc904e48 <_end+c687ec0/1058e078>
>>edi; cc8f5600 <_end+c678678/1058e078>
>>ebp; cc904c60 <_end+c687cd8/1058e078>
>>esp; c021fd84 <init_task_union+1d84/2000>
Trace; d08768a3 <[sch_sfq]sfq_reset+17/34>
Trace; d0876c2d <[sch_sfq].text.end+4e/e1>
Trace; c01a994c <ip_finish_output2+0/d0>
Trace; c019c693 <qdisc_restart+13/d8>
Trace; c0196503 <dev_queue_xmit+f7/238>
Trace; c01e99dd <Unused_offset+1ad9/bdc0>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01a6bf0 <ip_forward_finish+0/50>
Trace; c01a9932 <ip_finish_output+102/108>
Trace; c01a994c <ip_finish_output2+0/d0>
Trace; c01a6c3a <ip_forward_finish+4a/50>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01a6b9b <ip_forward+1eb/240>
Trace; c01a6bf0 <ip_forward_finish+0/50>
Trace; c01a5f79 <ip_rcv_finish+1c1/1f8>
Trace; c01a5db8 <ip_rcv_finish+0/1f8>
Trace; c019bec6 <nf_hook_slow+ee/144>
Trace; c01e5c26 <_etext+5122/617c>
Trace; c01a5db8 <ip_rcv_finish+0/1f8>
Trace; c0196a9d <net_rx_action+1a5/280>
Trace; c011554a <do_softirq+5a/ac>
Trace; c0107f5d <do_IRQ+a1/b4>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c010a2d8 <call_do_IRQ+5/d>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c0105173 <default_idle+23/28>
Trace; c01051d9 <cpu_idle+41/54>
Trace; c0105000 <_stext+0/0>
Trace; c0105027 <rest_init+27/28>
Code; cc097c26 <_end+be1ac9e/1058e078>
00000000 <_EIP>:
Code; cc097c26 <_end+be1ac9e/1058e078> <== 0: 00 00 add %al,(%eax) <==Code; cc097c28 <_end+be1aca0/1058e078>
2: 00 20 add %ah,(%eax)
Code; cc097c2a <_end+be1aca2/1058e078>
4: 8e cc mov %esp,%cs
Code; cc097c2c <_end+be1aca4/1058e078>
6: 00 00 add %al,(%eax)
Code; cc097c2e <_end+be1aca6/1058e078>
8: 00 00 add %al,(%eax)
Code; cc097c30 <_end+be1aca8/1058e078>
a: 03 00 add (%eax),%eax
Code; cc097c32 <_end+be1acaa/1058e078>
c: 00 00 add %al,(%eax)
Code; cc097c34 <_end+be1acac/1058e078>
e: 00 40 89 add %al,0xffffff89(%eax)
Code; cc097c37 <_end+be1acaf/1058e078>
11: cc int3
<0>Kernel panic: Aiee, killing interrupt handler!
1 warning issued. Results may not be reliable.
--
Regards
tw
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-11-25 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-103822373129529@msgid-missing \
--to=tw@eter.tym.pl \
--cc=lartc@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