Summary: | sys-kernel/gentoo-sources-2.6.29.* skge module doesn't handle 64-bit interrupts | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Brian Beardall <brian> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=6212 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Brian Beardall
2009-05-15 19:53:06 UTC
Is gentoo-sources-2.6.29 the first kernel with this problem? If so, did you try to use the latest git-sources (sys-kernel/git-sources-2.6.30_rc6-r3) in order to reproduce it? I have not tried the latest git sources even though I have watched for changes in the interrupt code in the driver. There are a few changes in that respect and should test it. From googling I have learned that this is a bug in basically all previous kernels but has only begun to be noticed more lately because more users are installing 4 gig or more of ram. (In reply to comment #2) > From googling I have learned that this is a bug in > basically all previous kernels but has only begun to be noticed more lately > because more users are installing 4 gig or more of ram. > Could you post the sources that you mentioned? Also, are there any kernel.org bug reports/mailing list threads regarding this issue that we could monitor? http://lkml.org/lkml/2006/7/3/222 http://bugzilla.kernel.org/show_bug.cgi?id=6212 The claim is that it is the motherboards problem which might be true if ASUS didn't attach the ethernet device to the board to allow 64-bit interrupts or something dumb which I'd need datasheets from both Asus, and Marvell to really know why this isn't working. All other PCI devices are working with the 64-bit interrupts and I only discovered this bug after trying to fix a wireless access point. So this bug has been around forever. Upstream acknowledged bug with no resolution. Workaround identified: Forcing the iommu on is a reasonable workaround. |