r8169 exits with error -22 since 2.6.33
in [Kernel]
|
From: David Dillow on 8 Apr 2010 21:20 On Fri, 2010-04-09 at 01:04 +0200, Rafael J. Wysocki wrote: > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15454 > Subject : r8169 exits with error -22 since 2.6.33 > Submitter : Conrad Kostecki <ConiKost(a)gmx.de> > Date : 2010-03-05 22:32 (35 days old) Francois attached a patch to the bugzilla entry that ignores the failure to enable MWI on the device. That may get the NIC up and running, but that area of the driver doesn't seem to have changed since 2.6.32, so perhaps this is just a canary -- I'm betting that the cache line size is not getting set properly, and it probably affects more than just this NIC. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Rafael J. Wysocki on 9 Apr 2010 15:50 On Friday 09 April 2010, David Dillow wrote: > On Fri, 2010-04-09 at 01:04 +0200, Rafael J. Wysocki wrote: > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15454 > > Subject : r8169 exits with error -22 since 2.6.33 > > Submitter : Conrad Kostecki <ConiKost(a)gmx.de> > > Date : 2010-03-05 22:32 (35 days old) > > Francois attached a patch to the bugzilla entry that ignores the failure > to enable MWI on the device. That may get the NIC up and running, but > that area of the driver doesn't seem to have changed since 2.6.32, so > perhaps this is just a canary -- I'm betting that the cache line size is > not getting set properly, and it probably affects more than just this > NIC. Thanks for the update. Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: [Bug #15376] regression (oops) with usb in 2.6.33-rc8 Next: contact us... |