linux-kernel - Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18702.8817.634094.493649@cargo.ozlabs.ibm.com>
Date:	Mon, 3 Nov 2008 08:58:09 +1100
From:	Paul Mackerras <paulus@...ba.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	"Mel Gorman" <mel@....ul.ie>
Subject: Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/