Kernel 2.6.12 and 2.6.13 hangs for a while on boot
Hi all,
I'm having little hangs while booting with kernels 2.6.12 and 2.6.13-rc1, rc2 and rc3.
It is strange that 2.6.12-rc1 booted ok without hangs.
I saw a post of Alan Cox on rc-1 release notes:
"Old ISA/VESA systems sometimes put tertiary IDE controllers at addresses
0x1e8, 0x168, 0x1e0 or 0x160. Linux thus probes these addresses on x86 systems. Unfortunately some PCI systems now use these addresses for other purposes which leads to users seeing minute plus hangs during boot or even crashes."
I thought this could be my problem, but it still hangs on boot.
Hangs appears just before mounting filesystems message and before configuring system to use udev.
I'm using Gentoo with vanilla-sources. I already asked on gentoo lists and nobody saw this behaviour. I tried google with no luck too. So my last resource which could give me some light is here.
I'm using 2.6.13 on a Gateway laptop.
Do you know of something about this? Have you seen this problem? Where could I look for more information about that in my system? I saw logs but they don't say anything. Also, besides this hangs on boot, system seems to work perfectly, but I'd like to remove this hangs from boot.
For while, I'm using 2.6.11.10 which is working ok.
Thanks in advance.
--
Regards,
Francisco Figueiredo Jr.
_______________________________________________________
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/
Quoted 14 lines · Francisco Figueiredo Jr.
I'm having little hangs while booting with kernels 2.6.12 and 2.6.13-rc1, rc2
and rc3.It is strange that 2.6.12-rc1 booted ok without hangs.
I saw a post of Alan Cox on rc-1 release notes:
"Old ISA/VESA systems sometimes put tertiary IDE controllers at addresses
0x1e8,0x168,0x1e0or0x160. Linux thus probes these addresses on x86 systems. Unfortunately some PCI systems now use these addresses for other purposes which leads to users seeing minute plus hangs during boot or even crashes."
Quoted 4 lines
I thought this could be my problem, but it still hangs on boot.
Hangs appears just before mounting filesystems message and before configuring system to use udev.
Are these hangs temporary or permanent? If they are temporary (ie: the kernel recovers OK) then we should call them "stalls". Because a "hang" is considered to be a permanent state.
Either way, we need to know where the kernel is stuck. Adding `initcall_debug' to your kernel boot command may help.
And when the hang/stall occurs, hit the ALT-SSQRQ-P and ALT-SYSRQ-T key combinations and send us the resulting traces.
Thanks.