View Single Post
Old 06-05-09, 09:16 PM   #7
marcan
Registered User
 
Join Date: Apr 2009
Posts: 10
Default Re: 185.18.10 - Xid errors and hang during VDPAU video playback

Grepping through old logs (including while I was running 180.xx and other driver versions), I see:
- a few rare scattered "Card present" messages with no matching "not present" messages. I was able to cause one of these by switching to a text console.
- some not present/present cycles when Xorg is manually killed/restarted
- this one time I had a hang with 180.44, although I don't remember what caused it (might have been the same vdpau thing or not):
Code:
May 18 17:26:55 raider pciehp 0000:00:01.0:pcie02: Card not present on Slot(1)
May 18 17:26:55 raider pciehp 0000:00:01.0:pcie02: Card present on Slot(1)
May 18 17:26:55 raider pciehp 0000:00:01.0:pcie02: Card not present on Slot(1)
May 18 17:26:55 raider pciehp 0000:00:01.0:pcie02: Card present on Slot(1)
May 18 17:27:04 raider NVRM: Xid (0001:00): 16, Head 00000001 Count 00000000
May 18 17:27:05 raider NVRM: Xid (0001:00): 16, Head 00000000 Count 0014a8ac
May 18 17:27:06 raider SysRq : SAK
May 18 17:27:06 raider SAK: killed process 21146 (X): task_session_nr(p)==tty->session
May 18 17:27:06 raider SAK: killed process 21146 (X): task_session_nr(p)==tty->session
May 18 17:27:07 raider /usr/sbin/gpm[7139]: *** info [mice.c(1988)]:
May 18 17:27:07 raider /usr/sbin/gpm[7139]: imps2: Auto-detected intellimouse PS/2
May 18 17:27:07 raider pciehp 0000:00:01.0:pcie02: Card present on Slot(1)
May 18 17:27:08 raider 1.3.1: FATAL: CXWindowsScreen.cpp,1590: X display has unexpectedly disconnected
May 18 17:27:08 raider kdm[7521]: X server for display :0 terminated unexpectedly
May 18 17:27:10 raider kdm: :0[21151]: pam_unix(kde:session): session closed for user marcansoft
Looking at yesterday's logs, I don't see a strong pattern. There are pciehp replugs interspersed with Xid errors. Sometimes there's a Xid, I restart, a pciehp cycle, then 20 minutes later another Xid and hang. Sometimes there's a pciehp and then an immediate Xid. Sometimes there's a Xid an then an immediate pciehp. So it looks like it's correlated, but not entirely clear.

I guess that means:
a) Yes, rarely alone, often when killing/restarting Xorg
b) Yes, but usually a problem happens soon thereafter
c) I can't find any of the Xid messages from yesterday that didn't have some pciehp message relatively nearby, but it's not entirely clear.

It's too erratic to make any solid conclusions as far as I can tell

Yes, the GPU is on an MXM card. This is a near stock laptop and quite new (bought it late 2008) - the only thing I've done to it is add a second hard drive (there's a vacant spot on this configuration; other configurations have it stock). I can see the MXM card when I take off the single "user-serviceable" cover (which uncovers a good part of the bottom of the laptop, including HDDs and RAM) but I can't remove the MXM card this way, as I'd have to take off the rest of the laptop's bottom case to be able to remove the thermal system on top of it. I haven't done or attempted to do anything to the card.

The laptop is stable as far as hardware is concerned, so far. I've had a few Xorg crashes over the past few months, but nothing worrisome. This is the first time I've had multiple repeatable crashes traceble to something in particular. Of note: I upgraded to 185.18.10 because it fixed the PowerMizer issues. Prior drivers never went beyond levels 0-1, while this one is able to switch all the way up to 3, and sometimes does while using VDPAU in this manner. So I guess it is possible that the increased GPU clocking at the higher PowerMizer levels is uncovering some stability issues. Or maybe the issue occurs when switching PowerMizer levels. On the other hand, unless Acer screwed up or this laptop is defective, there's no reason why there would be a hardware-caused stability issue.

I'm leaving the video looping all night now. No RegistryDwords, no Composite.
marcan is offline   Reply With Quote