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
signature.asc
Description: Digital signature
