#738521 xserver-xorg-video-ati: Persistant system lockup with ATI Radeon X300 GPU running firmware-linux-nonfree #738521
- Package:
- xserver-xorg-video-ati
- Source:
- xserver-xorg-video-ati
- Description:
- X.Org X server -- AMD/ATI display driver wrapper
- Submitter:
- Paul
- Date:
- 2015-03-09 18:45:04 UTC
- Severity:
- important
Specifics: Dell Dimension 8400 ATI/AMD Radeon X300 GPU (chip ID = 1002:5b60) Debian jessie/sid Linux Dimension 3.12-1-686-PAE #1 SMP Debian 3.12.9-1 (2014-02-01) i686 xserver-xorg-video-ati / radeon 1:7.3.0-1 firmware-linux-nonfree 0.40 libgl1-mesa-dri (and others) 9.2.2-1 1. Steps to reproduce the problem Running Debian Wheezy, by installing the package "firmware-linux-nonfree" which contains the firmware to enable 3D acceleration for the ATI card (Radeon X300), when the system starts and user logins, the system locks. 2. Symptoms The input devices are inoperative, the screen image is undistorted but unresponsive, the eth0 connection breaks (ssh is unavailable.) The REISUB keys are ineffective. The only recourse is to do a hard reset by holding the power button. Lockup occurs any where within seconds to within minutes of bootup. Lockup most often occurs when in the graphical desktop environment; rarely when in a virtual terminal (ALT F1-F6). 3. Tested kernels The user has tested kernel 3.2.0-4 (Wheezy's stable kernel) and 3.12.9-1 (from Debian's unstable branch). Both kernels exhibit the same result when firmware is installed. On the other hand, both kernels work fine as soon as the firmware package is uninstalled. 4. Additional information Lockup will occur sporatically with no specific action or application. Debian BTS #651532 shows similar symptoms and user has tried the suggested fixes without success. 5. Attached logs (4 files): Xorg.0.log, syslog, glxinfo and dmesg attached. The files are just prior to lockup. User has unsuccessfully attempted to obtain a dmesg during lockup via ssh. 6. Other considerations Running Debian wheezy without package "firmware-linux-nonfree", the user is unable to use the default desktop (GDM3); only "fallback" mode is available; 3D video acceleration is not available. Any suggestions are appreciated. I am willing to troubleshoot if knowledgeable advise is proffered. Thanks.
Monday 10 February 2014 00.22.05, Paul wrote: via Glamor became possible with my Southern Island card (Bonaire XTX [Radeon R7 260X]) about six months ago, although not immediately after logging in but rather after several hours, and never when using the computer but when I leave it unattended. I *think* it's locked up once while switched to a text console, but otherwise only while the graphical console has been active. Whenever it happens, the system starts spewing out _something_ on the ethernet interface, making it impossible to connect to my server connected to the same switch/AP (the LEDs of both ports flash furiously), but I haven't been able to see anything with tcpdump. No clues can be found in any logs, except sometimes a few "eth0: link up" in the server syslog, and just one time the affected system managed to get off a message about a GPU fault via netconsole: Feb 8 01:49:59 johansson [108159.201208] radeon 0000:01:00.0: GPU fault detected: 146 0x08075014 Feb 8 01:49:59 johansson [108159.201215] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0007B6C0 Feb 8 01:49:59 johansson [108159.201217] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x07050014 Once, a couple of weeks ago, I came back to the computer and found it unresponsive; the screen had gone black but not into sleep mode and I could still ssh in. chvt would just hang and when I tried restarting X (kdm), the system stopped responding completely as before. So it seems that the system might not lock up completely right away, but that it's a two-step process. Hope this is of any help at all.
The symptoms may be similar, but it's very unlikely to be one and the same problem. Please file your own report. Which version of libgl1-mesa-dri and the kernel are you using?
måndagen den 9 mars 2015 16.01.52 skrev du: OK. I didn't want to file a separate bug report yet since the problem description is rather vague and I'm not completely sure if it's a software bug or a hardware problem. The (until recently at least) current versions in jessie; linux- image-3.16.0-4-amd64 3.16.7-ckt4-3 and libgl1-mesa-dri 10.3.2-2 but with the patch to disable asynchronous DMA (http://cgit.freedesktop.org/mesa/mesa/commit/?id=ae4536b4f71c).