Skip to contentSkip to conversation

Weird: 30 sec delay during early boot

DISCUSSION Andi Kleen 2 participants 3 messages Jul 4, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#1 lore raw
Quoted 8 lines · Jeff Garzik

This appeared in -bk-latest in the past day or two.

BK-current on x86-64 (config/dmesg/lspci attached) will pause for 30 wall-clock seconds immediately after being loaded by the bootloader, then will proceed to boot successfully and function correctly. This is reproducible on every boot.

So, 30 seconds with no printk output, then boots normally.

Boot with earlyprintk=serial,ttySx,baud or earlyprintk=vga That should enable printk from the beginning and may give some clues.

-Andi

#2 lore raw
Quoted 10 lines · Andi Kleen
Quoted 7 lines · Jeff Garzik

This appeared in -bk-latest in the past day or two.

BK-current on x86-64 (config/dmesg/lspci attached) will pause for 30 wall-clock seconds immediately after being loaded by the bootloader, then will proceed to boot successfully and function correctly. This is reproducible on every boot.

Quoted 6 lines
Quoted 1 line

So, 30 seconds with no printk output, then boots normally.

Boot with earlyprintk=serial,ttySx,baud or earlyprintk=vga That should enable printk from the beginning and may give some clues.

would early printk show something that dmesg(8) would not?

Jeff

author
#3 lore raw
Quoted 1 line

would early printk show something that dmesg(8) would not?

Yes, it's real time and you can see where the delay occurs.

-Andi