[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373091
[Expired for linux (Ubuntu Trusty) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to clarify, the bug still exists in -proposed or the latest
upstream kernel?
Also, there is a newer version of the 3.13 upstream stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.9-trusty/
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
Sorry I've been away so only now had a chance to look. And it hasn't worked
I'm afraid
On 1 Oct 2014 19:30, Joseph Salisbury joseph.salisb...@canonical.com
wrote:
So it this bug fixed in the upstream stable kernel: 3.13.11.7 ? If it
is, you may want to test the latest -proposed Trusty kernel.
So it this bug fixed in the upstream stable kernel: 3.13.11.7 ? If it
is, you may want to test the latest -proposed Trusty kernel.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you in advance!
--
You received this bug notification
Before starting a bisect, I'd like to see if this bug is already fixed
in the latest upstream stable kernel. If not, we can also test the
latest mainline kernel to see if it's fixed there.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
Thest latest upstream stable kernel for Trusty
Ok, I've downloaded both and currently running the upstream kernel
On 24 September 2014 17:31, Joseph Salisbury joseph.salisb...@canonical.com
wrote:
Before starting a bisect, I'd like to see if this bug is already fixed
in the latest upstream stable kernel. If not, we can also test the
This issue started happening after a kernel update in 13.10? Do you
recall what kernel version last did not panic, and the first version
when this started?
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key
--
You received this bug notification because
I'm afraid I don't know exactly which one, but it was the one before I
upgraded today, will that be logged anywhere?
On 23 Sep 2014 20:55, Joseph Salisbury joseph.salisb...@canonical.com
wrote:
This issue started happening after a kernel update in 13.10? Do you
recall what kernel version last
