| Summary: | ck-sources-2.6.21_p2 - Kernel Oops with with e1000 and Debug shared IRQ handlers | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Watson <daniel.watsonbros> |
| Component: | [OLD] Core system | Assignee: | Micheal Marineau (RETIRED) <marineam> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | critical | CC: | kernel, pacho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://www.ussg.iu.edu/hypermail/linux/kernel/0702.1/2931.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Daniel Watson
2007-06-28 00:23:57 UTC
Does this still happen with the same config on either gentoo-sources or vanilla-sources or only with ck? (In reply to comment #1) > Does this still happen with the same config on either gentoo-sources or > vanilla-sources or only with ck? > Yes, this same config worked fine on gentoo-sources I forgot to add that when I disable 'Debug shared IRQ handlers' in the kernel, it works fantastic. Actually, I turned off all kernel debugging. The reason I believe it's narrowed down to 'Debug shared IRQ handlers' is because of this: http://www.ussg.iu.edu/hypermail/linux/kernel/0702.1/2931.html Don't ask me why I even had kernel debugging on. It's just an option I have always had on in the kernel. (In reply to comment #2) > (In reply to comment #1) > > Does this still happen with the same config on either gentoo-sources or > > vanilla-sources or only with ck? > > > > Yes, this same config worked fine on gentoo-sources > > I forgot to add that when I disable 'Debug shared IRQ handlers' in the kernel, > it works fantastic. Actually, I turned off all kernel debugging. The reason I > believe it's narrowed down to 'Debug shared IRQ handlers' is because of this: > http://www.ussg.iu.edu/hypermail/linux/kernel/0702.1/2931.html > > Don't ask me why I even had kernel debugging on. It's just an option I have > always had on in the kernel. > Ok, just to see if you are hitting the same bug you could try the patch that is proposed in that thread: http://www.ussg.iu.edu/hypermail/linux/kernel/0702.1/3023.html The patch was applied and reverted because the fix broke MSI, but I don't know for sure if an alternative fix was ever put in. http://www.ussg.iu.edu/hypermail/linux/kernel/0702.1/3023.html It may be related to this patch which is included in the latest gentoo sources but not ck-sources which would explain why gentoo-sources worked: http://lkml.org/lkml/2007/6/8/89 I bumped ck-sources to _p2-r1 to include genpatches-4 which has that patch so give that a try first once it hits the portage tree in an hour or so. If that doesn't fix it try the patch I suggested above, if it does we are good to go :-) (In reply to comment #3) > I bumped ck-sources to _p2-r1 to include genpatches-4 which has that patch so > give that a try first once it hits the portage tree in an hour or so. If that > doesn't fix it try the patch I suggested above, if it does we are good to go > :-) > Okay, I will sync in an hour and try it again and post the results. I have some questions for you: Should a novice even have kernel debugging on? Does it have any noticeable negative effects on the performance of the system? ck-sources were dropped from portage, maybe this bug should be closed Oops, yeah, didn't clear this out. Closing. |
