Latest working kernel version:2.6.24.x Earliest failing kernel version:2.6.26 Distribution:Mandriva Hardware Environment:mobo foxconn 975x7ab core 2 duo Software Environment:kde 4.2 Problem Description:system freeze on login Present system Mandriva 2009.1 beta. Problem currently only in kde. gnome 2.5.90 does not freeze, but on logout shows error "gnome-power-manager-desktop NOT RESPONDING". Shutdown and restart are normal. In kde 4.2 freeze can be prevented by booting with acpi=ht, or =off, or nolapic. Last working kernel version: 2.6.24.x (Mandriva 2007.1, kde 3.x) First problem kernel 2.6.26.x (Mandriva 2008.0, kde 3.5 or gnome) Problem went away with 2.6.26.x Mandriva 2008.1 kde 4.0, still good in Mandriva 2009.0 kde 4.1 BIOS has been upgraded (twice?). foxconn "support" have been unsupportive. Steps to reproduce:login to kde 4.2 (or kde 3.5?)
so the system can work well in console mode, right?
Created attachment 20280 [details] dmesg for crashed kde session.
Created attachment 20281 [details] output of dmidecode
Created attachment 20282 [details] output of lspci
Console seems to work OK. What commands could I enter in console to test acpi functions?
Reply from foxconn "support" to request for BIOS upgrade. "The 975X7AB-8ERKS does not need a BIOS fix to adjust for linux kernal bug." My BIOS version is dated Jan 2008. In Aug 2008 in response to a beating foxconn took on the ubuntu forum about a similar problem on another motherboard they created a test BIOS to fix. Might have been applicable if I could get it. <http://ubuntuforums.org/archive/index.php/t-877721.html>
> Problem went away with 2.6.26.x Mandriva 2008.1 kde 4.0, > still good in Mandriva 2009.0 kde 4.1 > Steps to reproduce:login to kde 4.2 (or kde 3.5?) sorry but I'm confused, you mean this only exists in kde 4.2 and 3.5, right? is the problem related with the kernel version? i.e. if kde 4.0 + 2.6.26.x works for you, can you verify if the problem can be reproduced with kde 4.2 + the same kernel? IMO, this is a KDE problem rather than a kernel bug.
See original report. At this moment - kde 4.2 freezes. gnome 2.5.90 shows an acpi problem. In the past - kde 3.5 and gnome (x) both showed system freeze. Only icewm worked at that time. Problem did not exist before Mandriva 2008 came out, kernel 2.6.26, kde 3.5. As I see it, an acpi feature implemented in linux a year and a bit ago but not called in kde 4.0 and 4.1 is reacting badly on this motherboard. kernel 2.6.28.4 is where I first saw the recurrence of this problem - i.e. the problem is reproduced this kernel. The problem has occurred before that with many kernel versions starting with 2.6.26.(0?) If it is a kde problem, then it is also a gnome problem I think. Can you think of any tests I could run?
Additional to comment #8. Note that booting with acpi=ht, or acpi=off, or nolapic prevent the system freeze. I think that this is the most relevant clue, and point to a problem at a more fundamental level than the desktop. I think that power management features introduced on the later desktops are using calls to acpi which are exposed as being problematic on my motherboard. Cheers
UPDATE I have been able to "fix" the system freeze problem in kde 4.2 by uninstalling the kde power manager "plasma-krunner-powerdevil". Further tests are required to determine if the problem is within powerdevil, or if powerdevil is calling an acpi function which is having a problem with my motherboard. I still think it is the latter, because booting with acpi=off is my other way of preventing the system freeze. Cheers
(In reply to comment #10) > UPDATE > > I have been able to "fix" the system freeze problem in kde 4.2 by > uninstalling > the kde power manager "plasma-krunner-powerdevil". > > Further tests are required to determine if the problem is within powerdevil, > or > if powerdevil is calling an acpi function which is having a problem with my > motherboard. I still think it is the latter, because booting with acpi=off is > my other way of preventing the system freeze. > hah, good catch. it seems that system freezes when kde invokes some ACPI functions. yeah, you're right that this seems to be an ACPI problem. I googled for "gnome-power-manager-desktop NOT RESPONDING", and it seems that this may be an EC regression. Alexey, can you confirm this?
For what it is worth - calling cpufreq-info and cpufreq-set from konsole does not generate any errors.
> ACPI Warning (tbutils-0242): Incorrect checksum in table [_HPT] - 1C, should > be 02 [20081204] maybe unrelated, maybe not... Please attach the output from acpidump
also, possibly unrelated.... > FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4) fcea94b (ACPI: fix FADT parsing) which added this warning, possibly in error...
what about the other ACPI drivers? can the bug be reproduced if CONFIG_ACPI_PROC_EVENT is cleared? if it's still reproducible, please try again with CONFIG_ACPI_PROCFS cleared.
ping Monty. :)
Created attachment 20418 [details] acpidump Format of dump OK? Do you want DSDT.asm? In reply to 15: System still freezes with "PowerDevil" installed if either or both of CONFIG_ACPI_PROC_EVENT, CONFIG_ACPI_PROCFS cleared. kernel-linus2.6.29-0.rc6.2mdv (vanilla kernel)
I thought the best approach is you could try ACPI functions manually at console, and see which one is broken. This could help a lot to narrow down the issue.
can you turn off the other optional CONFIG_ACPI_* options, eg. CONFIG_ACPI_BATTERY etc. to see if that helps?
Turning off CONFIG_ACPI_BATTERY does not help. Proceeding ...
Turned off (all at same time) CONFIG_ACPI_BATTERY CONFIG_ACPI_FAN CONFIG_ACPI_THERMAL No change - system still freezes. What else would PowerDevil call?
does the problem still exist if you boot with "idle=poll"?
re #22 Boot with idle=poll (config is at default values): System still freezes. At least now when it freezes the display is still live - i.e. the "swirling circle" "wait for it" around the cursor is in motion, but the mouse and keyboard are disabled, and no other signs of activity are seen. Was trying to browse forum with Firefox, which hung. Nothing in dmesg at crash. kde 4.2
could you please attach the /etc/X11/xorg.conf and /var/log/Xorg.0.log after X is started?
Created attachment 20495 [details] xorg.conf using nv driver while testing with kernel-linus. log to follow.
Created attachment 20496 [details] xorg.0.log log for crashed session. default config default boot parameters Did you want with idle=poll?
no, I have run out of my ideas about this issue. The problem still exists with CONFIG_ACPI_PROCFS cleared, and this suggests that the problem may be not caused by invoking ACPI driver functions. I knew a problem similar to this one , and it was fixed by updating the X. so my question would be does the problem still exists with the latest X driver? because this may be a driver issue which has already been fixed.
System in question is Mandriva 2009.1 (cooker) updated to rc1 with latest updates. X11-server-Xorg-1.6.0-2mdv2009.1 X11-driver-video-1.0.0-28mdv2009.1 X11-driver-nv-2.1.12-3mdv2009.1 X11-driver-nvidia-current-180.29-1mdv2009.1 I guess we will just have to watch and wait for developments. If this was a new issue here, I would have just ascribed it to a glitch in "cooker" software, but I have seen the problem in the past with "production" versions. I am content to run without PowerDevil. I just hope something new does not jump up to bite me. Cheers
please attach the dmesg output with boot option "nohpet" and see if the problem still exists.
Created attachment 20569 [details] dmesg for crashed kde session. As requested, booted with nohpet. PowerDevil installed. kde4.2 System froze as before on login. Can not see anything interesting in dmesg.
this is still a graphics problem to me as I've met a couple of similar problems before. And I got this in the Xorg.0.log you attached, "(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) " so let's fix this warning first and then see if the problem still exist, okay? please file a new bug report at: https://bugs.freedesktop.org/enter_bug.cgi And re-open this bug if the problem still exists after fixing the Xorg warnings. :)
Created attachment 20576 [details] latest xorg log Do not see that error message in the latest log, but freeze problem is still there. The errors I see now are: (WW) Warning, couldn't open module type1 (EE) Failed to load module "type1" (module does not exist, 0) (EE) Failed to load module "freetype" (module does not exist, 0) Do you still want me to open a new bug report?