Re: 2.6.11-rc3-mm1: kobject_register fails for processor on Athlon64

[Rafael J. Wysocki]

On Friday, 4 of February 2005 19:33, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/

This occurs on my box (Athlon64-based) if "processor" is directly compiled into
the kernel:

ACPI: Lid Switch [LID]
ACPI: Fan [FN00] (off)
kobject_register failed for processor (-17)

Call Trace:<ffffffff80273e16>{kobject_register+70} <ffffffff80161c3c>{sys_init_module+5980}
       <ffffffff8010f4bd>{error_exit+0} <ffffffff802ce13d>{acpi_bus_register_driver+0}
       <ffffffff8016de90>{file_read_actor+0} <ffffffff8016fa77>{__generic_file_aio_read+423}
       <ffffffff8016fc91>{generic_file_aio_read+49} <ffffffff8019a29d>{do_sync_read+173}
       <ffffffff801226bc>{do_page_fault+1100} <ffffffff80159c70>{autoremove_wake_function+0}
       <ffffffff8019afb6>{vfs_read+230} <ffffffff8019b143>{sys_read+83}
       <ffffffff8010ebf2>{system_call+126}
kobject_register failed for processor (-17)

Call Trace:<ffffffff80273e16>{kobject_register+70} <ffffffff80161c3c>{sys_init_module+5980}
       <ffffffff8010f4bd>{error_exit+0} <ffffffff802ce13d>{acpi_bus_register_driver+0}
       <ffffffff8016de90>{file_read_actor+0} <ffffffff8016fa77>{__generic_file_aio_read+423}
       <ffffffff8016fc91>{generic_file_aio_read+49} <ffffffff8019a29d>{do_sync_read+173}
       <ffffffff801226bc>{do_page_fault+1100} <ffffffff80159c70>{autoremove_wake_function+0}
       <ffffffff8019afb6>{vfs_read+230} <ffffffff8019b143>{sys_read+83}
       <ffffffff8010ebf2>{system_call+126}

It does not happen if it's a module.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"
-
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/