In http://bugzilla.kernel.org/show_bug.cgi?id=10586 Ryan is showing this: May 1 16:15:01 kernel: Call Trace: May 1 16:15:01 kernel: [<ffffffff81118269>] idr_get_new+0xb/0x28 May 1 16:15:01 kernel: [<ffffffff810d5e92>] proc_register+0xcb/0x14b May 1 16:15:01 kernel: [<ffffffff810d5ec5>] proc_register+0xfe/0x14b May 1 16:15:01 kernel: [<ffffffff810d5f96>] proc_create_data+0x84/0x9e May 1 16:15:01 kernel: [<ffffffffa013dd37>] :video:acpi_video_bus_add+0x98f/0xc6d May 1 16:15:01 kernel: [<ffffffff8115d4d9>] acpi_device_probe+0x43/0x91 May 1 16:15:01 kernel: [<ffffffff81192564>] driver_probe_device+0xd0/0x14d May 1 16:15:01 kernel: [<ffffffff81192627>] __driver_attach+0x46/0x6d May 1 16:15:01 kernel: [<ffffffff811925e1>] __driver_attach+0x0/0x6d May 1 16:15:01 kernel: [<ffffffff81191f09>] bus_for_each_dev+0x44/0x6f May 1 16:15:01 kernel: [<ffffffff8119186e>] bus_add_driver+0xb2/0x1ff May 1 16:15:01 kernel: [<ffffffff81192846>] driver_register+0x59/0xcd May 1 16:15:01 kernel: [<ffffffffa00d803c>] :video:acpi_video_init+0x3c/0x5e May 1 16:15:01 kernel: [<ffffffff81052db2>] sys_init_module+0x171a/0x1896 May 1 16:15:01 kernel: [<ffffffff8115d812>] acpi_bus_register_driver+0x0/0x3e May 1 16:15:01 kernel: [<ffffffff81098831>] vfs_read+0xa6/0xfe May 1 16:15:01 kernel: [<ffffffff8100bf3b>] system_call_after_swapgs+0x7b/0x80 May 1 16:15:01 kernel: May 1 16:15:01 kernel: proc_dir_entry 'info' already registered May 1 16:15:01 kernel: Pid: 1099, comm: modprobe Not tainted 2.6.25-git16 #3 May 1 16:15:01 kernel: May 1 16:15:01 kernel: Call Trace: May 1 16:15:01 kernel: [<ffffffff81118269>] idr_get_new+0xb/0x28 May 1 16:15:01 kernel: [<ffffffff810d5e92>] proc_register+0xcb/0x14b May 1 16:15:01 kernel: [<ffffffff810d5edb>] proc_register+0x114/0x14b May 1 16:15:01 kernel: [<ffffffff810d5f96>] proc_create_data+0x84/0x9e May 1 16:15:01 kernel: [<ffffffffa013dd37>] :video:acpi_video_bus_add+0x98f/0xc6d May 1 16:15:01 kernel: [<ffffffff8115d4d9>] acpi_device_probe+0x43/0x91 May 1 16:15:01 kernel: [<ffffffff81192564>] driver_probe_device+0xd0/0x14d May 1 16:15:01 kernel: [<ffffffff81192627>] __driver_attach+0x46/0x6d May 1 16:15:01 kernel: [<ffffffff811925e1>] __driver_attach+0x0/0x6d May 1 16:15:01 kernel: [<ffffffff81191f09>] bus_for_each_dev+0x44/0x6f May 1 16:15:01 kernel: [<ffffffff8119186e>] bus_add_driver+0xb2/0x1ff May 1 16:15:01 kernel: [<ffffffff81192846>] driver_register+0x59/0xcd May 1 16:15:01 kernel: [<ffffffffa00d803c>] :video:acpi_video_init+0x3c/0x5e May 1 16:15:01 kernel: [<ffffffff81052db2>] sys_init_module+0x171a/0x1896 May 1 16:15:01 kernel: [<ffffffff8115d812>] acpi_bus_register_driver+0x0/0x3e May 1 16:15:01 kernel: [<ffffffff81098831>] vfs_read+0xa6/0xfe May 1 16:15:01 kernel: [<ffffffff8100bf3b>] system_call_after_swapgs+0x7b/0x80 May 1 16:15:01 kernel: (etc). So acpi video is trying to re-register the same /proc files. Perhaps this is due to that one-video-card-pretends-to-be-two-video-cards thing? Full boot logs are at http://userweb.kernel.org/~akpm/x.txt Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
