Hi all,
I really apoligize for that, still don't know what was going on.
Sorry,
Klaus
--
Klaus Reichlklaus.rei...@gmail.com
Danhausergasse 8/16 +43 6991 84 137 94
1040 Wien
On Tue, Jun 5, 2012 at 9:33 PM, Zentai Andras
As far as I understand it has time racing condition between intel and
radeon modules. And it may be related with vgaswitcheroo too. On
earlyer versions of ubuntu changing the waiting time and the gfx mode in
grub seemed to affect the bug somehow. Some combination of that even
maked it disappear
Really clever way to invite all bug subscribers to your LinkedIn
network... ;)
--
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
Switched to 12.04. Bug seems to be gone.
--
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 recovery boot and in
normal
Switched to 12.04. Bug seems to be gone.
On my machine it is not true, I don't know if there was some updates but now
ubuntu starts in 50%
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
HP dm4t (ATI 5470), after several installs last weekend - bug no longer present
in Xubuntu 11.10 stock, also not present after upgrade to kernel 3.2.0-10. It
was still present with LinixMint Debian Edition stock (at that moment 2.6
kernel), but after upgrade to latest kernel it was fixed.
In
** Tags added: hybrid-graphics
--
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 recovery boot and in
normal boot
bug persist :(
someone have update the bios ? now can fix the graphic card?
--
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
I just ran into this bug after installing the latest 11.10 release on a
new ENVY, looks like the fix here didn't work :(
--
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
The bug is back now for me (( The thing I have done before to make it gone -
pass nosplash instead of quiet splash in grub and enable option
GRUB_TERMINAL=console and GRUB_GFXMODE=1024x768
Now i have reverted these options - and the bug is back for me on Natty
2.6.38-10-generic.
So it seems
No, the later fix is not working anymore. Now blacklisting radeon to
modprobe it manually when switching.
--
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
I have not such good experience with Oneiric on my HP G62-a35er. First
of all by default startup brightness is 0% (see bug #873191). The second
is that I tried to turn power on discrete card by adding corresponding
command to /etc/rc.local and once some kernel oops occurred at startup
(now I moved
one question i have ubuntu 10.04 LTS
the fix will be released on this version or not?
for fix the bug , What should I do? :D
thanks you !
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Moving status to Fix Released based on positive test results with
Oneiric noted in comment #172.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
Has anyone tested this yet since oneiric released? I'd like to get
confirmation that the problem is fixed there. Thanks!
--
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
** Changed in: xserver-xorg-driver-ati
Status: Confirmed = Fix Released
--
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
** Changed in: xserver-xorg-driver-ati
Importance: High = Critical
--
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
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
Seth,
To exam your assumption, I reverted that commit and replaced the
vga_arbiter_check_bridge_sharing() function call by some delays, but I still
encountered the issue.
The error message is the same.
Do you have any suggestion to do the test?
==
diff --git
** Tags added: blocks-hwcert
--
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 recovery boot and in
normal boot
@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
AceLan: The problem right now is that I suspect that the patch doesn't
actually do anything to directly fix the problem. I.e., that the patch
fixes this oops is just a side-effect of burning more time before the
driver tries to access the hardware or something like that. I'm not sure
though so I'd
Seth,
I can confirm the commit
3448a19 vgaarb: use bridges to control VGA routing where possible.
fixed this issue.
And this issue is a hwcert block issue, so is there anything that I can help to
make the SRU process faster?
--
You received this bug notification because you are a member of
I've been looking at the patch we identified as fixing the problem, but
I can't work out any causal relationship between what it does and the
GPU being on when nouveau probes. I've inquired about it on the upstream
bugzilla to see if I'm missing something. But I'm beginning to suspect
that the
Hi Seth,
One bad experience I have had since installing the patched kernel. After
countless good boots I decided to add the following lines to
/etc/tc.local in order to use switcheroo:
chown username /sys/kernel/debug/vgaswitcheroo/switch # change username
with your user name
echo OFF
I've tested the patched natty kernel and have over 30 boots without the
evergreen_cp_resume oops, so the bisected patch indeed appears to be the
right one. Does it explain the race?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
bisect018 is now available. This should be the last bisect build, then
we'll need to apply the commit identified as fixing the issue onto natty
and see if that fixes the problem there.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [3448a19da479b6bd1e28e2a2be9fa16c6a6feb39]
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
The bisect identified this as the commit that fixes the problem:
3448a19 vgaarb: use bridges to control VGA routing where possible.
A natty build with this patch applied is available at the link below.
Please test to see whether or not the bug is reproducible in this build.
Thanks!
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]
Cool! it seems to be working for me. I even got a little taste of
the Plymouth boot screen which I haven't seen in a long time :)
I'll continue testing and let you know if I experience the B[lack]SOD.
On Fri, Aug 26, 2011 at 8:19 PM, josejuan05
727...@bugs.launchpad.netwrote:
I have 20
bisect016 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# good: [63f7d9828bf55cc8ee6f460830c5285fe06bef3e] drm/radeon/kms: add support
for thermal chips on combios asics
git bisect good 63f7d9828bf55cc8ee6f460830c5285fe06bef3e
Now testing commit
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
bisect017 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# good: [99b38b4acc0d7dbbab443273577cff60080fcfad] platform/x86: add MXM WMI
driver.
git bisect good 99b38b4acc0d7dbbab443273577cff60080fcfad
Now testing commit 3448a19da479b6bd1e28e2a2be9fa16c6a6feb39.
--
You
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
bisect015 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [000703f44c77b152cd966eaf06f4ab043274ff46] mxm/wmi: add MXMX interface
entry point.
git bisect bad 000703f44c77b152cd966eaf06f4ab043274ff46
Now testing commit 63f7d9828bf55cc8ee6f460830c5285fe06bef3e.
--
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:
bisect014 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [2703c21a82301f5c31ba5679e2d56422bd4cd404] drm/nv50/gr: move to exec
engine interfaces
git bisect bad 2703c21a82301f5c31ba5679e2d56422bd4cd404
Now testing commit 000703f44c77b152cd966eaf06f4ab043274ff46.
After 30 boots with bisect 014 I got 3 oopses but none mentioning
evergreen_cp_resume, so I deem it not affected.
--
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:
Bisect 013 booted ok 24 times out of 30. 3 of the remaining times failed
with an afaics unrelated oops in azx_interrupt in the snd_hda_intel
driver. The last 3 times there were oops'es which didn't manage to get
sufficiently logged on the tty to see where they were (the computer
froze either
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
bisect013 is now available.
http://people.canonical.com/~sforshee/lp727620/bisect/
# bad: [fcfc768806f2ed8ad56d9fd3f0c6af1cdb5e10e2] drm/nva3: support for memory
timing map table
git bisect bad fcfc768806f2ed8ad56d9fd3f0c6af1cdb5e10e2
Now testing commit
I've put up a new build (bisect012) at:
http://people.canonical.com/~sforshee/lp727620/bisect/
Here's the bisect log I used to re-seed the bisection.
# bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1
# good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39
git bisect start
I'm trying to construct a list of good and bad commits to use for
starting a new bisection run. Please take note that it only takes a
single occurrence of the evergreen_cp_resume oops to qualify a commit as
bad, so there's no need to continue testing once you've seen that oops.
I do agree that
Yes, I have verified that it's an oops in evergreen_cp_resume that I've
gotten at least once in each of bisects 006-011.
--
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
Oops, just noticed that I included 005 in the bad and inconclusive
lists. I meant for it to be only in the inconclusive list.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Because testing good bisects is tedious, I went backwards:
Bisect 005 is inconclusive since it bugs out with no tty output. Got one
kernel hang, but since there's no tty output I don't know if it's this
bug or not (nothing in kern.log from that boot either).
Bisect 004 does not show the bug
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
Thanks for checking, Martin. I was afraid that might happen with this
bug. Can you also try the other builds before 006 that reported as good
(001, 004, 005) and see if any of those fail?
It's best if we can get as many testers as possible for each build. It's
pretty clear when we get a bad
Can confirm the evergreen_cp_resume oops in bisect 11 (on fifth boot).
--
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
Since I've always gotten the bug in all the bisects I've tried, I
thought I better reverify bisect 006 which has been reported as working
by others. Unfortunately it didn't work for me, so we're getting
different results here. :(
I didn't get the oops in the log file, but I checked on screen that
bisect011 is now available.
# good: [4697995b98417c6da9ab2708a36f5e2bc926c8ac] drm/i915: split irq handling
into per-chipset functions
git bisect good 4697995b98417c6da9ab2708a36f5e2bc926c8ac
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
[Closing out the -ati task; the issue has been pretty definitively
narrowed to the kernel and the kernel team is active on it; nothing else
we should do at the X end for this bug.]
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Triaged = Invalid
--
You received this bug
I have now tried bisect 010 and got the oops in evergreen_cp_resume on
the third boot.
--
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]
Martin, thanks for testing. Your results at least match those reported
for the builds you tested. I don't know whether there's a bug for your
backlight issue. If you can't find one then you should open a new one.
bisect010 is now available.
# good: [8eb572942ca02890f590d9251233038e27dd3842]
[Side note: Had to install module-init-tools from oneiric to satisfy
deps in these bisect builds.]
Just to double check a little, I've tried the three latest bisects
007-009, and I've seen the oops in evertgreen_cp_resume at least once in
each of them.
However, the trig ratio is fairly low for
Can confirm this bug with AMD Radeon HD 6470M
--
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 recovery boot and in
Yet another confirmation with AMD Radeon HD 6470M on Dell Vostro 3350
lspci | grep -i radeon
01:00.0 VGA compatible controller: ATI Technologies Inc NI Seymour [AMD Radeon
HD 6470M] (rev ff)
uname -a
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64
x86_64 GNU/Linux
kern.log from ubuntu 11.04.
** Attachment added: radeon_crash.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/727620/+attachment/2199470/+files/radeon_crash.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Sorry to sound stupid, but I think there are many people affected by
this in layman terms, what's the status of this issue?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
On Sat, Jul 09, 2011 at 09:34:42PM -, harry wrote:
Sorry to sound stupid, but I think there are many people affected by
this in layman terms, what's the status of this issue?
The status is that there are multiple reports of this being fixed in
kernel version 3.0, and if this is true
bisect009 is now available.
# good: [fcca7926299944841569515da321bef9655b7703] drm/i915: reference counted
forcewake
git bisect good fcca7926299944841569515da321bef9655b7703
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Same issue than the previous one.
--
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 recovery boot and in
normal boot
this bug also affects
AMD Radeon HD 3300
--
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 recovery boot and in
this bug affects
Ubuntu 11.04 -and- 11.10
--
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 recovery boot and in
@Jean, that log does display the bug.
bisect008 is now available. We're getting close to the end, should be 3
builds after this one. It's looking like it will end up identifying a
change to the i915 driver.
# good: [2c34b850ee1e9f86b41706149d0954eee58757a3] drm/i915: fix ilk rc6
teardown
@Jean: So as I understand it you were unable to tell whether you were
getting the oops or not? Did you check your kern.log to see whether or
not it appears when booting with the bisect007 kernel?
For now I'm going to wait and see if we get some more testing on this
one.
--
You received this bug
confirm: 2.6.39-2 from mainline does not fix it. 50% chance for a good
boot
HP DV6tqe with dual GPU of intel/ati(good boot reports 2G NVRAM, bad
boot report 3G)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
I think it is the same bug but symptoms are slighty not the same. But I
don't know how to recognize this bug in the logs. I put in attachment
the kern.log when the boot failed.
** Attachment added: Fail.txt
bisect007 is now available.
# bad: [4b65177b27ede9dee3186bc3a58c737997ee4749] drm/i915: add IS_IVYBRIDGE
macro for checks
git bisect bad 4b65177b27ede9dee3186bc3a58c737997ee4749
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Bisect 007 does not work as well as the others. Half boots end badly.
But when it bugs there is no writting but just some points every where
in the screen. It is impossible to change tty.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
bisect006 is now available.
# bad: [69f7876b2ab61e8114675d6092ad0b482e233612] Merge remote branch
'keithp/drm-intel-next' of /ssd/git/drm-next into drm-core-next
git bisect bad 69f7876b2ab61e8114675d6092ad0b482e233612
--
You received this bug notification because you are a member of Ubuntu-X,
Bisect 006 works fine too : no X bug and no CPU issue.
--
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 recovery boot
bisect005 is now available.
# bad: [931474c4c30633400ff0dff8fb452ae20e01d067] Merge branch
'drm-radeon-next' of /ssd/git/drm-radeon-next into drm-core-next
git bisect bad 931474c4c30633400ff0dff8fb452ae20e01d067
--
You received this bug notification because you are a member of Ubuntu-X,
which
Bisect 005 works fine : no X bug and no CPU issue.
--
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 recovery boot and
Bisect 004 works as the bisect 001. No X bug but CPU at 100% every time.
--
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
Yup, same with me. bisect004 boots fine.
--
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 recovery boot and in
normal
@Ap. Syvertsen: That's interesting about the headers. With the next
build that tests bad for you, can you compare the lsmod output with and
without the headers packages installed?
bisect003 is now available.
# good: [9461702d2a54cd4d9da09b7755c96815791a9d07] m68k: let Makefile sort out
First of all, bisect003 crashes as well, with or without headers.
I looks like I kinda jumped to a conclusion too fast, as I am unable to
reproduce the no-header-boot link.
The reason why I was led to believe this is that I installed
bisect001-image without headers and suddenly I could boot
So, I've tried the last bisect, and it doesn't work : 2 boots of 10 succeed. So
was wondering if the others was really not working. And the bisect 002 crashes
every time too whereas the bisect 001 worked every times.
For information for every kernel I have to add the option --force-depends.
--
bisect004 is now available.
# good: [2b030bda66b0a59f8ebf0ce2117088256a5f9f97] mach-ux500: set proper I2C
platform data from MOP500s
git bisect good 2b030bda66b0a59f8ebf0ce2117088256a5f9f97
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Same comportment with this bisect. No X bug but CPU at 100% all the
time.
--
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
Hi Seth, thanks a lot for clarifying.
I've now tested the the three bisects and bisect000 crashes while
bisect001 boots every time. I have no problems with CPU use either.
For me however, bisect002 also crashes during start-up (two out of three
times).
As a side note, I had to install the
Hrm, I've got a lurking suspicion that this issue has a timing component
(and that could actually be why it works in 3.0, not that it's really
fixed but that the timing that some change in timing makes the problem
much harder to trigger). If your CPU is being pegged then that could be
affecting
Hello every body,
Bisect #001 work for me. The bug does not show up. But with this kernel
my CPU is always at 100%, but nothing to deal with 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.
Are these bisects between 2.6.39-1 and 3.0-rc1 or between 2.6.39 and
3.0-rc1?
I'm more than willing to try the bisects, but as I've already outlined,
2.6.39-1 is already good, it crashes, and I don't want to try too many
bisects.
--
You received this bug notification because you are a member of
@Ap. Syvertsen: Let's try to lay out everything clearly to make sure
there isn't any confusion. The swapping of the meanings of good and
bad are bound to cause confusion, so let's use the usual meanings for
any discussion with the understanding that the meanings are swapped
*only in the bisect
For me bisect #000 does not work. The bug affect it.
--
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 recovery boot and
Second build (bisect001) is now available in the same location.
Bisect log:
# bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1
# good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39
git bisect start 'v3.0-rc1' 'v2.6.39'
# good: [c44dead70a841d90ddc01968012f323c33217c9e]
Unfortunately I don't have the laptop around where the bug showed up
originally for me.
I'll be there again on one of the next weekends.
But be warned, I thought the bug has gone after updating natty a two
weeks ago.
I happily installed packages, got googleearth running, everything
looked great,
Hi,
Just a quick question. Isn't v2.6.39.1-oneiric/ after v2.6.39-rc7-oneiric/ ?
Because for me, 2.6.39-1 (which I'm guessing Jean is also referring to,
since 11.04 comes with 2.6.38-8) doesn't work while 3.0-rc3 works.
Testing rc1 now.
--
You received this bug notification because you are a
Yup,
My linux crashes occasionally during startup with kernel 2.6.39-1 with
this kernel BUG, while I'm unable to produce this on 3.0-rc1.
It is also worth noting that my rc.local script that turns off the power
to the radeon card works on 3.0-rc1 while it was not run on earlier
kernels even the
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
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
Yes, 2.6.39-1 is after 2.6.39-rc7.
I've been looking between 2.6.39 and 3.0-rc1 now, but nothing stands out
as the change that potentially fixes this issue. The next step is to
perform a bisection to try and locate the commit that fixes the problem.
I'll provide a series of kernels, please test
No one has identified what patches fix the issue, if it is indeed fixed
at all. The thing to do now is to test these kernels on more affected
machines, and if it fixes the problem universally we can try to find the
fix and backport it. You can get mainline kernels for Ubuntu from the
following
Hi every body,
I've tried some kernel and I find that using the kernel 3.0-rc2, it
seems to work properly. But using the 2.36.1 it doesn't work. But i
didn't try the 3.0-rc1.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@Jean, thanks for testing.
I don't see anything in the radeon driver changes that looks like it
obviously fixes the issue, but I've identified a handful that could be
responsible. These commits were introduced between 2.6.39-rc5 and -rc7.
What would be most helpful right now would to be able to
1 - 100 of 160 matches
Mail list logo
