1002:9591 ring 0 stalled for more than 10100msec

Bug #1508944 reported by Daryl Lublink
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

The video card randomly locks up when radeon.dpm=1 is set as a kernel parameter on Radeon Mobile HD3650.

On Ubuntu 15.04, I can only reproduce it if I let the screen saver come on while a browser is open ( either google chrome or firefox will do ).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.34
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 1339 F.... pulseaudio
 /dev/snd/controlC1: david 1339 F.... pulseaudio
Date: Thu Oct 22 09:46:27 2015
HibernationDevice: RESUME=UUID=86c5a3d9-cb5c-4bcb-9d9d-a61d6e9a356f
InstallationDate: Installed on 2015-10-13 (9 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: Hewlett-Packard HP EliteBook 8530p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--mate--vg-root ro radeon.dpm=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-30-generic N/A
 linux-backports-modules-3.19.0-30-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.20
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.27
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.20:bd12/08/2011:svnHewlett-Packard:pnHPEliteBook8530p:pvrF.20:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530p
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Daryl Lublink (dlublink) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote : Re: ring 0 stalled for more than 10100msec

Daryl Lublink, thank you for reporting this and helping make Ubuntu better.

Could you please provide a log of when running this under the latest mainline kernel, and provide a comment to if the PC locks up?

description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Daryl Lublink (dlublink) wrote :

It says "It appears you are currently running a mainline kernel. It would be better to report this bug...."

*** Problem in linux-image-4.3.0-040300rc6-generic

Revision history for this message
Daryl Lublink (dlublink) wrote :

i have added the dmesg log taken manually after the GPU lock up.

Revision history for this message
Daryl Lublink (dlublink) wrote :

This ticket was filed using ubuntu-bug linux using the default kernel.

After that, you requested that I test against a mainline kernel, I did that.

Now you want me to refile the ticket all over again?

This is the second ticket I opened, can you please clarify what I have done wrong ?

Revision history for this message
Daryl Lublink (dlublink) wrote :

Both the accounts are me. Sorry for the confusion. I lost the password to the other one, and it's still logged in at work.

Revision history for this message
Daryl Lublink (dlublink) wrote :

I changed my name on this account to make them the same.

Revision history for this message
Daryl Lublink (dlublink) wrote :

This ticket was created in confusion because I had logged in with two different accounts.

Both 1507150 and 1508944 were opened by me. I closed 1507150 as it had comments about updating the firmware to the latest. This ticket started off cleanly with a 'ubuntu-bug linux' report that was made with the latest bios firmware for the laptop.

Revision history for this message
Daryl Lublink (dlublink) wrote :
penalvch (penalvch)
summary: - ring 0 stalled for more than 10100msec
+ 1002:9591 ring 0 stalled for more than 10100msec
Revision history for this message
Daryl Lublink (dlublink) wrote :

I just sent a request for an account merge. Both accounts should be unified into a single account now.

Revision history for this message
penalvch (penalvch) wrote :

Daryl Lublink, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (freedesktop driver/Radeon)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Low → High
status: Incomplete → Triaged
Revision history for this message
Daryl Lublink (dlublink) wrote :

I opened a ticket at freedesktop as requested :

https://bugs.freedesktop.org/show_bug.cgi?id=92662

Revision history for this message
Daryl Lublink (dlublink) wrote :

In my case, I can avoid the problem by setting the screen saver to 'blank screen'.

Revision history for this message
Daryl Lublink (dlublink) wrote :

My ticket at freedesktop was closed and marked as a duplicate :

Here is the new ticket : https://bugs.freedesktop.org/show_bug.cgi?id=66963

The new ticket was opened 2013-07-16, which means that bug has been open for 2+ years now.

Revision history for this message
Daryl Lublink (dlublink) wrote :

I found the following kernel patch in the comments of the freedesktop ticket :

https://bugs.freedesktop.org/attachment.cgi?id=106085

I can no longer produce the crash of my GPU with this patch.

It has the same effect as these two commands as root :

echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo performance > /sys/class/drm/card0/device/power_dpm_state

In my case, it seems to have worked-around the issues I am having with the radeon driver.

Revision history for this message
Teimuraz (tgasoft) wrote :

Hello everybody!

I have the same notebook HP EliteBook 8530p, the same version of BIOS as mentioned here, Kubuntu 15.10 on it and radeon video driver. I have problems with overheating (definitely related with video card and it's driver) and I was very glad to find some kind of workaround.

I mean
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo performance > /sys/class/drm/card0/device/power_dpm_state

But the problem is that this files - power_dpm_force_performance_level and power_dpm_state - are missed on my system ;-(

root@temo-HP-EliteBook-8530p:/sys/class/drm/card0/device/power# pwd
/sys/class/drm/card0/device/power
root@temo-HP-EliteBook-8530p:/sys/class/drm/card0/device/power# ls -la
total 0
drwxr-xr-x 2 root root 0 Jan 7 21:05 .
drwxr-xr-x 13 root root 0 Jan 7 15:07 ..
-rw-r--r-- 1 root root 4096 Jan 7 21:06 async
-rw-r--r-- 1 root root 4096 Jan 7 21:06 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 Jan 7 11:35 control
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_active_kids
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_active_time
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_enabled
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_status
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_suspended_time
-r--r--r-- 1 root root 4096 Jan 7 21:06 runtime_usage

What should be the reason?
Should I create separate thread to discuss my overheat problem?

Thank you all beforehead.

Norbert (nrbrtx)
tags: removed: vivid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.