LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Paul Mackerras <paulus@samba.org>
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 11:31:16 +0000 [thread overview]
Message-ID: <20081031113116.GA9872@csn.ul.ie> (raw)
In-Reply-To: <18698.59327.927555.732608@cargo.ozlabs.ibm.com>
On Fri, Oct 31, 2008 at 10:10:55PM +1100, Paul Mackerras wrote:
> Mel Gorman writes:
>
> > Yaboot in my case and I've heard it affected a DVD installation. I don't
> > know for sure if it affects netboot but as I think it's something the
> > kernel is doing, it probably doesn't matter how it gets loaded?
>
> What changed in that commit was the contents of a couple of structures
> that the firmware looks at to see what the kernel wants from
> firmware. Specifically the change was to say that the kernel (or
> really the zImage wrapper) would like the firmware to be based at the
> 32MB point (which is what AIX uses) rather than 12MB (which was the
> default on older machines).
>
> So, as I understand it, it's not anything the kernel is actively
> doing, it's how the firmware is reacting to what the kernel says it
> wants. And since we are requesting the same value as AIX (as far as I
> know) I'm really surprised it caused problems.
>
Same here, it sounds like an innocent change. While it is possible that AIX
could not work on this machine, it seems a bit unlikely.
> We can revert that commit, but I still need to solve the problem that
> the distros are facing, namely that their installer kernel + initramfs
> images are now bigger than 12MB and can't be loaded if the firmware is
> based at 12MB. That's why I really want to understand the problem in
> more detail.
>
> > It's been pointed out that it can be "fixed" by upgrading the firmware but
> > surely we can avoid breaking the machine in the first place?
>
> Have you upgraded the firmware on the machine you saw this problem on?
No. Luckily for us, it was scheduled to be upgraded but it got delayed
:). I've asked the guy to go somewhere else for a while so I should be able
to keep the machine in the state it's currently in.
> If not, would you be willing to run some tests for me?
>
Of course.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2008-10-31 11:31 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
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 [this message]
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=20081031113116.GA9872@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--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).