[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0611021240300.25218@g5.osdl.org>
Date: Thu, 2 Nov 2006 12:54:02 -0800 (PST)
From: Linus Torvalds <torvalds@...l.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Adrian Bunk <bunk@...sta.de>, Andrew Morton <akpm@...l.org>,
LKML <linux-kernel@...r.kernel.org>,
Laurent Riffard <laurent.riffard@...e.fr>,
Rajesh Shah <rajesh.shah@...el.com>, toralf.foerster@....de,
Jeff Garzik <jeff@...zik.org>, Pavel Machek <pavel@....cz>,
Greg KH <greg@...ah.com>, Auke Kok <auke-jan.h.kok@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: 2.6.19-rc4: known unfixed regressions
On Thu, 2 Nov 2006, Rafael J. Wysocki wrote:
> Can we please add the following two to the list of known regressions:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=7082
Ok, I think I'll just revert it.
Decoding the PCI IO range is fine - even if a driver has detached, the
kernel knows where the PCI devices are, and won't re-use the range. So
while the patch that triggers the problem seems valid in itself, it's
probably not worth the pain to apply it at this point. So I think I'll
revert it - the rationale for the patch was fairly weak.
Greg, or would you prefer to do the honors?
> http://bugzilla.kernel.org/show_bug.cgi?id=7207
This one is apparently purely an e1000 driver problem. Can't help you with
that one. Although I find it suspicious that the "e1000_resume()" path
doesn't seem to be calling "e1000_power_up_phy()" before e1000_up().
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists