This bug was fixed in the package linux - 3.13.0-141.190
---
linux (3.13.0-141.190) trusty; urgency=low
* linux: 3.13.0-141.190 -proposed tracker (LP: #1744308)
* ubuntu_32_on_64 test crash Trusty 3.13.0-140 amd64 system (LP: #1744199) //
test_too_early_vsyscall from ubuntu_q
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
-
Tested on another Trusty i386 node "onibi" (a node without smep in
/proc/cpuinfo too)
with the kernel built by smb
(linux-image-3.13.0-141-generic_3.13.0-141.190~ptifix1_amd64.deb), it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
F.Y.I. Here is the kernel panic message.
You can google for "PANIC: double fault, error_code: 0x0".
[ 193.361839] PANIC: double fault, error_code: 0x0
[ 193.363960] Kernel panic - not syncing: Machine halted.
[ 193.366020] CPU: 1 PID: 1822 Comm: a.out Not tainted 3.13.0-140-generic
#189-Ubuntu
** Description changed:
THIS IS A POTENTIAL REGRESSION
Steps:
1. Deploy a Trusty amd64 node (node pepe in this case)
2. sudo apt-get install git python-minimal -y
3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
4. git clone --depth=1 git:/
5 matches
Mail list logo
