Kernel Bug Tracker – Bug 16515
[bisected] Radeon rv280 can't boot on kernel 2.6.35.
Last modified: 2012-08-09 15:29:51 UTC
Created attachment 27350 [details]
git bisect 2.6.35 bad 2.6.34 god
Radeon agp rv280 can't boot on kernel 2.6.35 using dvi port, on vga port works as
well, on kernel 2.6.34 work fine all ports.
I try to revert this patch and post result here to night.
Created attachment 27351 [details]
Created attachment 27352 [details]
Created attachment 27353 [details]
radeontool regmatch '*' > working.dump on kernel 2.6.35 after git revert
Can you attach a a broken dump as well (2.6.35 without the revert)? Also, please only provide dumps with module option modeset=1.
(In reply to comment #4)
> Can you attach a a broken dump as well (2.6.35 without the revert)? Also,
> please only provide dumps with module option modeset=1.
No, on 2.6.35 without the revert always get a kernel panic or hard reboot and console not shows anything.
The first dump is good and have module option modeset=1 by default.
Handled-By : Alex Deucher <firstname.lastname@example.org>
Does booting with radeon.agpmode=-1 help? This might be related to bug 16581 or bug 16574. Can you try the patches attached to those bugs?
(In reply to comment #8)
> Does booting with radeon.agpmode=-1 help? This might be related to bug 16581
> or bug 16574. Can you try the patches attached to those bugs?
The option radeon.agpmode=-1 does not work and the patches do not solve the problem, the result is always the same as you know.
On Wednesday, September 01, 2010, Johan Kullstam wrote:
> "Rafael J. Wysocki" <email@example.com> writes:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.34 and 2.6.35.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.34 and 2.6.35. Please verify if it still should
> > be listed and let the tracking team know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16515
> > Subject : Radeon rv280 can't boot on kernel 2.6.35.
> > Submitter : Albert Gall <firstname.lastname@example.org>
> > Date : 2010-08-04 16:10 (26 days old)
> > Handled-By : Alex Deucher <email@example.com>
> This bug was introduced with 2.6.35-rc1 and continues through
> 2.6.36-rc3. It is still a bug. I cannot boot with modeset=1 on DVI
> port (not sure about VGA port status).
6b8b1786a8c29ce6e32298b93ac8d4a18a2b11c4 is the first bad commit
Author: Jerome Glisse <firstname.lastname@example.org>
Date: Wed Apr 7 10:21:31 2010 +0000
drm/radeon/kms: enable use of unmappable VRAM V2
This patch enable the use of unmappable VRAM thanks to
previous TTM infrastructure change.
V2 update after io_mem_reserve/io_mem_free callback balancing
Signed-off-by: Jerome Glisse <email@example.com>
Signed-off-by: Dave Airlie <firstname.lastname@example.org>
How much vram does your card actually have (not what's reported in dmesg)? Is it 128 MB or 256 MB? Also in comment 1, are you saying that vga works fine but dvi does not or that neither port works?
(In reply to comment #13)
> How much vram does your card actually have (not what's reported in dmesg)? Is
> it 128 MB or 256 MB? Also in comment 1, are you saying that vga works fine but
> dvi does not or that neither port works?
I think my video card have 128MB of video ram, but I'm not really sure.
Xorg.log show on UMS:
[ 45.948] (--) RADEON(0): Mapped VideoRAM: 131072 kByte (128 bit DDR SDRAM)
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at c000 [size=256]
Region 2: Memory at ff4f0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at ff4c0000 [disabled] [size=128K]
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at ff4e0000 (32-bit, non-prefetchable) [size=64K]
VGA to VGA work fine here but DVI to HDMI no.
This is the card:
This shows 256MB DDR.
I test git kernel 2.6.37-rc8 and bug persist.
Can you try these two patches:
(In reply to comment #17)
> Can you try these two patches:
Now I have new hardware and my old pc is in pieces when I have some time I'll try.