From: Borislav Petkov <bp@suse.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable
Date: Wed, 3 Jun 2015 12:56:40 +0200 [thread overview]
Message-ID: <20150603105640.GA4706@pd.tnic> (raw)
In-Reply-To: <CAHp75VfJWj-qnK9bMWdmVha24fZn64QnrT25T-1h4LKk7XrMkA@mail.gmail.com>
On Tue, Jun 02, 2015 at 08:31:58PM +0300, Andy Shevchenko wrote:
> Ditto.
"Ditto" means it doesn't work booting a normal 32-bit kernel too?
> I have a totally empty screen (serial console). So, if you teach me
> how to gather that I could do it later on.
That'll be hard - you'd probably need a hardware debugger or something
special to get a RIP or other data that early... Or hack up some very
early console printing with BIOS methods and so on. hpa had something
like that somewhere AFAIR...
> I can send our defconfig and kexec command line for sure.
Yes please.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-06-03 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 14:56 Andy Shevchenko
2015-06-02 16:24 ` Borislav Petkov
2015-06-02 16:49 ` Andy Shevchenko
2015-06-02 17:00 ` Borislav Petkov
2015-06-02 17:31 ` Andy Shevchenko
2015-06-03 10:56 ` Borislav Petkov [this message]
2015-06-03 15:27 ` Andy Shevchenko
2015-06-03 17:49 ` Shevchenko, Andriy
2015-06-03 21:13 ` Borislav Petkov
2015-06-04 9:21 ` [PATCH] x86/microcode: Disable builtin microcode loading on 32-bit for now Borislav Petkov
2015-06-04 9:47 ` Shevchenko, Andriy
2015-06-02 16:46 ` [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable Andy Shevchenko
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=20150603105640.GA4706@pd.tnic \
--to=bp@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome