kernel 2.6.30-6.fc12.i686.PAE is doing this. Problem?

Clyde E. Kunkel clydekunkel7734 at cox.net
Mon Jun 15 12:50:03 UTC 2009


 From dmesg (partial only):
...
platform microcode: firmware: requesting intel-ucode/06-17-07
platform microcode: firmware: requesting intel-ucode/06-17-07
platform microcode: firmware: requesting intel-ucode/06-17-07
platform microcode: firmware: requesting intel-ucode/06-17-07
Microcode Update Driver: v2.00 <tigran at aivazian.fsnet.co.uk>, Peter Oruba
Microcode Update Driver: v2.00 removed.
BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
Pid: 2076, comm: modprobe Not tainted 2.6.30-6.fc12.i686.PAE #1
Call Trace:
  [<c07f2af5>] ? printk+0x22/0x35
  [<c046a3f4>] save_trace+0x89/0xa3
  [<c046a47e>] add_lock_to_list+0x70/0xb3
  [<c046c634>] __lock_acquire+0x996/0xb08
  [<c0536162>] ? sysfs_new_dirent+0x66/0x101
  [<c0536162>] ? sysfs_new_dirent+0x66/0x101
  [<c046c85d>] lock_acquire+0xb7/0xeb
  [<c0536162>] ? sysfs_new_dirent+0x66/0x101
  [<c0536162>] ? sysfs_new_dirent+0x66/0x101
  [<c07f593d>] _spin_lock+0x31/0x72
  [<c0536162>] ? sysfs_new_dirent+0x66/0x101
  [<c0536162>] sysfs_new_dirent+0x66/0x101
  [<c05d5b63>] ? vsnprintf+0x8a/0x261
  [<c05368da>] create_dir+0x34/0x93
  [<c0536976>] sysfs_create_dir+0x3d/0x5e
  [<c05d00b0>] ? kobject_get+0x20/0x37
  [<c05d023c>] kobject_add_internal+0xfa/0x1d1
  [<c05d0414>] kobject_add_varg+0x41/0x5e
  [<c05d0467>] kobject_init_and_add+0x36/0x4f
  [<c073059b>] cpufreq_add_dev+0x31d/0x592
  [<c0730055>] ? handle_update+0x0/0x4d
  [<c068738b>] sysdev_driver_register+0xa6/0x106
  [<fbb6a000>] ? acpi_cpufreq_init+0x0/0xf9 [acpi_cpufreq]
  [<c072f04d>] cpufreq_register_driver+0xae/0x183
  [<fbb6a000>] ? acpi_cpufreq_init+0x0/0xf9 [acpi_cpufreq]
  [<fbb6a0bd>] acpi_cpufreq_init+0xbd/0xf9 [acpi_cpufreq]
  [<c040309e>] do_one_initcall+0x75/0x193
  [<c040c69c>] ? dump_trace+0x8f/0xcf
  [<c0413841>] ? save_stack_trace+0x30/0x5d
  [<c046a3b0>] ? save_trace+0x45/0xa3
  [<c046a47e>] ? add_lock_to_list+0x70/0xb3
  [<c046c6ea>] ? __lock_acquire+0xa4c/0xb08
  [<c049aaf4>] ? tracepoint_update_probe_range+0x2e/0xa7
  [<c046adcb>] ? mark_lock+0x29/0x1f6
  [<c046afe6>] ? mark_held_locks+0x4e/0x78
  [<c046adcb>] ? mark_lock+0x29/0x1f6
  [<c046b2b3>] ? trace_hardirqs_on_caller+0x122/0x155
  [<c046afe6>] ? mark_held_locks+0x4e/0x78
  [<c07f3ddc>] ? __mutex_unlock_slowpath+0x105/0x124
  [<c046b2b3>] ? trace_hardirqs_on_caller+0x122/0x155
  [<c046b2ff>] ? trace_hardirqs_on+0x19/0x2c
  [<c045eefe>] ? __blocking_notifier_call_chain+0x5b/0x78
  [<c040f94d>] ? sched_clock+0x9/0xd
  [<c0469b4c>] ? lock_release_holdtime+0x39/0x143
  [<c045eefe>] ? __blocking_notifier_call_chain+0x5b/0x78
  [<c045e292>] ? up_read+0x29/0x4f
  [<c045eefe>] ? __blocking_notifier_call_chain+0x5b/0x78
  [<c045ef3c>] ? blocking_notifier_call_chain+0x21/0x37
  [<c0475cbd>] sys_init_module+0xa7/0x1c2
  [<c0409feb>] sysenter_do_call+0x12/0x38
...




More information about the fedora-test-list mailing list