[Bug 209131] New: the power cuts off immediately when hit the poweron button on enclosure
https://bugzilla.novell.com/show_bug.cgi?id=209131 Summary: the power cuts off immediately when hit the poweron button on enclosure Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: william.gen@gmail.com QAContact: qa@suse.de in KDE,when hit the poweron button on enclosure,the power cuts off immediately rather than shutting down LINUX system gentlely.that would damage the sysytem and data in openSUSE system. and,when click the 'logout'button in KDE then select 'shut down the computer' instead of hitting the poweron button on enclosure,all works fine until turnning off the power souce.the power souce can not be turn off,so the bootsplash is still on screen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #1 from william.gen@gmail.com 2006-09-29 19:34 MST ------- BTW,two methods metiomed above works fine in SLED10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kde-maintainers@suse.de |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #2 from william.gen@gmail.com 2006-10-09 18:32 MST ------- It is because acpi driver module such as ac.ko,button.ko can not be loaded. when manually loads button.ko using insmod command,it says 'no such device'. but on the same machine SLED 10 is OK -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #3 from dmueller@novell.com 2006-10-10 01:34 MST ------- did you install the kernel security update? I think at some point the kernel people will merge the 10.1 and the sles kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 dmueller@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |kernel-maintainers@forge.provo.novell.com Component|Basesystem |Kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |trenn@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #4 from trenn@novell.com 2006-10-10 05:52 MST ------- Comment #3: This is about OpenSuse 10.2 Alpha and has nothing to do with any security update, right? Maybe it's better to try again on the latest kernel, it's likely that such a bug is already fixed mainline. Can you try: ftp://ftp.suse.com/pub/projects/kernel/kotd/{i386,x86_64}/HEAD/kernel-default.rpm If this one works the bug is already fixed. If not, pls attach dmesg, acpidump and "uname -r" output. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |william.gen@gmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 william.gen@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|william.gen@gmail.com | ------- Comment #5 from william.gen@gmail.com 2006-10-11 20:31 MST ------- ok.I'll try then report -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #6 from william.gen@gmail.com 2006-10-13 05:18 MST ------- Created an attachment (id=101410) --> (https://bugzilla.novell.com/attachment.cgi?id=101410&action=view) acpidump -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #7 from william.gen@gmail.com 2006-10-13 05:19 MST ------- Created an attachment (id=101411) --> (https://bugzilla.novell.com/attachment.cgi?id=101411&action=view) dmesg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #8 from william.gen@gmail.com 2006-10-13 05:20 MST ------- Created an attachment (id=101412) --> (https://bugzilla.novell.com/attachment.cgi?id=101412&action=view) uname -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #9 from william.gen@gmail.com 2006-10-16 18:10 MST ------- Alpha 5 is also in the same trouble -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #10 from william.gen@gmail.com 2006-10-16 18:13 MST ------- Comment #4 :I installed the kernel package you metioned,the problem is same as orgional one -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ak@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |william.gen@gmail.com ------- Comment #11 from trenn@novell.com 2006-10-17 07:10 MST ------- Your machine got blacklisted and ACPI disabled. Not sure whether this is intended or accident. You should be able to get your system into old state by passing: acpi=force kernel boot param. To be sure, are you still able to boot the working SLED 10 system and check whether you have this string at beginning of dmesg: ACPI: Disabling ACPI support If not and if ACPI modules like battery, ac, thermal, whatever are loaded it's probably Andi's change to drivers/acpi/blacklist.c? If ACPI was also disabled on the old system, something is broken in APM or other code paths or whatever and we still have to search. Ah I already have an idea..., maybe it's the processor module that always gets loaded and hangs when shutting down and trying to uninstall ACPI stuff that does not exits. This would explain the not shutting down symptom and I have an easy patch for that, which was in 10.1 but never made it mainline... In any case it would be nice if you can still provide dmesg output of the working kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #12 from william.gen@gmail.com 2006-10-20 00:59 MST ------- yeah,I add acpi=force as kernel boot param,system shut down gentlely,but in KDE stray,kpowersave become gray then cannot be clicked problem in ALPHA 4 AND ALPHA 5 are same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 william.gen@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|william.gen@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com, seife@novell.com ------- Comment #13 from trenn@novell.com 2006-10-20 02:30 MST ------- You don't have a 10.1 or SLE 10 on this machine anymore to cmp dmesg whether it was also blacklisted there? Andi's change shouldn't have any functional change. It may be an APM issue. If you could send us dmesg from 10.1 or SLE 10 that would help. Holger could it be that because of powersave changes the APM events are not processed correctly any more and the shutdown/power key event is not caught or it's an APM kernel problem? Hmm, if William cannot provide dmesg of an old kernel, we should give an APM machine a test whether all still works as expected... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #14 from seife@novell.com 2006-10-20 04:41 MST ------- (In reply to comment #13)
Holger could it be that because of powersave changes the APM events are not processed correctly any more and the shutdown/power key event is not caught or it's an APM kernel problem?
APM has no power button event. If you have an APM kernel and hit the button, the machine switches off immediately. Working as designed. => resolved invalid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #15 from william.gen@gmail.com 2006-10-24 18:20 MST ------- Created an attachment (id=102512) --> (https://bugzilla.novell.com/attachment.cgi?id=102512&action=view) output of dmesg in SLED10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ak@novell.com ------- Comment #16 from trenn@novell.com 2006-10-27 08:29 MST ------- Ok, on this system ACPI was and still should be enabled. If i checked correctly, Andi's blacklisting patch came in after SLES10. I think I found a little functional change there: if: char *s = dmi_get_system_info(DMI_BIOS_DATE); returns NULL, a machine will now get blacklisted, but did not get blacklisted on SLE 10. Andi, should this in dmi_scan.c in drivers/firmware: if (!s) return -1; be if (!s) return 0; I can build William a test kernel to verify we that it's really that one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #17 from trenn@novell.com 2006-10-27 08:40 MST ------- William can you provide dmidecode output and attach it to this bug, this should read out the same info. There should be a line called: Release Date: that does not contain any date on your system? If this is the case I think we can be sure that this is the problem. Hmm, have you already checked for a BIOS update? Maybe newer BIOSes define a Release Date, they normally should ... and this one could even be closed as invalid. If it's really that and we should/have to change the return value as stated above, I like to have a comment from Andi before doing anything. Blacklisting code is dangereous thing to touch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ak@novell.com | ------- Comment #18 from ak@novell.com 2006-10-27 09:10 MST ------- When there is no year then the bios is either very old (predates DMI) or very broken. In both cases black listing ACPI is probably the right thing to do. Complain to your BIOS vendor or use acpi=force I would suggest an INVALID -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |william.gen@gmail.com ------- Comment #19 from trenn@novell.com 2006-10-27 09:15 MST ------- The same what I thought. William can you still provide dmidecode info, so that we can be sure I didn't come on the wrong track... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #20 from william.gen@gmail.com 2006-10-28 21:06 MST ------- dmidecode output in ALPHA 5: # dmidecode 2.8 # No SMBIOS nor DMI entry point found, sorry. dmidecode output in SLED 10: # dmidecode 2.7 # No SMBIOS nor DMI entry point found, sorry. the following is the output of hwinfo in SLED 10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 william.gen@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #21 from william.gen@gmail.com 2006-10-28 21:12 MST ------- Created an attachment (id=102947) --> (https://bugzilla.novell.com/attachment.cgi?id=102947&action=view) the output of hwinfo in SLED10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #22 from trenn@novell.com 2006-10-30 05:20 MST ------- William, first I like to thank you very much for the detailed information you provided. I agree with Andi that we should not modify the blacklisting code. I can add a message if no dmidecode info is available and that you should try to upgrade the BIOS and if this does not help try acpi=force. What you can still try, is to upgrade to the latest BIOS, it's likely that they fixed or added dmidecode information and your machine does not get blacklisted anymore. If not, you have to use acpi=force. If you add this boot parameter at installation time, it should statically be added to later installed kernels and you shouldn't see any problems any more. I let this bug open as a reminder to add the "Try acpi=force" message, but won't do it right now as this is not that critical. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #23 from william.gen@gmail.com 2006-10-30 23:29 MST ------- BUT,I have a question:why SLED10 works fine on my same PC machine? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #24 from trenn@novell.com 2006-10-31 04:55 MST ------- Old machines don't boot via ACPI. Therefore there is a check how old your machine is. If the BIOS release date is before year xy your machine will be booted as if you pass the parameter acpi=off. Your machine may be newer, but the BIOS misses dmi information. Dmi information exists since a long time and if it's missing we should better assume that the machine is too old for ACPI. The blacklisting code has been modified to be better reused in other parts. There also has been changed, that if dmi information is missing, the machine should be booted acpi=off instead of (SLE 10) try to boot it with ACPI enabled. This probably fixed a lot old machines which a) are that old that they do not have dmi info and b) need acpi=off for booting. Unfortunately your BIOS is broken in respect of missing dmi information. Sorry the change is correct, either use acpi=force in future or try to update to a BIOS that includes dmi information. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #25 from ak@novell.com 2006-10-31 06:48 MST ------- Hmm, actually SLED10 should have the same cut off code as 10.2. 10.0 did it differently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holgi@novell.com ------- Comment #26 from trenn@novell.com 2006-10-31 07:48 MST ------- Sorry I don't understand comment #25, this is about ACPI enabled or disabled? The blacklist_by_year() func in driver/acpi/blacklist.c changed from SLE10 to 10.2. This is from SLED 10 SP1 kernel: static int __init blacklist_by_year(void) { int year; char *s = dmi_get_system_info(DMI_BIOS_DATE); if (!s) return 0; Where a return value of 0 means not blacklisted(in case of no dmi info) and acpi gets enabled. This changed with the move of this code to (can't find it right now) dmi_scan.c or similar? There 1 is returned if no dmi info is found and acpi gets disabled. Possibly Holgi also suffers from that on his workstation at home(he's going to check for dmi info). If more people are affected we should consider to revert that(if these guys upgraded the BIOS and should still have a non-working system)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 ------- Comment #27 from holgi@novell.com 2006-11-10 11:53 MST ------- Created an attachment (id=104737) --> (https://bugzilla.novell.com/attachment.cgi?id=104737&action=view) dmidecode.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209131 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #28 from trenn@novell.com 2006-11-11 10:32 MST ------- Holger: tks, your dmidecode info looks fine, seems to be something else. I am going to close this one as won't fix. If there pop up too many reports we should consider changing behaviour. This is a BIOS bug, not exporting dmi info. acpi=force workarounds it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com