Bug was migrated to other tracker per #13. Closing
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1247906
Title:
Repe
** Changed in: linux
Status: Confirmed => Unknown
--
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/1247906
Title:
Repeatable oops qxl_enc_commit
Status in Linux:
Unknown
Status i
This has 'gone away' on trusty but not saucy; I think it's the X server update,
but can't be sure.
Looking at the debug I sent upstream I'm wondering if the problem is the X
server stopping the VT change happening
as the 1st problem, and then things going down hill from there.
--
You received t
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=71365.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Also fails in set I built from drm-next, so I've reported it upstream in
the spice/qxl bug tracker and added the link here
** Bug watch added: freedesktop.org Bugzilla #71365
https://bugs.freedesktop.org/show_bug.cgi?id=71365
** Also affects: linux via
https://bugs.freedesktop.org/show_bug
Today's drm-next kernel also fails; linux-
headers-3.12.0-996_3.12.0-996.201311070425_all.deb
--
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/1247906
Title:
Repeatable oops qxl_enc_commit
Linux trusty 3.12.0-1-generic #3-Ubuntu SMP Tue Oct 29 18:41:32 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
corrupted console on 1st c-a-f1, oops on c-a-f3 (even via grub menu)
Linux trusty 3.10.0-031000-generic #201306301935 SMP Sun Jun 30 23:36:16 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
got oo
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kerne
Answer to 1st question 1st;
I've got this on both a saucy and a trusty guest, so not new in Trusty, but
Raring doesn't seem to exhibit it
Linux saucy 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
still oopsing - slightly different backtrace a
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.12 kernel[0].
If this bug is fixed in the mainline kernel, please add th
10 matches
Mail list logo
