I'm commenting here because I have a very similar problem (and have had
said problem for some time), but which manifests in something of the
opposite way:
After boot my script, as yours, does `echo OFF
/sys/kernel/debug/vgaswitcheroo/switch`. Several seconds later, I begin
receiving
[
If gart_ and evergreen_ are related errors (my presumption), I can
confirm an actual failure (complete with debug dump) on the patched
kernel.
It took about 100 or so boots for this to show up.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@harry
I don't know if it means anything, but in newer kernels you may be unable to
use that command, since /sys/kernel/debug may not be owned by you. A quick and
dirty (if dangerous) solution would be to change the first line to
chown username(:group) /sys/kernel/debug/ -R
where username is
Out of three boots, the first two failed on an evergreen_cp_ error.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Kernel BUG during
Oh. Clarification: Out of three boots of bisect018, the first two failed
on an evergreen_cp_ error.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD
I have 20 consecutive successful boots on this commit. I have no boot
failures yet.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470]
On five boots of bisect016 I have two evergreen_cp_start errors.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and 5470] Kernel BUG during
On bisect017 I've had 19 successful boots, and one that ended with the
gart_unbind error (not evergreen_cp_...)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
I have had 20 boots with one oops, but not evergreen_cp_resume on bisect
014. I second Martin.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD 5650 and
I have booted bisect015 twice, and both times got evergreen_cp_restart
oops.
This commit is affected by the bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
Ok.
So far I've had 11 consecutive successful boots with bisect012
I took another look at 005. While the screen goes black and I can bring
up no TTY, kern.log shows no evergreen_cp_resume errors. Furthermore,
the system eventually gets to the gdm login screen (I can hear the ding
noise and can
Here's what I got as an error with bisect 011:
[ 29.400514] Stack:
[ 29.400524] 88014d4dfc38 a01c7303 88014d4dfc08
0631815dd48e
[ 29.400561] 88014d4dfc38 88013f2b3240 0002
880143a60968
[ 29.400595] 880143a60560 88014db00148
I have a HP dm4-1100 (sometimes notated dm4t) with the 5470 switchable
graphics. I tested bisects 001, 004, 005, 006, and 011.
001, 004, and 006 each booted properly 10 times out of 10.
005 failed the first three times before I gave up on it.
011 booted 10 out of 13 times. The last two times I
13 matches
Mail list logo
