Skip to contentSkip to conversation

2.6.25-rc1 on Sun Ultra 40

DISCUSSION Jasper Bryant-Greene 3 participants 5 messages Feb 13, 2008 – Mar 28, 2008

lore
Share & tools
lore
#0 lore raw

I have been attempting to test 2.6.25-rc1 on my Sun Ultra 40 (two dual-core Opteron 2222 CPUs).

There is some issue with the HPET clocksource which causes it to hang the boot process if enabled, which I will look into in due course (the HPET works fine on at least 2.6.19).

More pressing is that the system will not boot at all even with HPET disabled - kernel gets no further than "NET: Registered protocol family 2".

I cannot think of a way to find out what the problem is, because the system has only USB ports, and the USB keyboard is not working at this stage, either because the system has locked up hard, or because the USB support has not yet loaded (I tried both standard USB-HID and boot protocol keyboard support, both compiled in). Thus I cannot use magic-sysrq, or even scrollback to look at boot messages. There is also no serial port to assist with the latter...

Any thoughts on a procedure for debugging this would be much appreciated.

-j

#1 lore raw

I can confirm neither the boot hang with HPET enabled nor the other unexplained boot hang after "NET: Registered protocol family 2" occur on 2.6.24.2 on the same hardware. I still don't have an appropriate way to debug the issue on 2.6.25-rc1, though...

-j

Quoted 23 lines · Jasper Bryant-Greene

I have been attempting to test 2.6.25-rc1 on my Sun Ultra 40 (two dual-core Opteron 2222 CPUs).

There is some issue with the HPET clocksource which causes it to hang the boot process if enabled, which I will look into in due course (the HPET works fine on at least 2.6.19).

More pressing is that the system will not boot at all even with HPET disabled - kernel gets no further than "NET: Registered protocol family 2".

I cannot think of a way to find out what the problem is, because the system has only USB ports, and the USB keyboard is not working at this stage, either because the system has locked up hard, or because the USB support has not yet loaded (I tried both standard USB-HID and boot protocol keyboard support, both compiled in). Thus I cannot use magic-sysrq, or even scrollback to look at boot messages. There is also no serial port to assist with the latter...

Any thoughts on a procedure for debugging this would be much appreciated.

-j

#2 lore raw
Quoted 4 lines · Jasper Bryant-Greene

I can confirm neither the boot hang with HPET enabled nor the other unexplained boot hang after "NET: Registered protocol family 2" occur on 2.6.24.2 on the same hardware. I still don't have an appropriate way to debug the issue on 2.6.25-rc1, though...

boot message with debug in command line

also .config please

YH

#3 lore raw
Quoted 9 lines · Yinghai Lu
Quoted 4 lines · Jasper Bryant-Greene

I can confirm neither the boot hang with HPET enabled nor the other unexplained boot hang after "NET: Registered protocol family 2" occur on 2.6.24.2 on the same hardware. I still don't have an appropriate way to debug the issue on 2.6.25-rc1, though...

boot message with debug in command line

also .config please

Is there any new info on this ? Does the problem still exist with 25-rc7 ?

Thanks,
tglx

#4 lore raw
Quoted 8 lines · Thomas Gleixner
Quoted 6 lines · Yinghai Lu
Quoted 4 lines · Jasper Bryant-Greene

I can confirm neither the boot hang with HPET enabled nor the other unexplained boot hang after "NET: Registered protocol family 2" occur on 2.6.24.2 on the same hardware. I still don't have an appropriate way to debug the issue on 2.6.25-rc1, though...

Quoted 5 lines
Quoted 3 lines

boot message with debug in command line

also .config please

Is there any new info on this ? Does the problem still exist with 25-rc7 ?

No response yet.

YH