Bug 6351

Wim, please attach any system log files. They may give us an idea around where the problem is occurring. 
Please include X11 logs too.

CC: (none) => as9902613

I've seen this too. It appears to be X-related, as I've seen it happen mid-screen-refresh (fglrx driver).  It is *very* intermittent, say once every few days, and doesn't appear to be related to any app or activity.

I've just gotten back from a 3-week trip, and was going to test with current cauldron before reporting it.

CC: (none) => ftg

This has happened to me as well in gnome. I tried KDE last week for few days and I don't remember experiencing the total system lockup. I had a freeze this morning in gnome. I will append some log files.

CC: (none) => philippe.l

Created attachment 2547 [details]
Xorg Log file

Created attachment 2548 [details]
System messages

crash occured between 8 and 9am on July 10th

I see nothing in your logs, you need the .old for the xorg


Thanks for the bug report.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.
In general it is welcome to search for existing reports first to avoid filing duplicates.

The pattern I've noticed is that, for me, when it does occur, it almost always occurs when I am running thunderbird or firefox through ssh.

"Thanks for the bug report.
This particular issue has already been reported in our bug tracking system, but
please feel free to report any further bugs you find.
In general it is welcome to search for existing reports first to avoid filing
duplicates."

forget that, bad script

Created attachment 2555 [details]
Old Xorg log file

Initially I thought the problem might be caused by opera since it seemed to occur while using opera more often than not. But this morning I experienced another freeze and this time I was using epiphany only so the freezes aren't tied to a specific program. I will append the .old file. I'm not knowledgeable enough on the details of a Linux system, but what does it mean that the logger doesn't have time to commit error messages to the log files when the freeze occurs?

