Bug 9318
Summary: | 2.6.23.1-smp kernel panic (network-related) | ||
---|---|---|---|
Product: | Networking | Reporter: | Krzysztof Mościcki (stivi) |
Component: | Other | Assignee: | Arnaldo Carvalho de Melo (acme) |
Status: | REJECTED INVALID | ||
Severity: | normal | CC: | jarkao2, marek |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.23.1 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
kernel 2.6.23.1 - config
Print timer running function in panic Print in panic plus verify timer function address |
Description
Krzysztof Mościcki
2007-11-07 12:03:58 UTC
Created attachment 13442 [details]
kernel 2.6.23.1 - config
Other people reported this bug on various forums/mailing lists. Examples: http://forums.gentoo.org/viewtopic-t-458545.html and http://lists.openwall.net/netdev/2007/12/05/43 It seems to be SMP & ifb related This looks very similar too: http://bugzilla.kernel.org/show_bug.cgi?id=9632 Marek, I think, it should be very helpful if you could repeat this test with this new Oleg Nesterov's patch, which could tell us which timer breaks here. ...Probably I should rather say Krzysztof? Or both?! Sorry guys! Thanks Jarek. Krzysztof and I are both work at the same company and we're at the same bottom of a pond with this bug metaphorically speaking. Thanks to Jamal Hadi Salim I'm aware of the bug #9632 since this morning. I've got testing environment that allows to reproduce kernel panic in 5-15 minutes. I gave the patch a try but with no positive outcome I'm afraid :(. Anyway bug #9632 may be a different thing. I've noticed my problems only with SMP+IFB+ingress in use. Badalian's example lets me think that he's not using IFB or ingress. Kernel panic message is different too. Badalian's message starts with "kernel BUG at kernel/timer.c:606!" and in this but there's: "PANIC: double fault, gdt at c1805000 [255 bytes]" or "general protection fault" Jamal has given me some pointers of how to conduct further testing to narrow down the problem and he promised more help. > Thanks to Jamal Hadi Salim I'm aware of the bug #9632 since this morning. > I've > got testing environment that allows to reproduce kernel panic in 5-15 > minutes. > I gave the patch a try but with no positive outcome I'm afraid :(. Since this bug could be quite old I don't think there is any reason to hurry. But it would be nice to fix this some day, of course. > Anyway bug #9632 may be a different thing. I've noticed my problems only with > SMP+IFB+ingress in use. Badalian's example lets me think that he's not using > IFB or ingress. Kernel panic message is different too. Badalian's message > starts with "kernel BUG at kernel/timer.c:606!" > and in this but there's: > "PANIC: double fault, gdt at c1805000 [255 bytes]" > or > "general protection fault" I don't claim it's the same bug, but since it breaks while timers are called, this Oleg's new patch could be very useful. So, if e.g. timer_list structure is used after kfree (e.g. when it's not deleted properly and the timer 'rearms' itself), it can break in a very unpredictable way, and it could be some different timer, as well. (BTW, it seems Badalian prefers 'Hungarian' way of signing, but it's a surname...) > Jamal has given me some pointers of how to conduct further testing to narrow > down the problem and he promised more help. Very nice! I hope you'll mention here any new observations. Thanks. > I gave the patch a try but with no positive outcome I'm afraid :(.
Hmm... I didn't read this with attention: does 'no positive outcome'
mean that with this new patch this still oopses exactly the same?
> Hmm... I didn't read this with attention: does 'no positive outcome'
> mean that with this new patch this still oopses exactly the same?
Yup... oopses the same way.
Created attachment 14231 [details]
Print timer running function in panic
Marek or Krzysztof, maybe you could try this test with this patch yet?
This could tell us the name of a timer function running during this panic. Thanks!
Created attachment 14239 [details]
Print in panic plus verify timer function address
Marek and Krzysztof! I wish you great New Year's Party!
(But, if there were any problems ...here is a bit completed testing patch!)
Cheers, Jarek P.
Closing out old stale bugs |