After using the "put server to s3 sleep"  script thats build in with unMenu, the server went down, automatically woke up and its log showed tons of cmds and errors like this:

 

 

Nov 17 12:20:34 Tower kernel: sh            R running      0  3685  3306 0x00000000

Nov 17 12:20:34 Tower kernel:  c136221b c136221b 00000000 f6cbbe28 f6c8def0 00000000 00000000 f6cbbe54

Nov 17 12:20:34 Tower kernel:  c1005820 00000000 c136221b f6cbbe78 c101ee81 c134b316 00000000 00000e65

Nov 17 12:20:34 Tower kernel:  00000cea 00000000 f6c8def0 f6c8def0 f6cbbe8c c101eec7 000007d0 00000064

Nov 17 12:20:34 Tower kernel: Call Trace: (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1005820>] ? show_stack+0x13/0x17 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c101ee81>] ? sched_show_task+0x8e/0x98 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c101eec7>] ? show_state_filter+0x3c/0x71 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c10439d8>] ? try_to_freeze_tasks+0x158/0x21b (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1043ab3>] ? freeze_processes+0x18/0x79 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1043d09>] ? enter_state+0x7c/0xd9 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1043d7f>] ? pm_suspend+0x19/0x1f (Errors)

Nov 17 12:20:34 Tower kernel:  [<c114c134>] ? acpi_suspend+0x3c/0x58 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c114c7e8>] ? acpi_system_write_sleep+0x54/0x66 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c114c794>] ? acpi_system_write_sleep+0x0/0x66 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1099fdc>] ? proc_reg_write+0x56/0x6a (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1099f86>] ? proc_reg_write+0x0/0x6a (Errors)

Nov 17 12:20:34 Tower kernel:  [<c106cac4>] ? vfs_write+0x8c/0x116 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c106cfcf>] ? sys_write+0x3b/0x60 (Errors)

Nov 17 12:20:34 Tower kernel:  [<c1002935>] ? syscall_call+0x7/0xb (Errors)

 

is this something to worry? or should i ignore them?

Old thread, yes but still relevant.

 

Tried it on 5.0 final and got a similar errorlist.

But the server was up and running.