Re: [git pull] drm fixes + agp + one fb patch (bisected)

[Markus Trippelsdorf]

On Wed, Jun 30, 2010 at 10:49:41AM -0400, Alex Deucher wrote:
> On Wed, Jun 30, 2010 at 3:31 AM, Markus Trippelsdorf
> <markus@xxxxxxxxxxxxxxx> wrote:
> > On Wed, Jun 30, 2010 at 08:54:40AM +0200, Markus Trippelsdorf wrote:
> >> On Wed, Jun 30, 2010 at 02:03:04AM +0100, Dave Airlie wrote:
> >> >
> >> > one fb layer fix in a flag I introduced,
> >> >
> >> > the rest are drm fixes:
> >> > radeon fixes: the larger ones in the command stream checker for older cards,
> >> > which was causing a lot of userspace apps to fail. Also some powerpc server fixes.
> >> > along with some updates to the evergreen command stream checker introduced in -rc1.
> >> >
> >> > agp: fix issue with warning on memory allocation + fallback to vmalloc.
> >> > ttm: fix regression introduced in -rc1 in memory allocation paths.
> >> >
> >> > The following changes since commit 7e27d6e778cd87b6f2415515d7127eba53fe5d02:
> >> >
> >> >   Linux 2.6.35-rc3 (2010-06-11 19:14:04 -0700)
> >> >
> >>
> >> I've tested these patches and they break my setup (RS780). On reboot, the
> >> monitor goes straight to powersaving mode and no framebuffer is shown.
> >
> > This is the result of the bisection:
> >
> > 07d4190327b02ab3aaad25a2d168f79d92e8f8c2 is the first bad commit
> > commit 07d4190327b02ab3aaad25a2d168f79d92e8f8c2
> > Author: Alex Deucher <alexdeucher@xxxxxxxxx>
> > Date:   Sat Jun 12 11:50:13 2010 -0400
> >
> >    drm/radeon/kms: fix bandwidth calculation when sideport is present
> >
> >    Fixes fdo bug 27529:
> >    https://bugs.freedesktop.org/show_bug.cgi?id=27529
> >
> >    Reported-by: steckdenis@xxxxxxxx
> >    Signed-off-by: Alex Deucher <alexdeucher@xxxxxxxxx>
> >    Cc: stable <stable@xxxxxxxxxx>
> >    Signed-off-by: Dave Airlie <airlied@xxxxxxxxxx>
> 
> Markus, can you send me a copy of your vbios? as root:
> cd /sys/bus/pci/devices/<pci bus id of video card>
> echo 1 > rom
> cat rom ? /tmp/vbio.rom
> echo 0 > rom

Attached.

> 
> Also, when you say "on reboot" do you mean the card comes up ok
> initially with the new kernel and then fails after a reboot, or fails
> directly after booting the new kernel?  Also, is there an oops or
> anything like that in dmesg?

It fails directly after booting the new kernel. There is no oops or
anything like it in dmesg, because the kernel fails so early that it
could not log anything.

-- 
Markus

Attachment: vbio.rom
Description: Binary data