[Bug 218377] New: acpi_cpufreq loaded on a celeron machine and prevent suspend
https://bugzilla.novell.com/show_bug.cgi?id=218377 Summary: acpi_cpufreq loaded on a celeron machine and prevent suspend Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: dkukawka@novell.com QAContact: qa@suse.de acpi_cpufreq is loaded here on a celeron machine, but shouldn't. I can also see this error message in dmesg: Stopping tasks: =======================================================================================================| Shrinking memory... done (34837 pages freed) pnp: Device 00:06 disabled. ACPI: PCI interrupt for device 0000:02:01.1 disabled ACPI: PCI interrupt for device 0000:02:01.0 disabled ACPI: PCI interrupt for device 0000:00:1f.5 disabled ACPI: PCI interrupt for device 0000:00:1d.7 disabled ACPI: PCI interrupt for device 0000:00:1d.2 disabled ACPI: PCI interrupt for device 0000:00:1d.1 disabled ACPI: PCI interrupt for device 0000:00:1d.0 disabled Class driver suspend failed for cpu0 Could not power down device �1�0�1�1� error -22 Some devices failed to power down, aborting suspend -- 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=218377 dkukawka@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=218377 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pavel@novell.com, venkatesh.pallipadi@intel.com Status|NEW |ASSIGNED ------- Comment #1 from trenn@novell.com 2006-11-06 08:32 MST ------- Why shouldn't it get loaded? Does cpufreq work and does /sys/devices/system/cpu/cpu0/cpufreq/* provide sane information? Can you provide /proc/cpuinfo and whole dmesg output, pls. Suspend works fine if acpi-cpufreq is not loaded? -- 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=218377 ------- Comment #2 from dkukawka@novell.com 2006-11-06 08:48 MST ------- It should not get loaded because this machine is a Celeron machine which not support CPUFreq! And sysfs does not provide any usefull info: honey:~ # l /sys/devices/system/cpu/cpu0/* -r-------- 1 root root 4096 6. Nov 16:44 /sys/devices/system/cpu/cpu0/crash_notes /sys/devices/system/cpu/cpu0/topology: insgesamt 0 drwxr-xr-x 2 root root 0 6. Nov 2006 ./ drwxr-xr-x 3 root root 0 6. Nov 16:44 ../ -r--r--r-- 1 root root 4096 6. Nov 16:44 core_id -r--r--r-- 1 root root 4096 6. Nov 16:44 core_siblings -r--r--r-- 1 root root 4096 6. Nov 16:44 physical_package_id -r--r--r-- 1 root root 4096 6. Nov 16:44 thread_siblings honey:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 9 model name : Intel(R) Celeron(R) M processor 1500MHz stepping : 5 cpu MHz : 1500.153 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 tm pbe up bogomips : 3002.16 And as you can see in the output from the suspend, the module generate strange output. And yes, you can suspend if the module is unloaded, but this fill the log with waste! -- 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=218377 ------- Comment #3 from seife@novell.com 2006-11-06 08:49 MST ------- Pavel, Thomas, the "Could not power down device"-gibberish looks scary. -- 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=218377 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com Severity|Critical |Normal ------- Comment #4 from pavel@novell.com 2006-11-08 12:44 MST ------- Yep, I've seen this before. cpufreq has some problems with name it registers :-(. -- 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=218377 ------- Comment #5 from trenn@novell.com 2006-11-13 08:31 MST ------- Created an attachment (id=104975) --> (https://bugzilla.novell.com/attachment.cgi?id=104975&action=view) Workaround to only load acpi-cpufreq on machines with acpi functions It really looks like acpi-cpufreq registers unconditionally as long as no other cpufreq driver already got loaded. IMO the main (design) problem is that sysdev_driver_register() does always return zero (success) in drivers/base/sys.c. -- 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=218377 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Status|ASSIGNED |NEEDINFO Info Provider| |aj@novell.com ------- Comment #6 from trenn@novell.com 2006-11-14 01:11 MST ------- It's quite late for 10.2, patch (revert CPUFREQ_STICKY flag) went mainline: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobd... waiting for approval from Andreas. -- 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=218377 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|aj@novell.com | ------- Comment #7 from aj@novell.com 2006-11-14 01:34 MST ------- Fine with me if the kernel team agrees. -- 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=218377 ------- Comment #8 from trenn@novell.com 2006-11-14 01:38 MST ------- Created an attachment (id=105059) --> (https://bugzilla.novell.com/attachment.cgi?id=105059&action=view) Another acpi-cpufreq fix that popped up on list which IMO should also be included -- 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=218377 ------- Comment #9 from trenn@novell.com 2006-11-14 02:46 MST ------- Forget the other one..., the validate duplicate steps code seems to be missing totally in 2.6.18... -- 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=218377 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #10 from trenn@novell.com 2006-11-14 05:40 MST ------- Patch that also went mailine stated in comment #6 is in. That one should help. -- 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=218377 dotsa@hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Minor Status|RESOLVED |VERIFIED OS/Version|Other |Linux Priority|P5 - None |P4 - Low Platform|Other |i586 Version|Beta 1 plus |Beta 2 ------- Comment #11 from dotsa@hotmail.com 2006-11-14 10:35 MST ------- Confirming the presence of this bug in OpenSuse 10.2 Beta 2. Also, I hope you don't mind me switching the status to Verified. "Resolved Fixed" gives a wrong impression that it IS Resolved Fixed. Since for Beta 2 this is still not fixed, it was hard to find this bugreport. # ls /sys/devices/system/cpu/cpu0/* /sys/devices/system/cpu/cpu0/crash_notes /sys/devices/system/cpu/cpu0/topology: core_id core_siblings physical_package_id thread_siblings # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Pentium III (Coppermine) stepping : 6 cpu MHz : 933.449 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up bogomips : 1868.77 -- 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=218377 ------- Comment #12 from dkukawka@novell.com 2006-11-14 12:03 MST ------- Sorry, but IMO it's the job of the reporter (or the QA) to verify and close the bug. If the bug is marked as fixed (and please take a look at the date) you don't need to config a bug for an old release as e.g. Beta2 -- 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=218377 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|VERIFIED |REOPENED Resolution|FIXED | ------- Comment #13 from seife@novell.com 2006-11-14 15:24 MST ------- of course the bug is not verified. There is not even a package released that contains the fix, so how can anybody verify it? ARGH! -- 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=218377 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dotsa@hotmail.com Severity|Minor |Major Status|REOPENED |RESOLVED Priority|P4 - Low |P5 - None Platform|i586 |x86 Resolution| |FIXED Fixed in Milestone|--- |RC 1 Version|Beta 2 |Beta 1 ------- Comment #14 from seife@novell.com 2006-11-14 15:27 MST ------- also, please don't mess with the priority and severity of a bug that's already fixed. -- 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=218377 ------- Comment #15 from trenn@novell.com 2006-11-15 00:24 MST ------- Hehe. But it would really be nice if someone could try the kernel of the day: ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/kernel-default.i586.rpm It should contain this change (rpm -qp --changelog kernel-default*.rpm): * Tue Nov 14 2006 - trenn@suse.de - patches.fixes/acpi_cpufreq_do_not_load_unconditionally.patch: Do not load acpi_cpufreq if there are on ACPI cpufreq funcs provided by BIOS (218377). I only tried my workaround patch, Venkatesh (tks a lot!) pointed me to and confirmed me that this one should fix the problem, but verification would even be better... you never know. -- 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=218377 ------- Comment #16 from bwalle@novell.com 2006-11-15 02:20 MST ------- I didn't test this KOTD yet, but I had the same problem, applied your patch to beta2 kernel sources and this resolved the problem. Celeron Mobile CPU. -- 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=218377 ------- Comment #17 from dkukawka@novell.com 2006-11-17 16:50 MST ------- *** Bug 222179 has been marked as a duplicate of this bug. *** -- 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=218377 ------- Comment #18 from dotsa@hotmail.com 2006-11-21 11:55 MST ------- I take it "Verified" does not mean "The bug is verified to be present" then? -- 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=218377 ------- Comment #19 from seife@novell.com 2006-11-21 13:03 MST ------- No, VERIFIED FIXED means that somebody actually verified that the fix is working. If you actually test the newer package and can verify that the original bug is fixed, set it to VERIFIED. Usually, the original reporter or QA does this (since you cannot be sure that you are hitting exactly the same bug, it is better if you just write "the fix works for me under circumstances foo, bar", then the developer can decide if you actually verified the bug) Hope that helps :-) -- 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=218377 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED -- 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=218377 ------- Comment #20 from dotsa@hotmail.com 2006-11-24 12:42 MST ------- Thx, Stefan for explanation and sorry for misunderstanding. You got yourself another suddenly slightly more intelligent OpenSuse user. :) -- 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