From: Mihai RUSU <dizzy@roedu.net>
To: lartc@vger.kernel.org
Subject: [LARTC] 2.4.20 htb3 oops
Date: Fri, 24 Jan 2003 12:54:56 +0000 [thread overview]
Message-ID: <marc-lartc-104341174125310@msgid-missing> (raw)
Hello
After 4 days of uptime the new 2.4.20 kernel with HTB3 (previously we used
HTB2 and 2.4.9-31) oopsed and in short time I could not even ssh to the
system. Here is the ksymoops filtered message:
ksymoops 2.4.8 on i686 2.4.20-xfs. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.20-xfs/ (default)
-m /usr/src/linux/System.map (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.
Oops: 0000
CPU: 1
EIP: 0010:[<c021be25>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 000000b0 ebx: 00000000 ecx: c031ad88 edx: 000000b0
esi: edb63de0 edi: f5220880 ebp: f5220880 esp: edb63d98
ds: 0018 es: 0018 ss: 0018
Process tc (pid: 7596, stackpageíb63000)
Stack: f5220800 00001831 ede963a0 ede963a0 f5220880 00000003 f5220860
c0214115
f5220800 edb63de0 f69b3960 f2bc0140 ede963a0 f2bc0140 ede963b8
f28f95b0
f757e800 00001831 00000000 000002a5 000002a6 c0214004 f69b3960
ede963a0
Call Trace: [<c0214115>] [<c0214004>] [<c0221db7>] [<c0208bd9>]
[<c0221b9b>]
[<c0221bc2>] [<c0203c91>] [<c020510f>] [<c0210010>] [<c0228186>]
[<c02281f0>]
[<c0226ffa>] [<c0114515>] [<c02053ed>] [<c0106f17>]
Code: 8b 03 0f 18 00 39 fb 75 c2 83 44 24 10 08 83 c5 08 ff 44 24
>>EIP; c021be25 <htb_walk+89/ad> <==
>>ecx; c031ad88 <irq_stat+28/400>
>>esi; edb63de0 <_end+2d81f388/384c35a8>
>>edi; f5220880 <_end+34edbe28/384c35a8>
>>ebp; f5220880 <_end+34edbe28/384c35a8>
>>esp; edb63d98 <_end+2d81f340/384c35a8>
Trace; c0214115 <tc_dump_tclass+dd/130>
Trace; c0214004 <qdisc_class_dump+0/34>
Trace; c0221db7 <netlink_dump+7f/1d4>
Trace; c0208bd9 <skb_free_datagram+1d/24>
Trace; c0221b9b <netlink_recvmsg+b7/134>
Trace; c0221bc2 <netlink_recvmsg+de/134>
Trace; c0203c91 <sock_recvmsg+3d/ac>
Trace; c020510f <sys_recvmsg+15b/204>
Trace; c0210010 <.text.lock.neighbour+24a/34a>
Trace; c0228186 <ip_forward+1a6/210>
Trace; c02281f0 <ip_forward_finish+0/60>
Trace; c0226ffa <ip_rcv+31a/3b0>
Trace; c0114515 <schedule+49d/560>
Trace; c02053ed <sys_socketcall+1f5/200>
Trace; c0106f17 <system_call+33/38>
Code; c021be25 <htb_walk+89/ad>
00000000 <_EIP>:
Code; c021be25 <htb_walk+89/ad> <== 0: 8b 03 mov (%ebx),%eax <==Code; c021be27 <htb_walk+8b/ad>
2: 0f 18 00 prefetchnta (%eax)
Code; c021be2a <htb_walk+8e/ad>
5: 39 fb cmp %edi,%ebx
Code; c021be2c <htb_walk+90/ad>
7: 75 c2 jne ffffffcb <_EIP+0xffffffcb>
c021bdf0 <htb_walk+54/ad>
Code; c021be2e <htb_walk+92/ad>
9: 83 44 24 10 08 addl $0x8,0x10(%esp,1)
Code; c021be33 <htb_walk+97/ad>
e: 83 c5 08 add $0x8,%ebp
Code; c021be36 <htb_walk+9a/ad>
11: ff 44 24 00 incl 0x0(%esp,1)
1 warning issued. Results may not be reliable.
$ /usr/src/linux/scripts/ver_linux
Linux htb 2.4.20-xfs #3 SMP Fri Jan 17 17:14:53 EET 2003 i686 unknown
Gnu C 2.95.3
Gnu make 3.79.1
util-linux 2.11r
mount 2.11r
modutils 2.4.16
e2fsprogs 1.27
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.7
Net-tools 1.60
Kbd 1.06
Sh-utils 2.0
Modules Loaded sch_sfq e1000
$ cat /etc/fstab
/dev/sda1 swap swap defaults 0 0
/dev/sda2 / ext2 defaults 1 1
/dev/sda3 /var xfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /dev/pts devpts gid=5,modeb0 0 0
none /proc proc defaults 0 0
After the oops applications that were trying to write to the /var (xfs)
partition were hanging in D state. We will reformat it and reboot with a
vanilla 2.4.20 having the same config except the XFS filesystem.
Help ?
----------------------------
Mihai RUSU
Disclaimer: Any views or opinions presented within this e-mail are solely
those of the author and do not necessarily represent those of any company,
unless otherwise specifically stated.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-24 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 12:54 Mihai RUSU [this message]
2003-01-24 14:29 ` [LARTC] 2.4.20 htb3 oops Catalin Bucur
2003-01-25 21:51 ` Alexey Sheshka
2003-03-03 13:22 ` Göran Runfeldt
2003-03-03 13:39 ` Abraham van der Merwe
2003-03-03 14:53 ` Göran Runfeldt
2003-03-03 16:29 ` Abraham van der Merwe
2003-05-06 16:10 ` Kabelweb
2003-05-07 18:31 ` Martin Volf
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-104341174125310@msgid-missing \
--to=dizzy@roedu.net \
--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 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.