Re: Tc bug (kernel crash) more info

2007-09-03 Thread Jarek Poplawski
On Mon, Sep 03, 2007 at 12:31:39PM +0400, Badalian Vyacheslav wrote: > May you also see that i need change to fix this: > > qdisc handle can >= 10 000 > > i have more then 10 000 qdiscs =( > As far as I know qdisc handle is hex, so you can have e.g.: handle 999a (or a999 too). But, does it mean

Re: Tc bug (kernel crash) more info

2007-09-03 Thread Badalian Vyacheslav
May you also see that i need change to fix this: qdisc handle can >= 10 000 i have more then 10 000 qdiscs =( - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Tc bug (kernel crash) more info

2007-09-03 Thread Badalian Vyacheslav
Your errors trigger in rbtree, which does indexing for HTB, but since it's something quite rare I think there is a very small probability that it's caused by HTB class/level handling (but it's possible, too), but more probable (to me) these indexes are corrupted by something e.g. like accessing

Re: Tc bug (kernel crash) more info

2007-09-03 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 06:51:24PM +0400, Badalian Vyacheslav wrote: > I found that bug in this place > > (gdb) l *0xc01c8973 > 0xc01c8973 is in rb_insert_color (lib/rbtree.c:80). ... > if i not wrong understand message "unable to handle kernel NULL pointer > dereference at virtual address 00

Re: Tc bug (kernel crash) more info

2007-09-01 Thread slavon
Hi All! I found another bugs in HTB 1. HTB Wrong calculate LEVELS. - try run "./create_nodes.sh" in archive and do "tc -d class show dev eth0" Hm.. i read http://luxik.cdi.cz/~devik/qos/htb/manual/theory.htm I understand that if Level calculation broken - HTB wrong work! I try to see sch_htb.

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
I found that bug in this place (gdb) l *0xc01c8973 0xc01c8973 is in rb_insert_color (lib/rbtree.c:80). 75 76 while ((parent = rb_parent(node)) && rb_is_red(parent)) 77 { 78 gparent = rb_parent(parent); 79 80 if (parent == gparent

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
Ok =) I hope in next week you found bug place and fix it! PS. if you ask where i can read "kernel panic dump logic" literature and try find bugline in code. I read dump and see that bug in function "rb_insert_color" + some shift (in asm?) that called from htb_dequeue? But in htb_dequeue not hav

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 02:48:31PM +0400, Badalian Vyacheslav wrote: ... > I can only see that say netconsole. If i look to monitor i look last > lines. last line is "...". Scrolling not work > netconsole run as module and start after system do full load. Then > netconsole is up - i run gener

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
Jarek Poplawski пишет: On Fri, Aug 31, 2007 at 02:59:55PM +0400, Badalian Vyacheslav wrote: May be this bug eq "[PATCH] [NET_SCHED] sch_prio.c: remove duplicate call of tc_classify()"? I get kernel panic on 2.6.23-rc4-git2 This is netconsole log! ... So, it looks like

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 02:59:55PM +0400, Badalian Vyacheslav wrote: > May be this bug eq "[PATCH] [NET_SCHED] sch_prio.c: remove duplicate > call of tc_classify()"? > > >I get kernel panic on 2.6.23-rc4-git2 > >This is netconsole log! > ... > So, it looks like you have found a really new (unkn

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
May be this bug eq "[PATCH] [NET_SCHED] sch_prio.c: remove duplicate call of tc_classify()"? I get kernel panic on 2.6.23-rc4-git2 This is netconsole log! ... - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info a

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
I get kernel panic on 2.6.23-rc4-git2 This is netconsole log! [ 3931.002707] BUG: unable to handle kernel NULL pointer dereference at virtual address 0008 [ 3931.002846] printing eip: [ 3931.002906] c01c8973 [ 3931.002967] *pde = [ 3931.003031] Oops: [#1] [ 3931.003093] SMP [

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
But sometime a new kernel can break binary compatibility with previous one (e.g. after data structures change) and e.g. iptables or iproute tools stop working or work in an unpredictable way. There were a few such changes before 2.6.20 - I don't track current changes too much. And I'm sure your

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 01:33:04PM +0400, Badalian Vyacheslav wrote: > > >>i not have testing mashine. > >>we have 2 mashine and dynamic routing. if 1 mashine down - all traffic > >>go to second mashine. > >>I can test is on this mashines but i need that testing mashine will > >>reboot on kernel

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
i not have testing mashine. we have 2 mashine and dynamic routing. if 1 mashine down - all traffic go to second mashine. I can test is on this mashines but i need that testing mashine will reboot on kernel panic (sysctl message). No freezes =) Ok. i try 2.6.23-rc4. ...but without test

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 11:05:09AM +0200, Jarek Poplawski wrote: ... > So, maybe you would better try this, 'less testing', version of my patch: Of course, the previous patch should be reverted (patch -p1 -R) or clean 2.6.22.5 used for this. Jarek P. - To unsubscribe from this list: send the lin

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 12:25:22PM +0400, Badalian Vyacheslav wrote: > i not have testing mashine. > we have 2 mashine and dynamic routing. if 1 mashine down - all traffic > go to second mashine. > I can test is on this mashines but i need that testing mashine will > reboot on kernel panic (sysct

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 12:25:22PM +0400, Badalian Vyacheslav wrote: > i not have testing mashine. > we have 2 mashine and dynamic routing. if 1 mashine down - all traffic > go to second mashine. > I can test is on this mashines but i need that testing mashine will > reboot on kernel panic (sysct

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
i not have testing mashine. we have 2 mashine and dynamic routing. if 1 mashine down - all traffic go to second mashine. I can test is on this mashines but i need that testing mashine will reboot on kernel panic (sysctl message). No freezes =) Ok. i try 2.6.23-rc4. On Fri, Aug 31, 2007 at 11

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Jarek Poplawski
On Fri, Aug 31, 2007 at 11:04:21AM +0400, Badalian Vyacheslav wrote: > > I try you patch. Also i try add more debug options to kernel. I catch > (BUG: spinlock lockup on CPU#3, tc/6403, f742e200) > All info in file. Ready for next patch ;) I've to look at this, but actually my patch wrongly adde

Re: Tc bug (kernel crash) more info

2007-08-31 Thread Badalian Vyacheslav
I try you patch. Also i try add more debug options to kernel. I catch (BUG: spinlock lockup on CPU#3, tc/6403, f742e200) All info in file. Ready for next patch ;) Jarek Poplawski ??: ... On the other hand disabling local interrupts shouldn't be enough here, so it's really st

Re: Tc bug (kernel crash) more info

2007-08-30 Thread Jarek Poplawski
On Thu, Aug 30, 2007 at 01:09:11PM +0400, Badalian Vyacheslav wrote: > Jarek Poplawski ??: ... > >On the other hand disabling local interrupts shouldn't be enough here, > >so it's really strange... Did you get this remotely? Are you sure LOC > >only? (Anyway this 2.6.23-rc4 should be intere

Re: Tc bug (kernel crash) more info

2007-08-30 Thread Badalian Vyacheslav
Jarek Poplawski пишет: On Thu, Aug 30, 2007 at 08:31:10AM +0200, Jarek Poplawski wrote: On Thu, Aug 30, 2007 at 12:16:32AM +0400, [EMAIL PROTECTED] wrote: ... PS. And also have we have strange bug in another computer (2.6.22-r5). Have computer XEON_CPUx2 (4 CPU) after boot have CPU

Re: Tc bug (kernel crash) more info

2007-08-30 Thread Jarek Poplawski
On Thu, Aug 30, 2007 at 08:31:10AM +0200, Jarek Poplawski wrote: > On Thu, Aug 30, 2007 at 12:16:32AM +0400, [EMAIL PROTECTED] wrote: ... > > PS. And also have we have strange bug in another computer (2.6.22-r5). > > Have computer XEON_CPUx2 (4 CPU) > > > > after boot have CPU0 and CPU3 SI = ~50%

Re: Tc bug (kernel crash) more info

2007-08-29 Thread Jarek Poplawski
On Thu, Aug 30, 2007 at 12:16:32AM +0400, [EMAIL PROTECTED] wrote: > Quoting Jarek Poplawski <[EMAIL PROTECTED]>: > > >On Wed, Aug 29, 2007 at 04:53:52PM +0400, Badalian Vyacheslav wrote: > >... > >>we have this kernel panic (then delete HTB) at all 2.6.18-x versions. > >>on older kernel (2.6.x) w

Re: Tc bug (kernel crash) more info

2007-08-29 Thread slavon
Quoting Jarek Poplawski <[EMAIL PROTECTED]>: On Wed, Aug 29, 2007 at 04:53:52PM +0400, Badalian Vyacheslav wrote: ... we have this kernel panic (then delete HTB) at all 2.6.18-x versions. on older kernel (2.6.x) we have another panic (then delete tc filter)... summary we have TC panics 1 year a

Re: Tc bug (kernel crash) more info

2007-08-29 Thread Jarek Poplawski
On Wed, Aug 29, 2007 at 04:53:52PM +0400, Badalian Vyacheslav wrote: ... > we have this kernel panic (then delete HTB) at all 2.6.18-x versions. > on older kernel (2.6.x) we have another panic (then delete tc filter)... > summary we have TC panics 1 year ago ;) Sysctl option "reboot on panic" I'

Re: Tc bug (kernel crash) more info

2007-08-29 Thread Badalian Vyacheslav
Jarek Poplawski пишет: On Wed, Aug 29, 2007 at 01:34:47PM +0200, Jarek Poplawski wrote: On 29-08-2007 11:34, Badalian Vyacheslav wrote: Again crash. Need more posts of panic or this message have full info that needed to fix bug? ... If it's possible you can try it shortly w

Re: Tc bug (kernel crash) more info

2007-08-29 Thread Jarek Poplawski
On Wed, Aug 29, 2007 at 01:34:47PM +0200, Jarek Poplawski wrote: > On 29-08-2007 11:34, Badalian Vyacheslav wrote: > > Again crash. Need more posts of panic or this message have full info > > that needed to fix bug? ... > If it's possible you can try it shortly without e.g. netconsole or > even w

Re: Tc bug (kernel crash) more info

2007-08-29 Thread Jarek Poplawski
On 29-08-2007 11:34, Badalian Vyacheslav wrote: > Again crash. Need more posts of panic or this message have full info > that needed to fix bug? Hi, Please, try to not create new threads each time: reply to the previous one if you have something new. And this one doesn't seem to show more. You

Tc bug (kernel crash) more info

2007-08-29 Thread Badalian Vyacheslav
Again crash. Need more posts of panic or this message have full info that needed to fix bug? BUG: unable to handle kernel NULL pointer dereference at virtual address 0008 printing eip: c01bf041 *pde = Oops: [#1] SMP Modules linked in: cls_u32 sch_sfq sch_htb netconsole xt_tc