Re: 2.6.27-rc5-mm1: rmmod ide-cd_mod: tried to init an initialized object, something is seriously wrong.
From: Rafael J. Wysocki
Date: Fri Sep 05 2008 - 09:24:47 EST
On Friday, 5 of September 2008, Mariusz Kozlowski wrote:
> Hello,
>
> Again 100% reproducible rmmod ide-cd_mod problem. Kernel is tainted because
> of earlier sysfs acpi problems similar (probably identical) to those reported
> by Li Zefan here http://marc.info/?l=linux-kernel&m=121921059026064&w=2
>
> Steps to reproduce: unload ide-cd_mod
>
> kobject (dd9e4a7c): tried to init an initialized object, something is seriously wrong.
> Pid: 4734, comm: modprobe Tainted: G W 2.6.27-rc5-mm1 #1
> [<c01ec982>] kobject_init+0xc4/0xc9
> [<c02cb84a>] ? _spin_unlock+0x27/0x3f
> [<c01aff2e>] ? sysfs_find_dirent+0x21/0x2b
> [<c01aff7e>] ? __sysfs_add_one+0x46/0x6d
> [<c01affb4>] ? sysfs_add_one+0xf/0x44
> [<c01b0036>] ? sysfs_addrm_start+0x4d/0x90
> [<c01b0f31>] ? sysfs_do_create_link+0x9a/0x14c
> [<c01ec9c5>] kobject_init_and_add+0x14/0x30
> [<c01b1009>] ? sysfs_create_link+0x12/0x19
> [<c01e8bad>] blk_register_filter+0x3b/0x46
> [<ded9e40a>] ide_cd_probe+0x253/0x5a8 [ide_cd_mod]
> [<c01b0000>] ? sysfs_addrm_start+0x17/0x90
> [<c01b0f31>] ? sysfs_do_create_link+0x9a/0x14c
> [<c01b004e>] ? sysfs_addrm_start+0x65/0x90
> [<c025145f>] generic_ide_probe+0x1f/0x21
> [<c024c002>] driver_probe_device+0x77/0x15b
> [<c02cb91b>] ? _spin_unlock_irqrestore+0x39/0x60
> [<c024c146>] __driver_attach+0x60/0x62
> [<c024b7bd>] bus_for_each_dev+0x44/0x62
> [<c0251461>] ? generic_ide_remove+0x0/0x1e
> [<c024bead>] driver_attach+0x19/0x1b
> [<c024c0e6>] ? __driver_attach+0x0/0x62
> [<c024bca8>] bus_add_driver+0x1ab/0x213
> [<c0251461>] ? generic_ide_remove+0x0/0x1e
> [<c024c291>] driver_register+0x4f/0x118
> [<de7bf000>] ? ide_cdrom_init+0x0/0xf [ide_cd_mod]
> [<de7bf00d>] ide_cdrom_init+0xd/0xf [ide_cd_mod]
> [<c0101114>] do_one_initcall+0x24/0x12f
> [<c02c9d8e>] ? mutex_unlock+0x8/0xa
> [<c01455ca>] sys_init_module+0xa5/0x1c1
> [<c0176a0a>] ? sys_read+0x3d/0x64
> [<c01030f1>] sysenter_do_call+0x12/0x35
> [<c012007b>] ? __set_special_pids+0x43/0x71
>
> First time I modprobe/rmmod ide-cd_mod the system works but quickly gets unstable.
> Second modprobe/rmmod is 100% fatal. Memory gets corruped seriously I guess.
> pcspeaker beeps all the time, kernel throws dumps on the screen until
> its really dead, sadly blinking 'leds of panic' ;)
Can you please verify if that happens with the current mainline?
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/