mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: Serious e1000e driver issue on Intrepid
       [not found] <48D8EC11.9010700@canonical.com>
@ 2008-09-23 13:57 ` Daniel J Blueman
  2008-09-23 14:27   ` Rafael J. Wysocki
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel J Blueman @ 2008-09-23 13:57 UTC (permalink / raw)
  To: tim.gardner; +Cc: ubuntu-devel, Linux Kernel

Hi Tim,

[cross-posting to LKML]

On Tue, Sep 23, 2008 at 2:16 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
> Folks,
>
> There are beginning to be an increasing number of reports regarding a
> serious regression in Intrepid with regard to the e1000e ethernet driver
> wherein it can be rendered permanently inoperable. The original Bugzilla
> report is here:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=11382
>
> SuSE has also made an announcement regarding this issue:
>
> http://news.opensuse.org/2008/09/22/serious-e1000e-driver-issue-in-sle-11-beta-1-and-opensuse-111-beta-1
>
> Given the severity of this issue, I'm inclined to blacklist the driver
> by default in modutils until such time as Intel develops a fix.
>
> How do we inform users when their ethernet suddenly stops working after
> an update?

The 2.6.27-rc7 changelog shows this problem has been fixed for e1000:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.27-rc7

and this patch in the -mm series fixes it for e1000e:
http://marc.info/?l=linux-mm-commits&m=122038324200305&w=2

Clearly, we need to ensure the second patch makes it into 2.6.27
final; the corruption is reported to occur during suspend/resume
cycles.

Thanks,
  Daniel
-- 
Daniel J Blueman

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Serious e1000e driver issue on Intrepid
  2008-09-23 13:57 ` Serious e1000e driver issue on Intrepid Daniel J Blueman
@ 2008-09-23 14:27   ` Rafael J. Wysocki
  0 siblings, 0 replies; 2+ messages in thread
From: Rafael J. Wysocki @ 2008-09-23 14:27 UTC (permalink / raw)
  To: Daniel J Blueman; +Cc: tim.gardner, ubuntu-devel, Linux Kernel

On Tuesday, 23 of September 2008, Daniel J Blueman wrote:
> Hi Tim,
> 
> [cross-posting to LKML]
> 
> On Tue, Sep 23, 2008 at 2:16 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
> > Folks,
> >
> > There are beginning to be an increasing number of reports regarding a
> > serious regression in Intrepid with regard to the e1000e ethernet driver
> > wherein it can be rendered permanently inoperable. The original Bugzilla
> > report is here:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=11382
> >
> > SuSE has also made an announcement regarding this issue:
> >
> > http://news.opensuse.org/2008/09/22/serious-e1000e-driver-issue-in-sle-11-beta-1-and-opensuse-111-beta-1
> >
> > Given the severity of this issue, I'm inclined to blacklist the driver
> > by default in modutils until such time as Intel develops a fix.
> >
> > How do we inform users when their ethernet suddenly stops working after
> > an update?
> 
> The 2.6.27-rc7 changelog shows this problem has been fixed for e1000:
> http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.27-rc7
> 
> and this patch in the -mm series fixes it for e1000e:
> http://marc.info/?l=linux-mm-commits&m=122038324200305&w=2

Well, actually this patch is against e1000, not e1000e and it's been merged
already.  Apparently, a separate fix for e1000e is necessary.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-09-23 14:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <48D8EC11.9010700@canonical.com>
2008-09-23 13:57 ` Serious e1000e driver issue on Intrepid Daniel J Blueman
2008-09-23 14:27   ` Rafael J. Wysocki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®