Hi all,
Bug 470225 crashes systems with Intel 3945/4965/5300 wireless cards on busy networks. The kernel warning generated is currently the #1 most-reported item at kerneloops (www.kerneloops.org -- several k reports mostly from FC10 machines)
Intel has produced a patch, and John Linville has applied this to the 2.6.28 kernel (available from koji), but it now sounds like 2.6.28 might not make it out soon, or ever. Can this fix be applied to the 2.6.27 branch?
Thanks much! Tom
References: https://bugzilla.redhat.com/show_bug.cgi?id=470225 (Bug at Redhat) http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1822 (Bug at Intel) http://kerneloops.org/searchweek.php?search=rs_get_rate (Counts of warnings reported to kerneloops)
On Tue, 27 Jan 2009 17:05:27 -0800, Tom Davidson tjd@mit.edu wrote:
Intel has produced a patch, and John Linville has applied this to the 2.6.28 kernel (available from koji), but it now sounds like 2.6.28 might not make it out soon, or ever. Can this fix be applied to the 2.6.27 branch?
Maybe the -stable team will pick it, so we'd get it automatically?
-- Pete
Pete Zaitcev (zaitcev@redhat.com) said:
Intel has produced a patch, and John Linville has applied this to the 2.6.28 kernel (available from koji), but it now sounds like 2.6.28 might not make it out soon, or ever. Can this fix be applied to the 2.6.27 branch?
Maybe the -stable team will pick it, so we'd get it automatically?
We should still add it in the meantime (there are other dups in bugzilla, such as #480701) - it's very common hardware, and at least when I was seeing it I was repeatedly getting hard panics requiring reboot within 1-2 minutes of the wireless interface being enabled.
Bill
On Wed, Jan 28, 2009 at 10:20:03AM -0500, Bill Nottingham wrote:
Pete Zaitcev (zaitcev@redhat.com) said:
Intel has produced a patch, and John Linville has applied this to the 2.6.28 kernel (available from koji), but it now sounds like 2.6.28 might not make it out soon, or ever. Can this fix be applied to the 2.6.27 branch?
Maybe the -stable team will pick it, so we'd get it automatically?
We should still add it in the meantime (there are other dups in bugzilla, such as #480701) - it's very common hardware, and at least when I was seeing it I was repeatedly getting hard panics requiring reboot within 1-2 minutes of the wireless interface being enabled.
IIRC, it will take some porting for 2.6.27. Is there an F-10-2_6_27 fork somewhere?
John
On Wed, Jan 28, 2009 at 10:30:27AM -0500, John W. Linville wrote:
On Wed, Jan 28, 2009 at 10:20:03AM -0500, Bill Nottingham wrote:
Pete Zaitcev (zaitcev@redhat.com) said:
Intel has produced a patch, and John Linville has applied this to the 2.6.28 kernel (available from koji), but it now sounds like 2.6.28 might not make it out soon, or ever. Can this fix be applied to the 2.6.27 branch?
Maybe the -stable team will pick it, so we'd get it automatically?
We should still add it in the meantime (there are other dups in bugzilla, such as #480701) - it's very common hardware, and at least when I was seeing it I was repeatedly getting hard panics requiring reboot within 1-2 minutes of the wireless interface being enabled.
IIRC, it will take some porting for 2.6.27. Is there an F-10-2_6_27 fork somewhere?
I started this last night, so I could submit it to stable...
The F10 2.6.27 branch is private-fedora-10-2_6_27.
cheers, Kyle
On Wed, Jan 28, 2009 at 12:53:12PM -0500, Kyle McMartin wrote:
I started this last night, so I could submit it to stable...
Forgot to mention this here:
Alas, Kyle's patched kernel does not fix the problem--I continue to get oopses and hard panics. Also, the problem is fixed by an unpatched build of 2.6.28 (2.6.28-3.fc10.i686). A closer read of the comments at the original bug reveals that no one was actually testing just the patch.
So while this remains a serious crasher, it's no longer just a packaging request. I'll retreat back to bugzilla until there is a better idea of the fix. Thanks very much to Kyle for producing a test kernel so quickly, and sorry for the wild goose chase.
If anyone has additional debugging tips/requests, please share them, as I have access to a network here that reliably triggers the issue. -Tom
On Wed, Jan 28, 2009 at 6:23 PM, Kyle McMartin kyle@infradead.org wrote:
On Wed, Jan 28, 2009 at 12:53:12PM -0500, Kyle McMartin wrote:
I started this last night, so I could submit it to stable...
Forgot to mention this here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1089515
Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
kernel@lists.fedoraproject.org
-
Bill Nottingham -
John W. Linville -
Kyle McMartin -
Pete Zaitcev -
Tom Davidson