Not noticed on other architectures as I am only testing against AArch64
at the moment. The failure was with the stock kernel that comes with the
vivid cloud image (3.19.0-9-generic). I had been building and using
3.19.1 on Trusty (AArch64 again) for about 3 days and hadn't noticed the
failure
I have seen this oops twice; I didn't report the issue first time round
as the machine I was using had been powered down and I was unable to
collect any logs. I happened to notice the stacktrace in my serial
console window so I tried again and saw the issue again (and raised this
bug). However, I
The appport-collect I just did was from the same machine, but a
different cloud image deployment (current/ 18-Mar-2015 06:05) . The
recent attachments may/may not be useful to the original bug report.
But if you look at the dmesg attachment you can see there is a different
(and new) stacktrace.
apport information
** Tags added: apport-collected
** Description changed:
I was installing OpenStack using devstack/stack.sh and noticed that at
some point a `pip install' had failed. I later untarred
linux-3.19.1.tar.xz and get the same (or similar) kernel backtrace.
ProblemType:
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
Title:
Kernel oops when running devstack/stack.sh
To manage notifications
I noticed you are on AArch64. Have you had this happen on other arches?
You said you saw a failure then tried the 3.19.1 vanilla kernel, which kernel
version exactly did you use before?
Does devstack even work on aarch64 systems? Are you using a special devstack
version?
Did this work on earlier
I will try and reproduce - but this machine is automatically deployed
and I have since destroyed it. Please bear with me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
Title:
Kernel oops
