http://bugzilla.kernel.org/show_bug.cgi?id=13249
--- Comment #15 from Werner Lemberg 2009-05-20 05:51:28 ---
Yes, plenty of them, like 0x307, 0x31B, or 0x305. None of them work.
However, I've now analyzed the situation more closely, and the change from good
to bad bisect just hides the rea
http://bugs.freedesktop.org/show_bug.cgi?id=20537
--- Comment #7 from [email protected] 2009-05-19 17:32:14 PST ---
I don't get the freeze with Mesa git from 2009/05/17, but I still have piglit
failures.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
---
http://bugs.freedesktop.org/show_bug.cgi?id=20537
--- Comment #8 from [email protected] 2009-05-19 17:34:34 PST ---
Created an attachment (id=26016)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26016)
Latest piglit main results file
--
Configure bugmail: http://bugs.freedesktop.
On Mon, 18 May 2009 11:56:16 +1000
Benjamin Herrenschmidt wrote:
> Currently, userspace fail to obtain the SAREA mapping (among others)
> because they pass SAREA_MAX to drmAddMap without aligning it to the
> page size. This breaks for example on PowerPC with 64K pages and
> radeon despite the ker
http://bugzilla.kernel.org/show_bug.cgi?id=13249
--- Comment #14 from Michal Januszewski 2009-05-19 22:19:27
---
(In reply to comment #13)
> and this is bad, using the configuration as described above:
>
> 4d31a2b74c6d063362ae10ce3be3e80d8713bf23 fbdev: ignore VESA modes if
> framebuffe
http://bugzilla.kernel.org/show_bug.cgi?id=13249
--- Comment #13 from Werner Lemberg 2009-05-19 22:02:28 ---
OK, I did bisecting as follows:
git bisect start v2.6.28 v2.6.27 -- drivers/video
and I found that this is good (this is, no black screen):
5ab4840968cd094586f65fce978e35c66d25
http://bugs.freedesktop.org/show_bug.cgi?id=21777
--- Comment #10 from Dan Nicholson 2009-05-19 11:20:44
PST ---
(In reply to comment #9)
> Not such a big deal, except that then ld doesn't process the DT_NEEDED entries
> in libdrm.so when linking dristat. Subsequently, it fails to add librt
http://bugs.freedesktop.org/show_bug.cgi?id=21777
--- Comment #9 from Dan Nicholson 2009-05-19 11:15:57
PST ---
(In reply to comment #8)
> After digging into this for an hour straight (without knowing about this
> bug...), my brain hurts a bit but I'd be interested in knowing who's to blame
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #8 from Brian Paul 2009-05-19
10:12:15 PST ---
Can you provide a direct link to the game so I can try it? I tried several of
the so-called "download" sites but I just get redirected to advertisements and
surveys and junk like th
http://bugs.freedesktop.org/show_bug.cgi?id=21791
--- Comment #2 from Alexey Shildyakov 2009-05-19
10:11:09 PST ---
I tried do it but it say:
break _mesa_problem
Function "_mesa_problem" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (_mesa_pro
http://bugs.freedesktop.org/show_bug.cgi?id=21816
--- Comment #3 from Maciej Cencora 2009-05-19 09:53:17
PST ---
(In reply to comment #2)
> Just FYI: I'm thinking of adding a -pedantic flag to glean and to make this
> sub-test (and some others) depend on that flag.
>
> The 0^0 case is unli
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #7 from Fabio 2009-05-19 09:29:24 PST ---
Created an attachment (id=26006)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26006)
second run under valgrind - crash with the mesa warning
--
Configure bugmail: http://bugs.fre
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #6 from Fabio 2009-05-19 09:28:26 PST ---
Created an attachment (id=26004)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26004)
first run under valgrind - crash but don't print the mesa warning
--
Configure bugmail: http:
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #5 from Fabio 2009-05-19 09:20:35 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > I've just checked in a Mesa change to print more info when this failure
> > occurs.
>
> I get this now:
>
> Mesa 7.6-devel implem
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #4 from Brian Paul 2009-05-19
09:18:58 PST ---
Another way to use gdb would be to start the game normally, then use 'ps -elf'
to find the PID for the game, then run gdb and use "attach " to attach gdb
to the running program.
Oth
http://bugs.freedesktop.org/show_bug.cgi?id=21816
--- Comment #2 from Brian Paul 2009-05-19
09:16:24 PST ---
Just FYI: I'm thinking of adding a -pedantic flag to glean and to make this
sub-test (and some others) depend on that flag.
The 0^0 case is unlikely to come up very often in practic
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #3 from Fabio 2009-05-19 09:09:12 PST ---
(In reply to comment #2)
> I've just checked in a Mesa change to print more info when this failure
> occurs.
I get this now:
Mesa 7.6-devel implementation error: invalid texture object
http://bugs.freedesktop.org/show_bug.cgi?id=21777
Rémi Cardona changed:
What|Removed |Added
CC||[email protected]
--- Comment #8 from Ré
http://bugs.freedesktop.org/show_bug.cgi?id=21816
--- Comment #1 from Maciej Cencora 2009-05-19 09:05:18
PST ---
Created an attachment (id=26003)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26003)
LIT 0^0 fix
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=ema
http://bugs.freedesktop.org/show_bug.cgi?id=21816
Summary: glean/vertProg1 test fails on some r300 and higher cards
Product: Mesa
Version: CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: m
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #2 from Brian Paul 2009-05-19
08:23:15 PST ---
I've just checked in a Mesa change to print more info when this failure occurs.
However, it would be great if you could also use gdb to print *tex in
valid_texture_object() when the
http://bugs.freedesktop.org/show_bug.cgi?id=21814
--- Comment #1 from Fabio 2009-05-19 08:01:22 PST ---
Created an attachment (id=26000)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26000)
full console output, including wine debug info and backtrace
--
Configure bugmail: http://bug
http://bugs.freedesktop.org/show_bug.cgi?id=21814
Summary: Mesa 7.6-devel implementation error: invalid texture
object Target value
Product: Mesa
Version: CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
http://bugs.freedesktop.org/show_bug.cgi?id=21400
Xavier Bestel changed:
What|Removed |Added
CC||[email protected]
--- Comment #6
http://bugs.freedesktop.org/show_bug.cgi?id=21400
--- Comment #5 from Maciej Cencora 2009-05-19 06:39:21
PST ---
I think the problem is radeon ddx and r300 dri driver interaction. I can easily
lock up the GPU by opening some 3d app in windowed mode and then doing some
stuff that heavily uti
http://bugs.freedesktop.org/show_bug.cgi?id=17099
Maciej Cencora changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=11384
Maciej Cencora changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=21756
Michel Dänzer changed:
What|Removed |Added
AssignedTo|dri-|mesa3d-
|[email protected]
http://bugs.freedesktop.org/show_bug.cgi?id=21770
--- Comment #1 from Jonathan Michalon 2009-05-19
00:50:11 PST ---
Created an attachment (id=25990)
--> (http://bugs.freedesktop.org/attachment.cgi?id=25990)
Xorg log without external screen
Here is the Xorg.0.log when starting X using KMS
http://bugs.freedesktop.org/show_bug.cgi?id=21756
--- Comment #5 from Tai Chi Minh Ralph Eastwood
2009-05-19 00:49:18 PST ---
Created an attachment (id=25989)
--> (http://bugs.freedesktop.org/attachment.cgi?id=25989)
A patch that corrects this bug.
Commit #63cde0ea0e2bc85005136c353c363777
Limit gem object mapping to below 4G. This fixes two issues:
1. remove limit that gem can't be enabled with PAE
2. in x64, shmem page can be higher than 4G, but for example, 945G GTT
mapping can only handle 4G mapping.
Am I missing anything?
Signed-off-by: Shaohua Li
---
drivers/gpu/drm/drm_gem
31 matches
Mail list logo
