linux-kernel - Re: linux-next: Tree for Jun 28 [ call-trace: workqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 28 Jun 2013 10:11:12 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tejun Heo <tj@...nel.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Dave Airlie <airlied@...il.com>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	DRI <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: Tree for Jun 28 [ call-trace: workqueue | drm
 releated? ]

On Fri, Jun 28, 2013 at 9:33 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130627:
>
> This tree produces the following warning when built for many (all?)
> configs (it has been fixed in the drm tree):
>
> drivers/video/Kconfig:42:error: recursive dependency detected!
> drivers/video/Kconfig:42:       symbol FB is selected by DRM_KMS_HELPER
> drivers/gpu/drm/Kconfig:29:     symbol DRM_KMS_HELPER is selected by DRM_OMAP
> drivers/gpu/drm/omapdrm/Kconfig:2:      symbol DRM_OMAP depends on FB_OMAP2
> drivers/video/omap2/omapfb/Kconfig:1:   symbol FB_OMAP2 depends on FB
>
> The arm-soc tree gained a conflict against the mfd tree.
>
> I applied a patch to the akpm tree to remove a lot of warnings.
>
> ----------------------------------------------------------------------------
>

[ CC wq and drm(-intel) folks ]

With next-20130628 I see the following call-trace:

[   11.941618] ------------[ cut here ]------------
[   11.941624] WARNING: CPU: 0 PID: 675 at kernel/workqueue.c:1445
__queue_delayed_work+0x18c/0x1a0()
[   11.941626] Modules linked in: i915(+) snd_page_alloc iwlwifi
snd_seq_midi snd_seq_midi_event btusb psmouse snd_rawmidi snd_seq
bluetooth cfg80211 i2c_algo_bit snd_timer samsung_laptop serio_raw
snd_seq_device drm_kms_helper lpc_ich drm snd wmi mac_hid soundcore
video lp parport hid_generic usbhid hid usb_storage r8169 mii
[   11.941651] CPU: 0 PID: 675 Comm: modprobe Not tainted
3.10.0-rc7-next20130628-1-iniza-small #1
[   11.941653] Hardware name: SAMSUNG ELECTRONICS CO., LTD.
530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
[   11.941655]  00000000000005a5 ffff88010b5596a8 ffffffff816db223
0000000000001908
[   11.941658]  0000000000000000 ffff88010b5596e8 ffffffff810661cc
ffffffffa00d3341
[   11.941661]  0000000000000100 ffff880119e72000 ffff88010765a000
0000000000000003
[   11.941664] Call Trace:
[   11.941671]  [<ffffffff816db223>] dump_stack+0x46/0x58
[   11.941675]  [<ffffffff810661cc>] warn_slowpath_common+0x8c/0xc0
[   11.941679]  [<ffffffff8106621a>] warn_slowpath_null+0x1a/0x20
[   11.941682]  [<ffffffff810845ac>] __queue_delayed_work+0x18c/0x1a0
[   11.941685]  [<ffffffff8108460d>] queue_delayed_work_on+0x4d/0x60
[   11.941691]  [<ffffffffa00f2950>]
drm_helper_probe_single_connector_modes+0x270/0x420 [drm_kms_helper]
[   11.941696]  [<ffffffffa00f0f12>]
drm_fb_helper_initial_config+0x1c2/0x550 [drm_kms_helper]
[   11.941700]  [<ffffffffa00f1721>] ?
drm_fb_helper_single_add_all_connectors+0x81/0xe0 [drm_kms_helper]
[   11.941705]  [<ffffffff81193f7c>] ? kmem_cache_alloc_trace+0x1bc/0x1f0
[   11.941725]  [<ffffffffa024c481>] ? i915_write32+0x81/0x130 [i915]
[   11.941748]  [<ffffffffa02a2ee1>] intel_fbdev_initial_config+0x21/0x30 [i915]
[   11.941763]  [<ffffffffa0250512>] i915_driver_load+0xe32/0xe60 [i915]
[   11.941777]  [<ffffffffa00b1c01>] drm_get_pci_dev+0x181/0x2a0 [drm]
[   11.941781]  [<ffffffff81376add>] ? do_raw_spin_unlock+0x5d/0xb0
[   11.941794]  [<ffffffffa024b6e6>] i915_pci_probe+0x36/0x70 [i915]
[   11.941799]  [<ffffffff813954cb>] local_pci_probe+0x4b/0x80
[   11.941801]  [<ffffffff81396da1>] pci_device_probe+0x101/0x120
[   11.941806]  [<ffffffff814736bb>] driver_probe_device+0x7b/0x240
[   11.941809]  [<ffffffff8147392b>] __driver_attach+0xab/0xb0
[   11.941813]  [<ffffffff81473880>] ? driver_probe_device+0x240/0x240
[   11.941816]  [<ffffffff814719be>] bus_for_each_dev+0x5e/0x90
[   11.941819]  [<ffffffff814731de>] driver_attach+0x1e/0x20
[   11.941823]  [<ffffffff81472cd4>] bus_add_driver+0x104/0x270
[   11.941826]  [<ffffffff81473e8d>] driver_register+0x7d/0x160
[   11.941830]  [<ffffffff81395d24>] __pci_register_driver+0x64/0x70
[   11.941833]  [<ffffffffa02ee000>] ? 0xffffffffa02edfff
[   11.941842]  [<ffffffffa00b1e3a>] drm_pci_init+0x11a/0x130 [drm]
[   11.941844]  [<ffffffffa02ee000>] ? 0xffffffffa02edfff
[   11.941858]  [<ffffffffa02ee066>] i915_init+0x66/0x68 [i915]
[   11.941861]  [<ffffffff8100207e>] do_one_initcall+0x4e/0x180
[   11.941865]  [<ffffffff810584a3>] ? set_memory_nx+0x43/0x50
[   11.941869]  [<ffffffff810d09e9>] load_module+0x1cf9/0x2620
[   11.941872]  [<ffffffff810cd880>] ? show_initstate+0x50/0x50
[   11.941875]  [<ffffffff810d13bc>] SyS_init_module+0xac/0xd0
[   11.941879]  [<ffffffff816ec12f>] tracesys+0xe1/0xe6
[   11.941881] ---[ end trace a06c6f52b0f09abe ]---

My dmesg and kernel-config are attached.

( I have seen there were new commits in drm-next which did not hit
today'n -next. )

- Sedat -

View attachment "dmesg_3.10.0-rc7-next20130628-1-iniza-small.txt" of type "text/plain" (96031 bytes)

Download attachment "config-3.10.0-rc7-next20130628-1-iniza-small" of type "application/octet-stream" (114320 bytes)