Hide Forgot
Description of problem: After reboot, kerneloops is reported. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Reboot 2. Login 3. Wait Actual results: abrt "proc_dir_entry 'video/GFX0' already registered" appears Expected results: no abrt Additional info: Copy of kerneloops traceback reported to kernel.org but probably not the kernel itself WARNING: at fs/proc/generic.c:583 proc_register+0x158/0x195() Hardware name: U30Jc proc_dir_entry 'video/GFX0' already registered Modules linked in: usb_storage i915(+) nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core video output Pid: 108, comm: modprobe Not tainted 2.6.35.12-90.fc14.x86_64 #1 Call Trace: [<ffffffff8104dce1>] warn_slowpath_common+0x85/0x9d [<ffffffff8104dd9c>] warn_slowpath_fmt+0x46/0x48 [<ffffffff811656b7>] proc_register+0x158/0x195 [<ffffffff81165d82>] proc_mkdir_mode+0x42/0x5a [<ffffffff81165db0>] proc_mkdir+0x16/0x18 [<ffffffffa00159ac>] acpi_video_bus_add+0x289/0x1029 [video] [<ffffffff81469bd4>] ? mutex_unlock+0x1b/0x1d [<ffffffff8116f5c9>] ? sysfs_addrm_finish+0x2f/0xb9 [<ffffffff8116f8bc>] ? sysfs_add_one+0x21/0xf8 [<ffffffff81469d23>] ? mutex_lock+0x36/0x50 [<ffffffff8117014b>] ? sysfs_do_create_link+0x144/0x18c [<ffffffff8126900f>] acpi_device_probe+0x50/0x122 [<ffffffff812d87c3>] driver_probe_device+0x14b/0x271 [<ffffffff812d8946>] __driver_attach+0x5d/0x81 [<ffffffff812d88e9>] ? __driver_attach+0x0/0x81 [<ffffffff812d76c7>] bus_for_each_dev+0x56/0x82 [<ffffffff812d8394>] driver_attach+0x1e/0x20 [<ffffffff812d7f6e>] bus_add_driver+0xf1/0x25e [<ffffffff812d8baa>] driver_register+0x9b/0x108 [<ffffffff81269615>] acpi_bus_register_driver+0x43/0x45 [<ffffffffa00167dc>] acpi_video_register+0x49/0x75 [video] [<ffffffffa01493db>] intel_opregion_init+0x401/0x464 [i915] [<ffffffff8146ab9f>] ? _raw_spin_unlock_irqrestore+0x17/0x19 [<ffffffffa012476c>] i915_driver_load+0x106b/0x113e [i915] [<ffffffff812d5a84>] ? device_register+0x1e/0x22 [<ffffffffa003f275>] drm_get_dev+0x39c/0x4ab [drm] [<ffffffffa0149895>] i915_pci_probe+0x15/0x17 [i915] [<ffffffff81233459>] local_pci_probe+0x17/0x1b [<ffffffff81233c14>] pci_device_probe+0xd2/0x104 [<ffffffff811701a6>] ? sysfs_create_link+0x13/0x15 [<ffffffff812d87c3>] driver_probe_device+0x14b/0x271 [<ffffffff812d8946>] __driver_attach+0x5d/0x81 [<ffffffff812d88e9>] ? __driver_attach+0x0/0x81 [<ffffffff812d76c7>] bus_for_each_dev+0x56/0x82 [<ffffffff812d8394>] driver_attach+0x1e/0x20 [<ffffffff812d7f6e>] bus_add_driver+0xf1/0x25e [<ffffffff812d8baa>] driver_register+0x9b/0x108 [<ffffffff81233e40>] __pci_register_driver+0x56/0xc2 [<ffffffffa016a000>] ? i915_init+0x0/0x96 [i915] [<ffffffffa0039f62>] drm_init+0x77/0xdd [drm] [<ffffffffa016a000>] ? i915_init+0x0/0x96 [i915] [<ffffffffa016a094>] i915_init+0x94/0x96 [i915] [<ffffffff810021a1>] do_one_initcall+0x5e/0x155 [<ffffffff8107d155>] sys_init_module+0xa6/0x1e4 [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b
Do you still see this with the latest f14 or f15 kernel?
*** This bug has been marked as a duplicate of bug 689749 ***
Josh - sorry I did not respond to your 8/29 comment. I no longer see this bug, but I have replaced the laptop on which it appeared since the bug was filed. I did thait for unrelated reasons (AFAICT).