Re: Kernel 2.6.30 and udevd problem

[Jesse Barnes <jbarnes@virtuousgeek.org>]

On Sun, 5 Jul 2009 00:10:43 +0200
Alberto Gonzalez <alberto6674@gmail.com> wrote:

> On Friday 03 July 2009 00:00:49 Michal Soltys wrote:
> > Regarding Arch's default distro kernel - it's a bit patched. Most
> > of the patch file is addition of aufs, but there're other diffs
> > included as well, some of them modifying i915_reg.h,
> > intel_display.c and intel_tv.c
> >
> > ftp://ftp.archlinux.org/other/kernel26/patch-2.6.30-5-ARCH.bz2
> >
> > Not sure how relevant that is, but fyi.
> 
> Yes, thanks for pointing that out.
> 
> I now tried a vanilla 2.6.30.1 kernel with a custom config (so I
> don't have to wait 45 minutes for it to compile) and I still see the
> problem. This is what I get in dmesg:
> 
> [   83.506496] ------------[ cut here ]------------
> [   83.506500] WARNING: at drivers/gpu/drm/drm_sysfs.c:452 
> drm_sysfs_hotplug_event+0x2b/0x63()
> [   83.506502] Hardware name: Studio 540
> [   83.506503] hotplug uevent
> [   83.506504] Modules linked in:
> [   83.506506] Pid: 7, comm: events/0 Tainted: G        W  2.6.30.1 #1
> [   83.506507] Call Trace:
> [   83.506511]  [<c1025df9>] warn_slowpath_common+0x65/0x7c
> [   83.506514]  [<c11e9f9e>] ? drm_sysfs_hotplug_event+0x2b/0x63
> [   83.506517]  [<c1025e44>] warn_slowpath_fmt+0x24/0x27
> [   83.506520]  [<c11e9f9e>] drm_sysfs_hotplug_event+0x2b/0x63
> [   83.506523]  [<c11f33de>] i915_hotplug_work_func+0xe/0x10
> [   83.506525]  [<c1032f28>] worker_thread+0x131/0x1ab
> [   83.506528]  [<c11f33d0>] ? i915_hotplug_work_func+0x0/0x10
> [   83.506531]  [<c1035f61>] ? autoremove_wake_function+0x0/0x2f
> [   83.506534]  [<c1032df7>] ? worker_thread+0x0/0x1ab
> [   83.506536]  [<c1035c84>] kthread+0x46/0x6a
> [   83.506538]  [<c1035c3e>] ? kthread+0x0/0x6a
> [   83.506541]  [<c10033cf>] kernel_thread_helper+0x7/0x10
> [   83.506542] ---[ end trace 08f91010f92f7c3c ]---

Sorry I missed this update; what about the register dump part of the
patch?  Presumably you get a ton of these in your log, but with some
IIR register info beforehand?

-- 
Jesse Barnes, Intel Open Source Technology Center