Re: [opensuse] openSUSE 11.0 on Dell Precision 490: Reboot problems

Hi, Larry Stotler wrote:

Are these dual processor(not just dual core)?

Those Dell Precision 490 with reboot problems are dual core: Model: 6.15.11 "Intel(R) Xeon(R) CPU 5140 @ 2.33GHz" Those without are quad core: Model: 15.6.4 "Intel(R) Xeon(TM) CPU 3.20GHz"

Actually, you shouldn't need a reboot. I've installed on a Core2 system and when it says it will reboot, kexec kicks in and restarts with the new kernel without rebooting. Only after a kernel update should a reboot be neccessary.

Unfortunately we need to do some reboots during the Autoyast init scripts (first because we need to change some local system users which UID/GID conflicts with users in LDAP, second after applying all patches and updated kernel)

...

Are there any known issues about this or does someone have have a clue? I didn't find something in the BIOS settings.

I had a problem with my Precision 610(Dual P3/Xeon 500) where it wouldn't turn off the machine. I ended up having to clear the CMOS, and then it worked afterwards.

ACPI should have corrected this, but it could be a bug.

Look here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/220820

If you add:

reboot=p

to the boot command, then it seems to reboot ok. This was for uBuntu 32bit tho. Are you doing 32 or 64bit?

I own several Precision machines. Not bad machines. Solid and reliable.

Thanks a lot! The 'reboot=b' parameter solved this issue. It means that reboot is done "by jumping through the BIOS" /usr/src/linux/Documentation/kernel-parameters.txt reboot= [BUGS=X86-32,BUGS=ARM,BUGS=IA-64] Rebooting mode Format: [,[,...]] See arch/*/kernel/reboot.c or arch/*/kernel/process.c /usr/src/linux/arch/x86/kernel/reboot.c /* reboot=b[ios] | s[mp] | t[riple] | k[bd] | e[fi] [, [w]arm | [c]old] warm Don't set the cold reboot flag cold Set the cold reboot flag bios Reboot by jumping through the BIOS (only for X86_32) smp Reboot by executing reset on BSP or other CPU (only for X86_32) triple Force a triple fault (init) kbd Use the keyboard controller. cold reset (default) acpi Use the RESET_REG in the FADT efi Use efi reset_system runtime service force Avoid anything that could hang. */ We need to install 32bit Linux on 64bit capable hardware because programmers are developing 32bit C/C++ code on these machines and can't/don't want to use cross compiling. The 64bit installation did not have such problem on these machines - neither did Suse 10.1 have. Best regards, Bernd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org