Bug 62882 - Lockup after attempt to enable discrete Radeon GPU on Linux 3.9rc4
Summary: Lockup after attempt to enable discrete Radeon GPU on Linux 3.9rc4
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-28 21:50 UTC by russianneuromancer
Modified: 2013-04-01 01:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
crash log (6.47 KB, text/plain)
2013-03-28 21:50 UTC, russianneuromancer
no flags Details

Description russianneuromancer 2013-03-28 21:50:43 UTC
Created attachment 77173 [details]
crash log

When I try to enable discrete GPU I get kernel module crash (please look into attached log) and system lockup (few seconds later).

Software:
Kubuntu 13.04 x86_64 updated from Canonical X Staging PPA (there is just stable X.Org Server 1.14, stable Mesa 9.1 and stable 7.1.0 radeon driver)
Linux 3.9rc4 
Mesa: 9.1
libdrm-radeon1: 2.4.43
xserver-xorg-video-radeon: 7.1.0
xserver-xorg-core: 1.14.0

Hardware:
Acer Aspire 7560G laptop,
AMD APU A8-3500M with integrated Radeon HD 6620G (SUMO)
Discrete AMD Radeon HD 6650M (TURKS)

"xrandr --listproviders" output:
Providers: number : 2
Provider 0: id: 138 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 1 name:radeon
Provider 1: id: 85 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 1 name:radeon
Comment 1 Alex Deucher 2013-03-28 22:14:34 UTC
Your dGPU is not powering up for some reason.
Comment 2 russianneuromancer 2013-04-01 01:01:12 UTC
Tested with proprietary driver - issues reproducible (GPU not power-up without reboot) so probably problems with hardware or maybe BIOS.


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.