From: Pavel Machek <pavel@ucw.cz>
To: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
sfr@canb.auug.org.au, kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org
Subject: Re: -next20181010,1011 regression: thinkpad x60 (32 bit) dies during boot.
Date: Fri, 12 Oct 2018 14:35:12 +0200 [thread overview]
Message-ID: <20181012123512.GA5565@amd> (raw)
In-Reply-To: <20181012105254.GA114888@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
Hi!
> > > > 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?
>
> Does latest -tip fail too? If yes then I suspect bisection would be needed.
I already started bisect on -next (T40p is my test machine, so bisect
is not that bad).
The log so far is:
Pavel
# bad: [771b65e89c8a51d611b8049718693a4202e4f732] Add linux-next specific files for 20181011
# good: [7876320f88802b22d4e2daf7eb027dd14175a0f8] Linux 4.19-rc4
git bisect start '771b65e89c8a51d611b8049718693a4202e4f732' '7876320f88802b22d4e2daf7eb027dd14175a0f8'
# good: [43faff25da004eabce691268da34065b3690f5ca] Merge remote-tracking branch 'net-next/master'
git bisect good 43faff25da004eabce691268da34065b3690f5ca
# good: [3e2beb7db82a880319aa2f0dcafa820f3f5206d3] Merge remote-tracking branch 'spi/for-next'
git bisect good 3e2beb7db82a880319aa2f0dcafa820f3f5206d3
# bad: [74411e5fd30ae540491c4d6142af6ee6b2b22f09] Merge remote-tracking branch 'char-misc/char-misc-next'
git bisect bad 74411e5fd30ae540491c4d6142af6ee6b2b22f09
# bad: [c810d907775aa2aa753e836a122613fd2416b14d] Merge remote-tracking branch 'kvm/linux-next'
git bisect bad c810d907775aa2aa753e836a122613fd2416b14d
# good: [fac07d2ba7b2764e3002ff9bc7861742a84a2ef6] Merge branch 'perf/core'
git bisect good fac07d2ba7b2764e3002ff9bc7861742a84a2ef6
# bad: [d74865bd3996c7a6f3e8ce6e626c1fe474e39494] Merge branch 'x86/mm'
git bisect bad d74865bd3996c7a6f3e8ce6e626c1fe474e39494
# good: [dcd2d0cece1608b2be9184786c900807ec947076] Merge branch 'x86/asm'
git bisect good dcd2d0cece1608b2be9184786c900807ec947076
--
(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 --]
next prev parent reply other threads:[~2018-10-12 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 19:59 -next20181010 regression: thinkpad x60 (32 bit) dies during boot Pavel Machek
2018-10-10 20:03 ` Pavel Machek
2018-10-11 18:03 ` -next20181010,1011 " Pavel Machek
2018-10-11 20:09 ` Thomas Gleixner
2018-10-12 10:24 ` Pavel Machek
2018-10-12 10:52 ` Ingo Molnar
2018-10-12 12:35 ` Pavel Machek [this message]
2018-10-12 18:10 ` Avoid VLA in pgd_alloc kills boot on 32-bit machines was " Pavel Machek
2018-10-12 18:13 ` Borislav Petkov
2018-10-12 18:57 ` Pavel Machek
2018-10-12 18:22 ` Pavel Machek
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=20181012123512.GA5565@amd \
--to=pavel@ucw.cz \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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