On system boot from kernels post 3.6, both the discrete radeon and integrated intel card are powered on. This creates confusion in Xorg since it believes there are two displays - It creates a smaller box on the top left of screen as it attempts to use both. It can cause kernel panics during suspend resume. cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD: :Pwr:0000:00:02.0 1:DIS:+:Pwr:0000:01:00.0 2:DIS-Audio:+:Pwr:0000:01:00.1 Should be cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD: :Off:0000:00:02.0 1:DIS:+:Pwr:0000:01:00.0 2:DIS-Audio:+:Pwr:0000:01:00.1 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M Series] The system is an apple macbook pro 8,2 with gmux using EFI.
no we never turn off either card, can you post the X org log? since your diagnosis of the problem seems way off.
Created attachment 83744 [details] Output of vgaswitch, xorg.0.log and dmesg Here is the Xorg.0.log, dmesg and output of vgaswitch. I have taken no steps to alter the behaviour : IE this is how a default install of linux functions on an MBP 8,2. There is no external monitor connected to the system at this time : Only the inbuilt panel that is connected via LVDS.
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.
Hmmmm... Additionally, if I try to switch to the radeon driver (either from the first state, where both sets of outputs are available, or from the second state, where only the intel outputs are available), it often fails to switch, giving Oct 26 21:45:57 laptux-prime kernel: [ 219.271775] vga_switcheroo: processing delayed switch to 1 Oct 26 21:45:57 laptux-prime kernel: [ 219.271784] vga_switcheroo: client 101 refused switch If gdm comes up, regardless of the previous state (one driver's outputs or two), I will find that once again the outputs for both drivers are available, so once again there are phantom LVDS and VGA devices. xrandr lists nearly the same outputs, except that those for the radeon driver are now like 'LVDS-1' rather than 'LVDS-1-1', as they typically are on first boot. After some repeated assertions of echoing ON and DDIS to /sys/kernel/debug/vgaswitcheroo/switch (a deterministic procedure for which I have not managed to identify), I can get X/gdm to come back up under the radeon driver, at which point only the radeon-specific outputs are visible to XRandR and the vgaswitcheroo state is: 0:IGD: :Off:0000:00:02.0 1:DIS:+:Pwr:0000:01:00.0 2:DIS-Audio: :Pwr:0000:01:00.1 I'm also attaching my Xorg.0.log. I can get dmesg, but kernel 3.11 has a separate bug that keeps spamming it with unrelated errors, and I'd need to determine what to grep out of it.
Created attachment 88164 [details] Xorg.0.log - hp dm4t-1100 Mobile Radeon HD 5450/Intel hybrid This log includes a boot-up during which the radeon device is turned off. Then the radeon device is powered back on. This is followed by several failed attempts to switch to the radeon device. Toward the end there is a successful change to the radeon device, at which point the intel device should be powered off.
Please retest with latest upstream, specifically drm-intel-nightly from http://cgit.freedesktop.org/drm-intel We've reworked the vgaswitcheroo handling in i915, so things might have improved.
Bug report seems to have gone missing unfortunately, so closing. If this is still an issue on latest kernels please reopen.
This is still the case. Both cards are powered on at boot with kernel 3.18.
Trying to contact Daniel in order to see if we have a solution for this bug since there wasn't activity since december last year
(In reply to William Brown from comment #8) > This is still the case. Both cards are powered on at boot with kernel 3.18. Timeout, closing, please reopen if the problem persists with latest kernels.
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.