linux-kernel - Re: -next20181010,1011 regression: thinkpad x60 (32 bit) dies during boot.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1810112208200.1457@nanos.tec.linutronix.de>
Date:   Thu, 11 Oct 2018 22:09:48 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Pavel Machek <pavel@....cz>
cc:     kernel list <linux-kernel@...r.kernel.org>, mingo@...hat.com,
        bp@...en8.de, hpa@...or.com, x86@...nel.org
Subject: Re: -next20181010,1011 regression: thinkpad x60 (32 bit) dies during
 boot.

On Thu, 11 Oct 2018, Pavel Machek wrote:

> On Wed 2018-10-10 22:03:32, Pavel Machek wrote:
> > Hi!
> > 
> > > I updated to todays next... and boot crashes with
> > > 
> > > ..
> > > Call Trace:
> > > kick_ilb
> > > trigger_load_balance
> > > ? active_load..
> > > scheduler_tick
> > > update_process_times
> > > tick_nohz_handler
> > > 
> > > -next20181005 worked ok.
> 
> Problem is still there in today's next.

So what came in between -next20181005 and the first bad one? kernel/sched/*
being the first place to look at.

Thanks,

	tglx