From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mackerras Subject: Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot Date: Mon, 3 Nov 2008 08:58:09 +1100 Message-ID: <18702.8817.634094.493649@cargo.ozlabs.ibm.com> References: <4xS1r6m15_B.A.2F.3ueDJB@chimera> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4xS1r6m15_B.A.2F.3ueDJB@chimera> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Mel Gorman 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.