Date: Sat, 13 Dec 2014 18:40:50 +0200 From: Mikael Ikivesi <mikael@ikivesi.net> To: Pete French <petefrench@ingresso.co.uk> Cc: rleigh@codelibre.net, stable@FreeBSD.org Subject: Re: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related Message-ID: <86iohfv6y5.fsf@ikivesi.net> In-Reply-To: <E1Xzo9k-000HwJ-55@dilbert.ingresso.co.uk> References: <20141212193447.GA1657@codelibre.net> <E1Xzo9k-000HwJ-55@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I also experienced these hard freezes. Nothing on logs and I get forced to do a hard reset. This never happens on console and for me it has only happened while running X. The occurences have long and random intervals. With first beta of 10.1 I had few maybe separated by a week each. With 10.1 release I tought the issued had been resolved until I got the first one just yesterday. The machine just freezes and kills all the output to graphic card (screen instantly goes to power saving mode). Only once I was able to get anything to logs: Oct 23 23:11:23 localhost kernel: drmn0: error: GPU lockup CP stall for more than 10000msec Oct 23 23:11:23 localhost kernel: drmn0: warning: GPU lockup (waiting for 0x0000000000795fa9 last fence id 0x0000000000795f85) Oct 23 23:11:23 localhost kernel: drmn0: info: Saved 1143 dwords of commands on ring 0. Oct 23 23:11:23 localhost kernel: drmn0: info: GPU softreset: 0x00000003 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS = 0xA0003828 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00004100 Oct 23 23:11:23 localhost kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00020182 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008680_CP_STAT = 0x80028243 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_SOFT_RESET=0x00007F6B Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS = 0x00003828 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE0 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: GRBM_STATUS_SE1 = 0x00000007 Oct 23 23:11:23 localhost kernel: drmn0: info: SRBM_STATUS = 0x200000C0 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008674_CP_STALLED_STAT1 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008678_CP_STALLED_STAT2 = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_00867C_CP_BUSY_STAT = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: R_008680_CP_STAT = 0x00000000 Oct 23 23:11:23 localhost kernel: drmn0: info: GPU reset succeeded, trying to resume Oct 23 23:11:23 localhost kernel: info: [drm] probing gen 2 caps for device 1022:9603 = 2/0 Oct 23 23:11:23 localhost kernel: info: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Oct 23 23:11:23 localhost kernel: info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). Oct 23 23:11:23 localhost kernel: drmn0: info: WB enabled Oct 23 23:11:23 localhost kernel: drmn0: info: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0xfffff800324ecc00 Oct 23 23:11:23 localhost kernel: drmn0: info: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x0xfffff800324ecc0c Oct 23 23:11:23 localhost kernel: info: [drm] ring test on 0 succeeded in 2 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ring test on 3 succeeded in 1 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ib test on ring 0 succeeded in 0 usecs Oct 23 23:11:23 localhost kernel: info: [drm] ib test on ring 3 succeeded in 1 usecs This log was with RC2 if I rememeber correctly. The GPU stall happened first and produced otherwise same symptoms except it was able to resume few some seconds later. But after few minutes the hard freeze occured without anything in logs. These freezes have happened mostly with very low strain on system (idle, returning from screensaver, the one with the log happened while typing text in emacs). I have left the desktop powered on for days without any problems. (I usually power off for the night). I have not been able to ssh to system while in frozen state nor does it respond to power down button. Mikael Ikivesi http://ikivesi.net Pete French <petefrench@ingresso.co.uk> writes: >> Subject: Hard system lockups with 10.1, probably drm/newcons/radeonkms-related >> >> >> Hi folks, >> >> With 10.1-RELEASE, I've enabled newcons at boot with >> kern.vty="vt" >> in loader.conf. With the latest Xorg/drm installed with pkg, I'm >> seeing intermittent hangs and hard lockups of the system. I've >> included the logs for one which recovered earlier today, but later >> on it just locked up completely and I don't have logs for that >> since I had to do a hard reset. I had to install and enable >> hal+dbus to get a working keyboard and mouse when running X, >> despite both working fine on the console! > > Interesting, as I was about to write something very similar about > latest xorg under 9.3-STABLE. I have been seeing the same, > hangs and hard lockups. I thought it was the card so I replaced it, but > the result is the same. > > I am also using the new console, and I am also using Radeons. > > This is definetly video related - it never happens using the system > remotely, and sometimes it is just the graphics which locks up (I > can ssh in and shutdown). Occasionally, the lockup clears itself and > the graphics comes back. > > Very puzzling - it can go for days without a lokcup, then sometimes > I will gte several in the space of an afternoon. > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86iohfv6y5.fsf>