On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell sfr@canb.auug.org.au wrote:
Hi all,
Changes since 20130724:
Removed tree: arm-dt (at maintainer's request)
The wireless-next tree lost its build failure and gained a conflict against Linus' tree.
The tty tree lost its build failure.
The staging tree gained a build failure for which I disabled a driver.
[ CCing drm and drm-intel folks ]
With today's next-20130725 I see the following:
[ 17.122627] [drm] Memory usable by graphics device = 2048M [ 17.122639] i915 0000:00:02.0: setting latency timer to 64 [ 17.164740] BUG: spinlock bad magic on CPU#3, modprobe/635 [ 17.164797] lock: 0xffff8800bc534040, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0 [ 17.164856] CPU: 3 PID: 635 Comm: modprobe Not tainted 3.11.0-rc2-next20130725-1-iniza-small #1 [ 17.164914] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013 [ 17.164977] 0000000000000000 ffff8800c0fa1738 ffffffff816ddfc9 0000000000000007 [ 17.165101] ffff8800bc534040 ffff8800c0fa1758 ffffffff816de065 ffff8800bc534040 [ 17.165222] ffffffff81a5f497 ffff8800c0fa1778 ffffffff816de08b ffff8800bc534040 [ 17.165345] Call Trace: [ 17.165386] [<ffffffff816ddfc9>] dump_stack+0x46/0x58 [ 17.165428] [<ffffffff816de065>] spin_dump+0x8a/0x8f [ 17.165469] [<ffffffff816de08b>] spin_bug+0x21/0x26 [ 17.165511] [<ffffffff813787c4>] do_raw_spin_lock+0x84/0x120 [ 17.165554] [<ffffffff816e6db4>] _raw_spin_lock_irqsave+0x24/0x30 [ 17.165620] [<ffffffffa037a456>] i915_write32+0x36/0x150 [i915] [ 17.165690] [<ffffffffa03cf4c5>] intel_disable_gt_powersave+0xf5/0x360 [i915] [ 17.165768] [<ffffffffa03d1129>] intel_gt_sanitize+0x49/0xb0 [i915] [ 17.165827] [<ffffffffa037dd68>] i915_driver_load+0x638/0xed0 [i915] [ 17.165886] [<ffffffffa01b4b91>] drm_get_pci_dev+0x181/0x2a0 [drm] [ 17.165929] [<ffffffff813788fd>] ? do_raw_spin_unlock+0x5d/0xb0 [ 17.165987] [<ffffffffa03796f6>] i915_pci_probe+0x36/0x70 [i915] [ 17.166031] [<ffffffff813973ab>] local_pci_probe+0x4b/0x80 [ 17.166073] [<ffffffff81398c81>] pci_device_probe+0x101/0x120 [ 17.166115] [<ffffffff8147599b>] driver_probe_device+0x7b/0x240 [ 17.166158] [<ffffffff81475c0b>] __driver_attach+0xab/0xb0 [ 17.166200] [<ffffffff81475b60>] ? driver_probe_device+0x240/0x240 [ 17.166244] [<ffffffff81473c7e>] bus_for_each_dev+0x5e/0x90 [ 17.166286] [<ffffffff8147549e>] driver_attach+0x1e/0x20 [ 17.166330] [<ffffffff81474f94>] bus_add_driver+0x104/0x270 [ 17.166372] [<ffffffff8147616d>] driver_register+0x7d/0x160 [ 17.166415] [<ffffffff81397c04>] __pci_register_driver+0x64/0x70 [ 17.166460] [<ffffffffa0446000>] ? 0xffffffffa0445fff [ 17.166510] [<ffffffffa01b4dca>] drm_pci_init+0x11a/0x130 [drm] [ 17.166553] [<ffffffffa0446000>] ? 0xffffffffa0445fff [ 17.166610] [<ffffffffa0446066>] i915_init+0x66/0x68 [i915] [ 17.166652] [<ffffffff8100207e>] do_one_initcall+0x4e/0x180 [ 17.166696] [<ffffffff81058453>] ? set_memory_nx+0x43/0x50 [ 17.166742] [<ffffffff810d111c>] load_module+0x209c/0x25b0 [ 17.166784] [<ffffffff810cdd40>] ? show_initstate+0x50/0x50 [ 17.166827] [<ffffffff810d16dc>] SyS_init_module+0xac/0xd0 [ 17.166871] [<ffffffff816efdef>] tracesys+0xe1/0xe6 [ 17.167649] i915 0000:00:02.0: irq 49 for MSI/MSI-X [ 17.167709] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 17.167753] [drm] Driver supports precise vblank timestamp query.
I can't say what is the root cause and when it occured for the 1st time (my last Linux-next release was next-20130709).
Please, see also attached kernel-config and full dmesg.
- Sedat -