Summary: | [2.6.29 regression] r8169 can't transmit after a while | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Manfred Knick <Manfred.Knick> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | linux-2.6.29-regression linux-2.6.30 | ||
Package list: | Runtime testing required: | --- |
Description
Manfred Knick
2009-06-20 06:56:58 UTC
Thanks for reporting your test results! Looks like there is a backport to 2.6.29.4 of the fix from 2.6.30 (which you tested): http://patchwork.kernel.org/patch/25515/ (In reply to comment #1) > Thanks for reporting your test results! It's my pleasure! > Looks like there is a backport to > 2.6.29.4 of the fix from 2.6.30 (which you tested): Please, be careful and note that just exchanging the provided r8160 module in 2.6.29 did *not* solve the problem, as reported in the cited Fedora bug; there must be another problem in the interaction of the patched r8169 module with the rest of the 2.6.29 kernel. At my place, only 2.6.30 (including the new r8169 patches) worked again. For production machines, I'm really grateful that Adrian Bunk nourishes 2.6.27 as a stable "long-term edition" again. Please try that patch anyway, as it does seem like a likely candidate. Please, note https://bugzilla.redhat.com/show_bug.cgi?id=460747#c99 ff. Fixed in 2.6.30. If you want to test the patch for possible backport to 2.6.29, please feel free to do so. |