[Kernel-packages] [Bug 2077321] Re: Please backport the more restrictive XSAVES deactivation for Zen1/2 arch

[Louis Bouchard]

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Oracular)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077321

Title:
  Please backport the more restrictive XSAVES deactivation for  Zen1/2
  arch

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  New
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  Confirmed

Bug description:
  On recent kernels, commit https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/jammy/commit/?id=b0563468eeac88ebc70559d52a0b66efc37e4e9d
  deactivate the XSAVES instruction for Zen 1/2 architectures.

  This means that for a QEMU vm using cpu=host running on older kernels
  where XSAVES is activated, it will not be possible to migrate that VM
  to newer kernels which have the XSAVES disabled.

  The more recent commit
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29ba89f1895285f06c333546882e0c5ae9a6df23
  only deactivates XSAVES on kernel where the fixed microcode is not
  present.

  This will prevent the QEMU migration problem to occur on AMD system
  where the microcode has been correctly updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077321/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2077321] [NEW] Please backport the more restrictive XSAVES deactivation for Zen1/2 arch

[Louis Bouchard]

Public bug reported:

On recent kernels, commit https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?id=b0563468eeac88ebc70559d52a0b66efc37e4e9d
deactivate the XSAVES instruction for Zen 1/2 architectures.

This means that for a QEMU vm using cpu=host running on older kernels
where XSAVES is activated, it will not be possible to migrate that VM to
newer kernels which have the XSAVES disabled.

The more recent commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29ba89f1895285f06c333546882e0c5ae9a6df23
only deactivates XSAVES on kernel where the fixed microcode is not
present.

This will prevent the QEMU migration problem to occur on AMD system
where the microcode has been correctly updated.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Oracular)
 Importance: Undecided
 Status: Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077321

Title:
  Please backport the more restrictive XSAVES deactivation for  Zen1/2
  arch

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  New
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  Confirmed

Bug description:
  On recent kernels, commit https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/jammy/commit/?id=b0563468eeac88ebc70559d52a0b66efc37e4e9d
  deactivate the XSAVES instruction for Zen 1/2 architectures.

  This means that for a QEMU vm using cpu=host running on older kernels
  where XSAVES is activated, it will not be possible to migrate that VM
  to newer kernels which have the XSAVES disabled.

  The more recent commit
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29ba89f1895285f06c333546882e0c5ae9a6df23
  only deactivates XSAVES on kernel where the fixed microcode is not
  present.

  This will prevent the QEMU migration problem to occur on AMD system
  where the microcode has been correctly updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077321/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

** Also affects: grub2 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

** Also affects: grub2 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Impish)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in grub2 source package in Impish:
  New
Status in linux source package in Impish:
  Invalid
Status in grub2 source package in Jammy:
  New
Status in linux source package in Jammy:
  Invalid

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPa

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

So testing with Fedora's boot/efi/EFI/fedora/grubx64.efi in place of the
Ubuntu version solves the problem.

So it is indeed the situation that you describe in comment #15

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  d

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

Hi xnox,

Thanks for the reply. I'll test both options and report to you here.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version

[Kernel-packages] [Bug 1955395] Re: Jammy kernel does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

Recent tests with the most recent 5.15 kernel (5.15.0-25-generic) do
display the same problem, though the symptom is different.

Booting w/o the swiotlb=262144 leads to the boot sequence stopping after
these messages :

[1.376749] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating 
SPD
[1.379840] cryptd: max_cpu_qlen set to 1000
[1.381359] scsi host1: ahci
[1.384854] AVX2 version of gcm_enc/dec engaged.
[1.385579] AES CTR mode by8 optimization enabled
[1.386280] scsi host2: ahci
[1.387162] scsi host3: ahci
[1.387659] scsi host4: ahci
[1.388141] scsi host5: ahci
[1.388675] scsi host6: ahci
[1.389091] ata1: SATA max UDMA/133 abar m4096@0x9100 port 0x91000100 
irq 36
[1.389937] ata2: SATA max UDMA/133 abar m4096@0x9100 port 0x91000180 
irq 36
[1.390787] ata3: SATA max UDMA/133 abar m4096@0x9100 port 0x91000200 
irq 36
[1.391599] ata4: SATA max UDMA/133 abar m4096@0x9100 port 0x91000280 
irq 36
[1.392417] ata5: SATA max UDMA/133 abar m4096@0x9100 port 0x91000300 
irq 36
[1.393251] ata6: SATA max UDMA/133 abar m4096@0x9100 port 0x91000380 
irq 36
[1.707933] ata3: SATA link down (SStatus 0 SControl 300)
[1.709684] ata4: SATA link down (SStatus 0 SControl 300)
[1.711379] ata5: SATA link down (SStatus 0 SControl 300)
[1.712945] ata2: SATA link down (SStatus 0 SControl 300)
[1.714405] ata1: SATA link down (SStatus 0 SControl 300)
[1.715926] ata6: SATA link down (SStatus 0 SControl 300)
[3.352937] pcieport :00:1e.0: pciehp: Slot(0): No device found
[3.356935] pcieport :00:1e.2: pciehp: Slot(2): No device found
[3.368942] pcieport :00:1e.1: pciehp: Slot(1): No device found
[3.368958] pcieport :00:1e.3: pciehp: Slot(3): No device found
[3.384970] pcieport :00:1e.4: pciehp: Slot(4): No device found
[3.384991] pcieport :00:1e.6: pciehp: Slot(6): No device found
[3.396926] pcieport :00:1e.5: pciehp: Slot(5): No device found
[3.396957] pcieport :00:1e.7: pciehp: Slot(7): No device found

And after a period of time we start seeing  :
[  242.880954] INFO: task kworker/u16:0:8 blocked for more than 120 seconds.



[  242.882063]   Not tainted 5.15.0-25-generic #25-Ubuntu   



[  242.882895] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.


[  242.884165] task:kworker/u16:0   state:D stack:0 pid:8 ppid: 2 
flags:0x4000

  
[  242.885520] Workqueue: events_unbound async_run_entry_fn 



[  242.886383] Call Trace:  



[  242.886783]



[  242.887133]  __schedule+0x23d/0x590  



[  242.887716]  schedule+0x4e/0xb0  



[  242.888221]  async_synchronize_cookie_domain+0xcc/0x110  



