https://bugs.freedesktop.org/show_bug.cgi?id=67002
Priority: medium
Bug ID: 67002
Assignee: dri-devel(a)lists.freedesktop.org
Summary: evergreen: after resume from suspend-to-ram operation
is really slow with the latest DPM changes
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: jackdachef(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Using the drm-code from drm-fixes-3.11 branch
(http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11) against a 3.10
final kernel as explained in following post
(http://phoronix.com/forums/showthread.php?82357-drm-fixes-3-11-with-3-10-st…)
the card used is a HD5850, evergreen; ~amd64 Gentoo Linux, Intel Core i7 860,
gcc 4.8.1, 2.17
I tested suspend-to-ram which in a prior state of drm-next would lock up the
box (so much progress has been made - yay ! :) ):
via following command:
pm-suspend --quirk-dpms-on --quirk-s3-mode --quirk-vbe-post --quirk-vga-mode3
launched from VT1 (no X running)
first things noticable:
it takes longer (compared to the non-DPM driver) to turn off the computer so I
first thought that it had hardlocked (fans were still spinning, screen turned
off, harddisks +/- off - after some time the box went to suspend/sleep)
it also takes longer to resume and for the screen to turn on
following behavior is observable after the resume from suspend-to-ram:
dmesg shows:
[ 178.031724] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 178.430546] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control:
Rx
[ 178.430652] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 179.052821] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 180.073918] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 181.095014] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 182.116110] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 182.120733] ata1: link is slow to respond, please be patient (ready=0)
[ 182.122735] ata3: link is slow to respond, please be patient (ready=0)
[ 182.128740] ata5: link is slow to respond, please be patient (ready=0)
[ 182.130763] ata6: link is slow to respond, please be patient (ready=0)
[ 183.137207] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 184.158303] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 185.179399] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 186.200496] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 186.817477] ata1: COMRESET failed (errno=-16)
[ 186.819524] ata3: COMRESET failed (errno=-16)
[ 186.825487] ata5: COMRESET failed (errno=-16)
[ 186.827492] ata6: COMRESET failed (errno=-16)
[ 187.221593] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 187.241615] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[ 187.241618] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).
[ 187.241650] [drm] ib test on ring 0 succeeded in 0 usecs
[ 187.241683] [drm] ib test on ring 3 succeeded in 1 usecs
[ 187.246731] switching from power state:
[ 187.246732] ui class: none
[ 187.246733] internal class: boot
[ 187.246733] caps: video
[ 187.246734] uvd vclk: 0 dclk: 0
[ 187.246734] power level 0 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246735] power level 1 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246735] power level 2 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246736] status: c b
[ 187.246736] switching to power state:
[ 187.246737] ui class: performance
[ 187.246737] internal class: none
[ 187.246738] caps: single_disp video
[ 187.246738] uvd vclk: 0 dclk: 0
[ 187.246739] power level 0 sclk: 15700 mclk: 30000 vddc: 950
vddci: 1100
[ 187.246739] power level 1 sclk: 55000 mclk: 90000 vddc: 1038
vddci: 1100
[ 187.246740] power level 2 sclk: 72500 mclk: 100000 vddc: 1088
vddci: 1100
[ 187.246740] status: r
[ 188.350006] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 188.380064] ata3.00: configured for UDMA/133
[ 188.380117] sd 2:0:0:0: [sdb] Starting disk
[ 188.511188] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 188.523242] ata6.00: configured for UDMA/133
[ 188.523276] sd 5:0:0:0: [sdd] Starting disk
[ 190.500189] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 190.513376] ata5.00: configured for UDMA/133
[ 190.513455] sd 4:0:0:0: [sdc] Starting disk
[ 191.462213] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 191.506493] ata1.00: configured for UDMA/133
[ 191.506573] sd 0:0:0:0: [sda] Starting disk
[ 192.356977] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 192.356978] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D3DE (len 55, WS 0, PS 0) @ 0xD401
[ 192.376632] PM: resume of devices complete after 15600.251 msecs
so suspend & resume works but with caveats - now wanted to see how X is
running:
launched up lightdm & logged into xfce4.10 :
compiz-fusion (0.8*)/compositing is very very slow: e.g. when grabbing a window
at the top with left mouse button and trying to move it - it moves only for
several millimeters on screen (22'' screen with 1920x1080 resolution) - thus
unusable
when switching to xfwm4 (running Xfce4.10) moving windows around is somewhat
acceptable - appears even fluid, launching up chromium and switching between
tabs via ctrl + pgup/pgdown is noticably laggy
launching glxgears via gnome-terminal - it seemingly looks ok (gears smoothly
turning) [FPS locked to around 60]
running glxgears via: R600_LLVM=0 vblank_mode=0 glxgears
there's noticable, "micro"-stuttering and the FPS is around 260-290 if I recall
correctly
echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level
or
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
doesn't make a difference - also FPS is significantly lower compared to
"normal" operation (around 10x faster, e.g. 2900-3600 FPS with the non-DPM and
"high" profile)
next step was launching gnome-terminal from the below panel, then after sudo su
-> dmesg
and wanted to do further tests (e.g. sensors output)
-> X crashed
[ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199
last fence id 0x0000000000000198)
X (or lightdm) couldn't be launched after that anymore, VT output was still
shown - so I restarted via shutdown -r now
hope that information helps in tracking down this issue
I really love this new driver - now only operation after resume needs to work
also, since I used it quite a lot :) (it does work with the non-DPM)
similar message and behavior was seen on july 3rd/4th after several hours of
operation & uptime (no suspend and resume):
[ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199
last fence id 0x0000000000000198)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Priority: medium
Bug ID: 66963
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600: linux 3.11RC1 isn't booting with radeon.dpm=1
option in grub
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: ken20001(a)ukr.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Linux 3.11RC1 isnt' booting with radeon.dpm=1 option in grub: screen becomes
blank after grub trying to boot it. Without radeon.dpm=1 option system boots
well. So, it seems, DPM isn't working.
Graphics: Radeon HD2600 XT
Linux: 3.11RC1
OS: Kubuntu 13.04
KDE: 4.11 beta2
Please, ask me for any additional info needed to help fix this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=65091
Priority: medium
Bug ID: 65091
Assignee: dri-devel(a)lists.freedesktop.org
Summary: power_profile not working for HD5650
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: nevehanter(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
I have HD5650 with Intel i3 Ironlake (1-Gen) switcheable graphics.
My problem is that changing power_profile in radeon gives me nothing.
I have enabled KMS, use vgaswitcheroo to disable i915 and switch X to radeon.
Changing anything in radeon params at kernel parameters gives me also nothing.
It always stay at the same clocks:
For auto/low/mid/high profile
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 100000 kHz
current engine clock: 99990 kHz
default memory clock: 157000 kHz
current memory clock: 156930 kHz
voltage: 1000 mV
PCIE lanes: 16
And it should be engine: 550000 kHz and memory 800000 kHz ( values taken from
windows )
I wanted to know if you could provide fix for it, and I'm open in helping with
providing every information.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=65068
Priority: medium
Bug ID: 65068
Assignee: dri-devel(a)lists.freedesktop.org
Summary: AtomBIOS stuck after suspend/resume cycle whilst GPU
turned off
Severity: normal
Classification: Unclassified
OS: All
Reporter: austin.lund(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 79884
--> https://bugs.freedesktop.org/attachment.cgi?id=79884&action=edit
dmesg output when trying to switch back to radeon gpu.
I have two GPUs in my system:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Whistler [Radeon HD 6600M/6700M/7600M Series]
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
This is a macbookpro8,2 and hence the gmuxer is controlled by the apple-gmux
driver.
If I suspend the system to ram whilst on the integrated gpu (i.e. the intel
gpu), then after resume switch back to the radeon, I get a GPU hang.
I've attached the dmesg output that I get when I try this.
I'm using linux 3.10-rc3. I don't have X running when doing this
(vgaswitcheroo won't allow this).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=62671
Priority: medium
Bug ID: 62671
Assignee: dri-devel(a)lists.freedesktop.org
Summary: KDE thinks the monitor is reconnected each time it
resumes
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: chealer(a)gmail.com
Hardware: x86 (IA32)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
I experienced a regression after upgrading Linux from Debian's 3.2.35-2 to its
3.2.39-2. As Ben Hutchings explained to me, that is because some Linux 3.3/3.4
graphics changes were backported in Debian's 3.2.39. And indeed, if I try 3.4.4
or 3.8.3, the regression remains.
I have only experienced the problem on KDE, but I didn't try other
environments. My laptop has a Radeon HD 5650 card connected to an LCD screen
via HDMI. When I leave the laptop idle and come back after a while, the screen
resumes. What changed is that I now get 2 KDE dialogs telling me:
A monitor output has been disconnected.
Do you wish to run a configuration tool to adjust the monitor setup?
immediately followed by
A monitor output has been connected.
Do you wish to run a configuration tool to adjust the monitor setup?
(The latter shows on top) Obviously, this is incorrect. I simply press Escape
twice and the problem disappears until the next time I leave the PC. This is
just an annoyance.
I ran tail --follow on .xsession-errors to debug and found as only clue the
message "main input error: ES_OUT_RESET_PCR called" logged twice. For example,
after a monitor resume, the following had been logged:
[0x85fc680] main input error: ES_OUT_RESET_PCR called
[0xf1b0a9b8] main input error: ES_OUT_RESET_PCR called
I noticed that this error is logged every time the system detects a monitor
(dis)connection, real or spurious (On my good Linux version, a resume doesn't
trigger that error). Oddly enough, I searched the web quite a bit, asked
#debian-kde and #kde and found no one with the same problem. The
ES_OUT_RESET_PCR error is common, but in very different contexts. This does not
happen when using the vesa driver, nor when modeset is disabled, nor when I
plug the screen via VGA (the laptop has no DVI plug to test). There are no
hints in system logs.
The KDE prompts above are the standard prompts shown when a (dis)connection is
detected. Debian testing's KDE version is not the latest (4.8.4).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=62246
Priority: medium
Bug ID: 62246
Assignee: dri-devel(a)lists.freedesktop.org
Summary: LVDS screen mode switching fails
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: felix-freedesktop(a)fefe.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
I have a HP Envy 14 laptop, which has switchable graphics between:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Madison
[Radeon HD 5000M Series] (rev ff)
This used to work (I'm not using it very often, so I don't know which kernel
version broke it), and I think it caused total kernel hang in 3.0 till 3.3 or
so. Not it "works" in the sense that when a HDMI cable is connected, I get a
picture on the connected monitor. But the primary display output, LVDS-2,
stays black.
Here's the relevant dmesg parts:
agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
agpgart-intel 0000:00:00.0: detected 32768K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xb0000000
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: setting latency timer to 64
i915 0000:00:02.0: irq 40 for MSI/MSI-X
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0
ACPI: Deprecated procfs I/F for battery is loaded, please retry with
CONFIG_ACPI_PROCFS_POWER cleared
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Deprecated procfs I/F for battery is loaded, please retry with
CONFIG_ACPI_PROCFS_POWER cleared
ACPI: Battery Slot [BAT1] (battery absent)
[drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
fbcon: inteldrmfb (fb0) is primary device
Console: switching to colour frame buffer device 200x56
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
i915 0000:00:02.0: registered panic notifier
[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
acpi device:01: registered as cooling_device5
ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
[Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
acpi device:0a: registered as cooling_device6
ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no)
input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:08/LNXVIDEO:01/input/input4
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.
VGA switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle
radeon 0000:01:00.0: enabling device (0000 -> 0003)
[drm] initializing kernel modesetting (REDWOOD 0x1002:0x68C1 0x103C:0x1436).
[drm] register mmio base: 0xC4400000
[drm] register mmio size: 131072
vga_switcheroo: enabled
ATPX version 1
ATOM BIOS: MADISON
radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M
used)
radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF
mtrr: no more MTRRs available
[drm] Detected VRAM RAM=1024M, BAR=256M
[drm] RAM width 128bits DDR
[TTM] Zone kernel: Available graphics memory: 3980934 kiB
[TTM] Zone dma32: Available graphics memory: 2097152 kiB
[TTM] Initializing pool allocator
[TTM] Initializing DMA pool allocator
[drm] radeon: 1024M of VRAM memory ready
[drm] radeon: 512M of GTT memory ready.
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
radeon 0000:01:00.0: irq 45 for MSI/MSI-X
radeon 0000:01:00.0: radeon: using MSI.
[drm] radeon: irq initialized.
[drm] GART: num cpu pages 131072, num gpu pages 131072
[drm] probing gen 2 caps for device 8086:45 = 1/0
[drm] Loading REDWOOD Microcode
[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and
cpu addr 0xffff880251324c00
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and
cpu addr 0xffff880251324c0c
radeon 0000:01:00.0: enabling bus mastering
[drm] ring test on 0 succeeded in 1 usecs
[drm] ring test on 3 succeeded in 1 usecs
[drm] ib test on ring 0 succeeded in 0 usecs
[drm] ib test on ring 3 succeeded in 0 usecs
[drm] radeon atom DIG backlight initialized
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm] LVDS-2
[drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c
[drm] Encoders:
[drm] LCD1: INTERNAL_UNIPHY
[drm] Connector 1:
[drm] DP-1
[drm] HPD2
[drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c
[drm] Encoders:
[drm] DFP1: INTERNAL_UNIPHY1
[drm] Connector 2:
[drm] HDMI-A-1
[drm] HPD1
[drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[drm] Encoders:
[drm] DFP2: INTERNAL_UNIPHY1
[drm] Internal thermal controller with fan control
[drm] radeon: power management initialized
[drm] fb mappable at 0xA0142000
[drm] vram apper at 0xA0000000
[drm] size 5787648
[drm] fb depth is 24
[drm] pitch is 6400
radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device
[drm] Initialized radeon 2.29.0 20080528 for 0000:01:00.0 on minor 1
When I start the intel framebuffer, the display is also black, but I
found out that that is just the brightness set to 0, so I wrote a little
too that writes to /sys/class/backlight/acpi_video0/brightness to set a
sensible brightness.
When the radeon screen stayed black, I assumed the same problem, so I
changed my tool to also write to
/sys/class/backlight/acpi_video1/brightness, but this does not help.
To check whether this was related to VGA switcheroo interactions, I compiled a
kernel with no Intel driver in it and insmod'ed the radeon module. This time
the LVDS display stayed in text mode and "hung" in the sense that the text did
not continue scrolling.
I something is attacked on the HDMI output, that display gets a text console
when I insmod radeon.
When I start X, the LVDS screen still stays broken, but the console disappears
from the HDMI screen, and the laptop appears to hang. My default setup within
X is to have an xterm, so I moved my mouse into that xterm (without seeing any
of it) and started a shell script that uses xrandr to set up the second
display, but nothing happened. It felt as if the Intel driver still felt
responsible for LVDS.
Since I'm using X in non-radeon mode all the time, I have no Xorg.log left from
my radeon testing. I can tell you though what was in it. No (EE) lines. I
originally used X.org 1.12.3, then switched to 1.14 to see if that would make
the problem disappear. I tried the latest release versions of libdrm and
xf86-intel-radeon but when that did not work, I upgraded to the git versions of
both. No improvement.
I can try again tonight at home and produce an Xorg.0.log for you.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=59903
Priority: medium
Bug ID: 59903
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [RS880] Xorg.0.log: flip queue failed: Device or
resource busy
Severity: normal
Classification: Unclassified
OS: All
Reporter: michaell(a)gmx.org
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 73686
--> https://bugs.freedesktop.org/attachment.cgi?id=73686&action=edit
dmesg
/var/log/Xorg.0.log is full with:
[ 1599.434] (WW) RADEON(0): flip queue failed: Device or resource busy
[ 1599.434] (WW) RADEON(0): Page flip failed: Device or resource busy
running up-to-date gentoo-system, with the following (unstable) packages
linux-3.8.0-rc5 compiled a few minutes ago
xorg-server-1.13.1 compiled a few minutes ago
libdrm from git compiled a few minutes ago
mesa from git compiled a few minutes ago
xf86-video-ati from git compiled a few minutes ago
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880
[Radeon HD 4290]
my system is working as an htpc and is running fine, no crashes or oops
slim is login my user and starts xbmc automatic
xbmc in fullscreen is the only graphical application
the system is connected to my tv through hdmi
if i switch with my remote through the xbmc-menu or watch a video the xorg-log
is spam the whole time with page filp errors
if i leave xbmc alone, so the log is spam every few seconds with page flip
errors
is this related to this bug?
https://bugs.freedesktop.org/show_bug.cgi?id=58659
my system is working fine, no crashes or oops so far
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=59219
Priority: medium
Bug ID: 59219
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeon BUG] Sleeping function called from invalid
context
Severity: minor
Classification: Unclassified
OS: Linux (All)
Reporter: ebiggers3(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 72816
--> https://bugs.freedesktop.org/attachment.cgi?id=72816&action=edit
dmesg output showing 2 instances of radeon BUG during resume
I am running linux-3.8-rc3 on AMD64 with various debugging options enabled,
including CONFIG_DEBUG_SLAB. When resuming the system from suspend-to-memory,
I run into a warning and stacktrace regarding kmem_cache_alloc() being called
from an invalid context in ttm_bo_move_accel_cleanup(). dmesg output attached.
Marked as minor because suspend still works properly (at least the times I've
tried it).
Based on the source code and object file it appears that the memory allocation
is actually the kzalloc() at the beginning of ttm_buffer_object_transfer().
Graphics card is:
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880M
[Mobility Radeon HD 4200 Series]
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58914
Priority: medium
Bug ID: 58914
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Cannot start Radeon driver: "drmOpenByBusid:
drmGetBusid reports " no bus ID
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: david.hagood(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 72358
--> https://bugs.freedesktop.org/attachment.cgi?id=72358&action=edit
X Start up log messages
The Radeon driver will not load with the Radeon kernel drivers in Linux 3.8.0
The following is an excerpt from the startup:
[ 109.112] (II) Loading extension DRI2
[ 109.112] (II) LoadModule: "radeon"
[ 109.112] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 109.112] (II) Module radeon: vendor="X.Org Foundation"
[ 109.112] compiled for 1.12.3, module version = 7.0.99
[ 109.112] Module class: X.Org Video Driver
[ 109.112] ABI class: X.Org Video Driver, version 12.0
[ 109.112] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
(many cards snipped)
[ 109.114] (--) using VT number 8
[ 109.119] (II) [KMS] Kernel modesetting enabled.
[ 109.120] (II) RADEON(0): Creating default Display subsection in Screen
section
"Default Screen Section" for depth/fbbpp 24/32
[ 109.120] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 109.120] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp
pixmaps)
[ 109.120] (==) RADEON(0): Default visual is TrueColor
[ 109.120] (==) RADEON(0): RGB weight 888
[ 109.120] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 109.120] (--) RADEON(0): Chipset: "ATI Radeon HD 4350" (ChipID = 0x954f)
[ 109.120] drmOpenDevice: node name is /dev/dri/card0
[ 109.120] drmOpenDevice: open result is 9, (OK)
[ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0
[ 109.120] drmOpenDevice: node name is /dev/dri/card0
[ 109.120] drmOpenDevice: open result is 9, (OK)
[ 109.120] drmOpenByBusid: drmOpenMinor returns 9
[ 109.120] drmOpenByBusid: Searching for BusID pci:0000:04:00.0
[ 109.120] drmOpenDevice: node name is /dev/dri/card0
[ 109.120] drmOpenDevice: open result is 9, (OK)
[ 109.120] drmOpenByBusid: drmOpenMinor returns 9
[ 109.120] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 109.120] drmOpenByBusid: drmGetBusid reports
That last line is not a copy/paste issue - it literally is
"[ 109.120] drmOpenByBusid: drmGetBusid reports "
(as in, there is no bus ID given)
Then the X Radeon driver looks for any other DRI node, fails, and dies.
[ 109.120] drmOpenDevice: node name is /dev/dri/card1
[ 109.125] drmOpenByBusid: drmOpenMinor returns -1
(snip many other searches)
[ 109.170] drmOpenDevice: node name is /dev/dri/card14
[ 109.174] drmOpenByBusid: drmOpenMinor returns -1
[ 109.174] drmOpenDevice: node name is /dev/dri/card15
[ 109.178] drmOpenByBusid: drmOpenMinor returns -1
[ 109.178] drmOpenDevice: node name is /dev/dri/card0
[ 109.178] drmOpenDevice: open result is 9, (OK)
[ 109.178] drmOpenDevice: node name is /dev/dri/card0
[ 109.178] drmOpenDevice: open result is 9, (OK)
[ 109.178] drmGetBusid returned ''
[ 109.178] (EE) RADEON(0): [drm] failed to set drm interface version.
[ 109.178] (EE) RADEON(0): Kernel modesetting setup failed
[ 109.178] (II) UnloadModule: "radeon"
[ 109.178] (EE) Screen(s) found, but none have a usable configuration.
I have tried the following:
1) adding the following parameters in /etc/modprobe.d/radeon.conf
options radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1
2) Adding the following to /etc/initramfs-tools/modules
radeon modeset=1 dynclks=1 gartsize=256 audio=1 pcie_gen2=-1 msi=1
and rebuilding the ramdisk.
The kernel has the following configuration with respect to the Radeon drivers:
CONFIG_DRM_RADEON=m
CONFIG_DRM_RADEON_KMS=y
# CONFIG_FB_RADEON is not set
--
You are receiving this mail because:
You are the assignee for the bug.