lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <226dee610803040913h4718b61r4310fa78938bc386@mail.gmail.com>
Date:	Tue, 4 Mar 2008 22:43:50 +0530
From:	"JoJo jojo" <onetwojojo@...il.com>
To:	"Dave Airlie" <airlied@...ux.ie>
Cc:	"Jonathan McDowell" <noodles@...th.li>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	xorg-driver-ati@...ts.x.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-rc3 + RS690 + DRM + xf86-video-ati hang

Is 128 MB some sort of a sweet spot for ram allocated to gpu  ?
(hard coded?)

First Alex suggested that, & now you.

(asking 'coz i used 256 MB while testing)

-JoJo

On Tue, Mar 4, 2008 at 4:53 PM, Dave Airlie <airlied@...ux.ie> wrote:
> >
>  > Is xf86-driver-ati 6.8.0 not a proper release? I'm pretty sure the
>  > combination of that, 2.6.25-rc3 and CONFIG_DRM_RADEON causes my machine
>  > to become unresponsive. I only tried a git build of the driver after the
>  > released version was causing issues.
>
>  Yes we made a mistake with 6.8.0 enabling DRI on rs680 chips before we
>  knew it worked for everyone, I may be still able to fix this in the kernel
>  but there is a good chance that it'll require a 6.8.1 userspace, I can't
>  do anything else about it..
>
>  Jonathan I appreciate the bug report, I'm more saying to Andrew that
>  getting DRI right on new chipsets is non-trivial as there are lot of
>  configurations we can't test until we actually push the code to users..
>  and in this case you are one of those..
>
>  you might try setting the VRAM in your BIOS to 128MB instead of Auto and
>  seeing it helps..
>
>  I'll be trying to fix the problem properly quite soon.
>
>  The correct workaround is to add Option "DRI" "Off" to xorg.conf or for me
>  to travel back in time and unrelease 6.8.0. Removing the kernel DRI
>  support will just break lots of working systems.
>
>  Dave.
>
>
>   >
>  > Replacing 2.6.25-rc3 with 2.6.24 (still with CONFIG_DRM_RADEON enabled)
>  > results in a machine that boots to GDM successfully. Likewise if I
>  > disable CONFIG_DRM_RADEON in 2.6.25-rc3 the machine boots to GDM ok.
>  >
>  > J.
>  >
>  >
>
>
> _______________________________________________
>  xorg-driver-ati mailing list
>  xorg-driver-ati@...ts.x.org
>  http://lists.x.org/mailman/listinfo/xorg-driver-ati
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