** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404242
Title:
Radeon crash on 14.04 LTS stops Xorg from starting
To manage
To clarify the above - it works in 3.13.11.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404242
Title:
Radeon crash on 14.04 LTS stops Xorg from starting
To manage notifications about this
Yeah, that's a heck of a lot of bisecting and builds.
However, since 3.13 is the trusty kernel, I figured I'd try the latest
of that, and it works there as well - so upstream has patched it on that
maintenance branch as well. I'm going to reverse bisect that instead
(should be shorter).
** Tags
** Tags removed: kernel-fixed-upstream-3.19-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404242
Title:
Radeon crash on 14.04 LTS stops Xorg from starting
To manage notifications about this
Okay, digging in to this, I grabbed the kernel repos from upstream and
added the kernel.ubuntu.com remote, and in looking at those and getting
my bearings, I see that there is an Ubuntu-3.13.0-44.73, which is one
version greater than what I'm running, and I find that it is in trust-
proposed. So,
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404242
Title:
Radeon crash on 14.04 LTS stops Xorg from starting
To manage
Finally got around to testing this (apologies, holidays). This is fixed
in v3.19-rc2-vivid, which I think further lends credence to my
speculation that this bug is the same as #1397553, only for Trusty.
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.19-rc2
--
You received this
Matthew Caron, the next step is to fully reverse commit bisect from
kernel 3.13 to 3.19-rc2 in order to identify the last bad commit,
followed immediately by the first good one. Once this commit has been
identified, then it may be reviewed as a candidate for backporting into
your release. Could
Matthew Caron, thank you for reporting this and helping make Ubuntu better. As
per http://www.gigabyte.com/products/product-page.aspx?pid=2763#bios an update
to your computer's buggy and outdated BIOS is available (F7). If you update to
this following
Sorry about that - the board is so old, it never occurred to me that
there may be a BIOS update (indeed, IIRC, I build the system in June of
2008, so I didn't see the July update).
Anyway, updated BIOS to F7. No change in behavior. It is as originally
described.
Your requested output:
Matthew Caron, could you please test the latest upstream kernel
available from the very top line at the top of the page (the release
names are irrelevant for testing, and please do not test the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
allow additional upstream
Happens with 3.16.0-28-generic as well:
Dec 19 08:29:02 case kernel: [ 360.612037] INFO: task Xorg:2402 blocked for
more than 120 seconds.
Dec 19 08:29:02 case kernel: [ 360.614173] Tainted: G OX
3.13.0-43-generic #72-Ubuntu
Dec 19 08:29:02 case kernel: [ 360.616310] echo 0
apport information
** Tags added: apport-collected
** Description changed:
Kernel message:
[ 31.778064] BUG: unable to handle kernel paging request at ec200900
[ 31.778105] IP: [811a2046] kfree+0x56/0x140
[ 31.778133] PGD 0
[ 31.778145] Oops: [#1] SMP
13 matches
Mail list logo
