canonical-ubuntu-qa team mailing list archive

[Timo Aaltonen <2071756@xxxxxxxxxxxxxxxxxx>]

** Package changed: linux-oem-6.10 (Ubuntu Noble) => linux-oem-6.11
(Ubuntu Noble)

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2071756

Title:
   dev test from ubuntu_stress_smoke_tests cause VM crash with
  N-oem-6.10

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  The dev stressor from ubuntu_stress_smoke_tests will cause test
  interrupt with Noble OEM 6.10 VM on openstack since 6.10.0-1003.3

  With further investigation, this issue can be reproduced with a VM on
  a bare-metal. When this happens the VM will be terminated. (Bare-metal
  can pass with this test)

  It's 100% reproducible with the following steps:
  # On a bare-metal running with Noble
  sudo apt install uvtool build-essential -y
  sudo uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=noble arch=amd64
  SSH_KEY="$HOME/.ssh/id_rsa"
  ssh-keygen -f $SSH_KEY -t rsa -N ''
  sudo -u ubuntu uvt-kvm create oem610 release=noble arch=amd64 --memory 2048
  sleep 60
  ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610`
  # Inside the VM
  sudo apt-add-repository ppa:canonical-kernel-team/ubuntu/proposed -y
  sudo apt install kernel-testing--linux-oem-6.10--full--oem -y
  sudo reboot
  sleep 60
  ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610`
  git clone https://github.com/ColinIanKing/stress-ng.git
  cd stress-ng; make
  sudo ./stress-ng -v -t 5 --dev 4 --dev-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable
  # VM will be terminated here, you will have to restart it.

  Issue reported upstream: https://github.com/ColinIanKing/stress-ng/issues/407
  From Colin's investigation it looks like a kernel issue

  This issue can be reproduced with mainline kernel v6.10-rc4 (AMD64
  debs are not available for v6.10-rc6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071756/+subscriptions