[Kernel-packages] [Bug 1396961] Re: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396961 Title: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972) Status in linux package in Ubuntu: Expired Bug description: First seen after upgrading from precise to trusty, reproducible with both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS 07/29/2008 . The information that follows is mostly from booting 3.13.0 with drm.debug=4. (The apport attachment is from 3.16.0-25.33, however.) Symptom: at variable intervals (minutes to hours), starting immediately after boot, the kernel logs a pair of WARNING messages from drivers/gpu/drm/i915/intel_display.c:4197 and drivers/gpu/drm/i915/intel_display.c:4199: wrong connector dpms state active connector not linked to encoder The computer uses Intel integrated graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:300b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 18c0 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 The only attached display, via a DVI cable, is an Acer: [51.628] (II) intel(0): EDID vendor ACR, prod id 2032 It looks to me like the kernel is of two minds as to whether connector 10 (VGA-2) is connected or not. Eventually it concludes, correctly, that it is disconnected, but intel_sdvo_detect() thinks that it is connected and -get_hw_state() is fooled by this. The warnings reflect this confusion. There is no obvious loss of function but the warnings are noisy and I'd like to get rid of them. Here is a subset of kernel messages that seem relevant: [...] Nov 19 15:27:09 s1mt02 kernel: [0.584452] vesafb: mode is 1600x1200x32, line length=6400, pages=0 Nov 19 15:27:09 s1mt02 kernel: [0.584454] vesafb: scrolling: redraw Nov 19 15:27:09 s1mt02 kernel: [0.584456] vesafb: Truecolor: size=8:8:8:8, s hift=24:16:8:0 Nov 19 15:27:09 s1mt02 kernel: [0.585182] vesafb: framebuffer at 0xc000, mapped to 0xc9000118, using 7552k, total 7552k Nov 19 15:27:09 s1mt02 kernel: [0.662752] Console: switching to colour frame buffer device 200x75 [...] Nov 19 15:27:10 s1mt02 kernel: [ 10.529074] [drm] Initialized drm 1.1.0 20060810 Nov 19 15:27:10 s1mt02 kernel: [ 11.342875] [drm:intel_detect_pch], No PCH found. Nov 19 15:27:10 s1mt02 kernel: [ 11.342882] [drm] Memory usable by graphics device = 512M Nov 19 15:27:10 s1mt02 kernel: [ 11.342885] checking generic (c000 76) vs hw (c000 1000) Nov 19 15:27:10 s1mt02 kernel: [ 11.342887] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Nov 19 15:27:10 s1mt02 kernel: [ 11.342919] Console: switching to colour dummy device 80x25 Nov 19 15:27:10 s1mt02 kernel: [ 11.392088] i915 :00:02.0: irq 43 for MSI/MSI-X Nov 19 15:27:10 s1mt02 kernel: [ 11.392106] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Nov 19 15:27:10 s1mt02 kernel: [ 11.392109] [drm] Driver supports precise vblank timestamp query. Nov 19 15:27:10 s1mt02 kernel: [ 11.392113] [drm:init_vbt_defaults], Set default to SSC at 100MHz Nov 19 15:27:10 s1mt02 kernel: [ 11.392119] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT BROADWATER-G d Nov 19 15:27:10 s1mt02 kernel: [ 11.392123] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 96 display_clock_mode 0 fdi_rx_polarity_inverted 0 Nov 19 15:27:10 s1mt02 kernel: [ 11.392129] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 Nov 19 15:27:10 s1mt02 kernel: [ 11.392135] [drm:parse_sdvo_panel_data], Found SDVO panel mode in BIOS VBT tables: Nov 19 15:27:10 s1mt02 kernel: [ 11.392139]
[Kernel-packages] [Bug 1396961] Re: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972)
I'm unable to run apport-collect but the bug description already contains detailed information from the logs. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396961 Title: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972) Status in “linux” package in Ubuntu: Confirmed Bug description: First seen after upgrading from precise to trusty, reproducible with both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS 07/29/2008 . The information that follows is mostly from booting 3.13.0 with drm.debug=4. (The apport attachment is from 3.16.0-25.33, however.) Symptom: at variable intervals (minutes to hours), starting immediately after boot, the kernel logs a pair of WARNING messages from drivers/gpu/drm/i915/intel_display.c:4197 and drivers/gpu/drm/i915/intel_display.c:4199: wrong connector dpms state active connector not linked to encoder The computer uses Intel integrated graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:300b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 18c0 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 The only attached display, via a DVI cable, is an Acer: [51.628] (II) intel(0): EDID vendor ACR, prod id 2032 It looks to me like the kernel is of two minds as to whether connector 10 (VGA-2) is connected or not. Eventually it concludes, correctly, that it is disconnected, but intel_sdvo_detect() thinks that it is connected and -get_hw_state() is fooled by this. The warnings reflect this confusion. There is no obvious loss of function but the warnings are noisy and I'd like to get rid of them. Here is a subset of kernel messages that seem relevant: [...] Nov 19 15:27:09 s1mt02 kernel: [0.584452] vesafb: mode is 1600x1200x32, line length=6400, pages=0 Nov 19 15:27:09 s1mt02 kernel: [0.584454] vesafb: scrolling: redraw Nov 19 15:27:09 s1mt02 kernel: [0.584456] vesafb: Truecolor: size=8:8:8:8, s hift=24:16:8:0 Nov 19 15:27:09 s1mt02 kernel: [0.585182] vesafb: framebuffer at 0xc000, mapped to 0xc9000118, using 7552k, total 7552k Nov 19 15:27:09 s1mt02 kernel: [0.662752] Console: switching to colour frame buffer device 200x75 [...] Nov 19 15:27:10 s1mt02 kernel: [ 10.529074] [drm] Initialized drm 1.1.0 20060810 Nov 19 15:27:10 s1mt02 kernel: [ 11.342875] [drm:intel_detect_pch], No PCH found. Nov 19 15:27:10 s1mt02 kernel: [ 11.342882] [drm] Memory usable by graphics device = 512M Nov 19 15:27:10 s1mt02 kernel: [ 11.342885] checking generic (c000 76) vs hw (c000 1000) Nov 19 15:27:10 s1mt02 kernel: [ 11.342887] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Nov 19 15:27:10 s1mt02 kernel: [ 11.342919] Console: switching to colour dummy device 80x25 Nov 19 15:27:10 s1mt02 kernel: [ 11.392088] i915 :00:02.0: irq 43 for MSI/MSI-X Nov 19 15:27:10 s1mt02 kernel: [ 11.392106] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Nov 19 15:27:10 s1mt02 kernel: [ 11.392109] [drm] Driver supports precise vblank timestamp query. Nov 19 15:27:10 s1mt02 kernel: [ 11.392113] [drm:init_vbt_defaults], Set default to SSC at 100MHz Nov 19 15:27:10 s1mt02 kernel: [ 11.392119] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT BROADWATER-G d Nov 19 15:27:10 s1mt02 kernel: [ 11.392123] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 96 display_clock_mode 0 fdi_rx_polarity_inverted 0 Nov 19 15:27:10 s1mt02 kernel: [ 11.392129] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 Nov 19 15:27:10 s1mt02 kernel: [ 11.392135] [drm:parse_sdvo_panel_data], Found SDVO panel mode in BIOS VBT tables: Nov
[Kernel-packages] [Bug 1396961] Re: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972)
Sergio Gelato, could you please specify why exactly you cannot run the apport-collect? ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396961 Title: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972) Status in “linux” package in Ubuntu: Incomplete Bug description: First seen after upgrading from precise to trusty, reproducible with both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS 07/29/2008 . The information that follows is mostly from booting 3.13.0 with drm.debug=4. (The apport attachment is from 3.16.0-25.33, however.) Symptom: at variable intervals (minutes to hours), starting immediately after boot, the kernel logs a pair of WARNING messages from drivers/gpu/drm/i915/intel_display.c:4197 and drivers/gpu/drm/i915/intel_display.c:4199: wrong connector dpms state active connector not linked to encoder The computer uses Intel integrated graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:300b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 18c0 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 The only attached display, via a DVI cable, is an Acer: [51.628] (II) intel(0): EDID vendor ACR, prod id 2032 It looks to me like the kernel is of two minds as to whether connector 10 (VGA-2) is connected or not. Eventually it concludes, correctly, that it is disconnected, but intel_sdvo_detect() thinks that it is connected and -get_hw_state() is fooled by this. The warnings reflect this confusion. There is no obvious loss of function but the warnings are noisy and I'd like to get rid of them. Here is a subset of kernel messages that seem relevant: [...] Nov 19 15:27:09 s1mt02 kernel: [0.584452] vesafb: mode is 1600x1200x32, line length=6400, pages=0 Nov 19 15:27:09 s1mt02 kernel: [0.584454] vesafb: scrolling: redraw Nov 19 15:27:09 s1mt02 kernel: [0.584456] vesafb: Truecolor: size=8:8:8:8, s hift=24:16:8:0 Nov 19 15:27:09 s1mt02 kernel: [0.585182] vesafb: framebuffer at 0xc000, mapped to 0xc9000118, using 7552k, total 7552k Nov 19 15:27:09 s1mt02 kernel: [0.662752] Console: switching to colour frame buffer device 200x75 [...] Nov 19 15:27:10 s1mt02 kernel: [ 10.529074] [drm] Initialized drm 1.1.0 20060810 Nov 19 15:27:10 s1mt02 kernel: [ 11.342875] [drm:intel_detect_pch], No PCH found. Nov 19 15:27:10 s1mt02 kernel: [ 11.342882] [drm] Memory usable by graphics device = 512M Nov 19 15:27:10 s1mt02 kernel: [ 11.342885] checking generic (c000 76) vs hw (c000 1000) Nov 19 15:27:10 s1mt02 kernel: [ 11.342887] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Nov 19 15:27:10 s1mt02 kernel: [ 11.342919] Console: switching to colour dummy device 80x25 Nov 19 15:27:10 s1mt02 kernel: [ 11.392088] i915 :00:02.0: irq 43 for MSI/MSI-X Nov 19 15:27:10 s1mt02 kernel: [ 11.392106] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Nov 19 15:27:10 s1mt02 kernel: [ 11.392109] [drm] Driver supports precise vblank timestamp query. Nov 19 15:27:10 s1mt02 kernel: [ 11.392113] [drm:init_vbt_defaults], Set default to SSC at 100MHz Nov 19 15:27:10 s1mt02 kernel: [ 11.392119] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT BROADWATER-G d Nov 19 15:27:10 s1mt02 kernel: [ 11.392123] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 96 display_clock_mode 0 fdi_rx_polarity_inverted 0 Nov 19 15:27:10 s1mt02 kernel: [ 11.392129] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 Nov 19 15:27:10 s1mt02 kernel: [ 11.392135] [drm:parse_sdvo_panel_data], Found SDVO panel mode in BIOS
Re: [Kernel-packages] [Bug 1396961] Re: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972)
* Christopher M. Penalver [2014-11-27 20:21:56 +]: Sergio Gelato, could you please specify why exactly you cannot run the apport-collect? The authorization page doesn't work in my default browser (lynx); I get an error page after authentication. I've tried opening it in Firefox but didn't get anywhere either. I'd be happy to run apport-cli with the output sent to a local file, then upload that as an attachment (in case the apport output I attached when I filed the bug isn't enough). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396961 Title: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972) Status in “linux” package in Ubuntu: Incomplete Bug description: First seen after upgrading from precise to trusty, reproducible with both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS 07/29/2008 . The information that follows is mostly from booting 3.13.0 with drm.debug=4. (The apport attachment is from 3.16.0-25.33, however.) Symptom: at variable intervals (minutes to hours), starting immediately after boot, the kernel logs a pair of WARNING messages from drivers/gpu/drm/i915/intel_display.c:4197 and drivers/gpu/drm/i915/intel_display.c:4199: wrong connector dpms state active connector not linked to encoder The computer uses Intel integrated graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:300b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 18c0 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 The only attached display, via a DVI cable, is an Acer: [51.628] (II) intel(0): EDID vendor ACR, prod id 2032 It looks to me like the kernel is of two minds as to whether connector 10 (VGA-2) is connected or not. Eventually it concludes, correctly, that it is disconnected, but intel_sdvo_detect() thinks that it is connected and -get_hw_state() is fooled by this. The warnings reflect this confusion. There is no obvious loss of function but the warnings are noisy and I'd like to get rid of them. Here is a subset of kernel messages that seem relevant: [...] Nov 19 15:27:09 s1mt02 kernel: [0.584452] vesafb: mode is 1600x1200x32, line length=6400, pages=0 Nov 19 15:27:09 s1mt02 kernel: [0.584454] vesafb: scrolling: redraw Nov 19 15:27:09 s1mt02 kernel: [0.584456] vesafb: Truecolor: size=8:8:8:8, s hift=24:16:8:0 Nov 19 15:27:09 s1mt02 kernel: [0.585182] vesafb: framebuffer at 0xc000, mapped to 0xc9000118, using 7552k, total 7552k Nov 19 15:27:09 s1mt02 kernel: [0.662752] Console: switching to colour frame buffer device 200x75 [...] Nov 19 15:27:10 s1mt02 kernel: [ 10.529074] [drm] Initialized drm 1.1.0 20060810 Nov 19 15:27:10 s1mt02 kernel: [ 11.342875] [drm:intel_detect_pch], No PCH found. Nov 19 15:27:10 s1mt02 kernel: [ 11.342882] [drm] Memory usable by graphics device = 512M Nov 19 15:27:10 s1mt02 kernel: [ 11.342885] checking generic (c000 76) vs hw (c000 1000) Nov 19 15:27:10 s1mt02 kernel: [ 11.342887] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Nov 19 15:27:10 s1mt02 kernel: [ 11.342919] Console: switching to colour dummy device 80x25 Nov 19 15:27:10 s1mt02 kernel: [ 11.392088] i915 :00:02.0: irq 43 for MSI/MSI-X Nov 19 15:27:10 s1mt02 kernel: [ 11.392106] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Nov 19 15:27:10 s1mt02 kernel: [ 11.392109] [drm] Driver supports precise vblank timestamp query. Nov 19 15:27:10 s1mt02 kernel: [ 11.392113] [drm:init_vbt_defaults], Set default to SSC at 100MHz Nov 19 15:27:10 s1mt02 kernel: [ 11.392119] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT BROADWATER-G d Nov 19 15:27:10 s1mt02 kernel: [ 11.392123] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 1 lvds_use_ssc 0
[Kernel-packages] [Bug 1396961] Re: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972)
Sergio Gelato, could you please boot into a live environment via http://cdimage.ubuntu.com/daily-live/current/ and then execute via a terminal: apport-collect 1396961 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1396961 Title: WARNING: wrong connector dpms state (Intel 82946GZ/GL, 8086:2972) Status in “linux” package in Ubuntu: Incomplete Bug description: First seen after upgrading from precise to trusty, reproducible with both trusty (3.13.0-40) and backported utopic (3.16.0-25) kernels on the following hardware/BIOS: LENOVO 963673G/LENOVO, BIOS 2QKT29AUS 07/29/2008 . The information that follows is mostly from booting 3.13.0 with drm.debug=4. (The apport attachment is from 3.16.0-25.33, however.) Symptom: at variable intervals (minutes to hours), starting immediately after boot, the kernel logs a pair of WARNING messages from drivers/gpu/drm/i915/intel_display.c:4197 and drivers/gpu/drm/i915/intel_display.c:4199: wrong connector dpms state active connector not linked to encoder The computer uses Intel integrated graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:300b] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at d000 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 18c0 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 The only attached display, via a DVI cable, is an Acer: [51.628] (II) intel(0): EDID vendor ACR, prod id 2032 It looks to me like the kernel is of two minds as to whether connector 10 (VGA-2) is connected or not. Eventually it concludes, correctly, that it is disconnected, but intel_sdvo_detect() thinks that it is connected and -get_hw_state() is fooled by this. The warnings reflect this confusion. There is no obvious loss of function but the warnings are noisy and I'd like to get rid of them. Here is a subset of kernel messages that seem relevant: [...] Nov 19 15:27:09 s1mt02 kernel: [0.584452] vesafb: mode is 1600x1200x32, line length=6400, pages=0 Nov 19 15:27:09 s1mt02 kernel: [0.584454] vesafb: scrolling: redraw Nov 19 15:27:09 s1mt02 kernel: [0.584456] vesafb: Truecolor: size=8:8:8:8, s hift=24:16:8:0 Nov 19 15:27:09 s1mt02 kernel: [0.585182] vesafb: framebuffer at 0xc000, mapped to 0xc9000118, using 7552k, total 7552k Nov 19 15:27:09 s1mt02 kernel: [0.662752] Console: switching to colour frame buffer device 200x75 [...] Nov 19 15:27:10 s1mt02 kernel: [ 10.529074] [drm] Initialized drm 1.1.0 20060810 Nov 19 15:27:10 s1mt02 kernel: [ 11.342875] [drm:intel_detect_pch], No PCH found. Nov 19 15:27:10 s1mt02 kernel: [ 11.342882] [drm] Memory usable by graphics device = 512M Nov 19 15:27:10 s1mt02 kernel: [ 11.342885] checking generic (c000 76) vs hw (c000 1000) Nov 19 15:27:10 s1mt02 kernel: [ 11.342887] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Nov 19 15:27:10 s1mt02 kernel: [ 11.342919] Console: switching to colour dummy device 80x25 Nov 19 15:27:10 s1mt02 kernel: [ 11.392088] i915 :00:02.0: irq 43 for MSI/MSI-X Nov 19 15:27:10 s1mt02 kernel: [ 11.392106] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Nov 19 15:27:10 s1mt02 kernel: [ 11.392109] [drm] Driver supports precise vblank timestamp query. Nov 19 15:27:10 s1mt02 kernel: [ 11.392113] [drm:init_vbt_defaults], Set default to SSC at 100MHz Nov 19 15:27:10 s1mt02 kernel: [ 11.392119] [drm:intel_parse_bios], Using VBT from OpRegion: $VBT BROADWATER-G d Nov 19 15:27:10 s1mt02 kernel: [ 11.392123] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 1 lvds_use_ssc 0 lvds_ssc_freq 96 display_clock_mode 0 fdi_rx_polarity_inverted 0 Nov 19 15:27:10 s1mt02 kernel: [ 11.392129] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 Nov 19 15:27:10 s1mt02 kernel: [ 11.392135] [drm:parse_sdvo_panel_data], Found SDVO panel mode in BIOS VBT tables: Nov 19 15:27:10 s1mt02 kernel: [
