MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18702.8817.634094.493649@cargo.ozlabs.ibm.com>
Date: Mon, 3 Nov 2008 08:58:09 +1100
From: Paul Mackerras <paulus@samba.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Kernel Testers List <kernel-testers@vger.kernel.org>,
       "Mel Gorman" <mel@csn.ul.ie>
Subject: Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot
In-Reply-To: <4xS1r6m15_B.A.2F.3ueDJB@chimera>
References: <Sl8SUNhCbfL.A.O5H.yueDJB@chimera>
	<4xS1r6m15_B.A.2F.3ueDJB@chimera>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 974
Lines: 24

Rafael J. Wysocki writes:

> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.26 and 2.6.27.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.26 and 2.6.27.  Please verify if it still should
> be listed and let me know (either way).

The commit that introduced the problem went into Linus' tree after
2.6.27, so it's not a regression from 2.6.26.  In other words, 2.6.27
doesn't have the problem.  It's a firmware bug in some old firmware
versions that got triggered by the kernel change, not a kernel bug per
se.

The commit has been reverted in Linus' tree now, so there isn't a
regression from 2.6.27 any more.

Paul.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/