https://bugs.freedesktop.org/show_bug.cgi?id=81689
Priority: medium
Bug ID: 81689
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Black screen in info-beamer
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: sa(a)whiz.se
Hardware: x86 (IA32)
Status: NEW
Version: 10.2
Component: Drivers/Gallium/r600
Product: Mesa
The multimedia presenter info-beamer ( http://info-beamer.org/ ) just renders a
black screen with r600g.
It's working fine with software rendering and on Intel hardware.
Not a regression, or at least present in Mesa 9.2.
I've made an apitrace of one of the beamer demos:
https://my.owndrive.com/public.php?service=files&t=cef11b335be2741058363783…
The trace renders correctly but gives a lot of errors, so this might be a bug
in info-beamer:
0 87813 glGetUniformLocation(program = 0, name = "Color") = -1
87813: warning: glGetError(glGetUniformLocation) = GL_INVALID_VALUE
87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION
in glReadBuffer(buffer=0x405)
87872: glDebugOutputCallback: High severity API error 1, GL_INVALID_OPERATION
in glDrawBuffer(buffer=0x405)
0 87872 glPopAttrib()
87872: warning: glGetError(glPopAttrib) = GL_INVALID_OPERATION
87882: glDebugOutputCallback: High severity API error 1, GL_INVALID_VALUE in
glGetUniformLocation
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 7.4.0
-- xserver: 1.16.0
-- mesa: 10.2.4
-- drm: 2.4.54
-- kernel: 3.13
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=42941
Summary: Resume from suspend to memory leaves display blank on
Lenovo Ideapad U455
Product: Power Management
Version: 2.5
Kernel Version: 3.3.0-rc7+
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Hibernation/Suspend
AssignedTo: power-management_other(a)kernel-bugs.osdl.org
ReportedBy: e-mail(a)date.by
CC: drivers_video-dri(a)kernel-bugs.osdl.org
Regression: No
Created an attachment (id=72610)
--> (https://bugzilla.kernel.org/attachment.cgi?id=72610)
dmesg output
Hardware: Lenovo Ideapad U455 laptop with AMD Athlon Neo processor and two
video cards: Radeon HD 3200 and Radeon HD 4500.
Description: when system resumes from suspend to memory (`echo mem >
/sys/power/state`) system resumes fine as i can log into it via ssh and display
turns on, but the display stays black showing nothing. However it's possible to
make display show a picture by switching video cards with vga_switcheroo.
Steps to reproduce attached dmesg log (see my comments below):
[1]# mount -t debugfs none /sys/kernel/debug
[2]# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:01:05.0
1:DIS: :Pwr:0000:02:00.0
[3]# echo mem > /sys/power/state
[4]# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:01:05.0
1:DIS: :Pwr:0000:02:00.0
[5]# echo DIS > /sys/kernel/debug/vgaswitcheroo/switch
[6]# echo IGD > /sys/kernel/debug/vgaswitcheroo/switch
[7]# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:01:05.0
1:DIS: :Off:0000:02:00.0
[8]# echo mem > /sys/power/state
[9]# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:01:05.0
1:DIS: :Off:0000:02:00.0
[10]# echo DIS > /sys/kernel/debug/vgaswitcheroo/switch
[11]# echo IGD > /sys/kernel/debug/vgaswitcheroo/switch
Comments:
[2] This shows the state of the video cards before suspend.
[3] Suspend worked fine, but display was blank after resume.
[4] This shows the state of the video cards after resume.
[5] That command made display to show the picture.
[7] This shows the state of the video cards before second suspend, when only
IGD card was active.
[8] Suspend worked fine, but resume took a lot of time:
PM: resume devices took 82.256 seconds
------------[ cut here ]------------
WARNING: at kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()
Hardware name: 20046
Component: resume devices, time: 82256
Modules linked in: btusb bluetooth snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 ext2
mbcache cpufreq_ondemand powernow_k8 freq_table mperf lp parport_pc parport
fuse radeon brcmsmac ttm mac80211 drm_kms_helper joydev snd_hda_codec_hdmi
ohci_hcd snd_hda_codec_conexant brcmutil ssb snd_hda_intel drm mmc_core
snd_hda_codec sp5100_tco cfg80211 sg ideapad_laptop agpgart psmouse atl1c
thermal snd_hwdep processor video crc8 thermal_sys pcmcia snd_pcm snd_timer
cordic rtc_cmos pcmcia_core shpchp sparse_keymap evdev ehci_hcd i2c_piix4 snd
k8temp i2c_algo_bit bcma rfkill i2c_core serio_raw soundcore snd_page_alloc
battery ac hwmon button loop btrfs [last unloaded: pcmcia_rsrc]
Pid: 1834, comm: bash Not tainted 3.3.0-rc7+ #36
Call Trace:
[<ffffffff8103fe3f>] warn_slowpath_common+0x7f/0xc0
[<ffffffff8103ff36>] warn_slowpath_fmt+0x46/0x50
[<ffffffff8107fc96>] suspend_test_finish+0x86/0x90
[<ffffffff8107f9a1>] suspend_devices_and_enter+0x101/0x1e0
[<ffffffff8107fb51>] enter_state+0xd1/0x110
[<ffffffff8107e4c7>] state_store+0xb7/0x130
[<ffffffff812623cf>] kobj_attr_store+0xf/0x30
[<ffffffff811b0d22>] sysfs_write_file+0xf2/0x180
[<ffffffff81149793>] vfs_write+0xb3/0x180
[<ffffffff81149aba>] sys_write+0x4a/0x90
[<ffffffff8153f829>] system_call_fastpath+0x16/0x1b
---[ end trace 6802c35567ce73fa ]---
PM: Finishing wakeup.
[9] This shows the state of the video cards after second resume.
[10] That command turned display off and that's what appeared in dmesg output:
radeon: switched on
radeon 0000:02:00.0: enabling device (0000 -> 0003)
radeon 0000:02:00.0: Wait for MC idle timedout !
radeon 0000:02:00.0: Wait for MC idle timedout !
[drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
radeon 0000:02:00.0: WB enabled
[drm] fence driver on ring 0 use gpu addr 0x20000c00 and cpu addr
0xffff8800a4523c00
[drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8500)=0xFFFFFFFF)
[drm:rv770_resume] *ERROR* r600 startup failed on resume
fbcon: Remapping primary device, fb1, to tty 1-63
radeon: switched off
[11] That command made display to show the picture.
Notes:
* I have read Documentation/power/basic-pm-debugging.txt and made all described
tests and all of them were successful.
* I have tried different quirks with `pm-suspend --quirk-*`, but none of them
helped.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=50325
Bug #: 50325
Summary: Glyphy bad render on r600g (software render is fine)
Classification: Unclassified
Product: Mesa
Version: 8.0
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: edwin+mesa(a)etorok.net
Created attachment 62078
--> https://bugs.freedesktop.org/attachment.cgi?id=62078
apitrace (cf. https://github.com/apitrace/apitrace/tree/1.0)
I just tried Glyphy on r600g and the output is very bad.
Don't know if its Glyphy bug or Mesa bug, but if I force software rendering in
Mesa then I do see the output.
Attached screenshots of bad (r600g) and good (software render).
The bad render was obtained by:
demo/glyphy-demo
The good one:
LIBGL_ALWAYS_SOFTWARE=1 demo/glyphy-demo
I tested on:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 8.0.2
OpenGL shading language version string: 1.20
I'll try to test on mesa git later to see if its still an issue there.
Also attached is a an apitrace, and the bad render can be reproduced with:
build/glretrace lt-glyphy-demo.trace
The good render (initialization a bit slow, but works):
LIBGL_ALWAYS_SOFTWARE=1 build/glretrace lt-glyphy-demo.trace
The source code for Glyphy can be found here:
https://code.google.com/p/glyphy/source/checkout
--
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=50338
Bug #: 50338
Summary: r600g: EE r600_shader.c:140 r600_pipe_shader_create -
translation from TGSI failed !
Classification: Unclassified
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: edwin+mesa(a)etorok.net
Created attachment 62087
--> https://bugs.freedesktop.org/attachment.cgi?id=62087
R600_DUMP_SHADERS=1 output
Trying to reproduce bug #50325 on Mesa git caused this error:
EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !
Bug can be reproduced by one of these:
build/glretrace lt-glyphy-demo.trace
demo/glyphy-demo
I get the translation failed error both with R600_LLVM=0, and R600_LLVM=1.
I've attached the R600_DUMP_SHADERS=1 output.
glretrace is from https://github.com/apitrace/apitrace/tree/1.0
and glyphy is from https://code.google.com/p/glyphy/source/checkout
lt-glypy-demo.trace is here:
https://bugs.freedesktop.org/attachment.cgi?id=62078
git version of Mesa:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 8.1-devel (git-35f302d)
OpenGL shading language version string: 1.30
OpenGL extensions:
Built with (on Debian unstable):
./configure --with-dri-drivers= --with-gallium-drivers=r600,swrast
--enable-glx-tls --enable-gallium-llvm LLVM_CONFIG=/usr/bin/llvm-config-3.1
--
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=89831
Bug ID: 89831
Summary: [r600] r600_asm.c:310:assign_alu_units: Assertion `0'
failed.
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: HACKhalotwo(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 114743
--> https://bugs.freedesktop.org/attachment.cgi?id=114743&action=edit
Backtrace from wine
When I try to load a world in Space Engineers with mesa (64 bit and 32 bit),
wine, and the Radeon open source driver compiled with Gallium Nine support, and
mesa compiled with the --enable-debug flag, it crashes with the supplied
backtrace.
pastebin of the TSGI code it spits into the console:
http://pastebin.com/6eeuDs9A
full console logs:
https://drive.google.com/file/d/0Bx0XCc8l_ekmZU04djJkN1FfOWM/view?usp=shari…
Without using the Gallium Nine driver, the game works as anticipated.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=47201
Bug #: 47201
Summary: TGSI source register with absolute negative modifier
does not work correctly
Classification: Unclassified
Product: Mesa
Version: 8.0
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: llyzs(a)163.com
Recently I found a TGSI fragment shader does not render correctly with r600
driver and I further identified the issue down to instructions in this form:
CMP TEMP[0].yz, -|TEMP[1].xxxx|, TEMP[2].xxxx, CONST[0].xyxw
If I covert all those instructions to the equivalents:
ABS TEMP[5], TEMP[1].xxxx
CMP TEMP[0].yz, -TEMP[5], TEMP[2].xxxx, CONST[0].xyxw
It then works fine. However, the original instructions work just fine with
nouveau and swrast driver, so it should be a r600 bug. Any clue on this issue?
--
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=36072
Summary: celestia causes kernel oops when allocation a lot of
memory (for textures)
Product: Drivers
Version: 2.5
Kernel Version: 2.6.38
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: acelists(a)atlas.sk
Regression: Yes
The celestia program often allocates a lot of memory (like 1.5GB on my 2GB
machine with 3GB swap) for its textures. I don't know where it stores them
(probably not Video memory), but it seems in system RAM, because swap is used
much. Sometimes when this happens the kernel crashes. After that I can only
sync and reboot the machine with alt-sysrq commands. I have only noticed this
with kernel 2.6.38.x, not before. I was using the OSS ati driver 6.14.1, with
mesa 7.10.2. All including the kernel seft compiled (for AMD fam10h CPU). I do
not understand the first line of the log. Where can I increase the vmalloc
size. Is the on the kernel command line? But it should not crash the kernel in
any case, just the program.
Here is the kernel log:
May 19 21:26:52 coolbox kernel: vmap allocation for size 178982912 failed: use
vmalloc=<size> to increase size.
May 19 21:26:52 coolbox kernel: BUG: unable to handle kernel paging request at
b892a45d
May 19 21:26:52 coolbox kernel: IP: [<f9696a50>] ttm_mem_io_lock+0x0/0x20 [ttm]
May 19 21:26:52 coolbox kernel: *pde = 00000000
May 19 21:26:52 coolbox kernel: Oops: 0000 [#1] PREEMPT SMP
May 19 21:26:52 coolbox kernel: last sysfs file:
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:01/ATK0110:00/hwmon/hwmon0/fan3_input
May 19 21:26:52 coolbox kernel: Modules linked in: fbcon font bitblit
softcursor radeon ttm drm_kms_helper drm agpgart fb fbdev autofs4 cfbcopyarea
cfbimgblt cfbfillrect nf_conntrack_ftp xt_tcpudp xt_owner xt_multiport
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT ipt_LOG
iptable_filter ip_tables x_tables asus_atk0110 snd_seq_oss snd_seq_midi_event
snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss cpufreq_conservative
cpufreq_ondemand psmouse pcspkr cx88_blackbird firmware_class cx2341x cx8802
tuner_simple tuner_types tda9887 tda8290 tea5767 tuner cx8800 cx88xx rc_core
i2c_algo_bit tveeprom v4l2_common videodev btcx_risc videobuf_dma_sg
videobuf_core forcedeth snd_hda_codec_via snd_hda_intel snd_hda_codec snd_pcm
snd_timer snd soundcore snd_page_alloc i2c_nforce2 i2c_core ext4 mbcache jbd2
crc16 usbhid powernow_k8 processor mperf ohci_hcd ehci_hcd usbcore fuse
May 19 21:26:52 coolbox kernel:
May 19 21:26:52 coolbox kernel: Pid: 25014, comm: celestia Not tainted 2.6.38.6
#57 System manufacturer System Product Name/M2N68
May 19 21:26:52 coolbox kernel: EIP: 0060:[<f9696a50>] EFLAGS: 00010246 CPU: 3
May 19 21:26:52 coolbox kernel: EIP is at ttm_mem_io_lock+0x0/0x20 [ttm]
May 19 21:26:52 coolbox kernel: EAX: b892a420 EBX: d03cfc28 ECX: 00000000 EDX:
00000000
May 19 21:26:52 coolbox kernel: ESI: f519a40c EDI: b892a420 EBP: d03cfd48 ESP:
d03cfbf0
May 19 21:26:52 coolbox kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
May 19 21:26:52 coolbox kernel: Process celestia (pid: 25014, ti=d03ce000
task=f06fb830 task.ti=d03ce000)
May 19 21:26:52 coolbox kernel: Stack:
May 19 21:26:52 coolbox kernel: f9696f25 d03cfc28 d03cfd80 d03cfc98 f96970e2
f29e2c2c fffffff4 00040002
May 19 21:26:52 coolbox kernel: f519a40c f9695c16 f29e2c64 f50135c0 00040001
00000002 00000002 d03cfcd0
May 19 21:26:52 coolbox kernel: f519a45c f519a40c 00000000 af3e5000 d03cfc48
d03cfc9c f519a40c d03cfc98
May 19 21:26:52 coolbox kernel: Call Trace:
May 19 21:26:52 coolbox kernel: [<f9696f25>] ? ttm_mem_reg_iounmap+0x35/0x70
[ttm]
May 19 21:26:52 coolbox kernel: [<f96970e2>] ? ttm_bo_move_memcpy+0x182/0x310
[ttm]
May 19 21:26:52 coolbox kernel: [<f9695c16>] ? ttm_bo_mem_space+0x306/0x3a0
[ttm]
May 19 21:26:52 coolbox kernel: [<f97f4fb0>] ? radeon_bo_move+0xe0/0x330
[radeon]
May 19 21:26:52 coolbox kernel: [<f96944d5>] ?
ttm_bo_reserve_locked+0xa5/0x120 [ttm]
May 19 21:26:52 coolbox kernel: [<f97f4ed0>] ? radeon_bo_move+0x0/0x330
[radeon]
May 19 21:26:52 coolbox kernel: [<f9694e15>] ?
ttm_bo_handle_move_mem+0x135/0x330 [ttm]
May 19 21:26:52 coolbox kernel: [<f9695ddc>] ? ttm_bo_move_buffer+0x12c/0x140
[ttm]
May 19 21:26:52 coolbox kernel: [<f9695e86>] ? ttm_bo_validate+0x96/0x120
[ttm]
May 19 21:26:52 coolbox kernel: [<f97f5f5a>] ?
radeon_bo_list_validate+0x5a/0xe0 [radeon]
May 19 21:26:52 coolbox kernel: [<f980d14c>] ? radeon_cs_ioctl+0x7c/0x1a0
[radeon]
May 19 21:26:52 coolbox kernel: [<c0206466>] ?
prepare_for_delete_or_cut+0x3c6/0x650
May 19 21:26:52 coolbox kernel: [<f96b3b51>] ? drm_ioctl+0x191/0x380 [drm]
May 19 21:26:52 coolbox kernel: [<c0206466>] ?
prepare_for_delete_or_cut+0x3c6/0x650
May 19 21:26:52 coolbox kernel: [<f980d0d0>] ? radeon_cs_ioctl+0x0/0x1a0
[radeon]
May 19 21:26:52 coolbox kernel: [<c018ccf8>] ? handle_pte_fault+0x88/0x630
May 19 21:26:52 coolbox kernel: [<c026006f>] ? prio_tree_insert+0x12f/0x250
May 19 21:26:52 coolbox kernel: [<f96b39c0>] ? drm_ioctl+0x0/0x380 [drm]
May 19 21:26:52 coolbox kernel: [<c01b1edf>] ? do_vfs_ioctl+0x7f/0x590
May 19 21:26:52 coolbox kernel: [<c011df35>] ? do_page_fault+0x185/0x3a0
May 19 21:26:52 coolbox kernel: [<c0190bae>] ? mmap_region+0x16e/0x440
May 19 21:26:52 coolbox kernel: [<c01351d5>] ? irq_exit+0x35/0x70
May 19 21:26:52 coolbox kernel: [<c01b242d>] ? sys_ioctl+0x3d/0x70
May 19 21:26:52 coolbox kernel: [<c0206466>] ?
prepare_for_delete_or_cut+0x3c6/0x650
May 19 21:26:52 coolbox kernel: [<c03979a1>] ? syscall_call+0x7/0xb
May 19 21:26:52 coolbox kernel: [<c0206466>] ?
prepare_for_delete_or_cut+0x3c6/0x650
May 19 21:26:52 coolbox kernel: [<c0206466>] ?
prepare_for_delete_or_cut+0x3c6/0x650
May 19 21:26:52 coolbox kernel: Code: 00 00 00 66 31 c0 83 c8 01 89 47 50 eb 9f
90 8d 74 26 00 89 da 89 f0 e8 0f cb ff ff 85 c0 74 a4 89 c5 eb b2 8d b4 26 00
00 00 00 <80> 78 3d 00 74 03 31 c0 c3 84 d2 75 0a 83 c0 28 e8 db f5 cf c6
May 19 21:26:52 coolbox kernel: EIP: [<f9696a50>] ttm_mem_io_lock+0x0/0x20
[ttm] SS:ESP 0068:d03cfbf0
May 19 21:26:52 coolbox kernel: CR2: 00000000b892a45d
May 19 21:26:52 coolbox kernel: ---[ end trace 70c887d309b00b2d ]---
May 19 21:27:18 coolbox kernel: Emergency Sync complete
May 19 21:27:21 coolbox kernel: Emergency Sync complete
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=37474
Summary: Segmentation Fault in glCopyTexSubImage2D
Product: Mesa
Version: 7.10
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r128
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: asguthrie(a)gmail.com
Created an attachment (id=47011)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47011)
stracktrace
projectM-pulseaudio seg faults whilst calling glCopyTextSubImage2D.
stacktrace attached.
patch inspired by bug #27652 also attached.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.