Extremely frequent and unpredictable lockups

[recursor94]

Hello, I want to make this post as concise as possible because I am not sure if my system will lockup. I am using a Lenovo Thinkpad with Mint 13 installed using the Cinnamon desktop environment. For whatever reason I am experiencing frequent and unpredictable lockups while doing non resource intensive activities--particularly web browsing. This issue seems to always occur while I am browsing in chromium. when the lockups occur I can not move the mouse, nor kill X with C-M-delback (emacs lingo) nor even switch terminals. I have left the system running for over an hour after the system began to lock up, but the problem never disappears. Here is the output from my syslog:

Code: Select all

 

Oct  7 14:06:19 andrew-ThinkPad-T530 kernel: [ 1794.619344] [drm] nouveau 0000:01:00.0: unknown i2c port 51
Oct  7 14:06:19 andrew-ThinkPad-T530 kernel: [ 1794.619682] [drm] nouveau 0000:01:00.0: unknown i2c port 48
Oct  7 14:06:19 andrew-ThinkPad-T530 kernel: [ 1794.619714] [drm] nouveau 0000:01:00.0: unknown i2c port 54
Oct  7 14:06:19 andrew-ThinkPad-T530 kernel: [ 1794.619743] [drm] nouveau 0000:01:00.0: unknown i2c port 55
Oct  7 14:06:19 andrew-ThinkPad-T530 kernel: [ 1794.619773] [drm] nouveau 0000:01:00.0: unknown i2c port 56
Oct  7 14:06:29 andrew-ThinkPad-T530 kernel: [ 1804.609703] [drm] nouveau 0000:01:00.0: unknown i2c port 51
Oct  7 14:06:29 andrew-ThinkPad-T530 kernel: [ 1804.610042] [drm] nouveau 0000:01:00.0: unknown i2c port 48
Oct  7 14:06:29 andrew-ThinkPad-T530 kernel: [ 1804.610073] [drm] nouveau 0000:01:00.0: unknown i2c port 54
Oct  7 14:06:29 andrew-ThinkPad-T530 kernel: [ 1804.610103] [drm] nouveau 0000:01:00.0: unknown i2c port 55
Oct  7 14:06:29 andrew-ThinkPad-T530 kernel: [ 1804.610132] [drm] nouveau 0000:01:00.0: unknown i2c port 56

My thinkpad uses both an hd intel graphics card and a seperate nvidia graphics card. I think that it is supposed to primarily use the intel card when browsing to conserve power and switch to the nvidia card when doing resource intensive graphical computations. I do not experience the crash in windows.

I do not know if the output from syslogs is the culprit of the crashes. any help is appreciated, thank you.

[xenopeek]

Can you share the output of:

Code: Select all

inxi -SGx

This indeed sounds like a graphics card problem.

[recursor94]

Thank you for your response, here is the output of that command--does anything seem abnormal?

Code: Select all

System:    Host: andrew-ThinkPad-T530 Kernel: 3.2.0-23-generic x86_64 (64 bit, gcc: 4.6.3) 
           Desktop: Gnome Distro: Linux Mint 13 Maya
Graphics:  Card-1: Intel Ivy Bridge Graphics Controller bus-ID: 00:02.0 
           Card-2: NVIDIA Device 0def bus-ID: 01:00.0 
           X.Org: 1.11.3 drivers: intel (unloaded: vesa,fbdev) Resolution: 1600x900@60.0hz 
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile GLX Version: 2.1 Mesa 8.0.2 Direct Rendering: Yes 

[recursor94]

Aha! I may have isolated the problem--I do not believe that it is graphics card related at all!

I was curious to see if the problem happened when I cleared my browser cache and history in chrome--it did! While I did this, I tracked my syslog using tail -f /var/log/syslog, This is the last message I received before the system locked up:

Code: Select all

 
Oct  8 18:19:04 andrew-ThinkPad-T530 dhclient: DHCPREQUEST of 10.14.9.106 on wlan0 to 1.1.1.1 port 67

also...

Code: Select all

 
andrew-ThinkPad-T530 NetworkManager[803]: <warn> error monitoring device for netlink events: No buffer space available 

that looks worrisome, but all of those things seem to happen when the system crashes as well as when it does not.

Very odd--because at that time I was using an Ethernet connection. My wireless card was turned off and disabled in the bottom right hand menu. This happened immediately after clearing my browser cache, plugin data and history in chrome. This must be the error behind the system lock ups. How do I solve this issue?