From: Kai Ruhnau <kai@tragetaschen.dyndns.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Boot hang after io scheduler registration
Date: Sat, 27 Dec 2008 13:51:56 +0100 [thread overview]
Message-ID: <495624EC.4040907@tragetaschen.dyndns.org> (raw)
In-Reply-To: <20081226164827.48527739.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 27 Dec 2008 00:35:19 +0100 Kai Ruhnau <kai@tragetaschen.dyndns.org> wrote:
>
>
>> Hi,
>>
>> I have a somewhat weird hang problem when booting all recent kernel
>> versions including 2.6.28: When I boot my system and let grub start the
>> kernel after a 5 second timeout, the system will hang after registering
>> the io schedulers (see below). However, when I choose the default grub
>> entry manually by pressing ENTER in the menu, the kernel does not hang
>> and continues the normal booting process.
>>
>> Below, you can find the place of the hang and an excerpt of the messages
>> that follow on a normal boot as well as some system information.
>>
>> Thanks for your time on this problem.
>>
>> Best regards
>> Kai
>>
>>
[old dmesg]
> Please add `initcall_debug' to the kernel boot command line. That
> should tell us which initialisation function is getting stuck.
>
Sure:
[ 0.916827] initcall deadline_init+0x0/0x14 returned 0 after 93 usecs
[ 0.916932] calling cfq_init+0x0/0x9d @ 1
[ 0.917055] io scheduler cfq registered (default)
[ 0.917154] initcall cfq_init+0x0/0x9d returned 0 after 114 usecs
[ 0.917266] calling percpu_counter_startup+0x0/0x14 @ 1
[ 0.917369] initcall percpu_counter_startup+0x0/0x14 returned 0 after
1 usecs
[ 0.917480] calling pci_init+0x0/0x30 @ 1
Hang happens here.
Continuation when pressing ENTER in grub:
[ 1.022100] pci 0000:01:00.0: Boot video device
[ 1.025022] initcall pci_init+0x0/0x30 returned 0 after 104926 usecs
[ 1.025128] calling pci_proc_init+0x0/0x60 @ 1
[ 1.025279] initcall pci_proc_init+0x0/0x60 returned 0 after 49 usecs
[ 1.025385] calling pcie_portdrv_init+0x0/0x42 @ 1
[ 1.025553] pcieport-driver 0000:00:02.0: setting latency timer to 64
[ 1.025582] pcieport-driver 0000:00:02.0: found MSI capability
[ 1.025707] pcieport-driver 0000:00:02.0: irq 319 for MSI/MSI-X
[ 1.025716] pci_express 0000:00:02.0:pcie00: allocate port service
[ 1.025765] pci_express 0000:00:02.0:pcie03: allocate port service
[ 1.025845] pcieport-driver 0000:00:06.0: setting latency timer to 64
[ 1.025872] pcieport-driver 0000:00:06.0: found MSI capability
[ 1.025992] pcieport-driver 0000:00:06.0: irq 318 for MSI/MSI-X
[ 1.026003] pci_express 0000:00:06.0:pcie00: allocate port service
[ 1.026050] pci_express 0000:00:06.0:pcie03: allocate port service
Best regards
Kai
--
This signature is left as an exercise for the reader.
next prev parent reply other threads:[~2008-12-27 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 23:35 Kai Ruhnau
2008-12-27 0:48 ` Andrew Morton
2008-12-27 12:51 ` Kai Ruhnau [this message]
2009-08-26 3:43 Patrick
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=495624EC.4040907@tragetaschen.dyndns.org \
--to=kai@tragetaschen.dyndns.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®