Bug 101732

Summary:

TURKS GPU - radeon 0000:01:00.0: failed to get a new IB (-35)

Product:

DRI

Reporter:

Fede <fedevx>

Component:

DRM/Radeon

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED INVALID

QA Contact:

Severity:

major

Priority:

medium

Version:

DRI git

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Excerpt of journalctl -b -l \| grep radeon	none

Description Fede 2017-07-10 01:21:56 UTC

Created attachment 132578 [details]
Excerpt of journalctl -b -l | grep radeon

Environment info:

OS: Arch
xf86-video-ati:	1:7.9.0-1
Kernel: 4.11.9-1
Running Gnome on Wayland (the issue happens with Xorg too).

#############
lspci | grep -i radeon:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series]
#############
hwinfo --gfxcard

21: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: VCu0.dkF2+KIVH8C
  Parent ID: vSkL.zuRwVyuZRN1
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "Toshiba America Info Radeon HD 7670M"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x6840 "Thames [Radeon HD 7500M/7600M Series]"
  SubVendor: pci 0x1179 "Toshiba America Info Systems"
  SubDevice: pci 0xfb81 "Radeon HD 7670M"
  Driver: "radeon"
  Driver Modules: "drm"
  Memory Range: 0xb0000000-0xbfffffff (ro,non-prefetchable)
  Memory Range: 0xc0000000-0xc001ffff (rw,non-prefetchable)
  I/O Ports: 0x3000-0x30ff (rw)
  Memory Range: 0xc0040000-0xc005ffff (ro,non-prefetchable,disabled)
  IRQ: 25 (44749 events)
  Module Alias: "pci:v00001002d00006840sv00001179sd0000FB81bc03sc00i00"
  Driver Info #0:
    Driver Status: radeon is active
    Driver Activation Cmd: "modprobe radeon"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #18 (PCI bridge)

Primary display adapter: #21
#############

I receive the errors as per the attached logs. I do see them sometimes at boot, about the time plymouth is about to kick in but most of the time I can reproduce the issue by giving the GPU some work.

For example, I can trigger the issue by running:

vblank_mode=0 glxgears

After 10 to 15 seconds, the screen would then freeze. Then go blank as it was trying to reset itself then display the screen again before starting another reset loop. The system is then not responsive unless via SSH, which I then use to restart the display-manager service. Upon restarting it, the screen either is full of white noise (can't see anything but noise in it) or it has a frozen image of what it was there when the lockup happened. The mouse pointer is still visible and responding.

Looking at other bugs, this could be related to https://bugs.freedesktop.org/show_bug.cgi?id=67722 though the GPU is different. I'm booting with radeon.dpm=1. Booting without that option renders the screen unusable (https://bugzilla.kernel.org/show_bug.cgi?id=82431).

Comment 1 Fede 2017-07-21 02:30:56 UTC

More Details which might be relevant and might have missed the first time around:

Other packages:
linux-firmware 20170422.ade8332-1
kernel 4.11.9-1
Xorg driver: xf86-video-ati 1:7.9.0-1

Have also seen the following when booting the radeon kernel module is loaded:

Jul 21 09:51:06 hostname kernel: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!!
Jul 21 09:51:06 hostname kernel: radeon 0000:01:00.0: failed initializing UVD (-1).
Jul 21 09:51:06 hostname kernel: [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Jul 21 09:51:06 hostname kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110).
Jul 21 09:51:06 hostname kernel: [drm:radeon_device_init [radeon]] *ERROR* ib ring test failed (-110).

Current situation:

GDM with Wayland shows only white noise on the screen. Switching to Xorg shows the desktop as expected however it seems it is not using the radeon driver. As glxinfo puts it:

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)

Comment 2 Fede 2017-10-19 10:35:07 UTC

I don't have this laptop anymore. It might have been a motherboard issue as the laptop stopped booting not long after this issue.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.