linux-kernel - Re: today's linux-next fails to 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: <200807112306.39455.rjw@sisk.pl>
Date:	Fri, 11 Jul 2008 23:06:38 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Török Edwin <edwintorok@...il.com>,
	Takashi Iwai <tiwai@...e.de>, linux-next@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: today's linux-next fails to boot

On Friday, 11 of July 2008, Ingo Molnar wrote:
> 
> * Rafael J. Wysocki <rjw@...k.pl> wrote:
> 
> > On Friday, 11 of July 2008, Ingo Molnar wrote:
> > > 
> > > * Török Edwin <edwintorok@...il.com> wrote:
> > > 
> > > > On 2008-07-11 16:59, Ingo Molnar wrote:
> > > > > * Török Edwin <edwintorok@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/