From: "Rafael J. Wysocki" <rjw@sisk•pl>
To: Ingo Molnar <mingo@elte•hu>
Cc: "Stephen Rothwell" <sfr@canb•auug.org.au>,
"Török Edwin" <edwintorok@gmail•com>,
"Takashi Iwai" <tiwai@suse•de>,
linux-next@vger•kernel.org,
"Linux Kernel" <linux-kernel@vger•kernel.org>,
"Vegard Nossum" <vegard.nossum@gmail•com>
Subject: Re: today's linux-next fails to boot
Date: Fri, 11 Jul 2008 23:06:38 +0200 [thread overview]
Message-ID: <200807112306.39455.rjw@sisk.pl> (raw)
In-Reply-To: <20080711190749.GB21758@elte.hu>
On Friday, 11 of July 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk•pl> wrote:
>
> > On Friday, 11 of July 2008, Ingo Molnar wrote:
> > >
> > > * Török Edwin <edwintorok@gmail•com> wrote:
> > >
> > > > On 2008-07-11 16:59, Ingo Molnar wrote:
> > > > > * Török Edwin <edwintorok@gmail•com> wrote:
> > > > >
> > > > >
> > > > >>> [Added Ingo to Cc]
> > > > >>>
> > > > >>> I get the boot problem on i386 with 2008-07-11 linux-next tree, too.
> > > > >>> In my case, no error appears on the screen, just staying blank and
> > > > >>> dead. It seems stopping at the very beginning, soon after GRUB, so
> > > > >>> could be the same reason.
> > > > >>>
> > > > >>>
> > > > >> I don't see any boot messages on the screen, I get that BUG message as
> > > > >> soon as grub's menu dissapears.
> > > > >> I have bisected it to this range so far:
> > > > >> git-bisect good aa03060a78c1aec53075a0c8ca7be19cedfbea8f
> > > > >> git-bisect bad b1611c0058bc6635e7257e755c3f194933a7a6df
> > > > >>
> > > > >> Should I continue to bisect?
> > > > >>
> > > > >
> > > > > could you check latest tip/master, does it boot fine with the same
> > > > > config?
> > > >
> > > > tip/master boots fine.
> > >
> > > to update linux-next to the latest bits in -tip, you can perhaps do
> > > something like this:
> > >
> > > git-merge tip/auto-x86-next
> > > git-merge tip/auto-core-next
> > > git-merge tip/auto-cpus4096-next
> > > git-merge tip/auto-ftrace-next
> > > git-merge tip/auto-generic-ipi-next
> > > git-merge tip/auto-genirq-next
> > > git-merge tip/auto-latest
> > > git-merge tip/auto-safe-poison-pointers-next
> > > git-merge tip/auto-sched-next
> > > git-merge tip/auto-stackprotector-next
> > > git-merge tip/auto-timers-next
> > >
> > > but it's easily possible that the bug is in some other portion of
> > > linux-next.
> >
> > Hm, I haven't tested the linux-next from today myself yet, but I have
> > a related question. Namely, is there a way to get a log of commits
> > that have been added since the previous linux-next?
> >
> > That may help to find a guilty patch if the yesterday's linux-next
> > works.
>
> at least in -tip it works like this:
>
> git-shortlog tip-history-2008-07-10_09.58_Thu..
>
> or, a more practical format with commit IDs on the same line:
>
> git log --no-merges --pretty=format:"%h: %s" \
> tip-history-2008-07-10_09.58_Thu..
>
> you can restrict it to a given piece of code as well, say:
>
> git log --no-merges --pretty=format:"%h: %s" \
> tip-history-2008-07-10_09.58_Thu.. -- arch/x86/ include/asm-x86/
>
> this doesnt work in linux-next nearly as well, due to the Quilt imported
> trees. Every time a quilt queue is updated and reimported, there's a
> stream of repeat commits.
Thanks for the tips.
Well, it turns out that linux-next from today doesn't boot on my box too
(64-bit) and I don't see anything obviously suspicious. Bisection time.
Thanks,
Rafael
next prev parent reply other threads:[~2008-07-11 21:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 11:12 today's linux-next fails to boot Török Edwin
2008-07-11 13:03 ` Takashi Iwai
2008-07-11 13:13 ` Török Edwin
2008-07-11 13:59 ` Ingo Molnar
2008-07-11 14:48 ` Török Edwin
2008-07-11 14:53 ` Ingo Molnar
2008-07-11 15:10 ` Rafael J. Wysocki
2008-07-11 19:07 ` Ingo Molnar
2008-07-11 21:06 ` Rafael J. Wysocki [this message]
2008-07-12 0:50 ` Rafael J. Wysocki
2008-07-12 4:47 ` Ingo Molnar
2008-07-11 14:54 ` Vegard Nossum
2008-07-11 15:00 ` Vegard Nossum
2008-07-11 15:27 ` Török Edwin
2008-07-16 21:11 ` Thomas Meyer
2008-07-16 21:57 ` Frédéric Weisbecker
2008-07-11 13:04 ` Takashi Iwai
2008-07-11 13:36 ` Vegard Nossum
2008-07-15 2:11 ` Frédéric Weisbecker
2008-07-15 11:06 ` Takashi Iwai
2008-07-15 11:15 ` Bernhard Walle
2008-07-15 11:17 ` Bernhard Walle
2008-07-15 11:53 ` Takashi Iwai
2008-07-15 12:02 ` Bernhard Walle
[not found] ` <c62985530807150800l4f34a6a3m22d58d66316c1e09@mail.gmail.com>
2008-07-15 15:14 ` Bernhard Walle
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=200807112306.39455.rjw@sisk.pl \
--to=rjw@sisk$(echo .)pl \
--cc=edwintorok@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tiwai@suse$(echo .)de \
--cc=vegard.nossum@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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