Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-01-07, 10:59 AM   #1
roshi
Registered User
 
Join Date: Mar 2007
Posts: 19
Default How to recover your system and produce an error log

Well it's nothing new.
I'm still having soft and hard locks and lots of Xids.
When I have one of those locks that the music keeps playing but the screen totally freezes, usually the keyboard doesn't respond to key presses.
The power button works though.
Doing a total reset is not nice.
So I searched for a solution to restart X, which apparently also clears the flickering that you might get after one of these locks. (convenient right?)

The thing is, my pc, Dell M1210, has a few buttons other than the normal keyboard that keep on working even when the X locks.
At lest I get response on the first press, but apparently it also locks afterwards.
I realized this when I pressed mute during one of those locks, it mutted the sound, but I could not unmute it.

So I can press one of those buttons at least once.
Well that's good enough. I selected one that I didn't use for nothing, in my case a cute button called media direct. It actually has the drawing of a house, which conveniently means "go home..." to the start again hehe.
Afterwards I binded that button to a simple script:

#!/bin/sh
cd /tmp
sudo /usr/bin/nvidia-bug-report.sh
sudo /etc/init.d/xdm restart

Well this generates a bug report during the crisis situation, and restarts X/recovers the system.
I binded that command with xbindkeys, adding (in my case) the following command to my .xbindkeysrc

"/usr/local/bin/xrestart"
release+c:237

I tried another program, (can't remember the name) really good one, good interface etc, but it didn't respond to my presses upon X freeze.

So here's one bug report just freshly generated.
When I got home today, my pc was burning rubber.
It got an X freeze ar 12h something and ever since the cpu must of been @100%. So the fans were working at full steam.
The radio was sill playing though.
Then I pressed the magic key and everything was back to "normal" again.

I just noticed that because of log-rotate the nvidia bug report doesn't catches the Xids. They get archived everyday.
Also, when you use this technique to recover the system, you don't get a corresponding Xid message in you log file.
Apparently that message gets generated automatically but the driver when it recovers automatically.
Which is not the case here.

Well this is just a suggestion.
It works for me. (sometimes)
Attached Files
File Type: bz2 nvidia-bug-report.log.bz2 (51.0 KB, 88 views)
roshi is offline   Reply With Quote
Old 11-01-07, 11:04 AM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: How to recover your system and produce an error log

The bug report that you attached is badly mangled (lots of misformatted text, sections scrambling into one-another, etc). Is this actually what was generated by running nvidia-bug-report.sh on your system or did you manually edit it afterwards?
netllama is offline   Reply With Quote
Old 11-01-07, 11:19 AM   #3
roshi
Registered User
 
Join Date: Mar 2007
Posts: 19
Default Re: How to recover your system and produce an error log

Actually I didn't knew that. I did not open the file.
I just extracted the file from the attach and compared it's md5sum and it's the same as the one in my /tmp file.
Don't know what might of happened.
Anyway that was what was generated.
Maybe this time there was some problem during the generation.
The fact is that it was generated while the cpu was burning at 100%.
of course I don't know this (X was freezed) but I believe so since the heat coming out of the ventilation lead me to think so.
Here's one that I just generated.
Of course now the system is "stable".
Attached Files
File Type: bz2 nvidia-bug-report.log.bz2 (24.7 KB, 77 views)
roshi is offline   Reply With Quote
Old 11-01-07, 11:25 AM   #4
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: How to recover your system and produce an error log

The fact that the bug report was badly mangled is a bit worrisome, and suggests that your system might have problems outside of the nvidia driver.

Anyway, I have a few questions:
0) Does the instability persist if you remove Coolbits from xorg.conf ?
1) Does the instability persist if you disable the Composite extension in xorg.conf ?
2) Have you verified that you're using the latest motherboard BIOS?
3) Does the problem persist if you're using a kernel without vesafb support?
netllama is offline   Reply With Quote
Old 11-01-07, 11:33 AM   #5
roshi
Registered User
 
Join Date: Mar 2007
Posts: 19
Default Re: How to recover your system and produce an error log

2) Yes.
0,1,3) Will try those now. But I tried almost everything before, the "sticker post" stuff, maybe even that too, can't remember, and nothing helped.
I'll give new about that. But it will take some time to test, since the locks are random.
roshi is offline   Reply With Quote
Old 11-01-07, 02:13 PM   #6
xbobmx
Registered User
 
Join Date: May 2003
Posts: 191
Default Re: How to recover your system and produce an error log

'file' says the bunzipped attachment is a tar archive. The attachment should really be named nvidia-bug-report.log.tar.bz2. Extracting with e.g.
Code:
tar jxvf nvidia-bug-report.log.bz2
results in an uncorrupted nvidia-bug-report.log.
xbobmx is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 12:22 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.