[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Tue, Dec 03, 2013 at 11:03:05PM +0100, Paul Bolle wrote: > On Tue, 2013-12-03 at 16:19 +0100, Daniel Vetter wrote: > > I'd like to confirm the actual cause (I suspect that we switch > > pipes around) for why you see this but other machines don't show > > this to augment the commit message. But I've merged the fix already. > > The dmesg, up to and including the WARNING, is attached. Have fun! Yeah, we have a machine where we want to switch planes/pipes and it all blows to pieces while we try to fix that up. Usually the bios does that already, so no need for us to change anything. And it's only used on old gen2/3 machines. Theory perfectly confirmed, thanks ;-) -Daniel > > > Paul Bolle > > <6>[0.00] Initializing cgroup subsys cpuset > <6>[0.00] Initializing cgroup subsys cpu > <6>[0.00] Initializing cgroup subsys cpuacct > <5>[0.00] Linux version 3.13.0-0.rc2.1.local1.fc18.i686 ([...]) (gcc > version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #1 SMP Sun Dec 1 11:58:49 > CET 2013 > <6>[0.00] Disabled fast string operations > <6>[0.00] e820: BIOS-provided physical RAM map: > <6>[0.00] BIOS-e820: [mem 0x-0x0009efff] > usable > <6>[0.00] BIOS-e820: [mem 0x0009f000-0x0009] > reserved > <6>[0.00] BIOS-e820: [mem 0x000d-0x000d3fff] > reserved > <6>[0.00] BIOS-e820: [mem 0x000dc000-0x000f] > reserved > <6>[0.00] BIOS-e820: [mem 0x0010-0x7f6d] > usable > <6>[0.00] BIOS-e820: [mem 0x7f6e-0x7f6f4fff] ACPI > data > <6>[0.00] BIOS-e820: [mem 0x7f6f5000-0x7f6f] ACPI > NVS > <6>[0.00] BIOS-e820: [mem 0x7f70-0x7fff] > reserved > <6>[0.00] BIOS-e820: [mem 0xe000-0xefff] > reserved > <6>[0.00] BIOS-e820: [mem 0xf0008000-0xf000bfff] > reserved > <6>[0.00] BIOS-e820: [mem 0xfec0-0xfec0] > reserved > <6>[0.00] BIOS-e820: [mem 0xfed14000-0xfed19fff] > reserved > <6>[0.00] BIOS-e820: [mem 0xfed2-0xfed8] > reserved > <6>[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] > reserved > <6>[0.00] BIOS-e820: [mem 0xff00-0x] > reserved > <5>[0.00] Notice: NX (Execute Disable) protection cannot be enabled: > non-PAE kernel! > <6>[0.00] SMBIOS 2.3 present. > <7>[0.00] DMI: IBM 2525FAG/2525FAG, BIOS 74ET61WW (2.06 ) 03/14/2006 > <7>[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved > <7>[0.00] e820: remove [mem 0x000a-0x000f] usable > <6>[0.00] e820: last_pfn = 0x7f6e0 max_arch_pfn = 0x10 > <7>[0.00] MTRR default type: uncachable > <7>[0.00] MTRR fixed ranges enabled: > <7>[0.00] 0-9 write-back > <7>[0.00] A-B uncachable > <7>[0.00] C-C write-protect > <7>[0.00] D-DBFFF uncachable > <7>[0.00] DC000-D write-back > <7>[0.00] E-F write-protect > <7>[0.00] MTRR variable ranges enabled: > <7>[0.00] 0 base 0 mask F8000 write-back > <7>[0.00] 1 base 07F70 mask 0 uncachable > <7>[0.00] 2 base 07F80 mask FFF80 uncachable > <7>[0.00] 3 disabled > <7>[0.00] 4 disabled > <7>[0.00] 5 disabled > <7>[0.00] 6 disabled > <7>[0.00] 7 disabled > <6>[0.00] PAT not supported by CPU. > <7>[0.00] initial memory mapped: [mem 0x-0x013f] > <7>[0.00] Base memory trampoline at [c009b000] 9b000 size 16384 > <6>[0.00] init_memory_mapping: [mem 0x-0x000f] > <7>[0.00] [mem 0x-0x000f] page 4k > <6>[0.00] init_memory_mapping: [mem 0x36c0-0x36ff] > <7>[0.00] [mem 0x36c0-0x36ff] page 2M > <6>[0.00] init_memory_mapping: [mem 0x3000-0x36bf] > <7>[0.00] [mem 0x3000-0x36bf] page 2M > <6>[0.00] init_memory_mapping: [mem 0x0010-0x2fff] > <7>[0.00] [mem 0x0010-0x003f] page 4k > <7>[0.00] [mem 0x0040-0x2fff] page 2M > <6>[0.00] init_memory_mapping: [mem 0x3700-0x373fdfff] > <7>[0.00] [mem 0x3700-0x373fdfff] page 4k > <7>[0.00] BRK [0x00e6d000, 0x00e6dfff] PGTABLE > <7>[0.00] BRK [0x00e6e000, 0x00e6] PGTABLE > <6>[0.00] RAMDISK: [mem 0x33f7c000-0x35fb5fff] > <5>[0.00] ACPI: RSDP 000f6c00 24 (v02 IBM ) > <5>[0.00] ACPI: XSDT 7f6e4770 5C (v01 IBMTP-742060 > LTP ) > <5>[0.00] ACPI: FACP 7f6e4800 F4 (v03 IBMTP-742060 > IBM 0001) > <5>[0.00] ACPI BIOS
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Tue, 2013-12-03 at 16:19 +0100, Daniel Vetter wrote: > I'd like to confirm the actual cause (I suspect that we switch > pipes around) for why you see this but other machines don't show > this to augment the commit message. But I've merged the fix already. The dmesg, up to and including the WARNING, is attached. Have fun! Paul Bolle <6>[0.00] Initializing cgroup subsys cpuset <6>[0.00] Initializing cgroup subsys cpu <6>[0.00] Initializing cgroup subsys cpuacct <5>[0.00] Linux version 3.13.0-0.rc2.1.local1.fc18.i686 ([...]) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #1 SMP Sun Dec 1 11:58:49 CET 2013 <6>[0.00] Disabled fast string operations <6>[0.00] e820: BIOS-provided physical RAM map: <6>[0.00] BIOS-e820: [mem 0x-0x0009efff] usable <6>[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved <6>[0.00] BIOS-e820: [mem 0x000d-0x000d3fff] reserved <6>[0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved <6>[0.00] BIOS-e820: [mem 0x0010-0x7f6d] usable <6>[0.00] BIOS-e820: [mem 0x7f6e-0x7f6f4fff] ACPI data <6>[0.00] BIOS-e820: [mem 0x7f6f5000-0x7f6f] ACPI NVS <6>[0.00] BIOS-e820: [mem 0x7f70-0x7fff] reserved <6>[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved <6>[0.00] BIOS-e820: [mem 0xf0008000-0xf000bfff] reserved <6>[0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved <6>[0.00] BIOS-e820: [mem 0xfed14000-0xfed19fff] reserved <6>[0.00] BIOS-e820: [mem 0xfed2-0xfed8] reserved <6>[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved <6>[0.00] BIOS-e820: [mem 0xff00-0x] reserved <5>[0.00] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! <6>[0.00] SMBIOS 2.3 present. <7>[0.00] DMI: IBM 2525FAG/2525FAG, BIOS 74ET61WW (2.06 ) 03/14/2006 <7>[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved <7>[0.00] e820: remove [mem 0x000a-0x000f] usable <6>[0.00] e820: last_pfn = 0x7f6e0 max_arch_pfn = 0x10 <7>[0.00] MTRR default type: uncachable <7>[0.00] MTRR fixed ranges enabled: <7>[0.00] 0-9 write-back <7>[0.00] A-B uncachable <7>[0.00] C-C write-protect <7>[0.00] D-DBFFF uncachable <7>[0.00] DC000-D write-back <7>[0.00] E-F write-protect <7>[0.00] MTRR variable ranges enabled: <7>[0.00] 0 base 0 mask F8000 write-back <7>[0.00] 1 base 07F70 mask 0 uncachable <7>[0.00] 2 base 07F80 mask FFF80 uncachable <7>[0.00] 3 disabled <7>[0.00] 4 disabled <7>[0.00] 5 disabled <7>[0.00] 6 disabled <7>[0.00] 7 disabled <6>[0.00] PAT not supported by CPU. <7>[0.00] initial memory mapped: [mem 0x-0x013f] <7>[0.00] Base memory trampoline at [c009b000] 9b000 size 16384 <6>[0.00] init_memory_mapping: [mem 0x-0x000f] <7>[0.00] [mem 0x-0x000f] page 4k <6>[0.00] init_memory_mapping: [mem 0x36c0-0x36ff] <7>[0.00] [mem 0x36c0-0x36ff] page 2M <6>[0.00] init_memory_mapping: [mem 0x3000-0x36bf] <7>[0.00] [mem 0x3000-0x36bf] page 2M <6>[0.00] init_memory_mapping: [mem 0x0010-0x2fff] <7>[0.00] [mem 0x0010-0x003f] page 4k <7>[0.00] [mem 0x0040-0x2fff] page 2M <6>[0.00] init_memory_mapping: [mem 0x3700-0x373fdfff] <7>[0.00] [mem 0x3700-0x373fdfff] page 4k <7>[0.00] BRK [0x00e6d000, 0x00e6dfff] PGTABLE <7>[0.00] BRK [0x00e6e000, 0x00e6] PGTABLE <6>[0.00] RAMDISK: [mem 0x33f7c000-0x35fb5fff] <5>[0.00] ACPI: RSDP 000f6c00 24 (v02 IBM ) <5>[0.00] ACPI: XSDT 7f6e4770 5C (v01 IBMTP-742060 LTP ) <5>[0.00] ACPI: FACP 7f6e4800 F4 (v03 IBMTP-742060 IBM 0001) <5>[0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 0/32 (20131115/tbfadt-572) <5>[0.00] ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has zero address or length: 0x102C/0x0 (20131115/tbfadt-603) <5>[0.00] ACPI: DSDT 7f6e49e7 01038A (v01 IBMTP-742060 MSFT 010E) <5>[0.00] ACPI: FACS 7f6f6000 40 <5>[0.00] ACPI: SSDT 7f6e49b4 33 (v01 IBMTP-742060 MSFT 010E) <5>[0.00] ACPI: ECDT 7f6f4d71 52 (v01 IBMTP-742060 IBM
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Mon, Dec 02, 2013 at 07:05:25PM +0100, Paul Bolle wrote: > On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote: > > On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote: > > > This generated quite a bit of debug messages so I only copied the > > > WARNING and the drm (related) messages immediately preceding it. Please > > > feel free to prod again if that's insufficient. > > > > Yeah, the beginning of the drm message would are wanted since I need > > to know what exactly your hardware claims to support ;-) > > > > But the backtrace confirms my first hunch for now ... Just want to > > confirm before sending out a patch with commit message. > > It seems Ville's patch ( https://lkml.org/lkml/2013/12/2/77 ) does the > trick. Do you still need the additional info? I'd like to confirm the actual cause (I suspect that we switch pipes around) for why you see this but other machines don't show this to augment the commit message. But I've merged the fix already. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote: > On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote: > > This generated quite a bit of debug messages so I only copied the > > WARNING and the drm (related) messages immediately preceding it. Please > > feel free to prod again if that's insufficient. > > Yeah, the beginning of the drm message would are wanted since I need > to know what exactly your hardware claims to support ;-) > > But the backtrace confirms my first hunch for now ... Just want to > confirm before sending out a patch with commit message. It seems Ville's patch ( https://lkml.org/lkml/2013/12/2/77 ) does the trick. Do you still need the additional info? Paul Bolle
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote: > On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote: >> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote: >> > The WARNING is now gone during suspend and resume (having tested that >> > thoroughly - ie, twice). But I still see it at boot. Is there a related >> > fix for that WARNING during boot? >> >> Hm, I've never seen it during boot. Can you please boot with >> drm.debug=0xe and attach the dmesg with the WARN? > > Sure. > > This generated quite a bit of debug messages so I only copied the > WARNING and the drm (related) messages immediately preceding it. Please > feel free to prod again if that's insufficient. Yeah, the beginning of the drm message would are wanted since I need to know what exactly your hardware claims to support ;-) But the backtrace confirms my first hunch for now ... Just want to confirm before sending out a patch with commit message. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote: > On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote: > > The WARNING is now gone during suspend and resume (having tested that > > thoroughly - ie, twice). But I still see it at boot. Is there a related > > fix for that WARNING during boot? > > Hm, I've never seen it during boot. Can you please boot with > drm.debug=0xe and attach the dmesg with the WARN? Sure. This generated quite a bit of debug messages so I only copied the WARNING and the drm (related) messages immediately preceding it. Please feel free to prod again if that's insufficient. [...] <6>[2.727041] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3 <7>[2.729161] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter i915 gmbus panel <7>[2.729166] [drm:intel_lvds_init], using mode from VBT: <7>[2.729170] [drm:drm_mode_debug_printmodeline], <5>[2.729175] Modeline 0:"1024x768" 0 54160 1024 1048 1184 1344 768 771 777 806 0x8 0xa <7>[2.729464] [drm:intel_lvds_init], detected single-link lvds configuration <7>[2.729575] [drm:intel_panel_get_backlight], get backlight PWM = 13875 <7>[2.729579] [drm:intel_panel_get_max_backlight], max backlight PWM = 13875 <7>[2.729732] [drm:i915_gem_setup_global_gtt], clearing unused GTT space: [0, 000] <7>[2.733459] [drm:i915_gem_object_create_stolen], creating stolen object: size=2 <7>[2.733466] [drm:i915_pages_create_for_stolen], offset=0x0, size=131072 <7>[2.733514] [drm:i915_gem_context_init], Disabling HW Contexts; old hardware <6>[2.733649] [drm] initialized overlay support <7>[2.733654] [drm:intel_modeset_readout_hw_state], [CRTC:3] hw state readout: disabled <7>[2.733664] [drm:intel_modeset_readout_hw_state], [CRTC:4] hw state readout: enabled <7>[2.733670] [drm:intel_modeset_readout_hw_state], [ENCODER:6:LVDS-6] hw state readout: enabled, pipe B <7>[2.733674] [drm:intel_modeset_readout_hw_state], [ENCODER:10:DAC-10] hw state readout: disabled, pipe A <7>[2.733679] [drm:intel_modeset_readout_hw_state], [ENCODER:12:TV-12] hw state readout: disabled, pipe A <7>[2.733683] [drm:intel_modeset_readout_hw_state], [CONNECTOR:5:LVDS-1] hw state readout: enabled <7>[2.733687] [drm:intel_modeset_readout_hw_state], [CONNECTOR:9:VGA-1] hw state readout: disabled <7>[2.733690] [drm:intel_modeset_readout_hw_state], [CONNECTOR:11:SVIDEO-1] hw state readout: disabled <7>[2.733696] [drm:intel_dump_pipe_config], [CRTC:3][setup_hw_state] config for pipe A <7>[2.733699] [drm:intel_dump_pipe_config], cpu_transcoder: A <7>[2.733702] [drm:intel_dump_pipe_config], pipe bpp: 0, dithering: 0 <7>[2.733705] [drm:intel_dump_pipe_config], fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 <7>[2.733708] [drm:intel_dump_pipe_config], dp: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 <7>[2.733712] [drm:intel_dump_pipe_config], requested mode: <7>[2.733714] [drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0 <7>[2.733719] [drm:intel_dump_pipe_config], adjusted mode: <7>[2.733721] [drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0 <7>[2.733726] [drm:intel_dump_crtc_timings], crtc timings: 0 0 0 0 0 0 0 0 0, type: 0x0 flags: 0x0 <7>[2.733730] [drm:intel_dump_pipe_config], port clock: 0 <7>[2.733732] [drm:intel_dump_pipe_config], pipe src size: 0x0 <7>[2.733735] [drm:intel_dump_pipe_config], gmch pfit: control: 0x, ratios: 0x, lvds border: 0x <7>[2.733738] [drm:intel_dump_pipe_config], pch pfit: pos: 0x, size: 0x, disabled <7>[2.733741] [drm:intel_dump_pipe_config], ips: 0 <7>[2.733743] [drm:intel_dump_pipe_config], double wide: 0 <7>[2.733747] [drm:intel_sanitize_crtc], [CRTC:4] wrong plane connection detected! <4>[2.733750] [ cut here ] <4>[2.733815] WARNING: CPU: 0 PID: 173 at drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector+0x42/0x50 [i915]() <5>[2.733818] Modules linked in: i915(F+) ata_generic(F) pata_acpi(F) i2c_algo_bit(F) drm_kms_helper(F) yenta_socket(F+) drm(F) tg3(F) ptp(F) pps_core(F) i2c_core(F) video(F) sunrpc(F) <5>[2.733836] CPU: 0 PID: 173 Comm: systemd-udevd Tainted: GF 3.13.0-0.rc2.1.local1.fc18.i686 #1 <5>[2.733839] Hardware name: IBM 2525FAG/2525FAG, BIOS 74ET61WW (2.06 ) 03/14/2006 <5>[2.733842] f54979f4 c09b66d2 f5497a24 c0449b14 c0b541a4 <5>[2.733850] 00ad f82d3524 26dc f828c6a2 f828c6a2 f5561e00 00061200 <5>[2.733856] f56a4000 f5497a34 c0449b52 0009 f5497a40 f828c6a2 f563d000 <5>[2.733863] Call Trace: <5>[2.733875] [] dump_stack+0x41/0x52 <5>[2.733882] [] warn_slowpath_common+0x84/0xa0 <5>[2.733919] [] ? intel_get_pipe_from_connector+0x42/0x50
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote: > On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote: >> Should be fixed with >> >> commit 7c063c725987406d743cc7de7625ff224fab75de >> Author: Jesse Barnes >> Date: Tue Nov 26 09:13:41 2013 -0800 >> >> drm/i915: take mode config lock around crtc disable at suspend >> >> which is currently in drm-intel-fixes. I'll forward it early next week. > > Thanks! > > The WARNING is now gone during suspend and resume (having tested that > thoroughly - ie, twice). But I still see it at boot. Is there a related > fix for that WARNING during boot? Hm, I've never seen it during boot. Can you please boot with drm.debug=0xe and attach the dmesg with the WARN? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote: > Should be fixed with > > commit 7c063c725987406d743cc7de7625ff224fab75de > Author: Jesse Barnes > Date: Tue Nov 26 09:13:41 2013 -0800 > > drm/i915: take mode config lock around crtc disable at suspend > > which is currently in drm-intel-fixes. I'll forward it early next week. Thanks! The WARNING is now gone during suspend and resume (having tested that thoroughly - ie, twice). But I still see it at boot. Is there a related fix for that WARNING during boot? Paul Bolle
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
Should be fixed with commit 7c063c725987406d743cc7de7625ff224fab75de Author: Jesse Barnes Date: Tue Nov 26 09:13:41 2013 -0800 drm/i915: take mode config lock around crtc disable at suspend which is currently in drm-intel-fixes. I'll forward it early next week. -Daniel On Sat, Nov 30, 2013 at 9:38 PM, Paul Bolle wrote: > On both v3.13-rc1 and v3.13-rc2 is see this at every boot and during > every suspend and resume cycle: > > <4>[2.682468] WARNING: CPU: 0 PID: 173 at > drivers/gpu/drm/i915/intel_display.c:9948 > intel_get_pipe_from_connector+0x42/0x50 [i915]() > <5>[2.682470] Modules linked in: i915(F+) ata_generic(F) pata_acpi(F) > yenta_socket(F+) i2c_algo_bit(F) drm_kms_helper(F) tg3(F+) ptp(F) pps_core(F) > drm(F) i2c_core(F) video(F) sunrpc(F) > <5>[2.682489] CPU: 0 PID: 173 Comm: systemd-udevd Tainted: GF > 3.13.0-0.rc2.1.local0.fc18.i686 #1 > <5>[2.682492] Hardware name: IBM 2525FAG/2525FAG, BIOS 74ET61WW (2.06 ) > 03/14/2006 > <5>[2.682495] f54739f4 c09b66d2 f5473a24 > c0449b14 c0b541a4 > <5>[2.682502] 00ad f82c9524 26dc f8282692 f8282692 > f555ed80 00061200 > <5>[2.682509] f567c000 f5473a34 c0449b52 0009 f5473a40 > f8282692 f5578800 > <5>[2.682516] Call Trace: > <5>[2.682528] [] dump_stack+0x41/0x52 > <5>[2.682534] [] warn_slowpath_common+0x84/0xa0 > <5>[2.682571] [] ? intel_get_pipe_from_connector+0x42/0x50 > [i915] > <5>[2.682607] [] ? intel_get_pipe_from_connector+0x42/0x50 > [i915] > <5>[2.682612] [] warn_slowpath_null+0x22/0x30 > <5>[2.682648] [] intel_get_pipe_from_connector+0x42/0x50 [i915] > <5>[2.682689] [] intel_panel_disable_backlight+0x21/0x160 > [i915] > <5>[2.682725] [] intel_disable_lvds+0x41/0x160 [i915] > <5>[2.682760] [] i9xx_crtc_disable+0x200/0x2c0 [i915] > <5>[2.682802] [] ? gen4_read32+0x31/0x90 [i915] > <5>[2.682839] [] intel_modeset_setup_hw_state+0x92e/0xb00 > [i915] > <5>[2.682844] [] ? power_down+0x8c/0x8d > <5>[2.682884] [] ? gen4_write64+0xa0/0xa0 [i915] > <5>[2.682920] [] intel_modeset_gem_init+0x20/0x30 [i915] > <5>[2.682950] [] i915_driver_load+0xb53/0xdd0 [i915] > <5>[2.682978] [] ? i915_switcheroo_set_state+0xa0/0xa0 [i915] > <5>[2.683003] [] drm_dev_register+0x8c/0x1a0 [drm] > <5>[2.683043] [] drm_get_pci_dev+0x85/0x130 [drm] > <5>[2.683050] [] ? sysfs_do_create_link_sd.isra.3+0xa8/0x1c0 > <5>[2.683057] [] ? notifier_call_chain+0x43/0x60 > <5>[2.683086] [] i915_pci_probe+0x3a/0x80 [i915] > <5>[2.683093] [] pci_device_probe+0x79/0xc0 > <5>[2.683097] [] ? sysfs_create_link+0x25/0x40 > <5>[2.683104] [] driver_probe_device+0x79/0x360 > <5>[2.683108] [] ? pci_match_device+0x9e/0xb0 > <5>[2.683113] [] __driver_attach+0x91/0xa0 > <5>[2.683117] [] ? driver_probe_device+0x360/0x360 > <5>[2.683121] [] bus_for_each_dev+0x42/0x80 > <5>[2.683125] [] driver_attach+0x1e/0x20 > <5>[2.683130] [] ? driver_probe_device+0x360/0x360 > <5>[2.683134] [] bus_add_driver+0xec/0x210 > <5>[2.683138] [] driver_register+0x59/0xe0 > <5>[2.683142] [] ? 0xf7fb1fff > <5>[2.683147] [] __pci_register_driver+0x33/0x40 > <5>[2.683150] [] ? 0xf7fb1fff > <5>[2.683166] [] drm_pci_init+0xfd/0x110 [drm] > <5>[2.683170] [] ? 0xf7fb1fff > <5>[2.683198] [] i915_init+0x5e/0x60 [i915] > <5>[2.683203] [] do_one_initcall+0xda/0x1a0 > <5>[2.683206] [] ? 0xf7fb1fff > <5>[2.683211] [] ? __add_event_to_tracers+0x21/0x30 > <5>[2.683215] [] ? 0xf7fb1fff > <5>[2.683221] [] ? set_memory_ro+0x37/0x40 > <5>[2.683228] [] load_module+0x1abd/0x2390 > <5>[2.683235] [] SyS_init_module+0xa7/0x110 > <5>[2.683242] [] ? vm_mmap_pgoff+0x8b/0xb0 > <5>[2.683248] [] sysenter_do_call+0x12/0x28 > > Feel free to prod for further details. > > > Paul Bolle > -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
[i915] WARNING: [...] drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector
On both v3.13-rc1 and v3.13-rc2 is see this at every boot and during every suspend and resume cycle: <4>[2.682468] WARNING: CPU: 0 PID: 173 at drivers/gpu/drm/i915/intel_display.c:9948 intel_get_pipe_from_connector+0x42/0x50 [i915]() <5>[2.682470] Modules linked in: i915(F+) ata_generic(F) pata_acpi(F) yenta_socket(F+) i2c_algo_bit(F) drm_kms_helper(F) tg3(F+) ptp(F) pps_core(F) drm(F) i2c_core(F) video(F) sunrpc(F) <5>[2.682489] CPU: 0 PID: 173 Comm: systemd-udevd Tainted: GF 3.13.0-0.rc2.1.local0.fc18.i686 #1 <5>[2.682492] Hardware name: IBM 2525FAG/2525FAG, BIOS 74ET61WW (2.06 ) 03/14/2006 <5>[2.682495] f54739f4 c09b66d2 f5473a24 c0449b14 c0b541a4 <5>[2.682502] 00ad f82c9524 26dc f8282692 f8282692 f555ed80 00061200 <5>[2.682509] f567c000 f5473a34 c0449b52 0009 f5473a40 f8282692 f5578800 <5>[2.682516] Call Trace: <5>[2.682528] [] dump_stack+0x41/0x52 <5>[2.682534] [] warn_slowpath_common+0x84/0xa0 <5>[2.682571] [] ? intel_get_pipe_from_connector+0x42/0x50 [i915] <5>[2.682607] [] ? intel_get_pipe_from_connector+0x42/0x50 [i915] <5>[2.682612] [] warn_slowpath_null+0x22/0x30 <5>[2.682648] [] intel_get_pipe_from_connector+0x42/0x50 [i915] <5>[2.682689] [] intel_panel_disable_backlight+0x21/0x160 [i915] <5>[2.682725] [] intel_disable_lvds+0x41/0x160 [i915] <5>[2.682760] [] i9xx_crtc_disable+0x200/0x2c0 [i915] <5>[2.682802] [] ? gen4_read32+0x31/0x90 [i915] <5>[2.682839] [] intel_modeset_setup_hw_state+0x92e/0xb00 [i915] <5>[2.682844] [] ? power_down+0x8c/0x8d <5>[2.682884] [] ? gen4_write64+0xa0/0xa0 [i915] <5>[2.682920] [] intel_modeset_gem_init+0x20/0x30 [i915] <5>[2.682950] [] i915_driver_load+0xb53/0xdd0 [i915] <5>[2.682978] [] ? i915_switcheroo_set_state+0xa0/0xa0 [i915] <5>[2.683003] [] drm_dev_register+0x8c/0x1a0 [drm] <5>[2.683043] [] drm_get_pci_dev+0x85/0x130 [drm] <5>[2.683050] [] ? sysfs_do_create_link_sd.isra.3+0xa8/0x1c0 <5>[2.683057] [] ? notifier_call_chain+0x43/0x60 <5>[2.683086] [] i915_pci_probe+0x3a/0x80 [i915] <5>[2.683093] [] pci_device_probe+0x79/0xc0 <5>[2.683097] [] ? sysfs_create_link+0x25/0x40 <5>[2.683104] [] driver_probe_device+0x79/0x360 <5>[2.683108] [] ? pci_match_device+0x9e/0xb0 <5>[2.683113] [] __driver_attach+0x91/0xa0 <5>[2.683117] [] ? driver_probe_device+0x360/0x360 <5>[2.683121] [] bus_for_each_dev+0x42/0x80 <5>[2.683125] [] driver_attach+0x1e/0x20 <5>[2.683130] [] ? driver_probe_device+0x360/0x360 <5>[2.683134] [] bus_add_driver+0xec/0x210 <5>[2.683138] [] driver_register+0x59/0xe0 <5>[2.683142] [] ? 0xf7fb1fff <5>[2.683147] [] __pci_register_driver+0x33/0x40 <5>[2.683150] [] ? 0xf7fb1fff <5>[2.683166] [] drm_pci_init+0xfd/0x110 [drm] <5>[2.683170] [] ? 0xf7fb1fff <5>[2.683198] [] i915_init+0x5e/0x60 [i915] <5>[2.683203] [] do_one_initcall+0xda/0x1a0 <5>[2.683206] [] ? 0xf7fb1fff <5>[2.683211] [] ? __add_event_to_tracers+0x21/0x30 <5>[2.683215] [] ? 0xf7fb1fff <5>[2.683221] [] ? set_memory_ro+0x37/0x40 <5>[2.683228] [] load_module+0x1abd/0x2390 <5>[2.683235] [] SyS_init_module+0xa7/0x110 <5>[2.683242] [] ? vm_mmap_pgoff+0x8b/0xb0 <5>[2.683248] [] sysenter_do_call+0x12/0x28 Feel free to prod for further details. Paul Bolle
