<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB IVB HSW] Call trace appears after system booting up" href="https://bugs.freedesktop.org/show_bug.cgi?id=67462#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB IVB HSW] Call trace appears after system booting up" href="https://bugs.freedesktop.org/show_bug.cgi?id=67462">bug 67462</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=67462#c4">comment #4</a>) > (In reply to <a href="show_bug.cgi?id=67462#c3">comment #3</a>) > > This should be entertaining. I'll see what I can do with it. Now to find SNB > > hardware... > > Hi, I check this again(using a latest -next-queued kernel) and find this > issue happens on SNB, IVB and HSW platforms. > Besides, calltrace has nothing to do with DP, it happens even if system > booting without a monitor. So I think you can use any of these platforms to > reproduce it.. :) We have two calltraces in the dmesg here. The first one is [ 1.177979] WARNING: CPU: 1 PID: 1236 at drivers/gpu/drm/i915/intel_display.c:842 ironlake_crtc_disable+0xd6/0x83c [i915]() Thus far that tends to only happen with DP when we try to switch it off. The 2nd calltrace is [ 1.860783] firewire_ohci 0000:04:03.0: failed to read phy reg 2 [ 1.863475] CPU: 2 PID: 1435 Comm: udevd Tainted: G W 3.11.0-rc2_drm-intel-next-queued_fae5cb_20130727_+ #23723 [ 1.866130] Hardware name: /DQ67SW, BIOS SWQ6710H.86A.0060.2011.1220.1805 12/20/2011 [ 1.868786] 0000000000000000 ffff8802302fe000 ffffffff816ed6a8 0000000000000067 [ 1.871438] ffffffffa019929a ffff8802302fe000 ffffffffa0184300 0000000000000016 [ 1.874051] ffffffffa019b4ad ffffffffa019bda0 ffff8802302fe000 ffff8802302fe630 [ 1.876673] Call Trace: [ 1.879231] [<ffffffff816ed6a8>] ? dump_stack+0x41/0x51 [ 1.881843] [<ffffffffa019929a>] ? read_phy_reg+0x71/0x82 [firewire_ohci] [ 1.884455] [<ffffffffa019b4ad>] ? ohci_enable+0x26f/0x535 [firewire_ohci] [ 1.887023] [<ffffffffa017c91d>] ? fw_card_add+0x42/0x8a [firewire_core] [ 1.889594] [<ffffffffa01990bf>] ? pci_probe+0x548/0x6b2 [firewire_ohci] [ 1.892166] [<ffffffff8112cba7>] ? sysfs_do_create_link_sd+0x137/0x188 [ 1.894748] [<ffffffff81363fb9>] ? driver_probe_device+0x19e/0x19e [ 1.897369] [<ffffffff812e1a6d>] ? local_pci_probe+0x16/0x26 [ 1.899939] [<ffffffff812e232b>] ? pci_device_probe+0xbc/0xe0 [ 1.902502] [<ffffffff81363ea5>] ? driver_probe_device+0x8a/0x19e [ 1.905054] [<ffffffff8136400c>] ? __driver_attach+0x53/0x73 [ 1.907646] [<ffffffff813626d0>] ? bus_for_each_dev+0x4e/0x7f [ 1.910242] [<ffffffff813636ca>] ? bus_add_driver+0xe5/0x204 [ 1.912772] [<ffffffff8136452e>] ? driver_register+0x8c/0x104 [ 1.915302] [<ffffffffa019f000>] ? 0xffffffffa019efff [ 1.917855] [<ffffffff8100025a>] ? do_one_initcall+0x78/0xf6 [ 1.920393] [<ffffffff8104ebbf>] ? __blocking_notifier_call_chain+0x4f/0x5d [ 1.922917] [<ffffffff81073a2e>] ? load_module+0x17ec/0x1aba [ 1.925447] [<ffffffff8107151a>] ? free_notes_attrs+0x3f/0x3f [ 1.928027] [<ffffffff81073d8c>] ? SyS_init_module+0x90/0x9b [ 1.930563] [<ffffffff816f7ed2>] ? system_call_fastpath+0x16/0x1b [ 1.933178] firewire_ohci: probe of 0000:04:03.0 failed with error -16 That on is not our bug and you can ignore it (maybe it's fixed in latest upstream already).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>