Re: Kernel 2.6.30 and udevd problem

[Alberto Gonzalez <alberto6674@gmail.com>]

On Thursday 02 July 2009 18:35:47 Jesse Barnes wrote:
> On Thu, 2 Jul 2009 08:18:58 +0200
>
> Alberto Gonzalez <alberto6674@gmail.com> wrote:
> > Thanks, the patch applied to 2.6.30 and when the problem stars I get
> > these two lines repeated all the time in dmesg:
> >
> > [drm:i915_driver_irq_handler] *ERROR* hotplug event received, stat
> > 0x10200300 [drm:i915_driver_irq_handler] *ERROR* hotplug event
> > received, stat 0x18200300
> >
> > Is this enough or should I provide something else?
>
> Interesting.  That hotplug status shouldn't end up generating any
> uevents.  Can you try this patch to see what's going on?

This is what I get with the patch applied (repeated again and again):

------------[ cut here ]------------
WARNING: at drivers/gpu/drm/drm_sysfs.c:452 drm_sysfs_hotplug_event+0x3e/0x90 
[drm]()
Hardware name: Studio 540
hotplug uevent
Modules linked in: ipv6 usbhid hid ext4 jbd2 crc16 usb_storage snd_seq_dummy 
snd_hda_codec_intelhdmi snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device 
snd_hda_codec_realtek snd_pcm_oss snd_mixer_oss psmouse ohci1394 snd_hda_intel 
ieee1394 i2c_i801 uhci_hcd serio_raw sg dcdbas iTCO_wdt iTCO_vendor_support 
snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc r8169 
mii ehci_hcd usbcore evdev thermal fan button battery ac cpufreq_ondemand 
acpi_cpufreq freq_table processor rtc_cmos rtc_core rtc_lib ext3 jbd mbcache 
sd_mod sr_mod cdrom pata_acpi ata_generic ata_piix libata scsi_mod i915 
i2c_algo_bit video output drm i2c_core intel_agp agpgart
Pid: 9, comm: events/0 Tainted: G        W  2.6.30-ARCH #1
Call Trace:
 [<c013b17a>] ? warn_slowpath_common+0x7a/0xc0
 [<f82be0fe>] ? drm_sysfs_hotplug_event+0x3e/0x90 [drm]
 [<f83bb410>] ? i915_hotplug_work_func+0x0/0x30 [i915]
 [<c013b237>] ? warn_slowpath_fmt+0x37/0x60
 [<f82be0fe>] ? drm_sysfs_hotplug_event+0x3e/0x90 [drm]
 [<c014f61f>] ? worker_thread+0x11f/0x280
 [<c0154900>] ? autoremove_wake_function+0x0/0x60
 [<c014f500>] ? worker_thread+0x0/0x280
 [<c0154452>] ? kthread+0x52/0x90
 [<c0154400>] ? kthread+0x0/0x90
 [<c01047c7>] ? kernel_thread_helper+0x7/0x10
---[ end trace a39351f6aee6be08 ]---

Thanks,
Alberto.