Pete Zaitcev (zait...@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
On Wed, Jan 28, 2009 at 10:20:03AM -0500, Bill Nottingham wrote:
Pete Zaitcev (zait...@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
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 (zait...@redhat.com) said:
Intel has produced a patch, and John Linville has applied this to the
2.6.28
kernel (available from koji), but
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
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
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
On Tue, 27 Jan 2009 17:05:27 -0800, Tom Davidson t...@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?
