<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - On system boot both DIS and IGD cards are powered on."
href="https://bugs.freedesktop.org/show_bug.cgi?id=61114#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - On system boot both DIS and IGD cards are powered on."
href="https://bugs.freedesktop.org/show_bug.cgi?id=61114">bug 61114</a>
from <span class="vcard"><a class="email" href="mailto:pishposh.mcgee@gmail.com" title="PishPosh <pishposh.mcgee@gmail.com>"> <span class="fn">PishPosh</span></a>
</span></b>
<pre>I have this same problem on an HP dm4t-1100 with hybrid Radeon 5450/Intel
graphics. I'm not certain that it is caused by the devices both being powered
on at system start - the power-up state of both devices was 'ON' before and
after kernel 3.6.
However, kernel 3.6 caused several changes in behavior - it was the first
kernel where 'DIS-Audio' showed up in addition to 'DIS' in the switcher
debugfs.
The full set of outputs shows up in XRandR for both devices on boot. My dm4t
has the internal LVDS and an external VGA, plus an HDMI which is only
accessible when the radeon driver is in use. So I get output such as the
following (with the exception that the different outputs are offset differently
by default):
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis)
309mm x 173mm
1366x768 60.1*+ 40.1
1360x768 59.8 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
LVDS-1-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 0mm
x 0mm
1366x768 60.1*+
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x600 59.9
848x480 59.7
720x480 59.7
640x480 59.4
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
VGA-1-1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3 56.2
848x480 60.0
640x480 59.9
1366x768 (0x47) 69.3MHz
h: width 1366 start 1404 end 1426 total 1436 skew 0 clock 48.3KHz
v: height 768 start 771 end 777 total 803 clock 60.1Hz
1024x768 (0xc2) 65.0MHz
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
v: height 768 start 771 end 777 total 806 clock 60.0Hz
800x600 (0xc3) 40.0MHz
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
v: height 600 start 601 end 605 total 628 clock 60.3Hz
800x600 (0xc4) 36.0MHz
h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz
v: height 600 start 601 end 603 total 625 clock 56.2Hz
If I log out I get the following message, looping as you can see every 5
seconds for about 40 seconds:
Oct 26 19:40:15 laptux-prime kernel: [ 214.073219] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:15 laptux-prime kernel: [ 214.073228]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:20 laptux-prime kernel: [ 219.077108] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:20 laptux-prime kernel: [ 219.077117]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:25 laptux-prime kernel: [ 224.080995] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:25 laptux-prime kernel: [ 224.081006]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:30 laptux-prime kernel: [ 229.084901] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:30 laptux-prime kernel: [ 229.084908]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:35 laptux-prime kernel: [ 234.088826] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:35 laptux-prime kernel: [ 234.088838]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:40 laptux-prime kernel: [ 239.092694] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:40 laptux-prime kernel: [ 239.092703]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:45 laptux-prime kernel: [ 244.096586] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:45 laptux-prime kernel: [ 244.096599]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:50 laptux-prime kernel: [ 249.100456] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Oct 26 19:40:50 laptux-prime kernel: [ 249.100462]
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62,
WS 0, PS 0) @ 0xCEC2
Oct 26 19:40:55 laptux-prime kernel: [ 254.104400] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 5secs aborting
Then, X will come back up (in my case to the gdm greeter). I can log in and the
radeon-based drivers will not show up, at least if I'm running on the
integrated driver.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>