Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755296AbYGKOxm (ORCPT ); Fri, 11 Jul 2008 10:53:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751103AbYGKOxd (ORCPT ); Fri, 11 Jul 2008 10:53:33 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:40627 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750896AbYGKOxc (ORCPT ); Fri, 11 Jul 2008 10:53:32 -0400 Date: Fri, 11 Jul 2008 16:53:22 +0200 From: Ingo Molnar To: =?iso-8859-1?B?VPZy9ms=?= Edwin Cc: Takashi Iwai , linux-next@vger.kernel.org, Linux Kernel , Vegard Nossum Subject: Re: today's linux-next fails to boot Message-ID: <20080711145322.GA25698@elte.hu> References: <4877400B.1000400@gmail.com> <48775C69.6050107@gmail.com> <20080711135937.GA25004@elte.hu> <487772B6.4090100@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <487772B6.4090100@gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1695 Lines: 53 * T?r?k Edwin wrote: > On 2008-07-11 16:59, Ingo Molnar wrote: > > * T?r?k Edwin 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. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/