HTB/IMQ troubles (probably)
Hello,
I use HTB with linux-2.4.20-ac1 and iptables-1.2.7a (pathced for IMQ).
I configured one HTB qdisc on an IMQ device. This qdisc has some classes (about 5) and all of the classes has qdisc pfifo.
I sometimes got out from my linux (while I was working) and I found in logs:
Dec 4 11:49:27 core kernel: HTB init, kernel part version 3.7 Dec 4 11:49:28 core kernel: HTB: quantum of class 10020 is small.
Consider r2q change.<7>htb*g j„81720
and once:
Dec 4 13:47:10 core kernel: eth0: Transmit error, Tx status register 82. Dec 4 13:47:10 core kernel: Probably a duplex mismatch. See Documentation/networking/vortex.txt Dec 4 13:47:10 core kernel: Flags; bus-master 1, dirty 57343(15) current 57343(15) Dec 4 13:47:10 core kernel: Transmit list 00000000 vs. dec105c0. Dec 4 13:47:10 core kernel: 0: @dec10200 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 1: @dec10240 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 2: @dec10280 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 3: @dec102c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 4: @dec10300 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 5: @dec10340 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 6: @dec10380 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 7: @dec103c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 8: @dec10400 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 9: @dec10440 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 10: @dec10480 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 11: @dec104c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 12: @dec10500 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 13: @dec10540 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 14: @dec10580 length 800005ee status 800105ee Dec 4 13:47:10 core kernel: 15: @dec105c0 length 800005ee status
000105ee
My interfaces:
eth0 : a VLAN trunk interface
eth1 : not used yet
eth2 : my interface the IMQ is attached on (PRE- and POSTROUTING chains). 00:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
I tryed to make some download tests and it didn't work and I got out from computer (I don't have a monitor connected to the comp. - only a serial console port:).
What can I do with that? How can I fix the problem?
Thanks
Thomas
Queueing discipline statistics:
-------------------------------
qdisc pfifo 50: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc pfifo 20: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc pfifo 30: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc pfifo 10: limit 2p
Sent 896 bytes 10 pkts (dropped 0, overlimits 0)
qdisc pfifo 40: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc pfifo 60: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc htb 1: r2q 10 default 10 direct_packets_stat 0 ver 3.7 Sent 896 bytes 10 pkts (dropped 0, overlimits 0)
Class statistics:
-------------------
class htb 1:1 root rate 1920Kbit ceil 1920Kbit burst 4056b/8 mpu 0b cburst 4056b/8 mpu 0b level 7
Sent 1988 bytes 16 pkts (dropped 0, overlimits 0)
rate 23bps
lended: 0 borrowed: 0 giants: 0
tokens: 12963 ctokens: 12963
class htb 1:10 parent 1:1 leaf 10: prio 1 quantum 9011 rate 704Kbit ceil 1920Kbit burst 2500b/8 mpu 0b cburst 4056b/8 mpu 0b level 0
Sent 1988 bytes 16 pkts (dropped 0, overlimits 0)
rate 23bps
lended: 16 borrowed: 0 giants: 0
tokens: 21189 ctokens: 12963
class htb 1:20 parent 1:1 leaf 20: prio 1 quantum 1000 rate 64Kbit ceil 64Kbit burst 1680b/8 mpu 0b cburst 1680b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 168099 ctokens: 168099
class htb 1:30 parent 1:1 leaf 30: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149
class htb 1:40 parent 1:1 leaf 40: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149
class htb 1:50 parent 1:1 leaf 50: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149
class htb 1:60 parent 1:1 leaf 60: prio 1 quantum 13107 rate 1Mbit ceil 1Mbit burst 2909b/8 mpu 0b cburst 2909b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 18187 ctokens: 18187
Filter statistics:
--------------------
filter parent 1: protocol ip pref 1 u32
filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 60:
match c129cb80/ffffff80 at 16
filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 40:
match c129cb2a/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 10:
match c129cb00/ffffffe0 at 16
filter parent 1: protocol ip pref 1 u32 fh 800::803 order 2051 key ht 800 bkt 0 flowid 10:
match c0a801aa/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::804 order 2052 key ht 800 bkt 0 flowid 30:
match c129cb26/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::805 order 2053 key ht 800 bkt 0 flowid 20:
match c129cb22/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::806 order 2054 key ht 800 bkt 0 flowid 50:
match c129cb2e/ffffffff at 16
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello,
I also got (on the serial console):
Unable to handle kernel NULL pointer dereference at virtual address
0000003c
printing eip:c020fae0
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c020fae0>] Not tainted
EFLAGS: 00010246
eax: 00000000 ebx: df2335dc ecx: 00000002 edx: e6fc2498
esi: 000005b4 edi: fffffff5 ebp: df2334c0 esp: c02b9ed0
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage�2b9000)
Stack: 00000000 c0208f60 df2335dc df2334c0 df2335dc df233518 00000046
c0211c10
df2334c0 00000000 c24f6548 c01e14f1 c24f6548 c02b9f24 00000001
c01e1410
c24e3ac0 df2334c0 0003d39c 00000000 00000046 c0211eb0 df2334c0
c02b9fa8
Call Trace: [<c0208f60>] [<c0211c10>] [<c01e14f1>] [<c01e1410>][<c0211eb0>]
[<c0211de0>] [<c012151e>] [<c011d982>] [<c011d896>] [<c011d6d4>]
[<c010a47e>]
[<c0106ea0>] [<c0105000>] [<c010c9d8>] [<c0106ea0>] [<c0106ea0>]
[<c0105000>]
[<c0106ec3>] [<c0106f14>]
Code: 8b 48 3c 89 d0 03 43 54 39 c1 78 14 39 d1 bf f5 ff ff ff 74 <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
...probably similar thing has happened before (I didn't have the serial console, so I don't know).
I didn't find anything useful in messages logfile...
Regards,
Thomas
p.s.: I use gcc-3.2 on Athlon-XP 1700+ with 512M RAM (and again:
linux-2.4.20-ac1 on RedHat 8.0)
Quoted 173 lines · Thomas Jalsovsky
Hello,
I use HTB with linux-2.4.20-ac1 and iptables-1.2.7a (pathced for IMQ).
I configured one HTB qdisc on an IMQ device. This qdisc has some classes (about 5) and all of the classes has qdisc pfifo.
I sometimes got out from my linux (while I was working) and I found in logs:
Dec 4 11:49:27 core kernel: HTB init, kernel part version 3.7 Dec 4 11:49:28 core kernel: HTB: quantum of class 10020 is small.Consider r2q change.<7>htb*g j�81720
and once:
Dec 4 13:47:10 core kernel: eth0: Transmit error, Tx status register 82. Dec 4 13:47:10 core kernel: Probably a duplex mismatch. See Documentation/networking/vortex.txt Dec 4 13:47:10 core kernel: Flags; bus-master 1, dirty 57343(15) current 57343(15) Dec 4 13:47:10 core kernel: Transmit list 00000000 vs. dec105c0. Dec 4 13:47:10 core kernel: 0: @dec10200 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 1: @dec10240 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 2: @dec10280 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 3: @dec102c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 4: @dec10300 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 5: @dec10340 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 6: @dec10380 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 7: @dec103c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 8: @dec10400 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 9: @dec10440 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 10: @dec10480 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 11: @dec104c0 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 12: @dec10500 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 13: @dec10540 length 800005ee status 000105ee Dec 4 13:47:10 core kernel: 14: @dec10580 length 800005ee status 800105ee Dec 4 13:47:10 core kernel: 15: @dec105c0 length 800005ee status
000105eeMy interfaces:
eth0 : a VLAN trunk interface
eth1 : not used yet
eth2 : my interface the IMQ is attached on (PRE- and POSTROUTING chains). 00:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)I tryed to make some download tests and it didn't work and I got out from computer (I don't have a monitor connected to the comp. - only a serial console port:).
What can I do with that? How can I fix the problem?
Thanks
ThomasQueueing discipline statistics:
-------------------------------
qdisc pfifo 50: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)qdisc pfifo 20: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)qdisc pfifo 30: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)qdisc pfifo 10: limit 2p
Sent 896 bytes 10 pkts (dropped 0, overlimits 0)qdisc pfifo 40: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)qdisc pfifo 60: limit 2p
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)qdisc htb 1: r2q 10 default 10
direct_packets_stat0 ver 3.7 Sent 896 bytes 10 pkts (dropped 0, overlimits 0)Class statistics:
-------------------
class htb 1:1 root rate 1920Kbit ceil 1920Kbit burst 4056b/8 mpu 0b cburst 4056b/8 mpu 0b level 7
Sent 1988 bytes 16 pkts (dropped 0, overlimits 0)
rate 23bps
lended: 0 borrowed: 0 giants: 0
tokens: 12963 ctokens: 12963class htb 1:10 parent 1:1 leaf 10: prio 1 quantum 9011 rate 704Kbit ceil 1920Kbit burst 2500b/8 mpu 0b cburst 4056b/8 mpu 0b level 0
Sent 1988 bytes 16 pkts (dropped 0, overlimits 0)
rate 23bps
lended: 16 borrowed: 0 giants: 0
tokens: 21189 ctokens: 12963class htb 1:20 parent 1:1 leaf 20: prio 1 quantum 1000 rate 64Kbit ceil 64Kbit burst 1680b/8 mpu 0b cburst 1680b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 168099 ctokens: 168099class htb 1:30 parent 1:1 leaf 30: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149class htb 1:40 parent 1:1 leaf 40: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149class htb 1:50 parent 1:1 leaf 50: prio 1 quantum 1638 rate 128Kbit ceil 128Kbit burst 1762b/8 mpu 0b cburst 1762b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 88149 ctokens: 88149class htb 1:60 parent 1:1 leaf 60: prio 1 quantum 13107 rate 1Mbit ceil 1Mbit burst 2909b/8 mpu 0b cburst 2909b/8 mpu 0b level 0
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0
tokens: 18187 ctokens: 18187Filter statistics:
--------------------
filter parent 1: protocol ip pref 1 u32
filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 60:
match c129cb80/ffffff80 at 16
filter parent 1: protocol ip pref 1 u32 fh 800::801 order 2049 key ht 800 bkt 0 flowid 40:
match c129cb2a/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::802 order 2050 key ht 800 bkt 0 flowid 10:
match c129cb00/ffffffe0 at 16
filter parent 1: protocol ip pref 1 u32 fh 800::803 order 2051 key ht 800 bkt 0 flowid 10:
match c0a801aa/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::804 order 2052 key ht 800 bkt 0 flowid 30:
match c129cb26/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::805 order 2053 key ht 800 bkt 0 flowid 20:
match c129cb22/ffffffff at 16
filter parent 1: protocol ip pref 1 u32 fh 800::806 order 2054 key ht 800 bkt 0 flowid 50:
match c129cb2e/ffffffff at 16
Quoted 4 lines
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 4 Dec 2002, Thomas Jalsovsky wrote:
.. snip ..
Quoted 5 lines
Code: 8b 48 3c 89 d0 03 43 54 39 c1 78 14 39 d1 bf f5 ff ff ff 74 <0>Kernel panic: Aiee, killing interrupt handler!In interrupt handler - not syncing
Same problem here, until I found that one should (must?) use different IMQ devices for PREROUTING and POSTROUTING.
HTH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE970hclDG6Z61nQGIRAnaaAJ9xFoOrPIeQprbZ9jC/8XmCaJIaVACfVEbu Sh4WUqeahKwqFKADkUYK9+E=S6Tn
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 10 lines
.. snip ..
Quoted 5 lines
Code: 8b 48 3c 89 d0 03 43 54 39 c1 78 14 39 d1 bf f5 ff ff ff 74 <0>Kernel panic: Aiee, killing interrupt handler!In interrupt handler - not syncing
Same problem here, until I found that one should (must?) use different IMQ devices for PREROUTING and POSTROUTING.
HTH
Many, many thanks Razvan!!!
It was the problem. I removed one PRE- or POSTROUTING rule and see the
magic: I can't reproduce the kernel panic.
So now the question is:
Is it possible to use the SAME IMQ device for ingress and egress trafffic (as I tryed to use)? If not, why, and if yes how?
Thank you again,
Thomas
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/