none
Linux VM call traces in kernel log "bad: scheduling from the idle thread!" RRS feed

  • שאלה

  • Hi Experts,

    We are running a custom Linux VM on Microsoft Hyper-V installed on Cisco UCS-E Hardware. Suddenly it went unreachable and when checked the dmesg, we have the below call traces infinitely. ( the syslog file grows more than 1GB with this call trace )

    <snip>
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-3-900000: [7709225.057006] bad: scheduling from the idle thread!
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] Pid: 0, comm: swapper Tainted: P 2.6.32.59.cge #1
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] Call Trace:
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff8103b349>] dequeue_task_idle+0x24/0x30
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff81035ccb>] dequeue_task+0xbf/0xcb
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff81035cff>] deactivate_task+0x28/0x30
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff815b2aa7>] __schedule_nobkl+0xea/0x736
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff8124503e>] ? pm_idle_entry_callback+0x30/0x34
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff815b76a2>] ? notifier_call_chain+0x32/0x5e
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff8100c8de>] ? apic_timer_interrupt+0xe/0x20
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff815b3258>] __schedule+0x3c/0x55
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff8100aff9>] cpu_idle+0x8a/0x9d
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff81589a1f>] rest_init+0xa3/0xa5
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff819e4e7c>] start_kernel+0x3f7/0x402
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff819e42a5>] x86_64_start_reservations+0xac/0xb0
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-4-900000: [7709225.057006] [<ffffffff819e439d>] x86_64_start_kernel+0xf4/0x103
    2019 May 27 21:47:58 sn0859 kernel: %WAAS-SYS-3-900000:

    shell# uname -a
    Linux sn0859 2.6.32.59.cge #1 SMP PREEMPT Wed May 18 09:44:37 PDT 2016 x86_64 GNU/Linux

    Linux Integration Services version 3.4

    We could not have relevant error at the time of issue started as the logs got overridden.

    Anyone have an idea what happened?

    Any help is appreciated.

    יום שני 03 יוני 2019 09:54

כל התגובות

  • Hi Saleem,

    I don't see anything in particular in the call trace provided that would relate to the LIS drivers, and are more towards coming from the kernel itself.

    If possible I would suggest to use a newer kernel, even from the 2.6 series if a different tree is not an option.

    יום שני 03 יוני 2019 14:31
  • Hi Chris,

    Thanks for the comments.

    I have found a related patch in Hyper-V LIS driver. It is matching in the kernel version. Need to get more info on this.

    https://lore.kernel.org/patchwork/patch/636696/

    Thanks,

    Saleem


    יום חמישי 20 יוני 2019 16:28