Just some clarifications, @harry17
The reported issue isn't related only to a single ("current" - probably
latest) kernel. The issue isn't stick to any particular kernel; initial
report is related to a particular context, of course. When there is some
issue related to initial firmware loading (at boot time), this isn't
firmware issue, but a driver issue, the driver performing firmware load!
Am I wrong?! Here the case is very different. The issue is firmware
related, definitely, and the 'symptoms' come up all the time, not only
at boot time (at boot is more noticeable, but not restricted to)! There
could be (and I believe it is) a driver's 'guilty' too. Before the last
firmware update and next rollback, one part (error) from initial report
present yet. Especially:
...
[ +0.100566] radeon 0000:01:00.0: failed VCE resume (-110).
...
And repeats again and again all the time when 1.173.12 runs (same like
all errors from initial report get repeat while 1.173.15 runs) with
kernel 4.15.0-88-generic. The error in "/build/linux-
WUVVsw/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c" (in my case)
brings up once, initially.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1865130
Title:
[drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
reset the VCPU!!!
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
=== SRU Justification ===
[Impact]
Firmware update of radeon/oland_rlc.bin breaks some radeon cards.
[Fix]
Revert the new firmware.
[Regression Potential]
Low. The old firmware has been used for a long time.
=== Original Bug Report ===
when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
following
[ +0.000091] radeon 0000:01:00.0: WB enabled
[ +0.000002] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0x000000008ac2d26f
[ +0.000001] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0x00000000a848de20
[ +0.000001] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0x000000001e4494a9
[ +0.000001] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0x0000000098a9748e
[ +0.000001] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0x00000000b6ff734d
[ +0.000212] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0x000000006b4da526
[ +0.100566] radeon 0000:01:00.0: failed VCE resume (-110).
[ +0.179115] [drm] ring test on 0 succeeded in 1 usecs
[ +0.000004] [drm] ring test on 1 succeeded in 1 usecs
[ +0.000004] [drm] ring test on 2 succeeded in 1 usecs
[ +0.000006] [drm] ring test on 3 succeeded in 3 usecs
[ +0.000004] [drm] ring test on 4 succeeded in 3 usecs
[ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
trying to reset the VCPU!!!
[ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding,
giving up!!!
[ +0.000040] radeon 0000:01:00.0: failed initializing UVD (-1).
[ +0.000060] [drm] ib test on ring 0 succeeded in 0 usecs
[ +0.000051] [drm] ib test on ring 1 succeeded in 0 usecs
[ +0.000032] [drm] ib test on ring 2 succeeded in 0 usecs
[ +0.000052] [drm] ib test on ring 3 succeeded in 0 usecs
[ +0.000029] [drm] ib test on ring 4 succeeded in 0 usecs
Also it affects the boot time.
the used OpenGL renderer is:
"OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Fri Feb 28 11:50:50 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller
[17aa:3801]
Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
InstallationDate: Installed on 2019-09-17 (163 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: LENOVO 20238
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 79CN46WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 00000000Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G510
dmi.modalias:
dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr00000000NotDefined:cvnLENOVO:ct10:cvrLenovoG510:
dmi.product.family: IDEAPAD
dmi.product.name: 20238
dmi.product.sku: LENOVO_MT_20238
dmi.product.version: Lenovo G510
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
