Bugzilla – Bug 141171
reboot needs adjusting kernel parameters
Last modified: 2006-01-11 10:13:31 UTC
Test was done on a Compaq nx8220 notebook with factory from 30th of December. The machine reboots only, if 'reboot=bios' is specified as a boot parameter.
Can you please provide the output of hwinfo of your machine? Thanks!
Created attachment 61855 [details] hwinfo of compaq nx8220 notebook
Pavel, can you please look into this? Thanks!
there was a discussion on lkml and a patch from Matthew Garrett to enable "reboot=b" after DMI-match on hp notebooks unconditionally. I'll try to find it in my archives.
http://thread.gmane.org/gmane.linux.kernel/352196 Warning: whitespace breakage From: Matthew Garrett <mjg59 <at> srcf.ucam.org> Subject: [PATCH] Reboot through the BIOS on newer HP laptops Newsgroups: gmane.linux.kernel Date: 2005-11-24 05:21:07 GMT (5 weeks, 5 days, 9 hours and 13 minutes ago) Newer HP laptops (nc4200, nc6xxx, nc8xxx) hang on reboot with a standard configuration. Passing reboot=b makes them work. This patch adds a DMI quirk that defaults them to this mode, and doesn't appear to have any adverse affects on older HPs. Signed-off-by: Matthew Garrett <mjg59 <at> srcf.ucam.org> --- a/arch/i386/kernel/reboot.c.orig 2005-09-20 18:54:50.000000000 +0100 +++ a/arch/i386/kernel/reboot.c 2005-09-20 18:58:11.000000000 +0100 <at> <at> -135,6 +135,14 <at> <at> DMI_MATCH(DMI_PRODUCT_NAME, "PowerEdge 2400"), }, }, + { /* HP laptops have weird reboot issues */ + .callback = set_bios_reboot, + .ident = "HP Laptop", + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"), + DMI_MATCH(DMI_PRODUCT_NAME, "HP Compaq"), + }, + }, { } }; -- Matthew Garrett | mjg59 <at> srcf.ucam.org i can confirm that this is needed on a compaq nc6230, too.
It looks like this patch is on its way to Linus' tree, so we can just wait :-).
It looks like this patch is on its way to Linus' tree, so we can just wait :-). It is in -mm tree already.
It is very well possible that CODE10 will be based on 2.6.15 which will nog get this patch. Also, additional exposure may further lower the (already very low, i admit) risk of breakage or at least may let us know sooner. So i vote for including this patch in the suse kernels asap. I am also using an affected machine ;-)
AFAICS decision was to track at least 2.6.16-rc1, and that should be enough to fix this.