Linux Mint crashes; GLiB Warning

[deadlytackler]

In my case, though it was happening earlier also however I suppose Gwibber caused it occurrence frequent. Just removed Gwibber. Let's see.
Still no official/moderator's response

[PRK]

Hi have this problem where Mint 9 LXDE crashes after as little as 10 minutes. The screen rapidly goes black, then strange vertical white bars over black background, followed by Glib-warning crash message in white text on black background plus about 5 more services listed as OK.

I do note that during booting I always get a Glib failure waring. The computer is an old Intel board, P4 2.4GHz upgraded with 2GB RAM. MInt 5, Mint 6, Mint 7 (all gnome) have all run fine. Since recently upgrading to Mint 9 LXDE the system has become realistically unusable. The installation is stock Mint 9 LXDE updated + Chrome added. I would like to continue to use Mint 9 LXDE runs & boots super fast but it seems too unstable with this problem along with the uncertainty of when the crash will occur.

[Tsunum]

Hi,

I've noticed a similar problem when I tried various flavor of Mint 9 with the LiveCD. It basically refused to boot. I tried both on my old Toshiba laptop and on my desktop (which is a 4 years old box). On the laptop, I managed to boot in Mint 9 Xfce and Fluxbox in compatible mode. I did not install as my current installations (Mint 7 Xfce on the laptop and Mint 8 on the desktop) work great.

As far as my research led me, this seems to be an upstream problem with Ubuntu and they haven't found a solution yet. It also appears to be restricted to older hardware.

Hopefully, this will be fixed soon.

[Sigea]

I notice that error pops up before my system even finishes booting; I'm not sure it's symptomatic to the problem, but a general class of problems that lead to the system becoming unusable and displaying the final console messages prior to the window manager/desktop rendering on startup...if that makes any sense.

Anyway, with my particular problem like this, my window manager/desktop craps out and it displays the infamous GLiB warning + a few other status messages, in between a blank screen with vertical white lines or stripes in the top half.

I looked through /var/log/syslog, found the approximate time of the crash, then grep'd that time across the whole directory...syslog & kern.log had the following entries:

Code: Select all

Sep 16 10:55:59 d710459 kernel: [ 1222.760017] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Sep 16 10:56:00 d710459 kernel: [ 1222.760033] render error detected, EIR: 0x00000000
Sep 16 10:56:00 d710459 kernel: [ 1222.760266] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78279 at 78275)
Sep 16 10:56:02 d710459 kernel: [ 1224.988013] [drm:i915_gem_idle] *ERROR* hardware wedged
Sep 16 10:56:04 d710459 kernel: [ 1227.038595] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
Sep 16 10:56:04 d710459 kernel: [ 1227.352010] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Sep 16 10:56:04 d710459 kernel: [ 1227.352020] render error detected, EIR: 0x00000000
Sep 16 10:56:04 d710459 kernel: [ 1227.352807] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78281 at 78275)
Sep 16 10:56:06 d710459 kernel: [ 1229.412015] [drm:i915_gem_idle] *ERROR* hardware wedged
Sep 16 10:56:15 d710459 kernel: [ 1238.360604] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
Sep 16 10:56:15 d710459 kernel: [ 1238.672011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Sep 16 10:56:15 d710459 kernel: [ 1238.672021] render error detected, EIR: 0x00000000
Sep 16 10:56:15 d710459 kernel: [ 1238.672811] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78283 at 78275)
Sep 16 10:56:18 d710459 kernel: [ 1240.724013] [drm:i915_gem_idle] *ERROR* hardware wedged
Sep 16 10:56:27 d710459 kernel: [ 1249.938518] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
Sep 16 10:56:27 d710459 kernel: [ 1250.256011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Sep 16 10:56:27 d710459 kernel: [ 1250.256021] render error detected, EIR: 0x00000000
Sep 16 10:56:27 d710459 kernel: [ 1250.256045] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78285 at 78275)
Sep 16 10:56:29 d710459 kernel: [ 1252.324013] [drm:i915_gem_idle] *ERROR* hardware wedged
Sep 16 10:56:38 d710459 kernel: [ 1261.400274] [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck
Sep 16 10:56:38 d710459 kernel: [ 1261.712011] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Sep 16 10:56:38 d710459 kernel: [ 1261.712021] render error detected, EIR: 0x00000000
Sep 16 10:56:38 d710459 kernel: [ 1261.712792] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78287 at 78275)
Sep 16 10:56:41 d710459 kernel: [ 1263.764013] [drm:i915_gem_idle] *ERROR* hardware wedged
Sep 16 10:56:46 d710459 kernel: Kernel logging (proc) stopped.

At least in my case, it seems like the problem might have something to do with the i915 kernel module & this system's "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"

[hagrid_aragog]

same problem............same intel graphics.......i think it can be related to graphic card

[deadlytackler]

I am also of the same opinion that it's related to graphics card

[deadlytackler]

It happened today twice . One when I was trying to open Evolution after installing it thru Package Manager. Second time when there were 4/5 tabs were opened. Here is the log File attached, may be some program is setting it on sleep mode (though disabled in power management)......

Log File 22nd Sep.odt

May I request on reading the log file and finding the problem area.

Regards

[lolmint]

My computer keeps crashing within a few minutes after I turn it on. It shows a message:

(process:214): GLIB WARNING ** GLib - getpwuid_r(): failed due to unknown user id (0)

With three or four other lines(I can never make them out, as the message flashes quickly). Then, the computer doesn't exactly turn off; it goes in some sort of limbo. The screen flashes really quickly every twenty seconds or so until I manually power the computer down.

Kenya help me out?

On my computer it said Process 380 and it would not start, I changed the mode the HDD runs in in BIOS from SATA to Compatibility (even though it is a SATA drive) and now it works. Well Works means it starts up from the HDD and not a CD.

[Tsunum]

I've been away for some times and would like to know if any solution to this problem has came up?

[willie42]

After doing some digging I found that people using Ubuntu are having same issue. there is a bug report in. I also found this:

The boot menu your are booting from, if you take a look you will see
that the root=UUID= has a string of letters and numbers, the UUID is
correct on the kernel that is booting and wrong on the kernel that is
not booting, you can try first in the console 'sudo update-grub' and see
if that will fix the problem or use copy and paste on the
/boot/grub/grub.cfg. I'm not an expert on grub2 so that's the best I can
tell you.

http://us.generation-nt.com/answer/10-4 ... 07291.html

Bug report: https://bugs.launchpad.net/ubuntu/+sour ... bug/572279

maybe someone else with more knowledge can help more. try and update grub and see if that helps. I will keep digging

[willie42]

After getting "GLib WARNING **: getpwuid_r(): failed due to unknown user id (0)" on fresh install of Lubuntu 10.4 and reading lots of posts, I looked and /var/log/lxdm.log and found a message stating that no screens could be detected. I then found there was a rahter empty xorg.conf in /etc/X11. I renamed it to xorg.conf.bak and rebooted and whala - problem solved (for me at least).


Here is something I found that worked for someone else:

https://bugs.launchpad.net/ubuntu/+bug/531027

maybe someone else has an idea