IG82 Posted January 20, 2013 Share Posted January 20, 2013 I have upgraded one of my HP N36L Microservers to RC10. It was running beta12 prior to this. This is a spare machine really I am not using properly yet, I still have another running beta12. I ran a parity check prior to and after upgrading. Both ran clear in terms of parity errors but after upgrading my syslog contains a large number of errors, below is an excerpt. The parity check takes around 6 hours and these errors only occur for roughly the first half. The only addon I usually use is unmenu and the results are the same when I disable this and run as stock. The full syslog is also attached. Anyone have any ideas or suggestions? There are a few other threads but no of these are on RC10. Jan 18 10:18:31 hp2 kernel: INFO: rcu_sched self-detected stall on CPU { 1} (t=6000 jiffies) Jan 18 10:18:31 hp2 kernel: Pid: 1210, comm: unraidd Not tainted 3.4.24-unRAID #1 (Errors) Jan 18 10:18:31 hp2 kernel: Call Trace: (Errors) Jan 18 10:18:31 hp2 kernel: [<c1057ba2>] print_cpu_stall+0x6d/0xe5 (Errors) Jan 18 10:18:31 hp2 kernel: [<c1057c55>] __rcu_pending+0x3b/0x138 (Errors) Jan 18 10:18:31 hp2 kernel: [<c1057dc8>] rcu_check_callbacks+0x76/0xa1 (Errors) Jan 18 10:18:31 hp2 kernel: [<c102c96e>] update_process_times+0x2d/0x58 (Errors) Jan 18 10:18:31 hp2 kernel: [<c104b0fb>] tick_periodic+0x63/0x65 (Errors) Jan 18 10:18:31 hp2 kernel: [<c104b116>] tick_handle_periodic+0x19/0x6f (Errors) Jan 18 10:18:31 hp2 kernel: [<c121d968>] ? add_interrupt_randomness+0x125/0x12d (Errors) Jan 18 10:18:31 hp2 kernel: [<c104b467>] tick_do_periodic_broadcast+0x4f/0x88 (Errors) Jan 18 10:18:31 hp2 kernel: [<c104b4b0>] tick_handle_periodic_broadcast+0x10/0x4b (Errors) Jan 18 10:18:31 hp2 kernel: [<c1004265>] timer_interrupt+0xd/0x14 (Errors) Jan 18 10:18:31 hp2 kernel: [<c10534a1>] handle_irq_event_percpu+0x2a/0x11a (Errors) Jan 18 10:18:31 hp2 kernel: [<c1055866>] ? irq_set_chip_and_handler_name+0x27/0x27 (Errors) Jan 18 10:18:31 hp2 kernel: [<c10535b6>] handle_irq_event+0x25/0x3c (Errors) Jan 18 10:18:31 hp2 kernel: [<c1055866>] ? irq_set_chip_and_handler_name+0x27/0x27 (Errors) Jan 18 10:18:31 hp2 kernel: [<c1055914>] handle_edge_irq+0xae/0xce (Errors) Jan 18 10:18:31 hp2 kernel: <IRQ> [<c10036c3>] ? do_IRQ+0x37/0x9b Jan 18 10:18:31 hp2 kernel: [<c1240a62>] ? scsi_finish_command+0x9d/0xa3 (Errors) Jan 18 10:18:31 hp2 kernel: [<c10285ae>] ? irq_enter+0x41/0x41 (Errors) Jan 18 10:18:31 hp2 kernel: [<c133dfa9>] ? common_interrupt+0x29/0x30 (Errors) Jan 18 10:18:31 hp2 kernel: [<c10285ae>] ? irq_enter+0x41/0x41 (Errors) Jan 18 10:18:31 hp2 kernel: [<c10285ea>] ? __do_softirq+0x3c/0xfa (Errors) Jan 18 10:18:31 hp2 kernel: [<c10285ae>] ? irq_enter+0x41/0x41 (Errors) Jan 18 10:18:31 hp2 kernel: <IRQ> [<c1028462>] ? irq_exit+0x32/0x58 Jan 18 10:18:31 hp2 kernel: [<c1003713>] ? do_IRQ+0x87/0x9b (Errors) Jan 18 10:18:31 hp2 kernel: [<c10401f2>] ? default_wake_function+0xb/0xd (Errors) Jan 18 10:18:31 hp2 kernel: [<c133dfa9>] ? common_interrupt+0x29/0x30 (Errors) Jan 18 10:18:31 hp2 kernel: [<c11b6521>] ? memcmp+0x1a/0x25 (Errors) Jan 18 10:18:31 hp2 kernel: [<f851c902>] ? handle_stripe+0xb54/0xdc1 [md_mod] (Errors) Jan 18 10:18:31 hp2 kernel: [<c1028486>] ? irq_exit+0x56/0x58 (Errors) Jan 18 10:18:31 hp2 kernel: [<c103d03d>] ? __wake_up+0x3b/0x42 (Errors) Jan 18 10:18:31 hp2 kernel: [<f851cbe7>] ? unraidd+0x78/0xbc [md_mod] (Errors) Jan 18 10:18:31 hp2 kernel: [<f8519b31>] ? md_thread+0xcc/0xe3 [md_mod] (Errors) Jan 18 10:18:31 hp2 kernel: [<c10379a1>] ? wake_up_bit+0x5b/0x5b (Errors) Jan 18 10:18:31 hp2 kernel: [<f8519a65>] ? import_device+0x166/0x166 [md_mod] (Errors) Jan 18 10:18:31 hp2 kernel: [<c10376a8>] ? kthread+0x67/0x6c (Errors) Jan 18 10:18:31 hp2 kernel: [<c1037641>] ? kthread_freezable_should_stop+0x49/0x49 (Errors) Jan 18 10:18:31 hp2 kernel: [<c133dfb6>] ? kernel_thread_helper+0x6/0xd (Errors) syslog-2013-01-19.zip Link to comment
limetech Posted January 21, 2013 Share Posted January 21, 2013 That's a "harmless" warning message. I need to do some work in the unraid driver to get rid of it, which I'll do when I'm integrating with the 64-bit kernel. Link to comment
IG82 Posted January 22, 2013 Author Share Posted January 22, 2013 Ok, many thanks for the reply Tom. Link to comment
SnickySnacks Posted January 25, 2013 Share Posted January 25, 2013 Glad I found this thread, was having an issue this morning and saw the same errors and panicked a little >.< What's the cause of this, anyways? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.