Boot hang after io scheduler registration

Boot hang after io scheduler registration

[Kai Ruhnau]

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

# dmesg
...
[    0.309379] io scheduler noop registered
[    0.309473] io scheduler anticipatory registered
[    0.309569] io scheduler deadline registered
[    0.309679] io scheduler cfq registered (default)

Hang happens here.

Continuation when pressing ENTER in grub:

[    0.414098] pci 0000:01:00.0: Boot video device
[    0.417068] pcieport-driver 0000:00:02.0: setting latency timer to 64
[    0.417097] pcieport-driver 0000:00:02.0: found MSI capability
[    0.417222] pcieport-driver 0000:00:02.0: irq 319 for MSI/MSI-X
[    0.417231] pci_express 0000:00:02.0:pcie00: allocate port service
[    0.417294] pci_express 0000:00:02.0:pcie03: allocate port service
[    0.417376] pcieport-driver 0000:00:06.0: setting latency timer to 64
[    0.417403] pcieport-driver 0000:00:06.0: found MSI capability
[    0.417523] pcieport-driver 0000:00:06.0: irq 318 for MSI/MSI-X
[    0.417532] pci_express 0000:00:06.0:pcie00: allocate port service
[    0.417580] pci_express 0000:00:06.0:pcie03: allocate port service
...

# lspci
00:00.0 Host bridge: ATI Technologies Inc Device 7930
00:02.0 PCI bridge: ATI Technologies Inc Device 7933
00:06.0 PCI bridge: ATI Technologies Inc Device 7936
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
00:14.0 SMBus: ATI Technologies Inc SB600 SMBus (rev 13)
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
00:14.2 Audio device: ATI Technologies Inc SB600 Azalia
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
00:14.4 PCI bridge: ATI Technologies Inc SB600 PCI to PCI Bridge
01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800
GTS] (rev a2)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E
Gigabit Ethernet Controller (rev 12)
03:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
IEEE-1394a-2000 Controller (PHY/Link)
# uname -a
Linux 2.6.28-gentoo #1 SMP PREEMPT Thu Dec 25 23:33:06 CET 2008 x86_64
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz GenuineIntel GNU/Linux

I read about some usb related problems when searched with google:

# lsusb
Bus 001 Device 005: ID 0bda:0111 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002
Bus 006 Device 002: ID 147a:e00d Formosa Industrial Computing, Inc.
Bus 006 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 002 Device 003: ID 046d:c51a Logitech, Inc.
Bus 002 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic
Keyboard 4000 V1.0
Bus 002 Device 001: ID 1d6b:0001

-- 
This signature is left as an exercise for the reader.

Re: Boot hang after io scheduler registration

[Andrew Morton]

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
> 
> # dmesg
> ...
> [    0.309379] io scheduler noop registered
> [    0.309473] io scheduler anticipatory registered
> [    0.309569] io scheduler deadline registered
> [    0.309679] io scheduler cfq registered (default)
> 
> Hang happens here.
> 
> Continuation when pressing ENTER in grub:
> 
> [    0.414098] pci 0000:01:00.0: Boot video device
> [    0.417068] pcieport-driver 0000:00:02.0: setting latency timer to 64
> [    0.417097] pcieport-driver 0000:00:02.0: found MSI capability
> [    0.417222] pcieport-driver 0000:00:02.0: irq 319 for MSI/MSI-X
> [    0.417231] pci_express 0000:00:02.0:pcie00: allocate port service
> [    0.417294] pci_express 0000:00:02.0:pcie03: allocate port service
> [    0.417376] pcieport-driver 0000:00:06.0: setting latency timer to 64
> [    0.417403] pcieport-driver 0000:00:06.0: found MSI capability
> [    0.417523] pcieport-driver 0000:00:06.0: irq 318 for MSI/MSI-X
> [    0.417532] pci_express 0000:00:06.0:pcie00: allocate port service
> [    0.417580] pci_express 0000:00:06.0:pcie03: allocate port service
> ...
> 

Please add `initcall_debug' to the kernel boot command line.  That
should tell us which initialisation function is getting stuck.

Re: Boot hang after io scheduler registration

[Kai Ruhnau]

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.

Boot hang after io scheduler registration

[Patrick]

http://lkml.indiana.edu/hypermail/linux/kernel/0812.3/00547.html

The above archived post mimics my problem exactly, unfortunately it
offers no solution. I have added initcall_debug to my boot string and
I have transcribed the output below.

I have an Intel Core 2 Quad Q6600 cpu on an Asus P5K SE (Intel P35
chipset) motherboard. I built a 64-bit kernel yesterday (08/24/09)
from the git source, it reports itself as 2.6.31-rc7.

Please note that if I boot with the noapic and nolapic options, the
system will boot normally, but the kernel will only report a single
cpu/core (cat /proc/cpuinfo, top, etc). The trouble happens with
ubuntu 9.04 kernel, the latest weekly gentoo live cd, and the current
arch linux core install cd.

calling  aes_init+0x0/0xc @ 1
initcall aes_init+0x0/0xc returned 0 after 61 usecs
calling  deflate_mod_init+0x0/0xc @ 1
initcall deflate_mod_init+0x0/0xc returned 0 after 224 usecs
calling  krng_mod_init+0x0/0xc @ 1
alg: No test for stdrng (krng)
initcall krng_mod_init+0x0/0xc returned 0 after 134 usecs
calling  proc_genhd_init+0x0/0x3f @ 1
initcall proc_genhd_init+0x0/0x3f returned 0 after 2 usecs
calling  noop_init+0x0/0x17 @ 1
io scheduler noop registered
initcall noop_init+0x0/0x17 returned 0 after 123 usecs
calling  as_init+0x0/0x17 @ 1
io scheduler anticipatory registered
initcall as_init+0x0/0x17 returned 0 after 116 usecs
calling  deadline_init+0x0/0x18 @ 1
io scheduler deadline registered (default)
initcall deadline_init+0x0/0x18 returned 0 after 118 usecs
calling  cfq_init+0x0/0xb0 @ 1
io scheduler cfq registered
initcall cfq_init+0x0/0xb0 returned 0 after 138 usecs
calling  percpu_counter_startup+0x0/0x2d @ 1
initcall percpu_counter_startup+0x0/0x2d returned 0 after 0 usecs
calling  pci_init+0x0/0x38 @ 1
_