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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 12 Oct 2018 12:24:59 +0200
From:   Pavel Machek <pavel@....cz>
To:     Thomas Gleixner <tglx@...utronix.de>, sfr@...b.auug.org.au
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.

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.

kernel/sched does not seem to contain anything too scary.

I know that -next20181005 works ok, and I know -next20181010 is
bad. Is there easy way to bisect using that information? I can do
bisect between -next and mainline, but that's a lot of patches and
thus not much fun :-(.

In the meantime, I reproduced the failure with T40p. Is there someone
with working x86-32 in -next?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)