[Bug 16881] [REGRESSION, Radeon-KMS] 2.6.36-rc[1-3] - missing textures in 0 A.D.
https://bugzilla.kernel.org/show_bug.cgi?id=16881 --- Comment #14 from Alex Deucher 2010-08-31 07:11:58 --- I was finally able to reproduce this. It's a bug in the mesa development snapshot you are using. Upgrade to a newer snapshot or use a released version. The drm code is fine. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 16881] [REGRESSION, Radeon-KMS] 2.6.36-rc[1-3] - missing textures in 0 A.D.
https://bugzilla.kernel.org/show_bug.cgi?id=16881 --- Comment #15 from trapdo...@gmail.com 2010-08-31 07:35:39 --- There's no newer snapshot available for my system (Ubuntu Lucid) in that PPA yet, only for Maverick. The yesterdays snapshot failed to build on Launchpad for Lucid (i386 and amd64). So I'll wait until the next one shows up, which I'd expect very soon (and hopefully it will be build successfully on amd64). I never compiled mesa myself and don't want to do it now, neither revert to 7.8. But still: on kernel 2.6.35.4, with the same mesa version the game runs fine, no empty black squares at all.. I understand it's that bug in mesa which affects only 2.6.36-rc. And the bug is triggered by some recent drm-radeon commit in kernel, but there is nothing wrong with that commit itself.. I'll test again when a new mesa snapshot is available and let you know the outcome right away. Thanks a lot for looking into this. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 16881] [REGRESSION, Radeon-KMS] 2.6.36-rc[1-3] - missing textures in 0 A.D.
https://bugzilla.kernel.org/show_bug.cgi?id=16881 --- Comment #16 from Alex Deucher 2010-08-31 07:47:15 --- It's sort of random luck. The vbo size was getting garbage values. You'll also note that the vbo size errors in your kernel log are gone with a newer mesa snapshot. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 17241] Enabling KMS on Radeon X300 gives NULL pointer dereference
https://bugzilla.kernel.org/show_bug.cgi?id=17241 --- Comment #7 from b...@istram.info 2010-08-31 08:37:51 --- Ok, I've tested this kernel versions: 2.6.33 2.6.35.2 2.6.35.4 and all are affected. Is there any other information I should provide to be more helpful? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'master'
Dne 28.8.2010 05:55, Eric Anholt napsal(a): > On Fri, 27 Aug 2010 13:16:04 +0200, Zdenek Kabelac > wrote: >> On 27.8.2010 12:02, Julien Cristau wrote: >>> On Fri, Aug 27, 2010 at 11:26:59 +0200, Zdenek Kabelac wrote: >>> Why keeping different name for C++ and C ? >>> Because changing the name for C means breaking API for existing users, >>> which is not a nice thing to do. >>> >> >> >> Well if DRM would have very stable API - it would make sence - but from a >> view >> of occasional user who needs to compile drm for intel driver - it seems the >> API is changed so frequently and in such an incompatible way that this >> change >> doesn't look all that bad. >> >> How many libdrm project users are there - and how often is this variable >> used >> outside of libdrm ? >> >> Now C++ will use different names for same variables - that IMHO bigger >> issue... >> >> Also - if headers are supposed to be C++ friendly - maybe usage of >> extern "C" might be handy for such case ? > > Uh, you claim the API has changed, but I'm not aware of any circumstance > since TTM removal where upgrading libdrm on Intel should have broken > either API or ABI for its users. Can you back that up? Ok - I'm remembering this issue: Essentially I've had idea to try to bisect for this problem: https://bugs.freedesktop.org/show_bug.cgi?id=26937 As I'm quite sure, that there were times were I could use fullscreen for flash without fear of having to restart my desktop. So I've tried just some random older git versions of libdrm & intel driver - there were some minor compilations issue (I guess some list defines conflicts and few other minor things for compilation). However compiled driver & library actually never worked and all I got was usually black screen. It's probably hard to judge if the problem is kernel driver (using usually quite fresh vanilla git tree) or Xorg from Fedora Rawhide can't work with some slightly older libdrm/intel. It probably not reasonable to spend time to detect where exactly is problem - all I want to point out is, that some internal API must changed significantly so while I could usually boot with 2 year old kernel, I cannot use few months old drm&intel driver. And back to this issue - if this variable is used a lot by other projects, than this commit is probably ok - though looks ugly. But if there is just one project which uses it, than it's probably better to break API and keep it clean and use same variable for C & C++ programs. Zdenek -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 16881] [REGRESSION, Radeon-KMS] 2.6.36-rc[1-3] - missing textures in 0 A.D.
https://bugzilla.kernel.org/show_bug.cgi?id=16881 Rafael J. Wysocki changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #17 from Rafael J. Wysocki 2010-08-31 20:02:36 --- Not a kernel bug, so closing. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 16881] [REGRESSION, Radeon-KMS] 2.6.36-rc[1-3] - missing textures in 0 A.D.
https://bugzilla.kernel.org/show_bug.cgi?id=16881 Rafael J. Wysocki changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 17241] Enabling KMS on Radeon X300 gives NULL pointer dereference
https://bugzilla.kernel.org/show_bug.cgi?id=17241 --- Comment #8 from Alex Deucher 2010-08-31 20:27:00 --- Can you attach a copy of your video bios? As root: cd /sys/bus/pci/devices/ echo 1 > rom cat rom > /tmp/x300.rom echo 0 > rom -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 17241] Enabling KMS on Radeon X300 gives NULL pointer dereference
https://bugzilla.kernel.org/show_bug.cgi?id=17241 --- Comment #9 from b...@istram.info 2010-08-31 23:43:47 --- Created an attachment (id=28711) --> (https://bugzilla.kernel.org/attachment.cgi?id=28711) video bios Just remembered - on 2.6.33 is one difference, after invoking modprobe radeon modeset=1 I got error, but the screen doesn't went blank. Video bios attached. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: drm: Branch 'master'
On Tue, 31 Aug 2010 12:17:43 +0200, Zdenek Kabelac wrote: > Dne 28.8.2010 05:55, Eric Anholt napsal(a): > > On Fri, 27 Aug 2010 13:16:04 +0200, Zdenek Kabelac > > wrote: > >> On 27.8.2010 12:02, Julien Cristau wrote: > >>> On Fri, Aug 27, 2010 at 11:26:59 +0200, Zdenek Kabelac wrote: > >>> > Why keeping different name for C++ and C ? > > >>> Because changing the name for C means breaking API for existing users, > >>> which is not a nice thing to do. > >>> > >> > >> > >> Well if DRM would have very stable API - it would make sence - but from a > >> view > >> of occasional user who needs to compile drm for intel driver - it seems > >> the > >> API is changed so frequently and in such an incompatible way that this > >> change > >> doesn't look all that bad. > >> > >> How many libdrm project users are there - and how often is this variable > >> used > >> outside of libdrm ? > >> > >> Now C++ will use different names for same variables - that IMHO bigger > >> issue... > >> > >> Also - if headers are supposed to be C++ friendly - maybe usage of > >> extern "C" might be handy for such case ? > > > > Uh, you claim the API has changed, but I'm not aware of any circumstance > > since TTM removal where upgrading libdrm on Intel should have broken > > either API or ABI for its users. Can you back that up? > > Ok - I'm remembering this issue: > > Essentially I've had idea to try to bisect for this problem: > https://bugs.freedesktop.org/show_bug.cgi?id=26937 > > As I'm quite sure, that there were times were I could use fullscreen for flash > without fear of having to restart my desktop. > > So I've tried just some random older git versions of libdrm & intel driver - > there were some minor compilations issue (I guess some list defines conflicts > and few other minor things for compilation). > > However compiled driver & library actually never worked and all I got was > usually black screen. It's probably hard to judge if the problem is kernel > driver (using usually quite fresh vanilla git tree) or Xorg from Fedora > Rawhide can't work with some slightly older libdrm/intel. It probably not > reasonable to spend time to detect where exactly is problem - all I want to > point out is, that some internal API must changed significantly so while I > could usually boot with 2 year old kernel, I cannot use few months old > drm&intel driver. > > And back to this issue - if this variable is used a lot by other projects, > than this commit is probably ok - though looks ugly. But if there is just one > project which uses it, than it's probably better to break API and keep it > clean and use same variable for C & C++ programs. For bisecting, just hold libdrm at the new version and bisect in 2d, unless your initial test of old+old vs old+new of each component points at libdrm (in which case, hold the 2d driver old and bisect across libdrm). New drivers do require new symbols, but libdrm is API and ABI stable, exactly so that people can bisect successfully. pgpcqoVUWDGRH.pgp Description: PGP signature -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
