From: "Daniel Blueman" <daniel.blueman@gmx.net>
To: netdev@oss.sgi.com, linux-net@vger.kernel.org, devik@cdi.cz,
linux-kernel@vger.kernel.org
Subject: [2.6.0-test9] QoS HTB crash...
Date: Thu, 30 Oct 2003 17:10:25 +0100 (MET) [thread overview]
Message-ID: <26412.1067530225@www3.gmx.net> (raw)
With the LARTC 'wondershaper' HTB script [1] for good latency over ADSL, I
get an oops [3] when sending traffic via ppp0 (and when bringing the interface
down).
Kernel is 2.6.0-test9 and 'debug 3333333' appended to the 'tc' command, to
show HTB debug information [2] (not shown in [1]).
Please CC me when replying, and I can provide further details, debugging,
testing etc...this problem has been around for a while it seems.
--- [1] (relevant lines from http://lartc.org/wondershaper/)
tc qdisc add dev ppp0 root handle 1: htb default 20
tc class add dev ppp0 parent 1: classid 1:1 htb rate 210kbit burst 6k
tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 210kbit burst 6k prio
1
tc class add dev ppp0 parent 1:1 classid 1:20 htb rate 189kbit burst 6k prio
2
tc class add dev ppp0 parent 1:1 classid 1:30 htb rate 168kbit burst 6k prio
2
--- [2] (HTB debug messages)
HTB init, kernel part version 3.13
htb_init sch=dc28e7f8 handle=10000 r2q=10
htb_dump sch=dc28e7f8, handle=10000
htb*g j=179519 lj=0
htb*r7 m=0
htb*r6 m=0
htb*r5 m=0
htb*r4 m=0
htb*r3 m=0
htb*r2 m=0
htb*r1 m=0
htb*r0 m=0
htb_get clid=10010 q=dc28e86c cl=00000000 ref=0
htb_get clid=10010 q=dc28e86c cl=00000000 ref=0
htb_get clid=10020 q=dc28e86c cl=00000000 ref=0
htb_get clid=10020 q=dc28e86c cl=00000000 ref=0
htb_get clid=10030 q=dc28e86c cl=00000000 ref=0
htb_get clid=10030 q=dc28e86c cl=00000000 ref=0
htb_tcf q=dc28e86c clid=0 fref=0 fl=00000000
htb_bind q=dc28e86c clid=10010 cl=00000000 fref=0
htb_tcf q=dc28e86c clid=0 fref=1 fl=df4ecd7c
htb_bind q=dc28e86c clid=10010 cl=00000000 fref=1
htb_tcf q=dc28e86c clid=0 fref=2 fl=df4ecd7c
htb_bind q=dc28e86c clid=10010 cl=00000000 fref=2
htb_tcf q=dc28e86c clid=0 fref=3 fl=df4ecd7c
htb_bind q=dc28e86c clid=10020 cl=00000000 fref=3
htb_reset sch=dc28e7f8, handle=10000
--- [3] (ksymoops-processed oops report)
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c02cbbad>] Not tainted
>>EIP; c02cbbad <htb_enqueue+ab/126> <=====
>>ebx; ffffffff <__kernel_rt_sigreturn+1bbf/????>
>>ecx; dc28e86c <_end+1be20f60/3fb906f4>
>>esi; d9cf3f50 <_end+19886644/3fb906f4>
>>edi; dc28e7f8 <_end+1be20eec/3fb906f4>
>>ebp; dbef5ab8 <_end+1ba881ac/3fb906f4>
>>esp; dbef5a9c <_end+1ba88190/3fb906f4>
Trace; c02b3570 <dev_queue_xmit+593/73a>
Trace; c02e9c98 <ip_finish_output2+0/1c4>
Trace; c02e9d97 <ip_finish_output2+ff/1c4>
Trace; c02c0259 <nf_hook_slow+ef/13a>
Trace; c02e9c98 <ip_finish_output2+0/1c4>
Trace; c02e76d7 <ip_finish_output+21d/222>
Trace; c02e9c98 <ip_finish_output2+0/1c4>
Trace; c02bff12 <nf_iterate+6b/9f>
Trace; c02e9c80 <dst_output+15/2d>
Trace; c02c0259 <nf_hook_slow+ef/13a>
Trace; c02e9c6b <dst_output+0/2d>
Trace; c02e9620 <ip_push_pending_frames+3ac/408>
Trace; c02e9c6b <dst_output+0/2d>
Trace; c030da69 <udp_push_pending_frames+134/23c>
Trace; c030e1b4 <udp_sendmsg+60d/f3d>
Trace; c031900a <inet_sendmsg+4b/56>
Trace; c02aa4cc <sock_sendmsg+92/af>
Trace; c02aa582 <sock_recvmsg+99/b4>
Trace; c02a9f68 <move_addr_to_kernel+7e/a7>
Trace; c02b01a0 <verify_iovec+80/fa>
Trace; c02ac13d <sys_sendmsg+256/2f4>
Trace; c0141e28 <filemap_nopage+21c/2f9>
Trace; c0155610 <do_no_page+29b/631>
Trace; c0155c54 <handle_mm_fault+132/30c>
Trace; c018becd <inode_update_time+8e/b9>
Trace; c0119419 <do_page_fault+34b/56a>
Trace; c02ac67e <sys_socketcall+261/29a>
Trace; c0164327 <sys_write+5b/5d>
Trace; c010a3eb <syscall_call+7/b>
Code; c02cbbad <htb_enqueue+ab/126>
00000000 <_EIP>:
Code; c02cbbad <htb_enqueue+ab/126> <=====
0: 8b 43 04 mov 0x4(%ebx),%eax <=====
Code; c02cbbb0 <htb_enqueue+ae/126>
3: 89 44 24 04 mov %eax,0x4(%esp,1)
Code; c02cbbb4 <htb_enqueue+b2/126>
7: c7 04 24 2b 30 38 c0 movl $0xc038302b,(%esp,1)
Code; c02cbbbb <htb_enqueue+b9/126>
e: e8 e3 6e e5 ff call ffe56ef6 <_EIP+0xffe56ef6>
Code; c02cbbc0 <htb_enqueue+be/126>
13: 31 00 xor %eax,(%eax)
<0>Kernel panic: Fatal exception in interrupt
--
Daniel J Blueman
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService
Jetzt kostenlos anmelden unter http://www.gmx.net
+++ GMX - die erste Adresse für Mail, Message, More! +++
next reply other threads:[~2003-10-30 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 16:10 Daniel Blueman [this message]
2003-10-30 19:50 ` [2.6.0-test9] QoS HTB crash devik
2003-10-30 21:08 ` David S. Miller
2003-10-31 7:40 ` devik
2003-11-01 18:13 ` Daniel Blueman
2003-12-06 14:18 ` HTB 2.6.0-test10 oops related patch devik
2003-12-07 7:10 ` David S. Miller
2003-12-07 11:30 ` devik
2003-12-07 23:29 ` David S. Miller
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=26412.1067530225@www3.gmx.net \
--to=daniel.blueman@gmx.net \
--cc=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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).