From: Mike Galbraith <mgalbraith@suse.de>
To: Juergen Gross <jgross@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [x86-tip] RSDP changes converted i4790 box SMP -> UP
Date: Mon, 15 Jan 2018 16:08:50 +0100 [thread overview]
Message-ID: <1516028930.8238.87.camel@suse.de> (raw)
In-Reply-To: <2aeaae67-de23-423f-1233-fa0245bef575@suse.com>
On Mon, 2018-01-15 at 15:41 +0100, Juergen Gross wrote:
> On 12/01/18 09:01, Mike Galbraith wrote:
> > On Fri, 2018-01-12 at 07:40 +0100, Juergen Gross wrote:
> >> On 12/01/18 05:25, Mike Galbraith wrote:
> >>> Hi Juergen,
> >>>
> >>> Yesterday I wanted to test the RETPOLINE stuff in tip and tip-rt, but
> >>> discovered instead that my box had turned into a complete slug, not due
> >>> to incredible RETPOLINE overhead, rather because box had forgotten that
> >>> it had more than one CPU. I was going to leave it for the weekend, but
> >>> firing up gitk over morning java, I noticed the commits below, and sure
> >>> enough, that's what broke my box. Given other people's boxen work,
> >>> seems likely that the authors of the AMI BIOS in this box were a bit
> >>> more creative than usual.
> >>
> >> So I'm curious how this should be possible.
> >
> > Box is absolutely certain that it is.
> >
> >> Some questions:
> >>
> >> - which bootloader are you using?
> >
> > grub2, box is bog standard opensuse-42.3
>
> And this is the problem.
>
> grub2 of opensuse 42.3 is _wrong_.
>
> It copies the setup_header in the size it knows of (last fiels is
> handover_offset), fills in some stuff, and then copies back 1024 bytes.
> So grub2 of openSUSE 42.3 is _not_ ready to accept extensions of
> bootparams.
>
> This is a major breakage of the protocol, I think.
Oh joy, userspace b0rkage. Kernel b0rkage is a lot less annoying.
Hohum, I have zero problem with carrying a revert until grub2 gets
fixed up, but lord knows how many others out there may bisect, and
bless your mailbox with the fruit of their labors :)
-Mike
next prev parent reply other threads:[~2018-01-15 15:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1515675936.7350.15.camel@suse.de>
[not found] ` <20180111133723.d7x3sekanz5jhut2@gmail.com>
[not found] ` <1515682631.16805.3.camel@suse.de>
[not found] ` <20180111150331.7zzkd7awdxele54b@gmail.com>
[not found] ` <20180111151044.GC6176@hirez.programming.kicks-ass.net>
[not found] ` <1515694412.7054.10.camel@suse.de>
2018-01-12 4:25 ` [x86-tip] RSDP changes converted i4790 box SMP -> UP Mike Galbraith
2018-01-12 6:40 ` Juergen Gross
2018-01-12 8:01 ` Mike Galbraith
2018-01-12 11:17 ` Juergen Gross
2018-01-12 13:00 ` Mike Galbraith
2018-01-15 14:41 ` Juergen Gross
2018-01-15 15:08 ` Mike Galbraith [this message]
2018-01-12 12:23 ` Borislav Petkov
2018-01-12 13:11 ` Ingo Molnar
2018-01-15 14:52 ` Juergen Gross
2018-01-15 14:56 ` Borislav Petkov
2018-01-15 15:18 ` Juergen Gross
2018-01-15 15:32 ` Ingo Molnar
2018-01-15 15:40 ` Juergen Gross
2018-01-15 16:29 ` Gabriel C
2018-01-15 16:42 ` Juergen Gross
2018-01-15 16:56 ` Gabriel C
2018-01-15 17:04 ` Juergen Gross
2018-01-15 17:22 ` Gabriel C
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=1516028930.8238.87.camel@suse.de \
--to=mgalbraith@suse.de \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.