When I run this kernel on my hyper threaded workstation I get a large 
number of messages (hundreds per second) of the form:

Dec 30 10:19:34 heathwren kernel: BUG: using smp_processor_id() in 
preemptible [00000001] code: nifd/2610
Dec 30 10:19:34 heathwren kernel: caller is mod_page_state_offset+0x10/0x26
Dec 30 10:19:34 heathwren kernel:  [<c01d703b>] 
debug_smp_processor_id+0x77/0x8c
Dec 30 10:19:34 heathwren kernel:  [<c013ae57>] 
mod_page_state_offset+0x10/0x26
Dec 30 10:19:34 heathwren kernel:  [<c013ae57>] 
mod_page_state_offset+0x10/0x26
Dec 30 10:19:34 heathwren kernel:  [<c0142b0f>] __handle_mm_fault+0x1c/0x18b
Dec 30 10:19:34 heathwren kernel:  [<c011269e>] do_page_fault+0x168/0x4aa
Dec 30 10:19:34 heathwren kernel:  [<c0112536>] do_page_fault+0x0/0x4aa
Dec 30 10:19:34 heathwren kernel:  [<c0103427>] error_code+0x4f/0x54
Dec 30 10:19:34 heathwren kernel:  [<c01d654c>] __copy_to_user_ll+0xd9/0xe4
Dec 30 10:19:34 heathwren kernel:  [<c016afb4>] seq_read+0x1e3/0x26a
Dec 30 10:19:34 heathwren kernel:  [<c015042b>] vfs_read+0x87/0x11e
Dec 30 10:19:34 heathwren kernel:  [<c0150706>] sys_read+0x3b/0x64
Dec 30 10:19:34 heathwren kernel:  [<c01028a7>] sysenter_past_esp+0x54/0x75

in the system log and on all consoles and terminal windows.

When I run the kernel on my old dual CPU celeron test box the messages 
do not appear.

I assume from the fact that the messages go to all terminals that 
whoever wrote the code that initiated these messages is keen to hear 
about them if they occur.  Hence this message.

I'm willing to do whatever I can to help resolve this issue in the way 
of testing etc.

The .config file used to compile the kernel is attached.

The relevant system log is too large to attach to an e-mail but can be 
made available on request.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce