Skip to contentSkip to conversation

Machine reboot

DISCUSSION Lukas Hejtmanek 4 participants 6 messages Oct 5, 2006 – Oct 9, 2006

lore
Share & tools
lore
#0 lore raw

Hello,

I'm facing troubles with machine restart. While sysrq-b restarts machine, reboot command does not. Using printk I found that kernel does not hang and issues reset properly but BIOS does not initiate boot sequence. Is there something I could do?

Signature · 1 line
Lukáš Hejtmánek
#1 lore raw
Quoted 7 lines · Lukas Hejtmanek

Hello,

I'm facing troubles with machine restart. While sysrq-b restarts machine, reboot command does not. Using printk I found that kernel does not hang and issues reset properly but BIOS does not initiate boot sequence. Is there something I could do?

You can try playing with different combinations of these options :

CONFIG_APM_ALLOW_INTS
CONFIG_APM_REAL_MODE_POWER_OFF

Signature · 3 lines
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
#2 lore raw
Quoted 10 lines · Jesper Juhl
Quoted 6 lines

I'm facing troubles with machine restart. While sysrq-b restarts machine, reboot
command does not. Using printk I found that kernel does not hang and issues reset properly but BIOS does not initiate boot sequence. Is there something I could do?

You can try playing with different combinations of these options :

CONFIG_APM_ALLOW_INTS
CONFIG_APM_REAL_MODE_POWER_OFF

I'm not using APM (as I think my board DP965LT does not support APM).

Also power off works OK (using halt cmd).

Signature · 1 line
Lukáš Hejtmánek
#3 lore raw
In reply to Lukas Hejtmanek
Quoted 6 lines · Lukas Hejtmanek

Hello,

I'm facing troubles with machine restart. While sysrq-b restarts machine, reboot command does not. Using printk I found that kernel does not hang and issues reset properly but BIOS does not initiate boot sequence. Is there something I could do?

A long shot, but switching to real mode does not work if the cpu is running in VMX root mode ie on hardware with Intel VT extensions enabled. So if you are using some kind of kernel virtualization module on rather new hardware, consider rmmod:ing the module before rebooting.

I'm about to post patches for kexec that fixes this problem, but I'm not sure about the current reboot status.

/ magnus

#4 lore raw
Quoted 8 lines · Magnus Damm

A long shot, but switching to real mode does not work if the cpu is running in VMX root mode ie on hardware with Intel VT extensions enabled. So if you are using some kind of kernel virtualization module on rather new hardware, consider rmmod:ing the module before rebooting.

I'm about to post patches for kexec that fixes this problem, but I'm not sure about the current reboot status.

You are right, I'm using Intel Core 2 Duo processor with DP965LT board that is capable of VT extensions. However, I'm using vanilla 2.6.18 kernel in X86_64, no additional patches, nor XEN or VMWARE is running (even their modules are not loaded). Moreover, SYSRQ-B (emergency reboot) works fine. System graceful reboot does not work.

Signature · 1 line
Lukáš Hejtmánek
#5 lore raw
Quoted 7 lines · Lukas Hejtmanek
Quoted 6 lines · Magnus Damm

A long shot, but switching to real mode does not work if the cpu is running in VMX root mode ie on hardware with Intel VT extensions enabled. So if you are using some kind of kernel virtualization module on rather new hardware, consider rmmod:ing the module before rebooting.

Quoted 8 lines
Quoted 2 lines

I'm about to post patches for kexec that fixes this problem, but I'm not sure about the current reboot status.

You are right, I'm using Intel Core 2 Duo processor with DP965LT board that is capable of VT extensions. However, I'm using vanilla 2.6.18 kernel in X86_64, no additional patches, nor XEN or VMWARE is running (even their modules are not loaded). Moreover, SYSRQ-B (emergency reboot) works fine. System graceful reboot does not work.

Of course... copy/paste pieces of sysrq-b sequence into regular sequence to find out what the critical difference is... no, it will not be easy.

Perhaps your box *likes* to reboot with apic on or something? Perhaps device_shutdown() breaks your ability to reboot?

Signature · 1 line
Thanks for all the (sleeping) penguins.