https://bugzilla.novell.com/show_bug.cgi?id=408728
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=408728#c13
Thomas Renninger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |astarikovskiy@novell.com
--- Comment #13 from Thomas Renninger 2008-09-01 11:13:52 MDT ---
Some suggestions:
1)
Does reading ACPI information generally work:
cat /proc/acpi/{fan,thermal,ac,processor,battery}/*/*
2)
you might want to try increased ACPI IO debug info on the broken and the
working kernel:
#!/bin/bash
logger "start debug"
echo 0x400181F >/sys/module/acpi/parameters/debug_level;
cat /proc/acpi/{fan,thermal,ac,processor,battery}/*/*
echo 0x3 >/sys/module/acpi/parameters/debug_level;
logger "end debug"
(Please double check, written out of my mind, not copy and pasted)
(first command increased ACPI debug to):
ACPI_LV_ERROR
ACPI_LV_WARN
ACPI_LV_INIT
ACPI_LV_DEBUG_OBJECT
ACPI_LV_INFO
ACPI_LV_OPREGION
ACPI_LV_BFIELD
ACPI_LV_IO
then tries to poke on ACPI provided IO and then reduces debug again.
3)
You might want to try to compile a kernel yourself:
ftp.suse.com/pub/people/trenn/How_to_compile_a_SuSE_kernel.txt
Rafael suggested to try:
Does CONFIG_HIGHMEM4G vs CONFIG_HIGHMEM64G make any difference?
change this in .config before you compile.
Effort increases from 1-3, it's hard to debug this remotely...
Wait..., maybe first you should provide dmesg of -default and -pae kernel to
compare (or is that posted already on one of your bugs?).
--
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.