From: Andrew Morton <akpm@osdl.org>
To: Thomas Cataldo <tomc@compaqnet.fr>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, tgraf@suug.ch,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Hard freeze with 2.6.10-rc3 and QoS, worked fine with 2.6.9
Date: Mon, 6 Dec 2004 22:44:41 -0800 [thread overview]
Message-ID: <20041206224441.628e7885.akpm@osdl.org> (raw)
In-Reply-To: <1102380430.6103.6.camel@buffy>
Thomas Cataldo <tomc@compaqnet.fr> wrote:
>
> Tonight I upgraded to 2.6.10-rc3. Everything was fine until I started
> wondershaper to setup my Qos rules :
>
> wondershaper eth0 255 16
>
> And the machine freezed hard. No magic sysrq working, no oops in my
> logs.
>
> The computer is an x86 smp (dual p3)
>
> wondershaper was working fine with 2.6.9.
Me too, with your .config:
Using http://lartc.org/wondershaper/wondershaper-1.1a.tar.gz
vmm:/home/akpm/wondershaper-1.1a# ./wshaper eth0 255 16
u32 classifier
Perfomance counters on
input device check on
Actions configured
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c0290b58
*pde = 00000000
Oops: 0002 [#1]
SMP
Modules linked in: police sch_ingress cls_u32 sch_sfq sch_cbq usbcore
CPU: 1
EIP: 0060:[<c0290b58>] Not tainted VLI
EFLAGS: 00010206 (2.6.10-rc3)
EIP is at _spin_lock_bh+0x10/0x20
eax: cf690000 ebx: ce0d4d80 ecx: 00000008 edx: 00000000
esi: cf691ba0 edi: 00000000 ebp: 00000000 esp: cf691b48
ds: 007b es: 007b ss: 0068
Process tc (pid: 2743, threadinfo=cf690000 task=cf07b520)
Stack: c02372ab ce0d4d80 cd4d8800 cebd1c40 ce0d4d80 c0237346 ce0d4d80 00000008
00000000 00000000 00000000 cf691ba0 cf691ba0 c02478d6 ce0d4d80 00000008
00000000 cf691ba0 ce0d4d80 cf6a6070 30960094 cec44380 00000000 00019000
Call Trace:
[<c02372ab>] gnet_stats_start_copy_compat+0x1b/0x98
[<c0237346>] gnet_stats_start_copy+0x1e/0x24
[<c02478d6>] tcf_action_copy_stats+0x26/0xa0
[<c02473e2>] tcf_action_dump_old+0x36/0x3c
[<d0807174>] u32_dump+0x2c8/0x344 [cls_u32]
[<d08071a6>] u32_dump+0x2fa/0x344 [cls_u32]
[<c0246cf9>] tcf_fill_node+0x11d/0x170
[<c0246d9c>] tfilter_notify+0x50/0xa0
[<c0246bae>] tc_ctl_tfilter+0x542/0x570
[<c0240705>] rtnetlink_rcv+0x23d/0x360
[<c0249f08>] netlink_data_ready+0x1c/0x54
[<c02495c5>] netlink_sendskb+0x21/0x40
[<c024970b>] netlink_unicast+0xe3/0xec
[<c0249d04>] netlink_sendmsg+0x27c/0x28c
[<c02306d9>] sock_sendmsg+0xd5/0xf8
[<c02306d9>] sock_sendmsg+0xd5/0xf8
[<c01c0a70>] copy_from_user+0x30/0x60
[<c01c0a70>] copy_from_user+0x30/0x60
[<c0127cfc>] autoremove_wake_function+0x0/0x40
[<c0231db7>] sys_sendmsg+0x18f/0x1f4
[<c013c068>] handle_mm_fault+0x80/0x11c
[<c010fc3b>] do_page_fault+0x1a3/0x554
[<c01c0a70>] copy_from_user+0x30/0x60
[<c02321bc>] sys_socketcall+0x1d8/0x1f4
[<c01021cd>] sysenter_past_esp+0x52/0x71
Code: 3a 00 7e f9 fa eb e9 c3 8d 76 00 fa f0 fe 08 79 09 f3 90 80 38 00 7e f9 eb f2 c3 89 c2 b8 00 e0 ff ff 21 e0 81
<0>Kernel panic - not syncing: Fatal exception in interrupt
Somehow I don't think this is because "Performance" was misspelled ;)
tcf_act_hdr.stats_lock is NULL in tcf_action_copy_stats()
next prev parent reply other threads:[~2004-12-07 6:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 0:47 Hard freeze with 2.6.10-rc3 and QoS, worked fine with 2.6.9 Thomas Cataldo
2004-12-07 6:35 ` Patrick McHardy
2004-12-07 6:44 ` Andrew Morton [this message]
2004-12-07 12:29 ` jamal
2004-12-07 16:59 ` Patrick McHardy
2004-12-07 17:07 ` Thomas Graf
2004-12-07 17:23 ` Patrick McHardy
2004-12-08 4:27 ` jamal
2004-12-08 4:41 ` Jamal Hadi Salim
2004-12-08 5:17 ` Patrick McHardy
2004-12-08 12:31 ` jamal
2004-12-08 14:32 ` Thomas Graf
2004-12-08 14:59 ` Thomas Graf
2004-12-08 15:06 ` jamal
2004-12-08 15:05 ` jamal
2004-12-08 17:30 ` Thomas Graf
2004-12-08 5:30 ` David S. Miller
2004-12-08 12:04 ` jamal
2004-12-08 16:57 ` Patrick McHardy
2004-12-08 19:30 ` Stephen Hemminger
2004-12-08 19:49 ` jamal
2004-12-08 19:44 ` jamal
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=20041206224441.628e7885.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
--cc=tomc@compaqnet.fr \
/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.