public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux•vnet.ibm.com>
To: xinhui <xinhui.pan@linux•vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman•id.au>,
	linux-kernel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org
Cc: Andrzej Hajda <a.hajda@samsung•com>,
	Christophe Jaillet <christophe.jaillet@wanadoo•fr>,
	Nathan Fontenot <nfont@linux•vnet.ibm.com>,
	Hari Bathini <hbathini@linux•vnet.ibm.com>,
	Paul Mackerras <paulus@samba•org>,
	tglx@linutronix•de
Subject: Re: powerpc/nvram: Fix an incorrect partition merge
Date: Tue, 07 Jun 2016 15:24:16 +1000	[thread overview]
Message-ID: <87bn3dlgfz.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <57550AB2.8090500@linux.vnet.ibm.com>

xinhui <xinhui.pan@linux•vnet.ibm.com> writes:
>> Has it always been broken?
>>
>
> no. after nvram partition corruption hit, all nvram partitions will be
> erased and re-alloc after the second machine reboot.
> I don't know who does it but i guess it is the firmware. :)

It is. PAPR says we format NVRAM when it's corrupted. This is also true
for NVRAM for PowerNV (not just pseries guest).

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2016-06-07  5:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10  7:30 [PATCH] powerpc/nvram: Fix an incorrect partition merge xinhui
2015-12-11  5:42 ` xinhui
2016-06-03 11:47 ` Michael Ellerman
2016-06-06  5:31   ` xinhui
2016-06-07  5:24     ` Stewart Smith [this message]
2016-06-07 11:39     ` Michael Ellerman
2016-06-13  6:40       ` xinhui
2016-09-20 13:07 ` Michael Ellerman

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=87bn3dlgfz.fsf@linux.vnet.ibm.com \
    --to=stewart@linux$(echo .)vnet.ibm.com \
    --cc=a.hajda@samsung$(echo .)com \
    --cc=christophe.jaillet@wanadoo$(echo .)fr \
    --cc=hbathini@linux$(echo .)vnet.ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=nfont@linux$(echo .)vnet.ibm.com \
    --cc=paulus@samba$(echo .)org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=xinhui.pan@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox