From: Pavel Machek <pavel@ucw.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@redhat.com, hpa@zytor.com,
kernel list <linux-kernel@vger.kernel.org>,
sfr@canb.auug.org.au
Subject: Re: linux-next 20171018 to 20171108: reboot after 'freeing SMP alternatives memory'
Date: Fri, 10 Nov 2017 11:52:32 +0100 [thread overview]
Message-ID: <20171110105232.GA30677@amd> (raw)
In-Reply-To: <alpine.DEB.2.20.1711100003220.2690@nanos>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Fri 2017-11-10 00:04:07, Thomas Gleixner wrote:
> On Thu, 9 Nov 2017, Pavel Machek wrote:
> > Hi!
> >
> > > > Machine is thinkpad x60; 32-bit intel.
> > >
> > > On next-20171103: I get past kernel boot, but there's kernel panic
> > > (probably) while X is starting. (I can see the capslock led blinking.)
> > >
> > > Any ideas?
> >
> > With yesterday's git, it now hangs after "freeing SMP alternatives
> > memory".
> >
> > Does it work for anyone on 32-bit Intel?
>
> Yes, it does for me, but my test system is some arcane desktop box.
Ok, so I debugged some more, and it looks like I have two separate
problems:
1) Hang when the machine boots "hot". This has been there for long
long time, but the place of hang recently moved, which confused me.
2) next-20171103: I get past kernel boot, but there's kernel panic
(probably) while X is starting. (I can see the capslock led
blinking.). This still happens on next-20171110, if I boot the machine
"cold". This is new.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-11-10 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 11:42 linux-next 20171018: reboot after 'freeing SMP alternatives memory' Pavel Machek
2017-11-05 8:40 ` Pavel Machek
2017-11-09 11:47 ` linux-next 20171018 to 20171108: " Pavel Machek
2017-11-09 23:04 ` Thomas Gleixner
2017-11-10 10:52 ` Pavel Machek [this message]
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=20171110105232.GA30677@amd \
--to=pavel@ucw.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
--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 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).