nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Grokking log files - are these errors? (http://www.nvnews.net/vbulletin/showthread.php?t=95063)

skullmunky 07-17-07 03:25 PM

Grokking log files - are these errors?
 
i'm having what seem like the usual sort of random freezes, one of:

a) everything freezes but mouse can still move
b) monitor flashes black then returns to desktop, everything frozen

or

c) monitor just goes black, period.

in all cases, can't get to other virtual console; sysrq key to force sync and poweroff works, but that's all. can't ssh into frozen box, and don't have another machine w/ rs232 to try serial terminal. fixes in the stickies don't help. card is quadro fx 1400, driver is 100.14.11, motherboard is Abit KN8 Ultra (nvidia CK804).

not looking for a quick answer, i know this is voodoo territory :) but i'm trying to learn how to look at logs a bit to see if i can recognize an error if there is one. couple questions:

1) in syslog, does NVRM: Xid .... mean anything, or is it just info?
Jul 17 10:44:21 silverado kernel: [53369.560000] NVRM: Xid (0001:00): 16, Head 00000000 Count 004d924b
Jul 17 10:44:21 silverado kernel: [53369.560000] NVRM: Xid (0001:00): 16, Head 00000001 Count 004d924a
Jul 17 10:44:24 silverado kernel: [53372.560000] NVRM: Xid (0001:00): 8, Channel 00000000
Jul 17 10:44:24 silverado kernel: [53372.564000] NVRM: Xid (0001:00): 30, L1 -> L0
Jul 17 10:44:39 silverado kernel: [53387.564000] NVRM: Xid (0001:00): 16, Head 00000000 Count 004d942c
Jul 17 10:44:39 silverado kernel: [53387.564000] NVRM: Xid (0001:00): 16, Head 00000001 Count 004d942b
Jul 17 10:44:40 silverado kernel: [53388.564000] NVRM: Xid (0001:00): 8, Channel 0000007e
Jul 17 10:44:47 silverado kernel: [53395.572000] NVRM: Xid (0001:00): 16, Head 00000000 Count 004d942d


2) in Xorg.0.log, is this an error, or just info?

(WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00000620, 0x00000620)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00000620, 0x00000658)
(WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00000658, 0x00000658)
(WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00000668, 0x00000668)
(II) NVIDIA(0): Setting mode "1440x900@60"
(WW) NVIDIA(0): WAIT (2, 1, 0x8000, 0x00000668, 0x00000774)
(WW) NVIDIA(0): WAIT (0, 1, 0x8000, 0x00000774, 0x00000774)
(WW) NVIDIA(0): WAIT (0, 1, 0x8000, 0x000007a8, 0x000007a8)
(WW) NVIDIA(0): WAIT (2, 11, 0x8000, 0x000007a8, 0x00000cdc)
(WW) NVIDIA(0): WAIT (1, 11, 0x8000, 0x00000c28, 0x00000cdc)
(WW) NVIDIA(0): WAIT (2, 11, 0x8000, 0x00000c28, 0x00000d20)
(WW) NVIDIA(0): WAIT (1, 11, 0x8000, 0x00000c28, 0x00000d20)


3) maybe the problem's not with nvidia or X at all, maybe it's my ethernet card: anyone know if this looks suspicious?

Jul 17 10:44:54 silverado kernel: [53402.496000] NETDEV WATCHDOG: eth0: transmit timed out
Jul 17 10:44:54 silverado kernel: [53402.496000] eth0: transmit timed out, tx_status 00 status 6601.
Jul 17 10:44:54 silverado kernel: [53402.496000] diagnostics: net 0cc0 media 8802 dma 0000003b fifo 0000
Jul 17 10:44:54 silverado kernel: [53402.496000] eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Jul 17 10:44:54 silverado kernel: [53402.496000] Flags; bus-master 1, dirty 166114(2) current 166114(2)
Jul 17 10:44:54 silverado kernel: [53402.496000] Transmit list 00000000 vs. dfbb6340.
Jul 17 10:44:54 silverado kernel: [53402.496000] 0: @dfbb6200 length 8000002a status 8000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 1: @dfbb62a0 length 8000002a status 8000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 2: @dfbb6340 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 3: @dfbb63e0 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 4: @dfbb6480 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 5: @dfbb6520 length 800000cb status 000000cb
Jul 17 10:44:54 silverado kernel: [53402.496000] 6: @dfbb65c0 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 7: @dfbb6660 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 8: @dfbb6700 length 8000004a status 0000004a
Jul 17 10:44:54 silverado kernel: [53402.496000] 9: @dfbb67a0 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 10: @dfbb6840 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 11: @dfbb68e0 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 12: @dfbb6980 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 13: @dfbb6a20 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 14: @dfbb6ac0 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] 15: @dfbb6b60 length 8000002a status 0000002a
Jul 17 10:44:54 silverado kernel: [53402.496000] eth0: Resetting the Tx ring pointer.


thanks for any pointers. once i've done more thorough diagnostics and tried more things, if i can't fix it i'll post the bug report logs here.

netllama 07-17-07 03:28 PM

Re: Grokking log files - are these errors?
 
The output that you've posted suggests that your system is experiencing one or more problems with multiple drivers.

I'd suggest reading the forum sticky posts.


All times are GMT -5. The time now is 09:39 PM.

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