[  242.889077]  ? wait_woken+0x70/0x70  
   

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.532575] general protection fault:  [#1] SMP NOPTI
  [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
  [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
  [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.535120] RBP: b96e4001be10 R08:  R09: 
0228
  [1.538947] R10: 0001 R11:  R12: 
978437e555a0
  [1.538947] R13:  R14:  R15: 

  [1.538947] FS:  () GS:97843f6c() 
knlGS:
  [1.538947] CS:  0010 DS:  ES:  CR0: 80050033
  [1.538947] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.538947] Call Trace:
  [1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
  [1.538947]  do_one_initcall+0x4a/0x200
  [1.538947]  kernel_init_freeable+0x1c0/0x263
  [1.538947]  ? rest_init+0xb0/0xb0
  [1.538947]  kernel_init+0xe/0x110
  [1.538947]  ret_from_fork+0x22/0x40
  [1.538947] Modules linked in:
  [1.545871] ---[ end trace 815dc8177e65da02 ]---
  [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.550617] RBP: b96e4001be10 R08:  R09: 
0228
  [1.551337] R10: 0001 R11:  R12: 
978437e555a0
  [1.552036] R13:  R14:  R15: 

  [1.552737] FS:  () GS:97843f6c() 
knlGS:
  [1.553529] CS:  0010 DS:  ES:  CR0: 80050033
  [1.554093] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
  -

  The previous kernel (linux-image-5.4.0-91-generic) boots correctly
  with SEV.

  Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
  following commit as the source of regresssion :

  # git bisect good
  7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit
  commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76
  Author: Lenny Szubowicz 
  Date:   Fri Sep 4 21:31:05 2020 -0400

  efi: Support for MOK variable config table

  BugLink: https://bugs.launchpad.net/bugs/1928679

  ...

  Since the panic happens in very early stages of boot, no trace of the
  panic is present in the log files and apparently it is not possible to
  collect a kernel crash dump, the crashkernel has not been enabled yet.

  [Test case]

  The kernel need to boot properly with SEV enabled.

  [Potential regression]

  The fix is very specific and restricted and should cause regressions,
  however it touches ioremap that is widely used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions


-- 
Mailing list: https://launchpad.net/~

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

Here is the result of a similar bisect on the bionic kernel :

https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=091554e4a5b2a7647830a1c7beea781148b51509

091554e4a5b2a7647830a1c7beea781148b51509 is the first bad commit
commit 091554e4a5b2a7647830a1c7beea781148b51509 
 
Author: Lenny Szubowicz
 
Date:   Tue Nov 30 12:04:00 2021 +0100  
 

 
efi: Support for MOK variable config table  
 

 
BugLink: https://bugs.launchpad.net/bugs/1928679 

 
Because of system-specific EFI firmware limitations, EFI volatile 
variables may not be capable of holding the required contents of  
the Machine Owner Key (MOK) certificate store when the certificate  
list grows above some size. Therefore, an EFI boot loader may pass  
 
the MOK certs via a EFI configuration table created specifically for
this purpose to avoid this firmware limitation. 

   

 
An EFI configuration table is a much more primitive mechanism   

   
compared to EFI variables and is well suited for one-way passage

   
of static information from a pre-OS environment to the kernel. 

 
This patch adds initial kernel support to recognize, parse, 
and validate the EFI MOK configuration table, where named   
 
entries contain the same data that would otherwise be provided  

   
in similarly named EFI variables.   

   


   
Additionally, this patch creates a sysfs binary file for each
EFI MOK configuration table entry found. These files are read-only
to root and are provided for use by user space utilities such as
mokutil. 
  
A subsequent patch will load MOK certs into the trusted platform
key ring using this infrastructure.   
 
Signed-off-by: Lenny Szubowicz 
Link: https://lore.kernel.org/r/20200905013107.10457-2-lszub...@redhat.com
Signed-off-by: Ard Biesheuvel  
 
(cherry picked from commit 58c909022a5a56cd1d9e89c8c5461fd1f6a27bb5)
Signed-off-by: Dimitri John Ledkov  
Acked-by: Thadeu Lima de Souza Cascardo   
Acked-by: Tim Gardner
Signed-off-by: Kleber Sacilotto de Souza 

 arch/x86/kernel/setup.c |   1 +
 
 drivers/firmware/efi/Makefile   |   1 +
 
 drivers/firmware/efi/arm-init.c |   1 +
 
 drivers/firmware/efi/efi.c  |   9 +
 drivers/firmware/efi/mokvar-table.c | 360 
 include/linux/efi.h |  34  
 
 6 files changed, 406 insertions(+) 
 
 create mode 100644 drivers/firmware/efi/mokvar-table.c

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

T

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

Hello @kmously, yes I am able to reproduce the same panic on 4.15.0-166.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.532575] general protection fault:  [#1] SMP NOPTI
  [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
  [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
  [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.535120] RBP: b96e4001be10 R08:  R09: 
0228
  [1.538947] R10: 0001 R11:  R12: 
978437e555a0
  [1.538947] R13:  R14:  R15: 

  [1.538947] FS:  () GS:97843f6c() 
knlGS:
  [1.538947] CS:  0010 DS:  ES:  CR0: 80050033
  [1.538947] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.538947] Call Trace:
  [1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
  [1.538947]  do_one_initcall+0x4a/0x200
  [1.538947]  kernel_init_freeable+0x1c0/0x263
  [1.538947]  ? rest_init+0xb0/0xb0
  [1.538947]  kernel_init+0xe/0x110
  [1.538947]  ret_from_fork+0x22/0x40
  [1.538947] Modules linked in:
  [1.545871] ---[ end trace 815dc8177e65da02 ]---
  [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.550617] RBP: b96e4001be10 R08:  R09: 
0228
  [1.551337] R10: 0001 R11:  R12: 
978437e555a0
  [1.552036] R13:  R14:  R15: 

  [1.552737] FS:  () GS:97843f6c() 
knlGS:
  [1.553529] CS:  0010 DS:  ES:  CR0: 80050033
  [1.554093] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
  -

  The previous kernel (linux-image-5.4.0-91-generic) boots correctly
  with SEV.

  Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
  following commit as the source of regresssion :

  # git bisect good
  7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit
  commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76
  Author: Lenny Szubowicz 
  Date:   Fri Sep 4 21:31:05 2020 -0400

  efi: Support for MOK variable config table

  BugLink: https://bugs.launchpad.net/bugs/1928679

  ...

  Since the panic happens in very early stages of boot, no trace of the
  panic is present in the log files and apparently it is not possible to
  collect a kernel crash dump, the crashkernel has not been enabled yet.

  [Test case]

  The kernel need to boot properly with SEV enabled.

  [Potential regression]

  The fix is very specific and restricted and should cause regressions,
  however it touches ioremap that is widely used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
P

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

According to the following advisory[1] from HP, this is a known issue
which is fixed upstream :

"Advisory: Red Hat Enterprise Linux 8.3 - Guest Stops Responding at
efi_mokvar_sysfs_init+0xa9/0x19d with AMD Secure Encrypted
Virtualization (SEV) Enabled"

The upstream fix cited in the article is the following :

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b

x86/ioremap: Map EFI-reserved memory as encrypted for SEV

Adding this commit on top of kernel 5.4.0-92.103 does fix the booting
issue.


[1] 
https://support.hpe.com/hpesc/public/docDisplay?docId=a00119071en_us&docLocale=en_US

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  New

Bug description:
  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.532575] general protection fault:  [#1] SMP NOPTI
  [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
  [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
  [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.535120] RBP: b96e4001be10 R08:  R09: 
0228
  [1.538947] R10: 0001 R11:  R12: 
978437e555a0
  [1.538947] R13:  R14:  R15: 

  [1.538947] FS:  () GS:97843f6c() 
knlGS:
  [1.538947] CS:  0010 DS:  ES:  CR0: 80050033
  [1.538947] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.538947] Call Trace:
  [1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
  [1.538947]  do_one_initcall+0x4a/0x200
  [1.538947]  kernel_init_freeable+0x1c0/0x263
  [1.538947]  ? rest_init+0xb0/0xb0
  [1.538947]  kernel_init+0xe/0x110
  [1.538947]  ret_from_fork+0x22/0x40
  [1.538947] Modules linked in:
  [1.545871] ---[ end trace 815dc8177e65da02 ]---
  [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.550617] RBP: b96e4001be10 R08:  R09: 
0228
  [1.551337] R10: 0001 R11:  R12: 
978437e555a0
  [1.552036] R13:  R14:  R15: 

  [1.552737] FS:  () GS:97843f6c() 
knlGS:
  [1.553529] CS:  0010 DS:  ES:  CR0: 80050033
  [1.554093] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
  -

  The previous kernel (linux-image-5.4.0-91-generic) boots correctly
  with SEV.

  Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
  following commit as the source of regresssion :

  # git bisect good
  7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit
  commit 7ca05228f713c24eb55574

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

** Description changed:

  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.
  
  The kernel panics with the following backtrace :
  
  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.532575] general protection fault:  [#1] SMP NOPTI
  [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
  [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
  [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.535120] RBP: b96e4001be10 R08:  R09: 
0228
  [1.538947] R10: 0001 R11:  R12: 
978437e555a0
  [1.538947] R13:  R14:  R15: 

  [1.538947] FS:  () GS:97843f6c() 
knlGS:
  [1.538947] CS:  0010 DS:  ES:  CR0: 80050033
  [1.538947] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.538947] Call Trace:
  [1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
  [1.538947]  do_one_initcall+0x4a/0x200
  [1.538947]  kernel_init_freeable+0x1c0/0x263
  [1.538947]  ? rest_init+0xb0/0xb0
  [1.538947]  kernel_init+0xe/0x110
  [1.538947]  ret_from_fork+0x22/0x40
  [1.538947] Modules linked in:
  [1.545871] ---[ end trace 815dc8177e65da02 ]---
  [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.550617] RBP: b96e4001be10 R08:  R09: 
0228
  [1.551337] R10: 0001 R11:  R12: 
978437e555a0
  [1.552036] R13:  R14:  R15: 

  [1.552737] FS:  () GS:97843f6c() 
knlGS:
  [1.553529] CS:  0010 DS:  ES:  CR0: 80050033
  [1.554093] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
  -
  
- 
- The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV.
+ The previous kernel (linux-image-5.4.0-91-generic) boots correctly with
+ SEV.
  
  Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
  following commit as the source of regresssion :
  
  # git bisect good
- Bisecting: 0 revisions left to test after this (roughly 1 step)
- [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) 
Make get_cert_list() not complain about cert lists that aren't present."
+ 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit
+ commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76
+ Author: Lenny Szubowicz 
+ Date:   Fri Sep 4 21:31:05 2020 -0400
+ 
+ efi: Support for MOK variable config table
+ 
+ BugLink: https://bugs.launchpad.net/bugs/1928679
+ 
+ ...
  
  Since the panic happens in very early stages of boot, no trace of the
  panic is present in the log files and apparently it is not possible to
  collect a kernel crash dump, the crashkernel has not been enabled yet.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.53257

[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

Details of the bisected commit :

https://kernel.ubuntu.com/git/ubuntu/ubuntu-
focal.git/commit/?id=5f79bc17fd8d078378a9f3c8773ebcb506cb6f40

Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert 
lists that aren't present."
BugLink: https://bugs.launchpad.net/bugs/1932029

This partially reverts commit f32d73b5b9b4d8cb8e64bf51091c971d05116d48.

The reverted commit fixed stray warnings, and changed get_cert_list()
function prototype (return rc, pass cert-list by reference). The stray
warnings fix was incomplete, and was done again in mainline with a
different change of get_cert_list() function prototype (return
cert-list pointer, pass EFI error status by reference), which got also
cherrypicked into Ubuntu kernel ending up with passing both cert-list
& efi error status by reference.

Cherrypicking both get_cert_list() function prototype changes is
redundant, and prevents clean cherrypicks from mainline. Revert the
get_cert_list() function prototype to the one in mainline.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registered to indicate activity on CPUs
  [1.531760] EFI Variables Facility v0.08 2004-May-17
  [1.532575] general protection fault:  [#1] SMP NOPTI
  [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
  [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
  [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.535120] RBP: b96e4001be10 R08:  R09: 
0228
  [1.538947] R10: 0001 R11:  R12: 
978437e555a0
  [1.538947] R13:  R14:  R15: 

  [1.538947] FS:  () GS:97843f6c() 
knlGS:
  [1.538947] CS:  0010 DS:  ES:  CR0: 80050033
  [1.538947] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.538947] Call Trace:
  [1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
  [1.538947]  do_one_initcall+0x4a/0x200
  [1.538947]  kernel_init_freeable+0x1c0/0x263
  [1.538947]  ? rest_init+0xb0/0xb0
  [1.538947]  kernel_init+0xe/0x110
  [1.538947]  ret_from_fork+0x22/0x40
  [1.538947] Modules linked in:
  [1.545871] ---[ end trace 815dc8177e65da02 ]---
  [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
  [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
  [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
  [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 

  [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: 
a2121860
  [1.550617] RBP: b96e4001be10 R08:  R09: 
0228
  [1.551337] R10: 0001 R11:  R12: 
978437e555a0
  [1.552036] R13:  R14:  R15: 

  [1.552737] FS:  () GS:97843f6c() 
knlGS:
  [1.553529] CS:  0010 DS:  ES:  CR0: 80050033
  [1.554093] CR2:  CR3: 00080011a060a001 CR4: 
00360ee0
  [1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
  [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
  -

  
  The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV.

  Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
  following commit as the source of regresssion :

  # git bisect good
  Bisecting: 0 revisions left to test after this (roughly 1 step)
  [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) 

[Kernel-packages] [Bug 1956575] [NEW] [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled

[Louis Bouchard]

Public bug reported:

The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
when SEV is enabled.

The kernel panics with the following backtrace :

[1.531125] ledtrig-cpu: registered to indicate activity on CPUs
[1.531760] EFI Variables Facility v0.08 2004-May-17
[1.532575] general protection fault:  [#1] SMP NOPTI
[1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15
[1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015
[1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
[1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
[1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
[1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 
[1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860
[1.535120] RBP: b96e4001be10 R08:  R09: 0228
[1.538947] R10: 0001 R11:  R12: 978437e555a0
[1.538947] R13:  R14:  R15: 
[1.538947] FS:  () GS:97843f6c() 
knlGS:
[1.538947] CS:  0010 DS:  ES:  CR0: 80050033
[1.538947] CR2:  CR3: 00080011a060a001 CR4: 00360ee0
[1.538947] Call Trace:
[1.538947]  ? efi_rci2_sysfs_init+0x29a/0x29a
[1.538947]  do_one_initcall+0x4a/0x200
[1.538947]  kernel_init_freeable+0x1c0/0x263
[1.538947]  ? rest_init+0xb0/0xb0
[1.538947]  kernel_init+0xe/0x110
[1.538947]  ret_from_fork+0x22/0x40
[1.538947] Modules linked in:
[1.545871] ---[ end trace 815dc8177e65da02 ]---
[1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184
[1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd 
f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 
0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85
[1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202
[1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: 
[1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860
[1.550617] RBP: b96e4001be10 R08:  R09: 0228
[1.551337] R10: 0001 R11:  R12: 978437e555a0
[1.552036] R13:  R14:  R15: 
[1.552737] FS:  () GS:97843f6c() 
knlGS:
[1.553529] CS:  0010 DS:  ES:  CR0: 80050033
[1.554093] CR2:  CR3: 00080011a060a001 CR4: 00360ee0
[1.554818] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b ]---
-


The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV.

Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the
following commit as the source of regresssion :

# git bisect good
Bisecting: 0 revisions left to test after this (roughly 1 step)
[5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) 
Make get_cert_list() not complain about cert lists that aren't present."

Since the panic happens in very early stages of boot, no trace of the
panic is present in the log files and apparently it is not possible to
collect a kernel crash dump, the crashkernel has not been enabled yet.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure Encrypted 
Virtualization(SEV) is enagbled
+ [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure Encrypted 
Virtualization(SEV) is enabled

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956575

Title:
  [Regression] Focal kernel  5.4.0-92.103 fails to boot when Secure
  Encrypted Virtualization(SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot
  when SEV is enabled.

  The kernel panics with the following backtrace :

  [1.531125] ledtrig-cpu: registere

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

As a complement of information, here are the messages pertaining to the
TLB during the log :

$ grep -i tlb swiotlb_crash.out 
[0.003802] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
[0.037784] kvm-guest: KVM setup pv remote TLB flush
[0.040674] software IO TLB: Cannot allocate buffer
[0.229918] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
[0.230877] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[0.322941] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[0.324641] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[0.799064] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[0.800761] software IO TLB: No low mem
[1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
[1.258821]  swiotlb_tbl_map_single.cold+0x57/0x7c
[1.259750]  swiotlb_map+0x61/0x240
[1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

Hello,
The kernel panic occurs very early in the boot sequence, even before the root 
fs is mounted to capture the log. Here is the kenrel backtrace :

[1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
[1.253440] CPU: 2 PID: 212 Comm: systemd-udevd Not tainted 
5.13.0-23-generic #23-Ubuntu
[1.255022] Hardware name: Scaleway SCW-ENT1-S, BIOS 0.0.0 02/06/2015
[1.256228] Call Trace:
[1.256697]  show_stack+0x52/0x58
[1.257355]  dump_stack+0x7d/0x9c
[1.257989]  panic+0x101/0x2e3
[1.258821]  swiotlb_tbl_map_single.cold+0x57/0x7c
[1.259750]  swiotlb_map+0x61/0x240
[1.260428]  dma_direct_map_page+0x115/0x1a0
[1.261255]  dma_map_page_attrs+0x35/0x50
[1.262016]  vring_map_one_sg+0x4c/0x50
[1.262787]  virtqueue_add_split+0x23c/0x4a0
[1.263427]  virtqueue_add_inbuf+0x48/0x50
[1.263909]  virtscsi_kick_event.isra.0+0x8b/0xd0 [virtio_scsi]
[1.264616]  virtscsi_probe+0x31e/0x33b [virtio_scsi]
[1.265216]  virtio_dev_probe+0x163/0x220
[1.265683]  really_probe+0x24b/0x4c0
[1.266134]  driver_probe_device+0xf0/0x160
[1.266647]  device_driver_attach+0xab/0xb0
[1.267188]  __driver_attach+0xb2/0x140
[1.267648]  ? device_driver_attach+0xb0/0xb0
[1.268163]  bus_for_each_dev+0x7e/0xc0
[1.268620]  driver_attach+0x1e/0x20
[1.269061]  bus_add_driver+0x135/0x1f0
[1.269516]  driver_register+0x95/0xf0
[1.269957]  ? 0xc038e000
[1.270344]  register_virtio_driver+0x20/0x30
[1.270885]  init+0x8d/0x1000 [virtio_scsi]
[1.271380]  ? 0xc038e000
[1.271762]  do_one_initcall+0x48/0x1d0
[1.272213]  ? kmem_cache_alloc_trace+0xfb/0x240
[1.272759]  do_init_module+0x62/0x290
[1.273199]  load_module+0xa8f/0xb10
[1.273620]  __do_sys_finit_module+0xc2/0x120
[1.274155]  __x64_sys_finit_module+0x18/0x20
[1.274680]  do_syscall_64+0x61/0xb0
[1.275118]  ? syscall_exit_to_user_mode+0x27/0x50
[1.275667]  ? __x64_sys_newfstatat+0x1c/0x20
[1.276177]  ? do_syscall_64+0x6e/0xb0
[1.276614]  ? ksys_read+0x67/0xe0
[1.277049]  ? exit_to_user_mode_prepare+0x37/0xb0
[1.277614]  ? syscall_exit_to_user_mode+0x27/0x50
[1.278180]  ? __x64_sys_read+0x19/0x20
[1.278653]  ? do_syscall_64+0x6e/0xb0
[1.279116]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[1.279709] RIP: 0033:0x7fe040ccd94d
[1.280140] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48
[1.282337] RSP: 002b:7ffe2399a6d8 EFLAGS: 0246 ORIG_RAX: 
0139
[1.283252] RAX: ffda RBX: 562e8ab7a030 RCX: 7fe040ccd94d
[1.284077] RDX:  RSI: 7fe040e61441 RDI: 0005
[1.284910] RBP: 0002 R08:  R09: 7ffe2399a810
[1.285754] R10: 0005 R11: 0246 R12: 7fe040e61441
[1.286594] R13: 562e8ab79ef0 R14: 562e8abd1c50 R15: 562e8abd4400
[1.288517] Kernel Offset: 0x25a0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---
-

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
bu

[Kernel-packages] [Bug 1955655] WifiSyslog.txt

[Louis Bouchard]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549375/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QE

[Kernel-packages] [Bug 1955655] acpidump.txt

[Louis Bouchard]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549376/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
 

[Kernel-packages] [Bug 1955655] UdevDb.txt

[Louis Bouchard]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1955655/+attachment/5549374/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.

[Kernel-packages] [Bug 1955655] ProcModules.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549373/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1955655] ProcInterrupts.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549372/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.ve

[Kernel-packages] [Bug 1955655] ProcCpuinfo.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549370/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1955655] Lspci.txt

[Louis Bouchard]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1955655/+attachment/5549368/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.ch

[Kernel-packages] [Bug 1955655] Lspci-vt.txt

[Louis Bouchard]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549369/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
 

[Kernel-packages] [Bug 1955655] ProcCpuinfoMinimal.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549371/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.ch

[Kernel-packages] [Bug 1955655] CurrentDmesg.txt

[Louis Bouchard]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1955655/+attachment/5549367/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955655

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor

[Kernel-packages] [Bug 1955655] [NEW] kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

[Louis Bouchard]

Public bug reported:

While investigating LP: #1955395 by using the -generic kernel image, it
appeared that it is impossible to boot the kernel unless the boot
parameter swiotlb is set to 512M (swiotlb=262144).

Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it
fails and later trigger a kernel panic with the following trace :

$ grep TLB /tmp/console.log
[0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
[0.034219] kvm-guest: KVM setup pv remote TLB flush
[0.037063] software IO TLB: Cannot allocate buffer
[0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
[0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[1.019552] software IO TLB: No low mem
[1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
[1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

The SWIOTLB adjustment comes from the following kernel commit :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

For some reason, the LowMem allocation fails (as seen by the "software
IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
completed.

When booting with the swiotlb=262144 value, we get the following output :
$ grep TLB /tmp/console.log

[0.050908] kvm-guest: KVM setup pv remote TLB flush
[0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
[0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
[0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
[1.529804] software IO TLB: Memory encryption is active and system is using 
DMA bounce buffers


For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

We can make SEV enabled resources available for testing if needed.

...Louis
--- 
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
 crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Scaleway SCW-ENT1-S
Package: linux (not installed)
PciMultimedia:
 
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-23-generic N/A
 linux-backports-modules-5.13.0-23-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags:  jammy uec-images
Uname: Linux 5.13.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-3.0
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-S:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
dmi.product.name: SCW-ENT1-S
dmi.product.version: pc-q35-3.0
dmi.sys.vendor: Scaleway

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-collected jammy uec-images

** Tags added: apport-collected jammy uec-images

** Description changed:

  While investigating LP: #1955395 by using the -generic kernel image, it
  appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).
  
  

[Kernel-packages] [Bug 1955395] ProcCpuinfoMinimal.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548705/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] Lspci.txt

[Louis Bouchard]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1955395/+attachment/5548702/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] acpidump.txt

[Louis Bouchard]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548710/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] WifiSyslog.txt

[Louis Bouchard]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548709/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] ProcInterrupts.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548706/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] ProcCpuinfo.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548704/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] ProcModules.txt

[Louis Bouchard]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548707/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] Lspci-vt.txt

[Louis Bouchard]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548703/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] UdevDb.txt

[Louis Bouchard]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1955395/+attachment/5548708/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
  dmi.product.name: SCW-ENT1-XL
  dmi.product.version: pc-q35-3.0
  dmi.sys.vendor: Scaleway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

apport information

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Confirmed

** Tags added: apport-collected uec-images

** Description changed:

  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor
  of the kernel does not boot on a QEMU server with Secure Encrypted
  Virtualization( SEV) enabled.
  
  Using the same kernel without the -kvm optimisation does boot correctly
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
+  crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu74
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: Scaleway SCW-ENT1-XL
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
+ ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-23-generic N/A
+  linux-backports-modules-5.13.0-23-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  jammy uec-images
+ Uname: Linux 5.13.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 02/06/2015
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: EFI Development Kit II / OVMF
+ dmi.bios.version: 0.0.0
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-q35-3.0
+ dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku:
+ dmi.product.name: SCW-ENT1-XL
+ dmi.product.version: pc-q35-3.0
+ dmi.sys.vendor: Scaleway

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1955395/+attachment/5548701/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot correctly
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 10:41 seq
   crw-rw 1 root audio 116, 33 Dec 20 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-XL
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendo

[Kernel-packages] [Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548694/+files/version.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot
  correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548693/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot
  correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955395] [NEW] KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled

[Louis Bouchard]

Public bug reported:

Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor
of the kernel does not boot on a QEMU server with Secure Encrypted
Virtualization( SEV) enabled.

Using the same kernel without the -kvm optimisation does boot correctly

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Incomplete


** Tags: jammy

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955395

Title:
  KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted
  Virtualization( SEV) is enabled

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm
  flavor of the kernel does not boot on a QEMU server with Secure
  Encrypted Virtualization( SEV) enabled.

  Using the same kernel without the -kvm optimisation does boot
  correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks

[Louis Bouchard]

** Also affects: linux-base (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1929255

Title:
  update-initrd-links creates incorrect symlinks

Status in linux-base package in Ubuntu:
  Confirmed
Status in linux-base source package in Bionic:
  Confirmed

Bug description:
  ## Problem description

  Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script
  incorrectly detects symbolic links targets and then creates malformed
  (hence broken) ones instead:

  /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic
  /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic

  while it should actually be:

  /initrd.img -> boot/initrd.img-5.3.0-53-generic
  /initrd.img.old -> boot/initrd.img-5.3.0-53-generic

  The problem appeared with the release of the version 4.5ubuntu1.5 of
  the linux-base package, which made this script executable.

  ## Solution

  A solution is proposed through the attached patch file.

  ## System information

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Uname: Linux 5.3.0-53-generic x86_64

  ## Package information

  Package: linux-base 4.5ubuntu1.5
  PackageArchitecture: all
  SourcePackage: linux-base
  Tags:  bionic package-from-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello,
Sorry to switch this bug back to Confirmed, but the fix that you mention is 
clearly not present in the latest kernel available in Focal :

root@launchpad-kernel:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal
root@launchpad-kernel:~# uname -a
Linux launchpad-kernel 5.4.0-1030-kvm #31-Ubuntu SMP Wed Dec 9 17:27:05 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
root@launchpad-kernel:~# grep IP_VS /boot/config-5.4.0-1030-kvm
# CONFIG_IP_VS is not set
root@launchpad-kernel:~# modprobe ip_vs
modprobe: FATAL: Module ip_vs not found in directory /lib/modules/5.4.0-1030-kvm

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Focal:
  Fix Released

Bug description:
  The NF_TABLES options are not included in the -kvm flavor of the 5.4
  kernel. This package is used in the Ubuntu Cloud Image.

  The linux-image-5.4.0-31-generic package has the options present in
  the config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello again,

Sorry for the noise, I blindly reported what one of our user told me
without checking. Its problem is IP_VS which has nothing to do with this
bug.

Thanks for your help in fixing this and, once again sorry.

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Focal:
  Fix Released

Bug description:
  The NF_TABLES options are not included in the -kvm flavor of the 5.4
  kernel. This package is used in the Ubuntu Cloud Image.

  The linux-image-5.4.0-31-generic package has the options present in
  the config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Hello Stefan,

Any hint on who could check on that ? What needs to be clarified is if
this is a requirement and there to stay or not.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Focal:
  Confirmed

Bug description:
  The NF_TABLES options are not included in the -kvm flavor of the 5.4
  kernel. This package is used in the Ubuntu Cloud Image.

  The linux-image-5.4.0-31-generic package has the options present in
  the config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880522] [NEW] CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

[Louis Bouchard]

Public bug reported:

The NF_TABLES options are not included in the -kvm flavor of the 5.4
kernel. This package is used in the Ubuntu Cloud Image.

The linux-image-5.4.0-31-generic package has the options present in the
config file.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880522

Title:
  CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm

Status in linux package in Ubuntu:
  New

Bug description:
  The NF_TABLES options are not included in the -kvm flavor of the 5.4
  kernel. This package is used in the Ubuntu Cloud Image.

  The linux-image-5.4.0-31-generic package has the options present in
  the config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880522/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs

[Louis Bouchard]

Hello,

Just tested the latest image in ./current and it boots fine :

root@focal-ok:~# uname -a
Linux focal-ok 5.4.0-1009-kvm #9-Ubuntu SMP Mon Apr 20 20:23:56 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
root@focal-ok:~# cat /etc/cloud/build.info
build_name: server
serial: 20200421
root@focal-ok:~# uname -r
5.4.0-1009-kvm
root@focal-ok:~# grep -i ^CONFIG_EFI /boot/config-5.4.0-1009-kvm 
CONFIG_EFI=y
CONFIG_EFI_STUB=y
CONFIG_EFI_MIXED=y
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_PARTITION=y
CONFIG_EFIVAR_FS=m

Thanks for the quick turnaround !
...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809

Title:
  Make linux-kvm bootable in LXD VMs

Status in cloud-images:
  Invalid
Status in linux-kvm package in Ubuntu:
  Triaged

Bug description:
  The `disk-kvm.img` images which are to be preferred when run under
  virtualization, currently completely fail to boot under UEFI.

  A workaround was put in place such that LXD instead will pull generic-
  based images until this is resolved, this however does come with a
  much longer boot time (as the kernel panics, reboots and then boots)
  and also reduced functionality from cloud-init, so we'd still like
  this fixed in the near future.

  To get things behaving, it looks like we need the following config
  options to be enable in linux-kvm:

   - CONFIG_EFI_STUB
   - CONFIG_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS_COMMON

  == Rationale ==
  We'd like to be able to use the linux-kvm based images for LXD, those will 
directly boot without needing the panic+reboot behavior of generic images and 
will be much lighter in general.

  We also need the LXD agent to work, which requires functional virtio
  vsock.

  == Test case ==
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz 
focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809
   - lxc launch bug1873809 v1
   - lxc console v1
   - 
   - 
   - lxc exec v1 bash

  To validate a new kernel, you'll need to manually repack the .img file
  and install the new kernel in there.

  == Regression potential ==
  I don't know who else is using those kvm images right now, but those changes 
will cause a change to the kernel binary such that it contains the EFI stub 
bits + a signature. This could cause some (horribly broken) systems to no 
longer be able to boot that kernel. Though considering that such a setup is 
common to our other kernels, this seems unlikely.

  Also, this will be introducing virtio vsock support which again, could
  maybe confused some horribly broken systems?

  
  In either case, the kernel conveniently is the only package which ships 
multiple versions concurently, so rebooting on the previous kernel is always an 
option, mitigating some of the risks.

  
  -- Details from original report --
  User report on the LXD side: https://github.com/lxc/lxd/issues/7224

  I've reproduced this issue with:
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda 
focal-server-cloudimg-amd64-disk-kvm.img -m 1G

  On the graphical console, you'll see EDK2 load (TianoCore) followed by basic 
boot messages and then a message from grub (error: can't find command 
`hwmatch`).
  Those also appear on successful boots of other images so I don't think 
there's anything concerning that. However it'll hang indefinitely and eat up 
all your CPU.

  Switching to the text console view (serial0), you'll see the same
  issue as that LXD report:

  BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
  BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  error: can't find command `hwmatch'.
  e X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
  ExceptionData - 
  RIP  - 3FF2DA12, CS  - 0038, RFLAGS - 00200202
  RAX  - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF
  RBX  - 0398, RSP - 3FF1C638, RBP - 3FF34360
  RSI  - 3FF343B8, RDI - 1000
  R8   - 3E80F108, R9  - 3E815B98, R10 - 0065
  R11  - 2501, R12 - 0004, R13 - 3E80F100
  R14  - , R15 - 
  DS   - 0030, ES  - 0030, FS  - 0030
  GS   - 0030, SS  - 0

[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs

[Louis Bouchard]

Hello,
thanks for the quick turnaround.

For the record, some EFI configs did exist in prior 5.3 images :

root@focal:/boot# cat /etc/cloud/build.info
build_name: server
serial: 20200223
root@focal:/boot# uname -r
5.3.0-1009-kvm
root@focal:/boot# grep -i ^CONFIG_EFI config-5.3.0-1009-kvm 
CONFIG_EFI=y
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
CONFIG_EFI_RUNTIME_WRAPPERS=y
CONFIG_EFI_EARLYCON=y
CONFIG_EFI_PARTITION=y
CONFIG_EFIVAR_FS=m

I'll be using the other image for testing in the meantime
...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1873809

Title:
  Make linux-kvm bootable in LXD VMs

Status in Cloud-Bio-Linux Tutorials:
  Confirmed
Status in cloud-images:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed

Bug description:
  The `disk-kvm.img` images which are to be preferred when run under
  virtualization, currently completely fail to boot under UEFI.

  A workaround was put in place such that LXD instead will pull generic-
  based images until this is resolved, this however does come with a
  much longer boot time (as the kernel panics, reboots and then boots)
  and also reduced functionality from cloud-init, so we'd still like
  this fixed in the near future.

  To get things behaving, it looks like we need the following config
  options to be enable in linux-kvm:

   - CONFIG_EFI_STUB
   - CONFIG_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS_COMMON

  == Rationale ==
  We'd like to be able to use the linux-kvm based images for LXD, those will 
directly boot without needing the panic+reboot behavior of generic images and 
will be much lighter in general.

  We also need the LXD agent to work, which requires functional virtio
  vsock.

  == Test case ==
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz 
focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809
   - lxc launch bug1873809 v1
   - lxc console v1
   - 
   - 
   - lxc exec v1 bash

  To validate a new kernel, you'll need to manually repack the .img file
  and install the new kernel in there.

  == Regression potential ==
  I don't know who else is using those kvm images right now, but those changes 
will cause a change to the kernel binary such that it contains the EFI stub 
bits + a signature. This could cause some (horribly broken) systems to no 
longer be able to boot that kernel. Though considering that such a setup is 
common to our other kernels, this seems unlikely.

  Also, this will be introducing virtio vsock support which again, could
  maybe confused some horribly broken systems?

  
  In either case, the kernel conveniently is the only package which ships 
multiple versions concurently, so rebooting on the previous kernel is always an 
option, mitigating some of the risks.

  
  -- Details from original report --
  User report on the LXD side: https://github.com/lxc/lxd/issues/7224

  I've reproduced this issue with:
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda 
focal-server-cloudimg-amd64-disk-kvm.img -m 1G

  On the graphical console, you'll see EDK2 load (TianoCore) followed by basic 
boot messages and then a message from grub (error: can't find command 
`hwmatch`).
  Those also appear on successful boots of other images so I don't think 
there's anything concerning that. However it'll hang indefinitely and eat up 
all your CPU.

  Switching to the text console view (serial0), you'll see the same
  issue as that LXD report:

  BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
  BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  error: can't find command `hwmatch'.
  e X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
  ExceptionData - 
  RIP  - 3FF2DA12, CS  - 0038, RFLAGS - 00200202
  RAX  - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF
  RBX  - 0398, RSP - 3FF1C638, RBP - 3FF34360
  RSI  - 3FF343B8, RDI - 1000
  R8   - 3E80F108, R9  - 3E815B98, R10 - 0065
  R11  - 2501, R12 - 0004, R13 - 3E80F100
  R14  - , R15 - 
  DS   - 0030, ES  - 0030, FS  - 0030
  GS   - 0030, SS  - 0030
  CR0  - 80010033, CR2 - 0

[Kernel-packages] [Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have been seeing many kernel panic in QEMU instances on newly
  deployed servers all running on the EPYC architecture. Many of the KP
  occur early after the start of the QEMU process or within a few hours.

  All the servers are running an up to date Bionic. After the first few
  panics on 4.15 kernels, we upgraded to 4.18 and still had panics.

  The only thing running on the underlying server is QEMU processes.
  Here is a typical backtrace of a kernel panic :

  [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
  [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
  [58034.612992] Oops:  [#1] SMP NOPTI
  [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
  [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), 
BIOS 0.0.0 02/06/2015
  [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0
  [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 
d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 
64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5>
  [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087
  [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: 

  [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 
94327fe3e000
  [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: 

  [58034.621835] R10:  R11:  R12: 
94327f822c00
  [58034.622723] R13:  R14:  R15: 

  [58034.623539] FS:  () GS:94327f80() 
knlGS:
  [58034.624513] CS:  0010 DS:  ES:  CR0: 80050033
  [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 
003406f0
  [58034.626268] Call Trace:
  [58034.626605]  
  [58034.626924]  scheduler_ipi+0xa9/0x130
  [58034.627400]  smp_reschedule_interrupt+0x39/0xe0
  [58034.627925]  reschedule_interrupt+0xf/0x20
  [58034.628398]  
  [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70
  [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 
4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 
00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0>
  [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: 
ff02
  [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 
94327f81a680
  [58034.633557] RDX:  RSI: 94327f81a680 RDI: 
0202
  [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 
0001
  [58034.635292] R10: b2e03d98 R11:  R12: 
0202
  [58034.636107] R13:  R14:  R15: 
7e369c93
  [58034.637052]  do_idle+0x13f/0x280
  [58034.637453]  cpu_startup_entry+0x73/0x80
  [58034.638067]  rest_init+0xae/0xb0
  [58034.638506]  start_kernel+0x539/0x55a
  [58034.638938]  x86_64_start_reservations+0x24/0x26
  [58034.639470]  x86_64_start_kernel+0x74/0x77
  [58034.639958]  secondary_startup_64+0xa5/0xb0
  [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp 
ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi>

  None of the server has experienced any kernel panic itself.

  After analysing many of the crashes and seeing many of them handling
  interrupts, we decided to reboot the instances with the  noapic
  parameter.

  No kernel panic has been seen since but this is just a workaround
  until a solution is found.

  AMD has been informed of the issue.

  TIA,

  ...Louis (aka Caribou)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

** Description changed:

  We have been seeing many kernel panic in QEMU instances on newly
  deployed servers all running on the EPYC architecture. Many of the KP
  occur early after the start of the QEMU process or within a few hours.
+ 
+ All the servers are running an up to date Bionic. After the first few
+ panics on 4.15 kernels, we upgraded to 4.18 and still had panics.
  
  The only thing running on the underlying server is QEMU processes. Here
  is a typical backtrace of a kernel panic :
  
  [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
  [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
  [58034.612992] Oops:  [#1] SMP NOPTI
  [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
  [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), 
BIOS 0.0.0 02/06/2015
  [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0
  [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 
d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 
64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5>
  [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087
  [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: 

  [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 
94327fe3e000
  [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: 

  [58034.621835] R10:  R11:  R12: 
94327f822c00
  [58034.622723] R13:  R14:  R15: 

  [58034.623539] FS:  () GS:94327f80() 
knlGS:
  [58034.624513] CS:  0010 DS:  ES:  CR0: 80050033
  [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 
003406f0
  [58034.626268] Call Trace:
  [58034.626605]  
  [58034.626924]  scheduler_ipi+0xa9/0x130
  [58034.627400]  smp_reschedule_interrupt+0x39/0xe0
  [58034.627925]  reschedule_interrupt+0xf/0x20
  [58034.628398]  
  [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70
  [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 
4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 
00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0>
  [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: 
ff02
  [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 
94327f81a680
  [58034.633557] RDX:  RSI: 94327f81a680 RDI: 
0202
  [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 
0001
  [58034.635292] R10: b2e03d98 R11:  R12: 
0202
  [58034.636107] R13:  R14:  R15: 
7e369c93
  [58034.637052]  do_idle+0x13f/0x280
  [58034.637453]  cpu_startup_entry+0x73/0x80
  [58034.638067]  rest_init+0xae/0xb0
  [58034.638506]  start_kernel+0x539/0x55a
  [58034.638938]  x86_64_start_reservations+0x24/0x26
  [58034.639470]  x86_64_start_kernel+0x74/0x77
  [58034.639958]  secondary_startup_64+0xa5/0xb0
  [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp 
ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi>
  
  None of the server has experienced any kernel panic itself.
  
  After analysing many of the crashes and seeing many of them handling
  interrupts, we decided to reboot the instances with the  noapic
  parameter.
  
  No kernel panic has been seen since but this is just a workaround until
  a solution is found.
  
  AMD has been informed of the issue.
  
  TIA,
  
  ...Louis (aka Caribou)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have been seeing many kernel panic in QEMU instances on newly
  deployed servers all running on the EPYC architecture. Many of the KP
  occur early after the start of the QEMU process or within a few hours.

  All the servers are running an up to date Bionic. After the first few
  panics on 4.15 kernels, we upgraded to 4.18 and still had panics.

  The only thing running on the underlying server is QEMU processes.
  Here is a typical backtrace of a kernel panic :

  [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
  [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
  [58034.612992] Oops:  [#1] SMP NOPTI
  [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
  [58034.614685] Hardware name: Scaleway St

[Kernel-packages] [Bug 1834505] [NEW] Random kernel panics in QEMU instances when running on EPYC architecture

[Louis Bouchard]

Public bug reported:

We have been seeing many kernel panic in QEMU instances on newly
deployed servers all running on the EPYC architecture. Many of the KP
occur early after the start of the QEMU process or within a few hours.

All the servers are running an up to date Bionic. After the first few
panics on 4.15 kernels, we upgraded to 4.18 and still had panics.

The only thing running on the underlying server is QEMU processes. Here
is a typical backtrace of a kernel panic :

[58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
[58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
[58034.612992] Oops:  [#1] SMP NOPTI
[58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
[58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0
[58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 
d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 
64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5>
[58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087
[58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: 
[58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 94327fe3e000
[58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: 
[58034.621835] R10:  R11:  R12: 94327f822c00
[58034.622723] R13:  R14:  R15: 
[58034.623539] FS:  () GS:94327f80() 
knlGS:
[58034.624513] CS:  0010 DS:  ES:  CR0: 80050033
[58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 003406f0
[58034.626268] Call Trace:
[58034.626605]  
[58034.626924]  scheduler_ipi+0xa9/0x130
[58034.627400]  smp_reschedule_interrupt+0x39/0xe0
[58034.627925]  reschedule_interrupt+0xf/0x20
[58034.628398]  
[58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70
[58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 
4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 
00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0>
[58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: 
ff02
[58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 94327f81a680
[58034.633557] RDX:  RSI: 94327f81a680 RDI: 0202
[58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 0001
[58034.635292] R10: b2e03d98 R11:  R12: 0202
[58034.636107] R13:  R14:  R15: 7e369c93
[58034.637052]  do_idle+0x13f/0x280
[58034.637453]  cpu_startup_entry+0x73/0x80
[58034.638067]  rest_init+0xae/0xb0
[58034.638506]  start_kernel+0x539/0x55a
[58034.638938]  x86_64_start_reservations+0x24/0x26
[58034.639470]  x86_64_start_kernel+0x74/0x77
[58034.639958]  secondary_startup_64+0xa5/0xb0
[58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi>

None of the server has experienced any kernel panic itself.

After analysing many of the crashes and seeing many of them handling
interrupts, we decided to reboot the instances with the  noapic
parameter.

No kernel panic has been seen since but this is just a workaround until
a solution is found.

AMD has been informed of the issue.

TIA,

...Louis (aka Caribou)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: cosmic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834505

Title:
  Random kernel panics in QEMU instances when running on EPYC
  architecture

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have been seeing many kernel panic in QEMU instances on newly
  deployed servers all running on the EPYC architecture. Many of the KP
  occur early after the start of the QEMU process or within a few hours.

  All the servers are running an up to date Bionic. After the first few
  panics on 4.15 kernels, we upgraded to 4.18 and still had panics.

  The only thing running on the underlying server is QEMU processes.
  Here is a typical backtrace of a kernel panic :

  [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64
  [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 
800076c49163
  [58034.612992] Oops:  [#1] SMP NOPTI
  [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 
4.18.0-20-generic #21~18.04.1-Ubuntu
  [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), 
BIOS 

[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

[Louis Bouchard]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1820755

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1815178] Re: 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on NVMe devices

[Louis Bouchard]

** Summary changed:

- 18.04: Raid5 performances on kernel 4.15 are suboptimal
+ 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on 
NVMe devices

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815178

Title:
  18.04: Raid performances on kernel 4.15 and newer are suboptimal when
  used on NVMe devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1815178] Re: 18.04: Raid5 performances on kernel 4.15 are suboptimal

[Louis Bouchard]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815178

Title:
  18.04: Raid5 performances on kernel 4.15 are suboptimal

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1815178] [NEW] 18.04: Raid5 performances on kernel 4.15 are suboptimal

[Louis Bouchard]

Public bug reported:

Hello,
We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

Test (Threads)  QCT JBODQCT RAID5 (8 threads)   QCT RAID10
read(1) 838751 (-10%)   572 (-32%)
read(2) 1226   1172 (-4%)   1057 (-14%)
read(4) 1129   2006 (+78%)  1760 (+56%)
write(1)804382 (-52%)   398 (-50%)
write(2)1047   175 (-83%)   667 (-36%)
write(4)883415 (-53%)   871 (-1%)
randread(1) 863749 (-13%)   619 (-28%)
randread(2) 1346   1067 (-21%)  1020 (-24%)
randread(4) 1648   1785 (+8%)   1650 (=)
randwrite(1)766287 (-63%)   391 (-50%)
randwrite(2)1044   313 (-70%)   664 (-36%)
randwrite(4)916282 (-69%)   885 (-3%)

We are preparing tests with one of the latest mainline kernel.

TIA,

...Louis

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815178

Title:
  18.04: Raid5 performances on kernel 4.15 are suboptimal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

[Louis Bouchard]

Hello,
I have noticed the same issue on our recently released scaleway images with 
cloud-init enabled on Bionic running 4.15.0-24.

Testing with the 4.15.0-26-generic kernel in -proposed _DOES_ fix the
delay issue on our image.

I'm taking the liberty of marking the bug tested.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1780817] [NEW] kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)

[Louis Bouchard]

Public bug reported:

When starting a nested VM in a Bionic VM, the "host" VM kernel panics
following a simple drop to QEMU monitor by hitting A-c. For some
reason kdump is unable to capture the kernel panic so I only have a
screen capture of the panic.

It also happens on the latest mainline kernel(4.18-rc4). It is fairly
trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the
following :

qemu-system-x86_64 -enable-kvm \
-name balloontest \
-display none \
-monitor none \
-nographic \
-nodefaults \
-m 2048M \
-serial mon:stdio \
-smp 2 \
-cpu host \
-drive 
if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \
-drive 
if=pflash,format=raw,file=/home/caribou/balloon/efi.vars

Use A-c to drop to QEMU monitor and .

^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[  
267.784299] general protection fault:  [#1] SMP PTI
[  267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  267.804312]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  267.811666] RIP: 0010:native_write_cr4+0x4/0x10
[  267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006
[  267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8
[  267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0
[  267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: 
[  267.818625] R10:  R11:  R12: 00025040
[  267.820130] R13: 0001 R14:  R15: 
[  267.821638] FS:  () GS:8c01ffd8() 
knlGS:
[  267.823352] CS:  0010 DS:  ES:  CR0: 80050033
[  267.824592] CR2:  CR3: 00058c00a006 CR4: 003626e0
[  267.826108] DR0:  DR1:  DR2: 
[  267.827567] DR3:  DR6: fffe0ff0 DR7: 0400
[  267.828973] Call Trace:
[  267.829470]  
[  267.829893]  hardware_disable+0xaa/0xc0 [kvm_intel]
[  267.830897]  kvm_arch_hardware_disable+0x19/0x40 [kvm]
[  267.831928]  hardware_disable_nolock+0x2b/0x30 [kvm]
[  267.832912]  flush_smp_call_function_queue+0x4c/0xf0
[  267.833911]  generic_smp_call_function_single_interrupt+0x13/0x30
[  267.835121]  smp_call_function_interrupt+0x36/0xd0
[  267.836069]  call_function_interrupt+0x84/0x90
[  267.836950]  
[  267.837396] RIP: 0010:native_safe_halt+0x6/0x10
[  267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: 
ff03
[  267.839698] RAX: acd97150 RBX: 0006 RCX: 
[  267.840978] RDX:  RSI:  RDI: 
[  267.842258] RBP: a2e1431afe80 R08: 0002 R09: 
[  267.843554] R10: 00b3 R11: 00a6 R12: 0006
[  267.844826] R13:  R14:  R15: 
[  267.846107]  ? __cpuidle_text_start+0x8/0x8
[  267.846875]  default_idle+0x20/0x100
[  267.847533]  arch_cpu_idle+0x15/0x20
[  267.848186]  default_idle_call+0x23/0x30
[  267.848917]  do_idle+0x172/0x1f0
[  267.849516]  cpu_startup_entry+0x73/0x80
[  267.850255]  start_secondary+0x1ab/0x200
[  267.850971]  secondary_startup_64+0xa5/0xb0
[  267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 
00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 
e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0>
[  267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48
[  268.848104] invalid opcode:  [#2] SMP PTI
[  268.848524] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i>
[  268.854013]  xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy 
aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_piix4 virtio_net virtio_blk
[  268.855212] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic 
#26-Ubuntu
[  268.855790] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 
0.0.0 02/06/2015
[  268.856438] RIP: 0010:native_machine_crash_shutdown+0x136/0x190
[  268.856893] RSP: 0018:8c01ffd83cc0 EFLAGS: 00010002
[  268.857295] RAX: 0

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Louis Bouchard]

Hello,
For information, the current presence of kexec-tools in -proposed causes a 
dependency problem when installing the linux-crashdump meta-package :

# apt update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
# apt install linux-crashdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-crashdump : Depends: kdump-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When adding the -proposed archive, linux-crashdump installs correctly.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1743529

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  root@whip:~# kdump-config status
  current state   : ready to kdump

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bn

[Kernel-packages] [Bug 1743537] [NEW] linux-crashdump meta-package does not exist for arm64

[Louis Bouchard]

Public bug reported:

The linux-crashdump meta-package should be enabled for arm64 now that
kdump-tools & makedumpfile are enabled for this architecture

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1743537

Title:
  linux-crashdump meta-package does not exist for arm64

Status in linux-meta package in Ubuntu:
  New

Bug description:
  The linux-crashdump meta-package should be enabled for arm64 now that
  kdump-tools & makedumpfile are enabled for this architecture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1743537/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Louis Bouchard]

Hello,

I would like to add that triggering a kernel dump in seconds following
the installation of the package remains a corner case in a test context
and not the usual behavior.

I have seen that too in my test scripts and syncing right after the
installation fixed the issue as well.

Bringing in the upstream change is a good solution.

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1714485

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: In Progress

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1714485

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Louis Bouchard]

*** This bug is a duplicate of bug 1635597 ***
https://bugs.launchpad.net/bugs/1635597

This bug is a duplicate of bug #1635597.

As outlined in the other bug, could you test the potential fix in the
following PPA :

ppa:louis/kdump-tools-multipath


** This bug has been marked a duplicate of bug 1635597
   Ubuntu16.10:talclp1: Kdump failed with multipath disk

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RA

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Louis Bouchard]

Hello,

Would it be possible to test a potential fix in the following PPA :

ppa:louis/kdump-tools-multipath

I do not have the hardware to fully test a kernel dump but the partial
test I have confirm that the modules are correctly loaded.

Please let me know the outcome of you tests whenever possible.

Kind regards,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1635597

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive 

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
   Status: Triaged => In Progress

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux (Ubuntu Zesty)
   Status: New => Invalid

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis)

** Changed in: makedumpfile (Ubuntu Zesty)
 Assignee: (unassigned) => Louis Bouchard (louis)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1635597

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  New
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  New

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a&g

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Louis Bouchard]

** Also affects: kexec-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: kexec-tools (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: kexec-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Louis Bouchard]

** Changed in: kexec-tools (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis)

** Changed in: makedumpfile (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis)

** Changed in: kexec-tools (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reali

[Kernel-packages] [Bug 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le

[Louis Bouchard]

Hello,

Well, this is to be expected as the postinst script will only change the
target of the symlink if the architecture is ppc64EL and not ppc64LE (
EL != LE).

Now if both are interchangeable (I must admit my ignorance of this
architecture), I don't mind fixing the script to apply to both EL and
LE.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1676884

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676884/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: makedumpfile (Ubuntu Wily)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1536904

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: c00fe022f990 TRAP: 0300   Not tainted  
(4.3.0-5-generic)
  [  238.873200] MSR: 90009033   CR: 28004222  
XER: 2000
  [  238.873392] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c06475f8 c00fe022fc10 c155e400 0063 
  GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 
  GPR08: 0007 0001  c01fff861780 
  GPR12: c0646500 c7b87d80   
  GPR16:     
  GPR20:   10009d88 0001 
  GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 
  GPR28: c14a6070 0063 c1460de4  
  [  238.875062] NIP [c

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

** Changed in: crash (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1655625

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.

  [Impact]
  Kernel crashes cannot be analysed with the crash tool.
  makedumpfile incorrectly filter pages.

  [Fix]
  Cherry-pick upstream commits fixing those issues.

  [Test Case]
  Running crash tool on a kernel crash file will display something like :

  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
     renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem

  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!

  With the fix, the crash command will work as expected

  Running the crash tool on a vmcore file produced by makedumpfile may
  return :

  crash: page excluded: kernel virtual address: <> type:
  "fill_task_struct"

  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.

  The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after

  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash

  Userspace tool common name: crash/makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'c

[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => (unassigned)

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1626269

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  makedumpfile fails to execute if executed on a 4.8 kernel

  [Impact]
  Unable to generate compressed kernel dumps on those platform

  [Fix]
  Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 
  0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8.

  The second commit is required since, once the initial issue is fixed,
  it triggers a second issue fixed on Debian by https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=842019

  [Test Case]
  - Install kernel 4.8 along with the linux-crashdump metapackage
  - Reboot to enable kdump
  - Trigger a kernel panic with "echo c > /proc/sysrq-trigger"

  Without the patch, the following message will appear and makedumpfile
  will fail :

   get_mem_map: Can't distinguish the memory type.

  With the fix, makedumpfile completes correctly.

  [Regression]
  None expected. The modification keeps the initial structure when kernels 
before 4.8 are used.

  [Original description of the problem]

  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@ubuntu:/home/ubuntu# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970
  GPR08: 0007 0001  0001
  GPR12: c05af3c0 c7b31200  2200
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 310b9624 0001 c0e9fd40 0

[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails

[Louis Bouchard]

Hello,

I am surprised by a few things : first of all, linux-crashdump, hence
kdump-tools, is not installed by default on a server install. So you
must have added that step somehow.

I have just installed Xenial using the mini.iso network install and
kdump-tool is not installed after completion. I installed it without any
issue, rebooted and the functionality works as expected.

Now your output shows that it is the kernel's post-install trigger that
fails, so this is where you should but the -x (add it to the sh -e
shebang at the top of the script). Then you can run the following &
paste the output here :

/etc/kernel/postinst.d/kdump-tools $(uname -r)

FYI, this script is responsible for building the smaller initrd used by
kdump when rebooting after a crash.

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1687791

Title:
  Install of kdump-tools fails

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  When installing Ubuntu xenial via netimage, installation fails because
  of an error, when configuring the kdump-tools. /var/log/syslog says:

  ...

  May  2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
  May  2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) 
...^M
  May  2 22:15:17 in-target: Running in chroot, ignoring request.^M
  May  2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of 
reload.^M
  May  2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M
  May  2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) 
...^M
  May  2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) 
...^M
  May  2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) 
...^M
  May  2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) 
...^M
  May  2 22:15:17 in-target: Errors were encountered while processing:^M
  May  2 22:15:17 in-target:  kdump-tools^M
  May  2 22:15:17 in-target:  linux-crashdump^M
  May  2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error 
code (1)
  May  2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
  May  2 22:15:18 in-target: dpkg: error processing package kdump-tools 
(--configure):
  May  2 22:15:18 in-target:  subprocess installed post-installation script 
returned error exit status 1
  May  2 22:15:18 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
  May  2 22:15:18 in-target:  linux-crashdump depends on kdump-tools; however:
  May  2 22:15:18 in-target:   Package kdump-tools is not configured yet.
  May  2 22:15:18 in-target: 
  May  2 22:15:18 in-target: dpkg: error processing package linux-crashdump 
(--configure):
  May  2 22:15:18 in-target:  dependency problems - leaving unconfigured
  May  2 22:15:18 in-target: Errors were encountered while processing:
  May  2 22:15:18 in-target:  kdump-tools
  May  2 22:15:18 in-target:  linux-crashdump
  May  2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
  May  2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed.

  
  After this the 'Select and install software' dialog pops up and says, that 
'Installation step failed'. If one presses '', one gets bombed back 
into the 'Ubuntu installer main menu'.
  Now you get into a loop, when choosing the 'Select and install software' item 
from the menu.

  Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan
  18 14:10:15 UTC 2017 x86_64 GNU/Linux'.

  The only workaround found so far is:
  cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \
  /target/var/lib/dpkg/info/kdump-tools.postinst.suck
  printf '#!/bin/sh\nexit 0\n' \
  >/target/var/lib/dpkg/info/kdump-tools.postinst

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Louis Bouchard]

Re-targetting the bug to the linux kernel as this is not a makedumpfile
issue

** Package changed: makedumpfile (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1687779

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [] do_one_initcall+0x50/0x1a0
  [   11.397431]  [] ? parse_args+0x2cf/0x490
  [   11.399313]  [] kernel_init_freeable+0x178/0x217
  [   11.402112]  [] kernel_init+0xe/0x100
  [   11.404013]  [] ret_from_fork+0x1f/0x40
  [   11.405895]  [] ? rest_init+0x80/0x80
  [   11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 
48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1687779

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [] do_one_initcall+0x50/0x1a0
  [   11.397431]  [] ? parse_args+0x2cf/0x490
  [   11.399313]  [] kernel_init_freeable+0x178/0x217
  [   11.402112]  [] kernel_init+0xe/0x100
  [   11.404013]  [] ret_from_fork+0x1f/0x40
  [   11.405895]  [] ? rest_init+0x80/0x80
  [   11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 
48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Louis Bouchard]

Hello,

Le 03/04/2017 à 12:02, Konrad Zapałowicz a écrit :
> Hey, to everyone interested we are currently testing and reviewing an
> improvement to PA that fixes problems with selecting A2DP mode for BT
> headsets.
> 
> Right now it is being tested internally with good results for Sony
> headsets, QC35 from Bose and BT speakers. Once it is in a silo/ppa I
> will share this information for much wider testing. Then it will be
> submitted as a SRU and will land in xenial.
> 

I've been subscribed to this bug for ages & I'm still seeing this issue with my
BT headset so I'd be more than happy to help you tests.

Kind regards,

...Louis

-- 
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer   Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1438510

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes

[Louis Bouchard]

** Tags removed: sts-sru
** Tags added: sts-sru-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1644771

Title:
  kdump-tools: Fails to load kdump kernel when /proc/cmdline contains
  double quotes

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  This fix is needed to avoid failure to load kdump-tools when one kernel boot 
parameter has double-quotes.

  [Impact]
  kdump functionality becomes unusable

  [Fix]
  Modify kdump-config to handle the presence of double-quotes in the cmdline

  [Test Case]
  Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT :

  \"acpi_osi=!Windows 2012\"
  $ sudo update-grub
  $ sudo reboot

  kdump-config will show the following error upon reboot :

  [   11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service': No s
  uch file or directory 
 
  [   11.602563] kdump-tools[1710]:  * failed to load kdump kernel  
 

  With this fix, the kdump-config command will run successfully

  [Regression]
  None expected. Fix is already in Zesty & Debian. Only one line added to the 
sed statement.

  [Original description of the problem]
  kdump-tools fails to load if one of the kernel parameter has double-quotes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1640275] Re: move nvme driver to linux-image

[Louis Bouchard]

** Tags removed: sts-sru
** Tags added: sts-sru-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1640275

Title:
  move nvme driver to linux-image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  The nvme driver is in the -extra package but should be in the linux-
  image package, to avoid the overhead of having to install the -extra
  package just to get the nvme driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640275/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1658491] Re: VLAN SR-IOV regression for IXGBE driver

[Louis Bouchard]

** Tags removed: sts-sru
** Tags added: sts-sru-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1658491

Title:
  VLAN SR-IOV regression for IXGBE driver

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Invalid

Bug description:
  
  IXGBE driver, for SR-IOV setups, is misbehaving with VLANs.

  Description from affected user:

  - Create 2 networks (sriov 100 and 102 vlan)

  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=100 PHY0_vlan_100
  # neutron net-create --provider:physical_network=PHY0 
--provider:network_type=vlan --provider:segmentation_id=102 PHY0_vlan_102

  - Create the subnets:

  # neutron subnet-create PHY0_vlan_100 192.168.50.0/24
  # neutron subnet-create PHY0_vlan_102 192.168.60.0/24

  - Create the neutron ports:

  # neutron port-create e450757f-fec6-466e-bb21-a42a2019fe6b --name 
vlan_100_port1 --vnic-type direct
  # neutron port-create 32c468ed-7e1e-4267-bbbf-ec72d33e4454 --name 
vlan_102_port1 --vnic-type direct

  - Boot 2 VMs on 2 different hosts (add only 1 port to each of them +
  ovs dhcp network):

  # nova boot --flavor 789 --image ubuntu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=92cf2867-cc0a-4e0d-aa87-14a345cdd708 102_port1_compute6 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-6.domain.tld --poll
  # nova boot --flavor 789 --image ubutnu --nic 
net-id=1cf2a512-8963-413d-a745-99e758789c2b --nic 
port-id=baec6fd6-933d-4c58-94b6-44c50405d409 100_port1_compute5 --key-name mkey 
--config-drive true --availability-zone nova:compute-0-5.domain.tld --poll

  - After the VMs booted, configure the VFs:

  root@102-port1-compute6:~# ifconfig eth1 192.168.34.6 up
  root@100-port1-compute5:~# ifconfig eth1 192.168.34.5 up

  If I ping each other it works but it shouldn't work because in this
  case both of the VMs's interface (host VF) are in different vlans:

  - Pinging shouldn't work because the VMs interface (host VF) are in
  different VLANs.

  root@compute-0-5:~# ip link show eth6
  8: eth6:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:1a:64 brd ff:ff:ff:ff:ff:ff
  vf 5 MAC fa:16:3e:f0:2c:e2, vlan 100, spoof checking on, link-state auto

  root@compute-0-6:~# ip link show eth5
  8: eth5:  mtu 2140 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  link/ether a0:36:9f:3f:20:88 brd ff:ff:ff:ff:ff:ff
  vf 7 MAC fa:16:3e:ce:69:41, vlan 101, spoof checking on, link-state auto 

  But user can ping both VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658491/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build

[Louis Bouchard]

I can confirm that this version fixes the following issue :

  crash: invalid structure member offset: module_num_symtab
 FILE: kernel.c LINE: 3049 FUNCTION: module_init()

using the latest linux-image-lts-xenial kernel

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1607894

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed

Bug description:
  [ Test case ]
  * trigger a kernel crash dump
  * use crash tool to analyse it
  * ... on ppc64el architecture

  
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29
  -generic-dbgsym_4.4.0-29.48_ppc64el.ddeb

  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux

  Machine Type = model   : 8247-22L machine : PowerNV
  8247-22L

  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and 
/var/crash/201606300840/dump.201606300840 do not match!

  Userspace rpm: linux-image-4.4.0-29-generic-
  dbgsym_4.4.0-29.48_ppc64el.ddeb

  == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 ==

  The Latest kernel I am having is as follows

  root@ltcalpine-lp6:~# uname -a
  Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 
01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@ltcalpine-lp6:~#

  >>> the issue same as posted originally.

  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and 
/var/crash/201607270248/dump.201607270248 do not match!

  == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 ==
  The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled
  from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc
  version 5.3.1 which is the source of the issue.

   Resolved this by pulling the kernel debug symbols package from:

    deb http://ddebs.ubuntu.com/ -updates  main

  which indeed has the vmlinux compiled with gcc version 4.8.4.
  But I got this error:

    crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3049  FUNCTION: module_init()

  after the update owning to couple of missing patches listed below:

    commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
    Author: Dave Anderson 
    Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

    commit 7523e4dc5057e157212b4741abd6256e03404cf1
    module: use a structure to encapsulate layout.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_init_text_size".
  (seb...@linux.vnet.ibm.com)

    commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
    Author: Dave Anderson 
    Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

    commit 8244062ef1e54502ef55f54cced659913f244c3e
    modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

  Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4,
  was able

[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Zesty)
   Importance: Low
 Assignee: Eric Desrochers (slashd)
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1670696

Title:
  Typo in error msg when no crashkernel memory reservation is set

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  [Impact]

   * There is a typo in ERRMSG of function show_mem_usage affecting
  Xenial and Zesty AND Debian.

  This should be :
  "show_mem_usage: No memory is reserved for crashkernel!" 

  instead of :
  "show_mem_usage: No memory is reserved for crashkenrel!"

  [Test Case]

   * Take a system with no crashkernel memory reservation set
   * run command : makedumpfile --mem-usage /proc/kcore

   * Error message :
  show_mem_usage: No memory is reserved for crashkenrel!

  [Regression Potential]

   * No regression, it is a trivial change with no behavioural change.

  [Other Info]

  The typo is located here in src code for Xenial and Zesty (devel
  release) AND Debian:

  # filename : makedumpfile.c
  10447 int show_mem_usage(void)
  10448 {
  10449 uint64_t vmcoreinfo_addr, vmcoreinfo_len;
  10450 struct cycle cycle = {0};
  10451
  10452 if (!is_crashkernel_mem_reserved()) {
  10453 ERRMSG("No memory is reserved for crashkenrel!\n");
  10454 return FALSE;
  10455 }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652595] Re: Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

[Louis Bouchard]

*** This bug is a duplicate of bug 1655625 ***
https://bugs.launchpad.net/bugs/1655625

** This bug has been marked a duplicate of bug 1655625
   ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1652595

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

  ---Steps to Reproduce---

  1. Install 16.04.02 [ 4.8.0-32-generic ].
  2. Configure kdump.
  3. Install debug package. 
  4. trigger crash.
  5. run crash tool on dump captured.

  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF 

  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym  


  
  path: /var/crash/201612190432

  Logs
  ===

  root@ltc-haba2:/var/crash/201612190432# crash
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic dump.201612190432

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

  
  It appears problem is with System.map-4.8.0-32-generic file 

  (gdb) symbol-file System.map-4.8.0-32-generic -readshow
  `/boot/System.map-4.8.0-32-generic': can't read symbols: File format not 
recognized.
  (gdb) 

  crash System.map-4.8.0-32-generic
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic
  /var/crash/201612260004/dump.201612260004

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

 
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1652595/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1652595] Re: Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

[Louis Bouchard]

So correct me if I'm wrong,but you are basically stating that this bug
should be Marked as "Fix Released" since it is corrected by the latest
crash/makedumpfile SRU ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1652595

Title:
  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Ubuntu 16.04.02: crash tool fails with error "cannot find
  'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or
  'cpu_active_map' symbols".

  ---Steps to Reproduce---

  1. Install 16.04.02 [ 4.8.0-32-generic ].
  2. Configure kdump.
  3. Install debug package. 
  4. trigger crash.
  5. run crash tool on dump captured.

  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted 
universe multiverse
  deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted 
universe multiverse
  EOF 

  sudo apt-get update
  sudo apt-get install linux-image-$(uname -r)-dbgsym  


  
  path: /var/crash/201612190432

  Logs
  ===

  root@ltc-haba2:/var/crash/201612190432# crash
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic dump.201612190432

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

  
  It appears problem is with System.map-4.8.0-32-generic file 

  (gdb) symbol-file System.map-4.8.0-32-generic -readshow
  `/boot/System.map-4.8.0-32-generic': can't read symbols: File format not 
recognized.
  (gdb) 

  crash System.map-4.8.0-32-generic
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic
  /var/crash/201612260004/dump.201612260004

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

 
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 
'cpu_online_map' or 'cpu_active_map' symbols

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1652595/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1655625

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed

Bug description:
  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.

  [Impact]
  Kernel crashes cannot be analysed with the crash tool.
  makedumpfile incorrectly filter pages.

  [Fix]
  Cherry-pick upstream commits fixing those issues.

  [Test Case]
  Running crash tool on a kernel crash file will display something like :

  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
     renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem

  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!

  With the fix, the crash command will work as expected

  Running the crash tool on a vmcore file produced by makedumpfile may
  return :

  crash: page excluded: kernel virtual address: <> type:
  "fill_task_struct"

  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.

  The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after

  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash

  Userspace tool common name: crash/makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  1. Missing v4.8 support related patches in crash tool

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

Hello,

I have just uploaded a fixed makedumpfile for SRU to xenial.

** Description changed:

  [SRU justification]
  This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.
  
  [Impact]
  Kernel crashes cannot be analysed with the crash tool.
+ makedumpfile incorrectly filter pages.
  
  [Fix]
  Cherry-pick upstream commits fixing those issues.
  
  [Test Case]
  Running crash tool on a kernel crash file will display something like :
  
  # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
  crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
-renders /dev/mem unusable as a live memory source.
+    renders /dev/mem unusable as a live memory source.
  crash: trying /proc/kcore as an alternative to /dev/mem
  
  crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
  crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
  crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
  crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!
  
  With the fix, the crash command will work as expected
  
+ Running the crash tool on a vmcore file produced by makedumpfile may
+ return :
+ 
+ crash: page excluded: kernel virtual address: <> type:
+ "fill_task_struct"
+ 
  [Regression]
  None expected as those modifications are part of the Zesty and upstream 
version.
+ 
+ The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after
  
  [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:
  
  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!
  
  Usage:
  
    crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
    crash [OPTION]... [NAMELIST]  (live system form)
  
  Enter "crash -h" for details.
  
  Looks like the 'linux_banner' cannot be understood by crash.
  
  And when the vmcore was dumping, this message being showed:
  
  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  
  Machine Type = lpar
  
  ---Debugger---
  A debugger is not configured
  
  ---Steps to Reproduce---
   1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash
  
  Userspace tool common name: crash/makedumpfile
  
  The userspace tool has the following bit modes: 64-bit
  
  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4
  
  Userspace tool obtained from project website:  na
  
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.
  
  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
    domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  
  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000
  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols
  
  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#
  
  1. Missing v4.8 support related patches in crash tool
  
     commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
     Author: Dave Anderson 
     Date:   Fri Feb 12 14:32:53 2016 -0500
  
  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:
  
    commit 8244062ef1e54502ef55f54cced659913f244c3e
    modules: fi

[Kernel-packages] [Bug 1661168] Re: In Ubuntu16.10: Kdump stuck in boot for longer time need to force reboot via HMC in 32TB Brazos System

[Louis Bouchard]

** Also affects: kexec-tools (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1661168

Title:
  In Ubuntu16.10: Kdump stuck in  boot for longer time need to force
  reboot via HMC in 32TB Brazos System

Status in kexec-tools package in Ubuntu:
  New
Status in kexec-tools source package in Yakkety:
  New

Bug description:
  Problem Description
  ===
In Ubuntu16.10 tried  kdump in Brazos system (32TB Memory and 192 core). 
when trigger panic  kdump process  stuck in boot process  need to do force 
reboot .After reboot system captured vmcore-incomplete.

  Reproducible Step:
  ==
  1- Install Ubuntu16.10
  2- boot system with 31TB and 192 Core 
  3- configure kdump in system 
  4- verify kdump in system that it is running 
  5- Trigger panic in system

  Actual Result
  --
  kdump process  stuck in boot process  need to do force reboot

  Expected Result 
  -
  Kdump will proceed and vmcore captured  successfully.

  LOG:

  root@ltc-brazos1:~# cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash crashkernel=4096M
  root@ltc-brazos1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-30-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ltc-brazos1:~# 
  root@ltc-brazos1:~# dpkg -l | grep kdump 
  ii  kdump-tools1:1.6.0-2 all  
scripts and tools for automating kdump (Linux crash dumps)
  root@ltc-brazos1:~# 
  root@ltc-brazos1:~# echo c > /proc/sysrq-trigger 

  
  ltc-brazos1 login: [  416.229464] sysrq: SysRq : Trigger a crash  

  
  [  416.229496] Unable to handle kernel paging request for data at address 
0x  
  
  [  416.229502] Faulting instruction address: 0xc0670014   

  
  [  416.229508] Oops: Kernel access of bad area, sig: 11 [#1]  

  
  [  416.229511] SMP NR_CPUS=2048 NUMA pSeries  

  
  [  416.229517] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
  [  416.229532] CPU: 65 PID: 404785 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  
 
  [  416.229537] task: c1f9d583c8e0 ti: c1fa13cd8000 task.ti: 
c1fa13cd8000

  [  416.229543] NIP: c0670014 LR: c06710c8 CTR: 
c066ffe0
 
  [  416.229548] REGS: c1fa13cdb990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

  [  416.229552] MSR: 80009033   CR: 2824  
XER: 0001   
 
  [  416.229565] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

  GPR00: c06710c8 c1fa13cdbc10 c15b5d00 0063

  
  GPR04: c1fab9049c50 c1fab905b4e0 c0001f3fff3d 0313

  
  GPR08: 0007 0001  c0001f3fff3dec68

  
  GPR1

[Kernel-packages] [Bug 1660519] Re: Windows guest got 0x5c BSOD when rebooting

[Louis Bouchard]

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1660519

Title:
  Windows guest got 0x5c BSOD when rebooting

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress

Bug description:
  [Impact]

  When rebooting Windows guest, it gets 0x5c BSOD
  Impact to 3.13 ( trusty )
  no Impact to 4.x

  [Fix]

  Upstream development
  4114c27d450bef228be9c7b0c40a888e18a3a636
  ("KVM: x86: reset RVI upon system reset")
  6d2a0526b09e551d0f395cfb63e7cb965db825af
  ("KVM: x86: Emulator should set DR6 upon GD like real CPU")

  and got one MACRO definition from below commit as 6d2a05's dependency
  6f43ed01e87c8a8dbd8c826eaf0f714c1342c039
  (whole 6f43ed commit has a lot of dependency to the other commits)

  [Testcase]

  Running 6 windows vms( 2012r2 ) on one single server.
  auto rebooting scripts in windows guest.
  after one day (around hundred rebooting), can get 0x5c certainly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660519/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

** Description changed:

+ [SRU justification]
+ This fix is required to make the crash tool usable. It does also improve 
makedumpfile filtering of pages.
+ 
+ [Impact]
+ Kernel crashes cannot be analysed with the crash tool.
+ 
+ [Fix]
+ Cherry-pick upstream commits fixing those issues.
+ 
+ [Test Case]
+ Running crash tool on a kernel crash file will display something like :
+ 
+ # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic
+ crash: read error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
+ crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which
+renders /dev/mem unusable as a live memory source.
+ crash: trying /proc/kcore as an alternative to /dev/mem
+ 
+ crash: seek error: kernel virtual address: 81e29ff0  type: 
"pv_init_ops"
+ crash: seek error: kernel virtual address: 82166130  type: 
"shadow_timekeeper xtime_sec"
+ crash: seek error: kernel virtual address: 81e0d304  type: 
"init_uts_ns"
+ crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and 
/var/crash/201701191308/dump.201701191308 do not match!
+ 
+ With the fix, the crash command will work as expected
+ 
+ [Regression]
+ None expected as those modifications are part of the Zesty and upstream 
version.
+ 
+ [Original description of the problem]
  vmcore captured by kdump cannot be opened with crash:
  
  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!
  
  Usage:
  
-   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
-   crash [OPTION]... [NAMELIST]  (live system form)
+   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
+   crash [OPTION]... [NAMELIST]  (live system form)
  
  Enter "crash -h" for details.
- 
  
  Looks like the 'linux_banner' cannot be understood by crash.
  
  And when the vmcore was dumping, this message being showed:
  
  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = lpar 
-  
+ 
+ Machine Type = lpar
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  1. config kdump 
+  1. config kdump
  2. trigger kdump
  3. analyse vmcore with crash
-  
- Userspace tool common name: crash/makedumpfile 
-  
- The userspace tool has the following bit modes: 64-bit 
+ 
+ Userspace tool common name: crash/makedumpfile
+ 
+ The userspace tool has the following bit modes: 64-bit
  
  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4
  
- Userspace tool obtained from project website:  na 
-  
- *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
+ Userspace tool obtained from project website:  na
+ 
+ *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.
  
  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
-  sysname: Linux
- nodename: boblp1
-  release: 4.8.0-32-generic
-  version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
-  machine: ppc64le
-   domainname: (none)
+  sysname: Linux
+ nodename: boblp1
+  release: 4.8.0-32-generic
+  version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
+  machine: ppc64le
+   domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  
  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000
  
  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols
  
  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#
  
- 
  1. Missing v4.8 support related patches in crash tool
  
-commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
-Author: Dave Anderson 
-Date:   Fri Feb 12

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch removed: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805918/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

** Patch added: "ubuntu_7.1.5_to_7.1.7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805920/+files/ubuntu_7.1.5_to_7.1.7.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1657488

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch added: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805918/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1657488

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1657488] Re: Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

** Patch added: "debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+attachment/4805917/+files/debian_7.1.7-1_to_ubuntu_7.1.7-1ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1657488

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1657488] [NEW] Please merge crash version 7.1.7-1 (main) from debian sid

[Louis Bouchard]

Public bug reported:

merge bug

** Affects: crash (Ubuntu)
 Importance: Wishlist
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Changed in: crash (Ubuntu)
   Status: New => Confirmed

** Changed in: crash (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1657488

Title:
  Please merge crash version 7.1.7-1 (main) from debian sid

Status in crash package in Ubuntu:
  Confirmed

Bug description:
  merge bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1657488/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

** Changed in: crash (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: crash (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: crash (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: crash (Ubuntu)
   Status: New => Confirmed

** Changed in: crash (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1655625

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in crash source package in Xenial:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed

Bug description:
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  
  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump 
  2. trigger kdump
  3. analyse vmcore with crash
   
  Userspace tool common name: crash/makedumpfile 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  
  1. Missing v4.8 support related patches in crash tool

 commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
 Author: Dave Anderson 
 Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

 commi

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

Hello,

First of all, two of the listed crash patches are in the 7.1.5-1ubuntu2
package awaiting in zesty-proposed. It is blocked there by an FTBS on
z390x. But even with those patches, it still fails so I assume that the
other three patches are also needed.

But while trying to test your solution on x86_64, it turns out that it
still fails with your patches. I suspect that other patches are needed
for this specific architecture.

Regarding your makedumpfile patches, as far as I can tell,they are not
required for the crash command to work. They will only improve the
filtering of some specific kind of pages.

I am preparing an SRU for makedumpfile, so I will add them for
completeness.

I am now trying to identify the missing commit for x86_64 and will see
to get that situation fixed.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1655625

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in crash source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New

Bug description:
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  
  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump 
  2. trigger kdump
  3. analyse vmcore with crash
   
  Userspace tool common name: crash/makedumpfile 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  
  1. Missing v4.8 support related patches in crash tool

 commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
 Author: Dave Anderson 
 Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

 commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
 Author: Dave Anderson 
 Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure intro

[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1655625

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by
  crash

Status in crash package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in crash source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New

Bug description:
  vmcore captured by kdump cannot be opened with crash:

  % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
  ... ...
  base kernel version: 0.8.0
  linux_banner:
  
  crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

  Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST]  (live system form)

  Enter "crash -h" for details.

  
  Looks like the 'linux_banner' cannot be understood by crash.

  And when the vmcore was dumping, this message being showed:

  [  729.609196] kdump-tools[5192]: The kernel version is not supported.
  [  729.609447] kdump-tools[5192]: The makedumpfile operation may be 
incomplete.
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump 
  2. trigger kdump
  3. analyse vmcore with crash
   
  Userspace tool common name: crash/makedumpfile 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
  utsname:
   sysname: Linux
  nodename: boblp1
   release: 4.8.0-32-generic
   version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
   machine: ppc64le
domainname: (none)
  base kernel version: 4.8.0
  verify_namelist:
  dumpfile /proc/version:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
  /usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
  Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

  hypervisor: (undetermined)
  crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
  ppc64_vmemmap_init: vmemmap base: f000

  crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map',
  'cpu_online_map' or 'cpu_active_map' symbols

  root@boblp1:/usr/lib/debug/boot# uname -a
  Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@boblp1:/usr/lib/debug/boot#

  
  1. Missing v4.8 support related patches in crash tool

 commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
 Author: Dave Anderson 
 Date:   Fri Feb 12 14:32:53 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 8244062ef1e54502ef55f54cced659913f244c3e
modules: fix longstanding /proc/kallsyms vs module insertion race.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_num_symtab".
  (ander...@redhat.com)

 commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
 Author: Dave Anderson 
 Date:   Wed Jan 20 09:56:36 2016 -0500

  Fix for the changes made to the kernel module structure introduced by
  this kernel commit for Linux 4.5 and later kernels:

commit 7523e4dc5057e157212b4741abd6256e03404cf1
module: use a structure to encapsulate layout.

  Without the patch, the crash session fails during initialization
  with the error message: "crash: invalid structure member offset:
  module_init_text_size".
  (seb...@linux.vnet.ibm.com)

 commit 1e92f9fad3a7e3042b16996306cb2335760ef8c8
 Author: Dave Anderson 
 Date:   Mon Feb 1 16:10:49 2016 -0500

  Fix for the replacements made to the kernel

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Yakkety)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1557751

Title:
  makedumpfile generates kernel version error

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1641235] Re: Ubuntu 16.10: kdump over nfs did not generate complete vmcore

[Louis Bouchard]

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Yakkety)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1641235

Title:
  Ubuntu 16.10: kdump over nfs did not generate complete vmcore

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 ==
  ---Problem Description---
  kdump over nfs did not generate complete vmcore
   
  ---uname output---
  Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 
14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV (Baremetal) - Firestone 
   
  ---Steps to Reproduce---
   1. Setup NFS
  2. Trigger crash: echo c > /proc/sysrq-trigger

  
  == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 ==

  Hi Harsha.

  It looks like the base kdump NFS functionality works just fine.  The
  known issue with makedumpfile is causing it to drop back to using "cp"
  to transfer the entire, non-compressed /proc/vmcore image.  That's a
  rather large amount of data to send over to the remote server, and it
  appears to be sending back an I/O error after the first 122G.

  Further debug would need to be done to determine if this is a client-
  side or server-side issue.  I recommend first bringing your remote NFS
  server up to the current release as it is currently a bit down-rev.

  == Comment: #8 - HARSHA THYAGARAJA  - 2016-11-10 02:02:31 ==

  Hi Kevin,
  I updated my peer to Ubuntu 16.10 and still saw the same observation. 
  A snippet of the problem at hand is pasted below. 

  [   20.610748] kdump-tools[4559]: Starting kdump-tools:  * Mounting NFS 
mountpoint 150.1.1.20:/home/tools ...
  [   53.400516] kdump-tools[4559]:  * Dumping to NFS mountpoint 
150.1.1.20:/home/tools/201611100158
  [   53.409242] kdump-tools[4559]:  * running makedumpfile -c -d 31 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete
  [   53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   53.527154] kdump-tools[4559]: The kernel version is not supported.
  [   53.527488] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   53.527813] kdump-tools[4559]: makedumpfile Failed.
  [   53.528117] kdump-tools[4559]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [   90.754092] kdump-tools[4559]: cp: error writing 
'/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error
  [   90.754857] kdump-tools[4559]:  * kdump-tools: failed to save vmcore in 
/mnt/var/crash/9.47.84.18-201611100158
  [   90.756155] kdump-tools[4559]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158
  [   90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory 
type.
  [   90.759089] kdump-tools[4559]: The kernel version is not supported.
  [   90.759436] kdump-tools[4559]: The makedumpfile operation may be 
incomplete.
  [   90.759780] kdump-tools[4559]: makedumpfile Failed.
  [   90.760094] kdump-tools[4559]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   90.760668] kdump-tools[4559]:  * kdump-tools: failed to save dmesg 
content in /mnt/var/crash/9.47.84.18-201611100158
  [   90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500
  [   90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No 
such file or directory
  [   90.887070] kdump-tools[4559]: Rebooting.

  == Comment: #13 - Kevin W. Rudd  - 2016-11-11 17:12:33 ==

  I was able to 

[Kernel-packages] [Bug 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1654068

Title:
  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 ==
  ---Problem Description---

  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

  
  ---Steps to Reproduce---

  1. Configure fadump.
  2. Trigger crash.

  Logs
  =

  root@alp9:/home/ubuntu#  service kdump status
  ? kdump.service
 Loaded: not-found (Reason: No such file or directory)
 Active: inactive (dead)
  root@alp9:/home/ubuntu# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-32-generic
  current state:ready to fadump


  [-1;-1f[3.187917] 
kdump-tools[1049]: Starting kdump-tools:  * running makedumpfile -c -d 31 
/proc/vmcore /var/crash/201612220208/dump-incomplete
  Copying data   : [100.0 %] |
  [5.711820] kdump-tools[1049]: The kernel version is not supported.
  [5.712201] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.712515] kdump-tools[1049]: The dumpfile is saved to 
/var/crash/201612220208/dump-incomplete.
  [5.712849] kdump-tools[1049]: makedumpfile Completed.
  [5.720901] kdump-tools[1049]:  * kdump-tools: saved vmcore in 
/var/crash/201612220208
  [5.916826] kdump-tools[1049]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201612220208/dmesg.201612220208
  [5.941113] kdump-tools[1049]: The kernel version is not supported.
  [5.941612] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.941969] kdump-tools[1049]: The dmesg log is saved to 
/var/crash/201612220208/dmesg.201612220208.
  [5.942340] kdump-tools[1049]: makedumpfile Completed.
  [5.942648] kdump-tools[1049]:  * kdump-tools: saved dmesg content in 
/var/crash/201612220208
  [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500
  [6.018241] kdump-tools[1049]: Rebooting.
  [6.025884] reboot: Restarting system

  == Comment: #3 - Hari Krishna Bathini  - 2017-01-04 07:14:19 ==

  Canonical,

  Please pick the latest version of makedumpfile (v1.6.1) which
  officially supports 4.8 kernels.

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1654068/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1366754] Re: kdump does not work with encrypted root partition

[Louis Bouchard]

Hello,

Unlike Fedora, Debian and ubuntu kernel dump mechanism is installed on
the root filesystem and not in the initrd. So in order to be able to run
kdump, the root filesystem needs to be mounted first.

This is handled by the /scripts/local-top/cryptroot script which is
where the prompt for the passphrase happens. So the kdump-tools scripts
have no way to interact with that phase of the boot. There is no kernel
argument to the cryptroot script that would allow it to receive a
passphrase when the second kernel is booted.

Using the cryptkeyscript / cryptkey boot parameters to pass a keyfile to
open the encrypted root would create major security issue so it is not
viable.

So kexec-tools has no solution for this issue as it lies outside of its
control.

** Changed in: makedumpfile (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: makedumpfile (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1366754

Title:
  kdump does not work with encrypted root partition

Status in makedumpfile package in Ubuntu:
  Won't Fix

Bug description:
  I have my root partition encrypted using dm-crypt.
  I could not get kdump working with the encrypted root partition, the computer 
simply hangs forever and will never reboot. (I tried the same kdump and grub 
settings on an identical install without encrypted root on the same machine and 
everything worked fine there.)

  No errors are shown on the screen, when I trigger a panic from an x
  session since the display is simply frozen and nothing will happen. I
  guess the crash kernel expects the luks password and therefore will
  wait for the password forever. I tried to blindly type in my password,
  but I have never succeeded.

  I can imagine 2 ways this bug could be solved:

  1.) the password for the root partition could be passed from the primary 
kernel to the crash kernel during load time
  This is discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=1028397 
in comment #9:
  "One could argue that password could be passed to second kernel in bootparams
  during load time. But this is very unconventional and first requires the work
  I am doing to implement a new kexec syscall which prepares bootparam in 
kernel (as opposed to user space).
  So in long term may be there is a case that pass credentials from old kernel 
to new kernel using bootparams. But don't expect anything soon."

  2.) kdump allows dumping to an external partition that is not
  encrypted without mounting the root partition, such as the /boot
  partition.

  Another redhat bug report where something similar is discussed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1053045.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1366754/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.

[Louis Bouchard]

Hello,

Version 1.6.1 of makedumpfile was announced upstream a bit more than one
week ago (27.12.16). As of this morning, it was not even packaged for
Debian.

I happen to be the debian maintainer for makedumpfile. I uploaded
1.6.1-1 minutes ago to Debian unstable. I will sync to Zesty in the
following days. So a version for the 4.8 kernel will be available in
Zesty shortly.

Regarding 16.04, the Stable Release Update procedure forbids uploads of
major releases as SRU. So makedumpfile 1.6.1 will not be released to
Xenial and Yakkety.

But 4.8 kernel specific issues have already been addressed in LP:
#1626269. Once makedumpfile 1.6.1 becomes available in Zesty, I will
investigate the possibility of disabling the "kernel not supported"
message for the 1.6.0 versions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1654068

Title:
  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 ==
  ---Problem Description---

  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

  
  ---Steps to Reproduce---

  1. Configure fadump.
  2. Trigger crash.

  Logs
  =

  root@alp9:/home/ubuntu#  service kdump status
  ? kdump.service
 Loaded: not-found (Reason: No such file or directory)
 Active: inactive (dead)
  root@alp9:/home/ubuntu# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-32-generic
  current state:ready to fadump


  [-1;-1f[3.187917] 
kdump-tools[1049]: Starting kdump-tools:  * running makedumpfile -c -d 31 
/proc/vmcore /var/crash/201612220208/dump-incomplete
  Copying data   : [100.0 %] |
  [5.711820] kdump-tools[1049]: The kernel version is not supported.
  [5.712201] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.712515] kdump-tools[1049]: The dumpfile is saved to 
/var/crash/201612220208/dump-incomplete.
  [5.712849] kdump-tools[1049]: makedumpfile Completed.
  [5.720901] kdump-tools[1049]:  * kdump-tools: saved vmcore in 
/var/crash/201612220208
  [5.916826] kdump-tools[1049]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201612220208/dmesg.201612220208
  [5.941113] kdump-tools[1049]: The kernel version is not supported.
  [5.941612] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.941969] kdump-tools[1049]: The dmesg log is saved to 
/var/crash/201612220208/dmesg.201612220208.
  [5.942340] kdump-tools[1049]: makedumpfile Completed.
  [5.942648] kdump-tools[1049]:  * kdump-tools: saved dmesg content in 
/var/crash/201612220208
  [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500
  [6.018241] kdump-tools[1049]: Rebooting.
  [6.025884] reboot: Restarting system

  == Comment: #3 - Hari Krishna Bathini  - 2017-01-04 07:14:19 ==

  Canonical,

  Please pick the latest version of makedumpfile (v1.6.1) which
  officially supports 4.8 kernels.

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1654068/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1654068] Re: Ubuntu 16.04.02: Error message "kernel version is not supported" is logged during fadump, dump capture will be successful.

[Louis Bouchard]

** Changed in: makedumpfile (Ubuntu)
   Status: New => Confirmed

** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: makedumpfile (Ubuntu Yakkety)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1654068

Title:
  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-12-25 23:00:37 ==
  ---Problem Description---

  Ubuntu 16.04.02: Error message "kernel version is not supported" is
  logged during fadump, dump capture will be successful.

  
  ---Steps to Reproduce---

  1. Configure fadump.
  2. Trigger crash.

  Logs
  =

  root@alp9:/home/ubuntu#  service kdump status
  ? kdump.service
 Loaded: not-found (Reason: No such file or directory)
 Active: inactive (dead)
  root@alp9:/home/ubuntu# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-32-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-32-generic
  current state:ready to fadump


  [-1;-1f[3.187917] 
kdump-tools[1049]: Starting kdump-tools:  * running makedumpfile -c -d 31 
/proc/vmcore /var/crash/201612220208/dump-incomplete
  Copying data   : [100.0 %] |
  [5.711820] kdump-tools[1049]: The kernel version is not supported.
  [5.712201] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.712515] kdump-tools[1049]: The dumpfile is saved to 
/var/crash/201612220208/dump-incomplete.
  [5.712849] kdump-tools[1049]: makedumpfile Completed.
  [5.720901] kdump-tools[1049]:  * kdump-tools: saved vmcore in 
/var/crash/201612220208
  [5.916826] kdump-tools[1049]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201612220208/dmesg.201612220208
  [5.941113] kdump-tools[1049]: The kernel version is not supported.
  [5.941612] kdump-tools[1049]: The makedumpfile operation may be 
incomplete.
  [5.941969] kdump-tools[1049]: The dmesg log is saved to 
/var/crash/201612220208/dmesg.201612220208.
  [5.942340] kdump-tools[1049]: makedumpfile Completed.
  [5.942648] kdump-tools[1049]:  * kdump-tools: saved dmesg content in 
/var/crash/201612220208
  [5.994508] kdump-tools[1049]: Thu, 22 Dec 2016 02:08:35 -0500
  [6.018241] kdump-tools[1049]: Rebooting.
  [6.025884] reboot: Restarting system

  == Comment: #3 - Hari Krishna Bathini  - 2017-01-04 07:14:19 ==

  Canonical,

  Please pick the latest version of makedumpfile (v1.6.1) which
  officially supports 4.8 kernels.

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1654068/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp