LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	benh@kernel.crashing.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected)
Date: Fri, 31 Oct 2008 07:52:02 +1100	[thread overview]
Message-ID: <18698.7794.500191.189515@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20081030142632.GA15645@csn.ul.ie>

Mel Gorman writes:

> On some ppc64 machines, NVRAM is being corrupted very early in boot (before
> console is initialised). The machine reboots and then fails to find yaboot
> printing the error "PReP-BOOT: Unable to load PRep image".  It's nowhere near
> as serious as the ftrace+e1000 problem as the machine is not bricked but it's
> fairly scary looking, the machine cannot boot and the fix is non-obvious. To
> "fix" the machine;
> 
> 1. Go to OpenFirmware prompt
> 2. type dev nvram
> 3. type wipe-nvram
> 
> The machine will reboot, reconstruct the NVRAM using some magic and yaboot
> work again allowing an older kernel to be used. I bisected the problem down
> to this commit.

Eek!

Which ppc64 machines has this been seen on, and how were they being
booted (netboot, yaboot, etc.)?

Is it just the Powerstations with their SLOF-based firmware, or is it
IBM pSeries machines as well?

Paul.

  reply	other threads:[~2008-10-30 20:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24  4:10 Linux 2.6.28-rc1 Linus Torvalds
2008-10-24  4:14 ` Roland Dreier
2008-10-24 18:08   ` Greg KH
2008-10-24 11:24 ` Alistair John Strachan
2008-10-24 11:45   ` Rafael J. Wysocki
2008-10-24 12:52     ` Alistair John Strachan
2008-10-24 13:13       ` Alexey Dobriyan
2008-10-24 14:56         ` git-clean [Was: Linux 2.6.28-rc1] Björn Steinbrink
2008-10-24 15:17       ` Linux 2.6.28-rc1 Linus Torvalds
2008-10-24 19:22         ` Sam Ravnborg
2008-10-24 22:31         ` David Miller
2008-10-24 22:51           ` Sam Ravnborg
2008-10-24 19:15   ` Sam Ravnborg
2008-10-24 23:44     ` Alistair John Strachan
2008-10-24 17:09 ` Matt Mackall
2008-10-24 17:54   ` Matt Mackall
2008-10-24 17:57     ` Randy Dunlap
2008-10-24 18:05       ` Fenghua Yu
2008-10-24 18:11         ` Matt Mackall
2008-10-24 22:28 ` nf_conntrack oopes on parisc/smp (was Re: Linux 2.6.28-rc1) Domenico Andreoli
2008-10-24 22:53 ` Linux 2.6.28-rc1 Tony Vroon
2008-10-24 23:01   ` Arjan van de Ven
2008-10-26 13:17     ` Tony Vroon
2008-10-30 14:26 ` 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected) Mel Gorman
2008-10-30 20:52   ` Paul Mackerras [this message]
2008-10-30 21:05     ` Josh Boyer
2008-10-30 21:35       ` Dave Kleikamp
2008-10-31 10:36     ` Mel Gorman
2008-10-31 11:10       ` Paul Mackerras
2008-10-31 11:31         ` Mel Gorman
2008-10-31 18:36         ` Mel Gorman
2008-10-31 11:18       ` Paul Mackerras
2008-10-31 11:31         ` Benjamin Herrenschmidt
2008-10-31 11:56           ` Paul Mackerras
2008-10-31 11:32         ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18698.7794.500191.189515@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mel@csn.ul.ie \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected)' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).