ups in dmesg sysfs_add_one()

[Infecto]

From time to time system freeze, caps lock blink :)
And what i see in dmesg,

[ 34.703209] sysfs: duplicate filename 'pcspkr' can not be created
[ 34.703211] WARNING: at /build/buildd/linux-2.6.24/fs/sysfs/dir.c:424 sysfs_add_one()
[ 34.703214] Pid: 3148, comm: modprobe Tainted: P 2.6.24-16-generic #1
[ 34.703217] [<c01d29af>] sysfs_add_one+0x9f/0xe0
[ 34.703225] [<c01d2ee8>] create_dir+0x48/0x90
[ 34.703229] [<c01d2f59>] sysfs_create_dir+0x29/0x50
[ 34.703231] [<c021098f>] kobject_get+0xf/0x20
[ 34.703234] [<c0210e53>] kobject_add+0x93/0x1b0
[ 34.703238] [<c0211001>] kobject_register+0x21/0x50
[ 34.703240] [<c027d121>] bus_add_driver+0x71/0x1e0
[ 34.703245] [<c01506b6>] sys_init_module+0x126/0x19c0
[ 34.703258] [<c013f190>] param_get_int+0x0/0x20
[ 34.703264] [<c01043c2>] sysenter_past_esp+0x6b/0xa9
[ 34.703270] =======================
[ 34.703272] kobject_add failed for pcspkr with -EEXIST, don't try to register things with the same name in the same directory.
[ 34.703276] Pid: 3148, comm: modprobe Tainted: P 2.6.24-16-generic #1
[ 34.703278] [<c0210ed3>] kobject_add+0x113/0x1b0
[ 34.703281] [<c0211001>] kobject_register+0x21/0x50
[ 34.703284] [<c027d121>] bus_add_driver+0x71/0x1e0
[ 34.703288] [<c01506b6>] sys_init_module+0x126/0x19c0
[ 34.703300] [<c013f190>] param_get_int+0x0/0x20
[ 34.703305] [<c01043c2>] sysenter_past_esp+0x6b/0xa9
[ 34.703311] =======================
[ 34.704108] ACPI: PCI interrupt for device 0000:02:00.0 disabled

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

[Brian Murray (brian-murray)]

Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".