(In reply to comment #10)
> what does it mean that the logger
> doesn't have time to commit error messages to the log files when the freeze
> occurs?

Usually that the freeze occurs in the kernel, and the filesystem calls are not reponsive.  BTW in most of my cases, X wasn't responding to C-A-B and the kernel wasn't responding to any of the A-SYSRQ keys.

Yeah same for me. I can move the mouse around but that's it. I can't click anything and the system won't respond to any keystrokes.

Created attachment 2560 [details]
a text-file with a copy of all the log-files (except auth.log and syslog)

I added a text-file with a copy of all the log-files (except auth.log and sys.log). I shall add syslog separately.

Personally I don't think that it is a X-org problem, but a kernel problem. I experienced similar problems with Mandriva 2011 versions with a 3-kernel.

Created attachment 2561 [details]
syslog

The promised syslog-file

I wish to revise my previous comment. My system crashed again this morning. This time, I decided to wait a bit before doing the hard reset. After about 1min, the program I was using as well as the gnome panel crashed leaving me to a screen containing only the wallpaper. The mouse had disappeared. The kernel is looking more and more like the culprit. However, I only found one error message in /var/log/kernel/error.log which is unlikely to be the problem.

Jul 12 09:04:49 localhost kernel: [   34.951574] microcode: failed to load file amd-ucode/microcode_amd.bin

(In reply to comment #7)
> The pattern I've noticed is that, for me, when it does occur, it almost always
> occurs when I am running thunderbird or firefox through ssh.

Frank, I'm seeing an issue which *may* be related but probably not.
In Cauldron after a re-boot both Firefox and Thunderbird lock the system for about 2 minutes when first run. 2 or 3 cores hit 100% during this time after which the application opens correctly. Subsequent runs of either program during that session start instantly.
I have switched to the nightly build of Firefox (16a1) and the problem does not exist for FF but it still happens in TB. I don't want to move to Daily build of TB as I lose Lightning compatibility.
It's hard to get any feedback from the system as nothing responds except mouse and I can switch windows - also KDE system monitor keeps running, but top freezes. Memory useage during freeze is minimal. 

If none of this ties in with your experiences of this bug then I will open another.

CC: (none) => zen25000

No, I never see a problem after a reboot.  My scenario always occurs when the system's been up for a while and FF or TB have been running nicely.

Given the logs don't provide any information as to the origin of the crash, is there a way to run the kernel in some kind of debug mode which would allow it to crash a bit more gracefully to collect some data?

Good news everyone! (sorry for the futurama reference :) ) I enabled the testing repositories 2 days ago and performed the updates that were pending. Since then, my machine has been much more stable. I have not experienced the system freeze so far. I noticed that kernel 3.3.8 was included in the upgrade. Maybe this bug has been fixed in-kernel since 3.3.6? I'm running very new hardware (AMD E2-1800 APU) so it's possible my system isn't fully supported yet. But at least it's now stable as far as I can tell.

I spoke too soon. I've experienced 2 freezes today. I'm at a lost as to what is wrong. :(

I'm thinking this might be due to a graphics driver problem. I stumbled on this thread from Arch Linux forums and it seems to match the patterns I'm experiencing. 

https://bbs.archlinux.org/viewtopic.php?pid=1104299#p1104299

Unfortunately, I can't fallback on the open source driver as my setup is not yet supported.

I restarted experimenting some days ago.
I made a new fresh install of Mageia 2 x86_64 with all the updates until now, using the nouveau driver.
I reset my bios and changed settings a little bit at random and brought them back to the best setting (I suppose).
I worked with Mageia a lot of hours and I don't experience any freezing problems until now (o.k. once, when a javaapplet in firefox did not want to start, I had to stop firefox).
The gnomes ......?

Created attachment 2751 [details]
Xsession errors

I'm still experiencing this issue as of 09/04/2012. I've discovered that the .xession-errors is full of messages. I have no idea what they mean but I was wondering if someone in the know could tell if the errors might lead to a total system freeze. So I'm appending my .xession-errors.old.

This bug is happening a lot less frequently now. But it's not completely gone. I get a hard freeze every 2-3 days. It's probably a problem either with the current kernel (3.3 series) or the ATI proprietary driver. I went and tried cauldron for a while a couple of weeks before Mageia 3 alpha one was released, and I didn't experience the hard freeze as before. The kernel in cauldron at the time was 3.5.3 I believe which is supposed to have better support for AMD HD7000 series graphics (which is what I'm running HD7340). Also, the volatile nature of cauldron caused the proprietary driver to not work at the time when I was using it so I ended up using the free driver. 

Unfortunately, I was experiencing other debilitating issues on cauldron (random X restarts) which made it impossible to use day to day. I think this current bug is probably a hardware incompatibilty issue (at least in my case) and once cauldron has figured out the automated /usr/move migration and Gnome 3.6 Final is released, I'll update. It may not be possible to fix this bug for Mageia 2.

FWIW, I experienced similar issues around this period 2012-06 -09, but after a kernel and other updates, they ceased.
Since then I have moved to a newer computer, and not experienced any such problems.

CC: (none) => andre999mga

Same problem here on Mageia 3 with gnome and kde.

I also suspect the video card.  I have NVIDIA Quadro FX 880M.  It is not in the mageia list of supported nvidia video cards.
However, I can find a recent linux driver for my video card on the nvidia site at: http://www.nvidia.com/object/linux-display-amd64-319.32-driver.html.

I attempted installing the custom driver from the nvidia site.  All steps seemed successful.  But I could not see the newly added driver in the list of nvidia drivers and it looked like the used nvidia driver was another one from the Mageia distribution, suffering from the same freezing problem at about the same frequency.

For me, the freezing seems to have happened particularly when visiting the menu bar to open a new application, not sure whether 100% systematically the same scenario.

CC: (none) => gpmpublic

This bug is for Mageia 2 (where I don't have this issue).

Please add any comments relating to Mageia 3 on Bug 7048.

Summary: total freezing of the system => total freezing of the system with nvidia cards
Source RPM: (none) => x11-driver-video-nouveau

*** Bug 6693 has been marked as a duplicate of this bug. ***

CC: (none) => yves.brungard_mageia

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD