← Back to team overview

kernel-packages team mailing list archive

[Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts


Bisect result:

cab4604d2bb86315c120630af75a5f012e476596 is the first bad commit
commit cab4604d2bb86315c120630af75a5f012e476596
Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Date:   Fri Mar 18 10:11:07 2016 -0400

    xen/events: Mask a moving irq
    BugLink: http://bugs.launchpad.net/bugs/1571034
    commit ff1e22e7a638a0782f54f81a6c9cb139aca2da35 upstream.
    Moving an unmasked irq may result in irq handler being invoked on both
    source and target CPUs.
    With 2-level this can happen as follows:
    On source CPU:
            evtchn_2l_handle_events() ->
                generic_handle_irq() ->
                    handle_edge_irq() ->
                           /***** WE ARE HERE *****/
                           if (VALID_EVTCHN(evtchn))
    If at this moment target processor is handling an unrelated event in
    evtchn_2l_handle_events()'s loop it may pick up our event since target's
    cpu_evtchn_mask claims that this event belongs to it *and* the event is
    unmasked and still pending. At the same time, source CPU will continue
    executing its own handle_edge_irq().
    With FIFO interrupt the scenario is similar: irq_move_irq() may result
    in a EVTCHNOP_unmask hypercall which, in turn, may make the event
    pending on the target CPU.
    We can avoid this situation by moving and clearing the event while
    keeping event masked.
    Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
    Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx>
    Signed-off-by: Kamal Mostafa <kamal@xxxxxxxxxxxxx>

:040000 040000 dcaea6af1e798cf41920479a8ef000f9ecd9edb2
de7990a681d7a717184418adb9a2399fe1f7d0fc M      drivers

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Kernel panic after migration between XenServer 6.5 hosts

Status in linux package in Ubuntu:

Bug description:
  Problem: after live migration from one XenServer 6.5 server to another
  XenServer 6.5 the Ubuntu VM crashes (see attached screenshot).

  Affected verions (at least):
  1. Ubuntu 14.04 (3.19.0-61-generic)
  2. Ubuntu 16.04 (4.4.0-24-generic)

  Not affected versions:
  1.Ubuntu 14.04 (3.19.0-49-generic)

  The issue is not dependent on installed XenServer updates.
   total 0
   crw-rw---- 1 root audio 116,  1 Jun 16 11:23 seq
   crw-rw---- 1 root audio 116, 33 Jun 16 11:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   69.046113] nf_conntrack version 0.5.0 (7868 buckets, 31472 max)
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=250f9548-2a14-41c1-bc6e-63199d6e9236
  InstallationDate: Installed on 2016-02-02 (136 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
   lo        no wireless extensions.
   eth1      no wireless extensions.
   eth0      no wireless extensions.
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic root=UUID=5a4cba3d-3be6-4a07-9c55-d5ea7b52585e ro ipv6.disable=1 net.ifnames=0 biosdevname=0
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware                             1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 05/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.4.1-xs125381
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: dmi:bvnXen:bvr4.4.1-xs125381:bd05/11/2016:svnXen:pnHVMdomU:pvr4.4.1-xs125381:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.4.1-xs125381
  dmi.sys.vendor: Xen

To manage notifications about this bug go to: