High load after swapper Tainted kernel message

  • Hi,


    I have a long running OMV server :-


      Version: 0.4.24 (Fedaykin)
      Processor: Intel(R) Pentium(R) CPU G630 @ 2.70GHz
      Kernel : Linux 2.6.32-5-amd64
      Uptime: 355 days 9 hours 5 minutes 43 seconds


    Out of the blue, yesterday it emitted this



      Dec 8 14:10:22 lovage kernel: [30597762.777615] Pid: 0, comm: swapper Tainted: G W 2.6.32-5-amd64 #1
      Dec 8 14:10:22 lovage kernel: [30597762.777618] Call Trace:
      Dec 8 14:10:22 lovage kernel: [30597762.777620] <IRQ> [<ffffffff81095d7d>] ? __report_bad_irq+0x30/0x7d
      Dec 8 14:10:22 lovage kernel: [30597762.777632] [<ffffffff81095ecf>] ? note_interrupt+0x105/0x16e
      Dec 8 14:10:22 lovage kernel: [30597762.777637] [<ffffffff81096534>] ? handle_fasteoi_irq+0x93/0xb5
      Dec 8 14:10:22 lovage kernel: [30597762.777642] [<ffffffff8101327f>] ? handle_irq+0x17/0x1d
      Dec 8 14:10:22 lovage kernel: [30597762.777646] [<ffffffff810128d9>] ? do_IRQ+0x57/0xb6
      Dec 8 14:10:22 lovage kernel: [30597762.777649] [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11
      Dec 8 14:10:22 lovage kernel: [30597762.777651] <EOI> [<ffffffffa021d271>] ? acpi_idle_enter_c1+0x9d/0xb8 [processor]
      Dec 8 14:10:22 lovage kernel: [30597762.777667] [<ffffffffa021d24c>] ? acpi_idle_enter_c1+0x78/0xb8 [processor]
      Dec 8 14:10:22 lovage kernel: [30597762.777673] [<ffffffff8123a2e2>] ? cpuidle_idle_call+0x94/0xee
      Dec 8 14:10:22 lovage kernel: [30597762.777678] [<ffffffff8100fe97>] ? cpu_idle+0xa2/0xda
      Dec 8 14:10:22 lovage kernel: [30597762.777683] [<ffffffff8151c140>] ? early_idt_handler+0x0/0x71
      Dec 8 14:10:22 lovage kernel: [30597762.777687] [<ffffffff8151ccdd>] ? start_kernel+0x3dc/0x3e8
      Dec 8 14:10:22 lovage kernel: [30597762.777691] [<ffffffff8151c3b7>] ? x86_64_start_kernel+0xf9/0x106


    There have been no further occurrences, but ever since, the load average has been high (3-6). I presume this will be cleared by a reboot which I will try and carry out tonight when I get home. The questions are :-


      has anyone seen this type of behavior before?
      do any of those messages tell me it might not come back after the reboot?
      with an uptime of 355 days, will an fsck be forced on reboot?
      is there anything worth checking before I reboot?
      what should I have in /etc/apt/sources.list?


    Regarding that last point, the Update manager looks healthy enough, its just that whilst I have all the clients shut down, assuming it recovers, now would be a good time to bring it up to latest (0.4.n at any rate).


    Thanks
    --
    Andy

    • Offizieller Beitrag

    It should be fine when you reboot. It will probably fsck the drives. Your /etc/apt/sources.list should be fine too.


    Just a note... You can update the OpenMediaVault package (and quite a few others) without rebooting.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hi,


    Thanks for the confidence inspiring reply, load average now back to normal. It did force an fsck on all the file systems which found a dozen or so orphaned nodes when it recovered the journal in the home directories.


    I was aware that the updates can be applied to the live system but I choose caution over any unnecessary changes, the domestic consequences of loosing a TV recording would make my life a misery :)


    Thanks all for a great piece of software and the terrific support, looking forward to another trouble free year!
    --
    Andy

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!