https://bugs.freedesktop.org/show_bug.cgi?id=31246
Summary: Reproducible hangs on piglit tests with 5850
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: temp9476-freedesktop(a)yahoo.no
Ignoring the occasional random hang, I have found that the following tests
create a lockup of the system every time:
glsl-fs-main-return
glsl-vs-main-return
glsl-max-varyings
glsl-fs-vec4-indexing-temp-dst-in-nested-loop-combined
glsl-vs-vec4-indexing-temp-dst-in-nested-loop-combined
How would I go about debugging these further? It would be very nice if the
piglit tests would at least fail, not hang...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=30693
Summary: [R600c KWin 4.5.2] Blur does not work with RV670 (it
works with RV710)
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: darkbasic4(a)gmail.com
Created an attachment (id=39272)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39272)
Blur not working
Hi, with 2.6.36-rc7|drm-radeon-testing and latest graphic stack snapshot kwin's
4.5.2 blur effect does not work. I have an HD3870, but someone else told me it
works with RV710 (http://www.phoronix.com/forums/showthread.php?t=26221).
I attached a screenshot.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=31423
Summary: Stars in Celestia misrendered
Product: Mesa
Version: 7.9
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bio_tube(a)yahoo.com
Created an attachment (id=40076)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40076)
Misrenderd stars from Celestia
All the stars in Celestia are rendered as yellow dots(zooming in on one gives
something that looks correct, however); r600g gets the colors right(if not the
shape, but that's another bug), so this seems to be a driver issue. I've tested
it on a Radeon HD 3450 and the bug was originally reported on #radeon today by
djzn, who tested with an HD 3200 and HD 2600XT and got the same result.
Celestia mentions loading a number of ARB shaders, but with no error and gives
no indication of problems(output below).
Initializing ARB vertex programs . . .
Loading ARB vertex program: shaders/diffuse_arb.vp
Loading ARB vertex program: shaders/specular_arb.vp
Loading ARB vertex program: shaders/haze_arb.vp
Loading ARB vertex program: shaders/bumpdiffuse_arb.vp
Loading ARB vertex program: shaders/bumphaze_arb.vp
Loading ARB vertex program: shaders/shadowtex_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff_arb.vp
Loading ARB vertex program: shaders/rings_arb.vp
Loading ARB vertex program: shaders/ringshadow_arb.vp
Loading ARB vertex program: shaders/night_arb.vp
Loading ARB vertex program: shaders/glossmap_arb.vp
Loading ARB vertex program: shaders/diffuse2_arb.vp
Loading ARB vertex program: shaders/haze2_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff2_arb.vp
Loading ARB vertex program: shaders/specular2_arb.vp
Loading ARB vertex program: shaders/night2_arb.vp
Loading ARB vertex program: shaders/star_arb.vp
Loading ARB vertex program: shaders/multishadow_arb.vp
Loading ARB vertex program: shaders/texphong_arb.vp
Loading ARB vertex program: shaders/texphong_alpha_arb.vp
Loading ARB vertex program: shaders/ell_galaxy_arb.vp
All ARB vertex programs loaded successfully.
render path: 8
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=29691
Summary: Lightsmark isnt rendering textures
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: schmaker(a)ifrit.eu
Hello there,
Lightsmark isnt rendering textures on R600 driver. I guess its some extension
missing or something. Screenshot is included.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=35838
Summary: Savage2 crashes when running Practice
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: kdekorte(a)yahoo.com
Install kernel from drm-radeon-testing, libdrm git, mesa git, ddx git as of
March 31, 2011
Run Savage2 64 bit
>From main screen, click Practice
While screen is loading application will crash with following backtrace
~/Savage2/savage2.bin
warning: The VAD has been replaced by a hack pending a complete rewrite
EE r600_pipe.c:343 r600_get_param - r600: unknown param 45
EE r600_pipe.c:343 r600_get_param - r600: unknown param 45
*** glibc detected *** /home/kdekorte/Savage2/savage2.bin: free(): invalid
pointer: 0x00000000099254d0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a34476d63]
/usr/lib64/dri/r600_dri.so(+0x123ebd)[0x7f80e94c5ebd]
Using git bisect, isolated crash to the following commit
89d81ab16c05818b290ed735c1343d3abde449bf is the first bad commit
commit 89d81ab16c05818b290ed735c1343d3abde449bf
Author: Ian Romanick <ian.d.romanick(a)intel.com>
Date: Tue Jan 25 10:41:20 2011 -0800
glsl: Calcluate Mesa state slots in front-end instead of back-end
This should be the last bit of infrastructure changes before
generating GLSL IR for assembly shaders.
This commit leaves some odd code formatting in ir_to_mesa and brw_fs.
This was done to minimize whitespace changes / reindentation in some
loops. The following commit will restore formatting sanity.
Reviewed-by: Eric Anholt <eric(a)anholt.net>
Reviewed-by: Chad Versace <chad.versace(a)intel.com>
:040000 040000 cad3ca6fb2a7b45cd21397a87f940da85102fcba
34a321443a5f0d58a5c15ea9330801c59a28c1f2 M src
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=31533
Summary: Black lines while scrolling on HD5850
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: temp9476-freedesktop(a)yahoo.no
When I scroll pages (example attached) there are partial or 1-2 lines of black
appearing on screen. The initial rendering of the page looks good, and if I
continue to scroll the area will look ok. I've not found a simple reproducible
case but it happens on any webpage big enough to scroll. Input boxes are
particularly badly affected, if I write beyond the size of an input box and
have to scoll it is almost always badly corrupted.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=31972
Summary: 2.6.38.1: radeon hd 6870: kms, hdmi, signal is correct
only for 1-2 seconds
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: arekm(a)maven.pl
Regression: No
Created an attachment (id=52182)
--> (https://bugzilla.kernel.org/attachment.cgi?id=52182)
dmesg with messages
I'm using 2.6.38.1 with radeon hd 6870
(http://www.gigabyte.com/products/product-page.aspx?pid=3615#ov) connected only
to toshiba regza tv with HDMI connector. Nothing else is connected.
After modprobe radeon KMS kicks in, resolution is changed and everything looks
fine for 1-2 seconds. Then signal is lost according to tv and there are tons
of:
"[drm:atom_dp_get_link_status] *ERROR* displayport link status failed", some
kworker eats 90% of cpu and fans go up.
dmesg 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.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=31892
Summary: Problems with nouveau on my HP laptop
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38-Linus-07088-gb973a3b
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: Larry.Finger(a)lwfinger.net
Regression: No
First of all, this is not a complaint. Using 2.6.38-gitX, my laptop works
correctly using the nouveau driver, at least for X. I previously tried it with
the 2.6.37 kernel in openSUSE 11.4. At that point, nothing worked. I
congratulate you on your improvements.
My hardware is given by "sudo lspci -vvv" as
00:12.0 VGA compatible controller: nVidia Corporation C67 [GeForce 7150M /
nForce 630M] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 30d6
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 22
Region 0: Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at f0000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at c0000000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Kernel driver in use: nouveau
The probllems are as follows:
(1) My logs are spammed with lots of
[drm] nouveau 0000:00:12.0: Load detected on output B
There are also the occasional
[drm] nouveau 0000:00:12.0: Setting dpms mode 0 on lvds encoder (output 0)
[drm] nouveau 0000:00:12.0: Calling LVDS script 2:
[drm] nouveau 0000:00:12.0: 0xD6D8: Parsing digital output script table
[drm] nouveau 0000:00:12.0: Calling LVDS script 5:
[drm] nouveau 0000:00:12.0: 0xD676: Parsing digital output script table
[drm] nouveau 0000:00:12.0: Setting dpms mode 0 on TV encoder (output 2)
(2) The fonts in terminals are not really sharp. The screen resolution is set
to 1024x768, not the 1280x800 that is native for the screen. The xrandr command
shows
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
LVDS-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 303mm
x 190mm
1280x800 60.0 +
1024x768 59.9*
800x600 59.9
640x480 59.4
720x400 59.6
640x400 60.0
640x350 59.8
The inability to switch to the higher resolution is probably my fault.
The worst problem is that the boot sequence and virtual terminals 1-6 all have
the text covering only the right-hand 2/3 of the screen, and the characters are
not dense as they are with the framebuffer driver I get with the "nomodeset"
option on the GRUB boot line.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=31712
Summary: GPU lockup CP stall after resume from hibernation
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: psusi(a)cfl.rr.com
Regression: No
When resuming from hibernation on my Asus P8P67 Pro Core-i5 2500K system with a
Radeon 4850, I get a GPU lockup CP stall error, which leaves the display in a
corrupt state. The kernel attempts to reset the display to no avail, landing
back in the lockup again and again. A sysrq-K to kill X.org resolves the issue.
The issue seems to be tied to plymouth. If I boot without the quiet and splash
options when resuming, it resumes just fine. Suspend also works fine. This
occurs with the stock Ubuntu Maverick 2.6.35 based kernel, the Natty 2.6.38
based kernel, and the Linus 2.6.38 kernel ( last two built from source ). The
kernel log shows:
Mar 22 22:34:34 faldara kernel: [ 808.672904] ------------[ cut here
]------------
Mar 22 22:34:34 faldara kernel: [ 808.672926] WARNING: at
drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x40f/0x470
[radeon]()
Mar 22 22:34:34 faldara kernel: [ 808.672929] Hardware name: System Product
Name
Mar 22 22:34:34 faldara kernel: [ 808.672931] GPU lockup (waiting for
0x00003DCC last fence id 0x00003DC8)
Mar 22 22:34:34 faldara kernel: [ 808.672933] Modules linked in: nls_iso8859_1
nls_cp437 vfat fat binfmt_misc kvm_intel kvm parport_pc ppdev dm_crypt dm_zero
snd_hda_codec_hdmi snd_hda_codec_realtek snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq snd_hda_intel snd_hda_codec snd_hwdep ath3k btusb
snd_pcm bluetooth pkgtemp snd_timer eeepc_wmi snd_seq_device sparse_keymap snd
joydev psmouse soundcore snd_page_alloc serio_raw lp parport raid10 raid456
async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1
raid0 multipath linear btrfs zlib_deflate crc32c libcrc32c hid_microsoft usbhid
hid usb_storage radeon ttm firewire_ohci firewire_core drm_kms_helper crc_itu_t
drm i2c_algo_bit ahci e1000e libahci intel_agp intel_gtt [last unloaded:
xhci_hcd]
Mar 22 22:34:34 faldara kernel: [ 808.672984] Pid: 8039, comm: Xorg Tainted: G
W 2.6.38 #13
Mar 22 22:34:34 faldara kernel: [ 808.672986] Call Trace:
Mar 22 22:34:34 faldara kernel: [ 808.672994] [<ffffffff8105b37f>] ?
warn_slowpath_common+0x7f/0xc0
Mar 22 22:34:34 faldara kernel: [ 808.672998] [<ffffffff8105b476>] ?
warn_slowpath_fmt+0x46/0x50
Mar 22 22:34:34 faldara kernel: [ 808.673011] [<ffffffffa011965f>] ?
radeon_fence_wait+0x40f/0x470 [radeon]
Mar 22 22:34:34 faldara kernel: [ 808.673015] [<ffffffff8107cc70>] ?
autoremove_wake_function+0x0/0x40
Mar 22 22:34:34 faldara kernel: [ 808.673027] [<ffffffffa0119ec1>] ?
radeon_sync_obj_wait+0x11/0x20 [radeon]
Mar 22 22:34:34 faldara kernel: [ 808.673034] [<ffffffffa00c4173>] ?
ttm_bo_wait+0x103/0x1c0 [ttm]
Mar 22 22:34:34 faldara kernel: [ 808.673040] [<ffffffffa00c50c8>] ?
ttm_bo_list_ref_sub+0x28/0x30 [ttm]
Mar 22 22:34:34 faldara kernel: [ 808.673055] [<ffffffffa0132543>] ?
radeon_gem_wait_idle_ioctl+0x93/0x110 [radeon]
Mar 22 22:34:34 faldara kernel: [ 808.673063] [<ffffffffa005f42b>] ?
drm_ioctl+0x42b/0x4e0 [drm]
Mar 22 22:34:34 faldara kernel: [ 808.673076] [<ffffffffa01324b0>] ?
radeon_gem_wait_idle_ioctl+0x0/0x110 [radeon]
Mar 22 22:34:34 faldara kernel: [ 808.673080] [<ffffffff81016565>] ?
save_i387_xstate+0x165/0x230
Mar 22 22:34:34 faldara kernel: [ 808.673085] [<ffffffff81585825>] ?
_raw_spin_lock_irq+0x15/0x20
Mar 22 22:34:34 faldara kernel: [ 808.673089] [<ffffffff8100b392>] ?
do_signal+0x182/0x7d0
Mar 22 22:34:34 faldara kernel: [ 808.673093] [<ffffffff81157bf5>] ?
do_vfs_ioctl+0xa5/0x5a0
Mar 22 22:34:34 faldara kernel: [ 808.673096] [<ffffffff81158191>] ?
sys_ioctl+0xa1/0xb0
Mar 22 22:34:34 faldara kernel: [ 808.673100] [<ffffffff8100bfc2>] ?
system_call_fastpath+0x16/0x1b
Mar 22 22:34:34 faldara kernel: [ 808.673103] ---[ end trace 746c9b8991f7ff2a
]---
Mar 22 22:34:34 faldara kernel: [ 808.673111] [drm] Disabling audio support
Mar 22 22:34:34 faldara kernel: [ 808.689259] radeon 0000:01:00.0: GPU
softreset
Mar 22 22:34:34 faldara kernel: [ 808.689261] radeon 0000:01:00.0:
R_008010_GRBM_STATUS=0xA27034A4
Mar 22 22:34:34 faldara kernel: [ 808.689262] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2=0x00000102
Mar 22 22:34:34 faldara kernel: [ 808.689263] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS=0x200000C0
Mar 22 22:34:34 faldara kernel: [ 808.689269] radeon 0000:01:00.0:
R_008020_GRBM_SOFT_RESET=0x00007FEE
Mar 22 22:34:34 faldara kernel: [ 808.704257] radeon 0000:01:00.0:
R_008020_GRBM_SOFT_RESET=0x00000001
Mar 22 22:34:34 faldara kernel: [ 808.720245] radeon 0000:01:00.0:
R_008010_GRBM_STATUS=0x00003028
Mar 22 22:34:34 faldara kernel: [ 808.720246] radeon 0000:01:00.0:
R_008014_GRBM_STATUS2=0x00000002
Mar 22 22:34:34 faldara kernel: [ 808.720248] radeon 0000:01:00.0:
R_000E50_SRBM_STATUS=0x200000C0
Mar 22 22:34:34 faldara kernel: [ 808.721248] radeon 0000:01:00.0: GPU reset
succeed
Mar 22 22:34:34 faldara kernel: [ 808.755893] radeon 0000:01:00.0: WB enabled
Mar 22 22:34:34 faldara kernel: [ 808.801714] [drm] ring test succeeded in 1
usecs
Mar 22 22:34:34 faldara kernel: [ 808.801728] [drm] ib test succeeded in 1
usecs
Mar 22 22:34:34 faldara kernel: [ 808.801731] [drm] Enabling audio support
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel