From: Thomas Gleixner <tglx@linutronix.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
x86@kernel.org, Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: Re: lapic-related boot crash in 4.15-rc1
Date: Wed, 10 Jan 2018 19:34:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801101931590.1919@nanos> (raw)
In-Reply-To: <alpine.LRH.2.21.1801101303350.11024@math.ut.ee>
On Wed, 10 Jan 2018, Meelis Roos wrote:
> On 3 of my test computers, boot hangs with 4.15 git kernels. So far I
> have traced it down to 4.14.0 being good and 4.15-rc1 being bad (bisect
> is slow because the computers are somwehat remote). Also because of
> trying to find when it started, I have not tries newer than rc5
> kernels.
>
> The hang happens after Performance Events feature table has been printed
> but before APIC initialization messages normally appear ("Enabling APIC
> mode: Flat. Using 0 I/O APICs" or something like that).
>
> It happens on at least 3 distinct computers:
> * AMD Athlon with AMD 750 chipset
> * P3 1 GHz with i815 chipset
> * P4 1.7 GHz with SiS chipset
>
> They all have have "lapic" parameter because they were telling me that
> lapic has been disabled by BIOS and I re-enabled it with the parameter
> to get apic timer interrupts. This worked up until 4.14.
>
> None of the computers have IO-APICs.
Oh. Then it possibly falls into Dou's realm.
Dou?
Thanks,
tglx
next prev parent reply other threads:[~2018-01-10 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 11:30 Meelis Roos
2018-01-10 11:52 ` Thomas Gleixner
2018-01-10 15:07 ` Meelis Roos
2018-01-10 15:10 ` Thomas Gleixner
2018-01-10 15:17 ` Meelis Roos
2018-01-15 15:22 ` Meelis Roos
2018-01-15 16:21 ` Thomas Gleixner
2018-01-16 5:37 ` Meelis Roos
2018-01-16 10:13 ` Thomas Gleixner
2018-01-16 5:42 ` Dou Liyang
2018-01-16 12:35 ` Meelis Roos
2018-01-16 15:04 ` Thomas Gleixner
2018-01-16 15:34 ` Meelis Roos
2018-01-10 18:34 ` Thomas Gleixner [this message]
2018-01-11 3:10 ` Dou Liyang
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=alpine.DEB.2.20.1801101931590.1919@nanos \
--to=tglx@linutronix.de \
--cc=douly.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mroos@linux.ee \
--cc=x86@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
all inboxes | Powered by JetHome®