All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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 17:48:22 +0300	[thread overview]
Message-ID: <487772B6.4090100@gmail.com> (raw)
In-Reply-To: <20080711135937.GA25004@elte.hu>

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.

On 2008-07-11 16:36, Vegard Nossum wrote:
> One really simple way of getting some more info out of this is to take
> the EIP value (here c0181ca0) and run it through addr2line:
>
>     $ addr2line -e vmlinux -i c0181ca0

Thanks for the hint, I rebuilt a failing kernel, and this is what
addr2line says:

$ addr2line -e vmlinux -i c0181ca0

??:0
$ addr2line -e vmlinux -f c0181ca0
kmem_cache_alloc
??:0

Best regards,
--Edwin

  reply	other threads:[~2008-07-11 14:48 UTC|newest]

Thread overview: 29+ 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-12 15: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 [this message]
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
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 14:54           ` Vegard Nossum
2008-07-11 15:00           ` 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-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=487772B6.4090100@gmail.com \
    --to=edwintorok@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tiwai@suse.de \
    --cc=vegard.nossum@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.