Subject : skbuff bug?
Submitter : "Yinghai Lu" <firstname.lastname@example.org>
Date : 2008-08-21 3:56
References : http://marc.info/?l=linux-kernel&m=121929102707658&w=4
This entry is being used for tracking a regression from 2.6.26. Please don't
close it until the problem is fixed in the mainline.
Reportedly caused by
Author: Bruce Allan <email@example.com>
Date: Fri Aug 8 18:36:11 2008 -0700
e1000e: test for unusable MSI support
Some systems do not like 82571/2 use of 16-bit MSI messages and some
other systems claim to support MSI, but neither really works. Setup a
test MSI handler to detect whether or not MSI is working properly, and
if not, fallback to legacy INTx interrupts.
Signed-off-by: Bruce Allan <firstname.lastname@example.org>
Signed-off-by: Jeff Kirsher <email@example.com>
Signed-off-by: Jeff Garzik <firstname.lastname@example.org>
On Fri, Aug 22, 2008 at 2:31 PM, <email@example.com> wrote:
> firstname.lastname@example.org changed:
> What |Removed |Added
> CC| |email@example.com
change msleep(50) to msleep(100) seems fix the problem.
On Tuesday, 26 of August 2008, Yinghai Lu <firstname.lastname@example.org> wrote:
> On Tue, Aug 26, 2008 at 3:17 AM, Jeff Kirsher
> <email@example.com> wrote:
> > On Tue, Aug 26, 2008 at 2:17 AM, Evgeniy Polyakov <firstname.lastname@example.org>
> >> Hi.
> >> On Thu, Aug 21, 2008 at 04:46:49PM -0700, Yinghai Lu
> (email@example.com) wrote:
> >>> it seems caused by
> >>> commit f8d59f7826aa73c5e7682fbed6db38020635d466
> >>> Author: Bruce Allan <firstname.lastname@example.org>
> >>> Date: Fri Aug 8 18:36:11 2008 -0700
> >>> e1000e: test for unusable MSI support
> >> Intel folks seems to be on vacations or whatever else without access to
> >> the mail. Can you confirm that bug still exists in the latest tree and
> >> reverting this commit fixes the problem?
> >> --
> >> Evgeniy Polyakov
> >> --
> > We are looking into the issue, I am sorry there has been no response until
> > I am still curious if you still see the issue with all the recent
> > changes. Please provide the device id you are using and system info
> > so that we can try and reproduce the issue, if the issue persists with
> > the latest git tree.
> can not duplicate any more...