Trouble shooting a ten minute boot delay (SiI3112)
I added a PCI SATA controller to my computer. Immediately after grub loads the kernel there is a consistent ten minute delay before the kernel displays its first message. I tested Linux 2.6.8 and 2.6.11 both from Debian, and 2.6.11 from Knoppix, all of which experience the same delay.
The SATA controller is connected to two 200 GB Seagate SATA ST3200826AS drives. I managed to install Debian on the system, though the install was perilous, and once booted the system runs wonderfully! Any suggestions on how I can trouble shoot the ten minute boot delay? I don't reboot frequently, but it is irksome.
What's the appropriate mailing list for SATA questions, perhaps linux-ide or linux-scsi?
Please cc me in your reply. Thanks!
Shaun
$ uname -a Linux quince 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 GNU/Linux # lspci 0000:00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2) 0000:00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) 0000:00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) 0000:00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev b2) 0000:00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3) 0000:00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev c1) 0000:00:02.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) 0000:00:03.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) 0000:00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet Controller(rev c2) 0000:00:05.0 Multimedia audio controller: nVidia Corporation: Unknown device 01b0 (rev c2) 0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2) 0000:00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge (rev c2) 0000:00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3) 0000:00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge (rev b2) 0000:01:06.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10) 0000:01:07.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) 0000:01:08.0 Unknown mass storage controller: Silicon Image, Inc. (formerly CMDTechnology Inc) SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02) 0000:02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev01)
Quoted 12 lines · Shaun Jackman
I added a PCI SATA controller to my computer. Immediately after grub loads the kernel there is a consistent ten minute delay before the kernel displays its first message. I tested Linux 2.6.8 and 2.6.11 both from Debian, and 2.6.11 from Knoppix, all of which experience the same delay.
The SATA controller is connected to two 200 GB Seagate SATA ST3200826AS drives. I managed to install Debian on the system, though the install was perilous, and once booted the system runs wonderfully! Any suggestions on how I can trouble shoot the ten minute boot delay? I don't reboot frequently, but it is irksome.
Quoted 6 lines
What's the appropriate mailing list for SATA questions, perhaps linux-ide or linux-scsi?
Please cc me in your reply. Thanks!
Shaun
Hi, Shaun Jackman.
The list would be linux-ide but it doesn't really seem like a SATA
problem.
* What do you mean by the `first' message? ie. What's the first line
you read?
* Is it really ten minutes?
Signature · 1 line
tejun
2005/8/11, Tejun Heo <[email protected]>:
Quoted 10 lines
Quoted 5 lines · Shaun Jackman
I added a PCI SATA controller to my computer. Immediately after grub loads the kernel there is a consistent ten minute delay before the kernel displays its first message. I tested Linux 2.6.8 and 2.6.11 both from Debian, and 2.6.11 from Knoppix, all of which experience the same delay.
* What do you mean by the `first' message? ie. What's the first line
you read?
* Is it really ten minutes?
Hello, Tejun. Thanks for the reply.
The message displayed by the bootloader, grub, is... root (hd2,2)
Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/md0 ro nodma [Linux-bzImage, setup=0x1600, size=0x122a667] initrd /boot/initrd.img-2.6.11-1-1-k7 [Linux-initrd @ 0x1fb29000, 0x4c6000 bytes]
boot
At this point there is a nine minute, fifteen second delay. As soon as the kernel starts printing messages it goes by quite fast, so I can't be certain what it's printing, but the first message according to dmesg is...
Linux version 2.6.11-1-k7 (dannf@firetheft) (gcc version 3.3.6 (Debian 1:3.3.6-6 )) #1 Mon Jun 20 21:26:23 MDT 2005
BIOS-provided physical RAM map:
...
Cheers,
Shaun
Quoted 26 lines · Shaun Jackman
2005/8/11, Tejun Heo <[email protected]>:
Quoted 11 lines
Quoted 5 lines · Shaun Jackman
I added a PCI SATA controller to my computer. Immediately after grub loads the kernel there is a consistent ten minute delay before the kernel displays its first message. I tested Linux 2.6.8 and 2.6.11 both from Debian, and 2.6.11 from Knoppix, all of which experience the same delay.
* What do you mean by the `first' message? ie. What's the first line
you read?
* Is it really ten minutes?Hello, Tejun. Thanks for the reply.
The message displayed by the bootloader, grub, is... root (hd2,2)
Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.11-1-k7 root=/dev/md0 ro nodma [Linux-bzImage, setup=0x1600, size=0x122a667] initrd /boot/initrd.img-2.6.11-1-1-k7 [Linux-initrd @ 0x1fb29000, 0x4c6000 bytes]boot
Quoted 7 lines
At this point there is a nine minute, fifteen second delay. As soon as the kernel starts printing messages it goes by quite fast, so I can't be certain what it's printing, but the first message according to dmesg is...
Linux version 2.6.11-1-k7 (dannf@firetheft) (gcc version 3.3.6 (Debian 1:3.3.6-6 )) #1 Mon Jun 20 21:26:23 MDT 2005
BIOS-provided physical RAM map:
It's doing something BIOS-related at that point.
Try booting with 'edd=off' or disabling CONFIG_EDD.
Jeff
2005/8/12, Jeff Garzik <[email protected]>:
Quoted 11 lines
Quoted 7 lines
At this point there is a nine minute, fifteen second delay. As soon as the kernel starts printing messages it goes by quite fast, so I can't be certain what it's printing, but the first message according to dmesg is...
Linux version 2.6.11-1-k7 (dannf@firetheft) (gcc version 3.3.6 (Debian 1:3.3.6-6 )) #1 Mon Jun 20 21:26:23 MDT 2005
BIOS-provided physical RAM map:It's doing something BIOS-related at that point.
Try booting with 'edd=off' or disabling
CONFIG_EDD.
Thanks for the hint. I tried edd=off but sadly the boot delay persists. It looks as though edd was already disabled, as my .config contains CONFIG_EDD=m and the edd module is not loaded. If it helps troubleshooting I can post my .config here.
Cheers,
Shaun
Quoted 5 lines
Thanks for the hint. I tried edd=off but sadly the boot delay persists. It looks as though edd was already disabled, as my .config contains
CONFIG_EDD=mand the edd module is not loaded. If it helps troubleshooting I can post my .config here.
Maybe you can get something using EARLY_PRINTK and/or Sysrq+T?
Jan Engelhardt
2005/8/12, Jan Engelhardt <[email protected]>:
Quoted 6 lines
Quoted 4 lines
Thanks for the hint. I tried edd=off but sadly the boot delay persists. It looks as though edd was already disabled, as my .config contains
CONFIG_EDD=mand the edd module is not loaded. If it helps troubleshooting I can post my .config here.Maybe you can get something using
EARLY_PRINTKand/or Sysrq+T?
I tried earlyprintk=vga, but it didn't provide any extra information. Although, CONFIG_EARLY_PRINTK is disabled in my .config. Does it need to be set to CONFIG_EARLY_PRINTK=y for earlyprintk=vga to work?
I haven't tried Sysrq+T yet. I'll report back.
Cheers,
Shaun
Quoted 3 lines
I tried earlyprintk=vga, but it didn't provide any extra information. Although,
CONFIG_EARLY_PRINTKis disabled in my .config. Does it need to be set toCONFIG_EARLY_PRINTK=yfor earlyprintk=vga to work?
I think yes, otherwise there would not be a .config entry at all.
Quoted 1 line
I haven't tried Sysrq+T yet. I'll report back.
Mind that it is unlikely to get a good trace at this stage, but it's worth the try.
Jan Engelhardt
2005/8/12, Jan Engelhardt <[email protected]>:
Quoted 10 lines
Quoted 3 lines
I tried earlyprintk=vga, but it didn't provide any extra information. Although,
CONFIG_EARLY_PRINTKis disabled in my .config. Does it need to be set toCONFIG_EARLY_PRINTK=yfor earlyprintk=vga to work?I think yes, otherwise there would not be a .config entry at all.
Quoted 1 line
I haven't tried Sysrq+T yet. I'll report back.
Mind that it is unlikely to get a good trace at this stage, but it's worth the try.
I compiled a vanilla 2.6.12.4 kernel, enabled EARLY_PRINTK and rebooted with earlyprintk=vga. The kernel didn't display any extra information before the delay.
$ uname -a Linux quince 2.6.12.4 #1 Fri Aug 12 13:02:40 PDT 2005 i686 GNU/Linux $ cat /proc/cmdline root=/dev/md0 ro nodma earlyprintk=vga $ grep EARLY_PRINTK /boot/config-2.6.12.4 CONFIG_EARLY_PRINTK=y
I tried Alt-SysRq-T but there was no response. SYSRQ is enabled.
$ grep SYSRQ /boot/config-2.6.12.4 CONFIG_MAGIC_SYSRQ=y
Cheers,
Shaun
Quoted 11 lines · Shaun Jackman
2005/8/12, Jan Engelhardt <[email protected]>:
Quoted 10 lines
Quoted 3 lines
I tried earlyprintk=vga, but it didn't provide any extra information. Although,
CONFIG_EARLY_PRINTKis disabled in my .config. Does it need to be set toCONFIG_EARLY_PRINTK=yfor earlyprintk=vga to work?I think yes, otherwise there would not be a .config entry at all.
Quoted 1 line
I haven't tried Sysrq+T yet. I'll report back.
Mind that it is unlikely to get a good trace at this stage, but it's worth the try.
Is the keyboard ever set up then? This is all happening before console_init (since that's when the prints start) and the early printk won't show anything before it parses the options. For other architectures, I use to write out to the serial really early, just an 'x'. If you know how to do that, you could give it a try. Start at start_kernel in main hopefully you see the 'x'. If you do, keep moving it until you find where it's delaying. Of course, this could be before start_kernel, then you're really screwed, unless you're good at doing the same in assembly (which I've done for MIPS, PPC and ARM, but never for x86).
Quoted 4 lines
I compiled a vanilla 2.6.12.4 kernel, enabled
EARLY_PRINTKand rebooted with earlyprintk=vga. The kernel didn't display any extra information before the delay.
Do you see grub saying "uncompressing kernel..." or whatever that says?
-- Steve
2005/8/12, Steven Rostedt <[email protected]>:
Quoted 10 lines
Is the keyboard ever set up then? This is all happening before
console_init(since that's when the prints start) and the early printk won't show anything before it parses the options. For other architectures, I use to write out to the serial really early, just an 'x'. If you know how to do that, you could give it a try. Start atstart_kernelin main hopefully you see the 'x'. If you do, keep moving it until you find where it's delaying. Of course, this could be beforestart_kernel, then you're really screwed, unless you're good at doing the same in assembly (which I've done for MIPS, PPC and ARM, but never for x86).
Since each reboot takes ten minutes, this would be a tedious process. Thanks for the suggestion though.
Quoted 5 lines
Quoted 3 lines
I compiled a vanilla 2.6.12.4 kernel, enabled
EARLY_PRINTKand rebooted with earlyprintk=vga. The kernel didn't display any extra information before the delay.Do you see grub saying "uncompressing kernel..." or whatever that says?
Grub says...
root (hd2,2)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.12.4 root=/dev/md0 ro nodma
[Linux-bzImage, setup=0x1e00, size=0x1302ff]
I suspect this second message is where grub decompresses the kernel. The last message grub displays is simply...
boot
Cheers,
Shaun