dri-devel October 2011

dri-devel@lists.freedesktop.org

82 participants
530 discussions

[Bug 41732] New: [radeon] KMS (and X.org) detect wrong outputs
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=41732 Summary: [radeon] KMS (and X.org) detect wrong outputs Product: Drivers Version: 2.5 Kernel Version: 3.1-rc3 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: niels_ole(a)salscheider-online.de Regression: No On my notebook, 6520G (mobile A6 APU), KMS detects a screen on VGA-0 although there is no attached. Because of that it chooses a lower resolution than the internal display's native resolution. The selected mode causes the internal display to flicker, though. In dmesg, I can see the following: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E3E6 (len 2585, WS 4, PS 4) @ 0xEAD0 Other issues I have with this : - xrandr reports a size of 0x0 inches for the internal display - the internal display uses only 6 bit/pixel and there seems to be no way to enable dithering - the brightness controls do not work although there is a sysfs acpi interface that gets updated - the display does not come back on after standby These issues may be unrelated and I will create further bug reports if so, but maybe they give a hint concerning this issue. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 11

[Bug 40622] New: [radeon] - kms wrong resolution mode used after backlight on/off switch
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=40622 Summary: [radeon] - kms wrong resolution mode used after backlight on/off switch Product: Drivers Version: 2.5 Kernel Version: 3.0 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: tkrah(a)fachschaft.imn.htwk-leipzig.de Regression: Yes Hi, updated to recent 3.0 kernel (oneiric ubuntu build package) and got some behaviour i would not expect. Got a Samsung P35 Notebook - pressing my "backlight" Key does give this in dmesg: keyboard: can't emulate rawmode for keycode 240 On and Off, both a mesage. The native resolution is 1400x1050 of my LVDS Panel. [ 23.577259] [drm] Panel ID String: Samsung LTN150P1-L02 [ 23.577264] [drm] Panel Size 1400x1050 But after pressing backlight twice (off+on) my screen resolution does change to 1600x1024 - afaik not supported, at least it is not mentioned in Xorg.0.log for detected valid panel Modelines. But it does use this mode after backlight switch: (II) RADEON(0): Allocate new frame buffer 1600x1024 stride 1600 I wonder why? However i am forced to switch my resolution back everytime - don't know if its good for the panel to use this resolution (because i don't know if it will blast my panel away i'll set prio to high - if this won't going to happen please set it back to normal ;-) ). Bug or Feature? Both (message and resolution change) did not happen with 2.6.32.x before, so i guess its a regression, is it? Tell me if you need more input or kernel testing. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 7

[Bug 40562] New: Shutting down X/KDE sometimes leads to kernel crash on kernel-3.0.1-rc1 with radeon/kms
by bugzilla-daemon＠bugzilla.kernel.org 30 Aug '12

30 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=40562 Summary: Shutting down X/KDE sometimes leads to kernel crash on kernel-3.0.1-rc1 with radeon/kms Product: Drivers Version: 2.5 Kernel Version: 3.0.1-rc1 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: bugzilla.kernel.org(a)boris64.net Regression: No Created an attachment (id=67542) --> (https://bugzilla.kernel.org/attachment.cgi?id=67542) foto of kernel panic My pc now crashed about the 2nd time (dunno how to reproduce, yet) when trying to restart. It looks like X dies and takes the whole kernel down. Please check the attached picture which is a foto of the kernel panic. I hope it is useful as it's somehow blurred. Used software: -kernel-3.0.1-rc1 -xorg-server-1.10.3 -radeon/kms -xf86-video-ati/mesa/libdrm from git Need more logs/infos? Please tell me what else would be required. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 5

[Bug 38792] New: Radeon HD 5750: GPU lockup CP stall while browsing in Firefox
by bugzilla-daemon＠bugzilla.kernel.org 24 Aug '12

24 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=38792 Summary: Radeon HD 5750: GPU lockup CP stall while browsing in Firefox Product: Drivers Version: 2.5 Kernel Version: 3.0-rc5 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: jlp.bugs(a)gmail.com Regression: No I was browsing with Firefox 5.0 (in KDE 4.6.4 with desktop effects enabled) and when I clicked on a button to return to the previous page the screen suddenly all got black and when it came back the mouse pointer was not visible but the windows under it reacted to mouse-over. I had to switch to bob-X virtual console and then back to restore everything. Well I also immediately checked dmesg and this is what was in there: radeon 0000:01:00.0: GPU lockup CP stall for more than 131410msec ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:267 radeon_fence_wait+0x2f1/0x330 [radeon]() Hardware name: System Product Name GPU lockup (waiting for 0x00A08F1B last fence id 0x00A08F18) Modules linked in: w83627ehf hwmon_vid coretemp snd_seq snd_seq_device usb_storage radeon snd_hda_codec_hdmi snd_hda_codec_realtek ttm drm_kms_helper drm snd_hda_intel snd_hda_codec hwmon i2c_i801 snd_pcm snd_timer xhci_hcd backlight ehci_hcd i2c_algo_bit r8169 mii snd snd_page_alloc Pid: 2162, comm: X Not tainted 3.0.0-rc5-dirty #9 Call Trace: [<ffffffffa0167b00>] ? radeon_fence_wait+0x2f0/0x330 [radeon] [<ffffffff81038e9b>] ? warn_slowpath_common+0x7b/0xc0 [<ffffffff81038f95>] ? warn_slowpath_fmt+0x45/0x50 [<ffffffffa0167b01>] ? radeon_fence_wait+0x2f1/0x330 [radeon] [<ffffffff81054dd0>] ? add_wait_queue+0x60/0x60 [<ffffffffa007cb0a>] ? ttm_bo_wait+0xba/0x1c0 [ttm] [<ffffffffa007f12b>] ? ttm_bo_move_buffer+0x7b/0x180 [ttm] [<ffffffffa007d642>] ? ttm_bo_reserve_locked+0xc2/0x160 [ttm] [<ffffffffa018311e>] ? radeon_cs_parser_relocs+0x5e/0x250 [radeon] [<ffffffffa0082b65>] ? ttm_eu_list_ref_sub+0x35/0x50 [ttm] [<ffffffffa007f2c5>] ? ttm_bo_validate+0x95/0x120 [ttm] [<ffffffffa01698c3>] ? radeon_bo_list_validate+0x73/0xd0 [radeon] [<ffffffffa018377c>] ? radeon_cs_ioctl+0xac/0x210 [radeon] [<ffffffffa00cb21c>] ? drm_ioctl+0x39c/0x460 [drm] [<ffffffffa01836d0>] ? radeon_cs_finish_pages+0xa0/0xa0 [radeon] [<ffffffff81022589>] ? do_page_fault+0x189/0x420 [<ffffffff810b726d>] ? mmap_region+0x27d/0x520 [<ffffffff810ecc0e>] ? do_vfs_ioctl+0x8e/0x4f0 [<ffffffff810ed0b9>] ? sys_ioctl+0x49/0x80 [<ffffffff8143aa7b>] ? system_call_fastpath+0x16/0x1b ---[ end trace edd1ae68ff942751 ]--- radeon 0000:01:00.0: GPU softreset radeon 0000:01:00.0: GRBM_STATUS=0xA0003828 radeon 0000:01:00.0: GRBM_STATUS_SE0=0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1=0x00000007 radeon 0000:01:00.0: SRBM_STATUS=0x200000C0 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: GRBM_STATUS=0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0=0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1=0x00000007 radeon 0000:01:00.0: SRBM_STATUS=0x200000C0 radeon 0000:01:00.0: GPU reset succeed radeon 0000:01:00.0: WB enabled [drm] ring test succeeded in 1 usecs [drm] ib test succeeded in 1 usecs [drm] force priority to high [drm] force priority to high [drm] force priority to high [drm] force priority to high Other software: Mesa 7.12-devel (git-3fccc14) libdrm from git xorg-server 1.10.99.901 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 13

[Bug 38622] New: [radeon cayman regresion] artefacts on screen
by bugzilla-daemon＠bugzilla.kernel.org 24 Aug '12

24 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=38622 Summary: [radeon cayman regresion] artefacts on screen Product: Drivers Version: 2.5 Kernel Version: 3.0.0-rc3 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: kernellist(a)neutrinus.com Regression: Yes When running kernel versions => 3.0.0-rc3 there are a lot of artifacts on screen when runing xorg. Kernel 3.0.0-rc2 and olders were producing clean image, right now there are artifacts on screen, making any fonts/graphics unreadable. 3.0.0-rc[3-5] are affected. It fully reproducible: just run kde :) Its happends everytime when I switch 3.0.0-rc2 kernel to something newer. I'm using debian AMD64 sid+experimental, kernel images from experimental. I'm using xorg "radeon" driver. Mesa: 7.11~0-2. There are no Ops, no strange logs in dmesg... CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GPU: AMD Radeon HD 6970 with six fullhd monitors (4x DP and 2x DVI) Modules: hmac 12923 0 - Live 0xffffffffa054c000 nls_utf8 12456 0 - Live 0xffffffffa0509000 cifs 242524 0 - Live 0xffffffffa050f000 parport_pc 22395 0 - Live 0xffffffffa0461000 ppdev 12763 0 - Live 0xffffffffa0436000 lp 17270 0 - Live 0xffffffffa0446000 parport 31929 3 parport_pc,ppdev,lp, Live 0xffffffffa0500000 fuse 62334 1 - Live 0xffffffffa04aa000 nfsd 260601 2 - Live 0xffffffffa04bf000 nfs 259361 0 - Live 0xffffffffa0469000 lockd 71503 2 nfsd,nfs, Live 0xffffffffa044e000 fscache 36663 2 cifs,nfs, Live 0xffffffffa043c000 auth_rpcgss 37204 2 nfsd,nfs, Live 0xffffffffa042b000 nfs_acl 12511 2 nfsd,nfs, Live 0xffffffffa03ec000 sunrpc 172969 6 nfsd,nfs,lockd,auth_rpcgss,nfs_acl, Live 0xffffffffa03ff000 max6650 12900 0 - Live 0xffffffffa03fa000 coretemp 12939 0 - Live 0xffffffffa03f5000 hwmon_vid 12388 0 - Live 0xffffffffa03e0000 loop 22711 0 - Live 0xffffffffa03e5000 sha256_generic 16797 2 - Live 0xffffffffa0387000 aesni_intel 50644 24 - Live 0xffffffffa03d2000 cryptd 14549 9 aesni_intel, Live 0xffffffffa00db000 aes_x86_64 16796 1 aesni_intel, Live 0xffffffffa034d000 aes_generic 33026 2 aesni_intel,aes_x86_64, Live 0xffffffffa0343000 cbc 12755 0 - Live 0xffffffffa017f000 dm_crypt 22611 1 - Live 0xffffffffa0380000 dm_mod 63164 3 dm_crypt, Live 0xffffffffa0332000 snd_hda_codec_hdmi 26321 1 - Live 0xffffffffa0289000 snd_hda_codec_realtek 278027 1 - Live 0xffffffffa038d000 snd_usb_audio 84855 1 - Live 0xffffffffa036a000 snd_usbmidi_lib 23475 1 snd_usb_audio, Live 0xffffffffa0363000 uvcvideo 57791 0 - Live 0xffffffffa0353000 snd_seq_midi 12848 0 - Live 0xffffffffa00ef000 videodev 66713 1 uvcvideo, Live 0xffffffffa0240000 snd_seq_midi_event 13316 1 snd_seq_midi, Live 0xffffffffa01f8000 media 18184 2 uvcvideo,videodev, Live 0xffffffffa023a000 v4l2_compat_ioctl32 16567 1 videodev, Live 0xffffffffa0234000 snd_rawmidi 23297 2 snd_usbmidi_lib,snd_seq_midi, Live 0xffffffffa01c4000 joydev 17262 0 - Live 0xffffffffa0185000 radeon 648169 3 - Live 0xffffffffa0292000 ttm 52979 1 radeon, Live 0xffffffffa027b000 drm_kms_helper 27216 1 radeon, Live 0xffffffffa01f0000 drm 163231 5 radeon,ttm,drm_kms_helper, Live 0xffffffffa0252000 snd_hda_intel 26140 5 - Live 0xffffffffa01d0000 snd_hda_codec 72699 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel, Live 0xffffffffa01ac000 evdev 17558 13 - Live 0xffffffffa0179000 i2c_algo_bit 12850 1 radeon, Live 0xffffffffa01a3000 snd_hwdep 13186 2 snd_usb_audio,snd_hda_codec, Live 0xffffffffa018d000 snd_pcm 68104 5 snd_hda_codec_hdmi,snd_usb_audio,snd_hda_intel,snd_hda_codec, Live 0xffffffffa0222000 snd_seq 45208 2 snd_seq_midi,snd_seq_midi_event, Live 0xffffffffa0215000 snd_timer 22581 3 snd_pcm,snd_seq, Live 0xffffffffa0199000 snd_seq_device 13137 3 snd_seq_midi,snd_rawmidi,snd_seq, Live 0xffffffffa0210000 i2c_i801 16870 0 - Live 0xffffffffa01ea000 snd 52823 22 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device, Live 0xffffffffa0202000 i2c_core 23909 7 max6650,videodev,radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_i801, Live 0xffffffffa01e3000 pcspkr 12579 0 - Live 0xffffffffa01fd000 serio_raw 12846 0 - Live 0xffffffffa01bf000 soundcore 13152 1 snd, Live 0xffffffffa01de000 snd_page_alloc 13043 2 snd_hda_intel,snd_pcm, Live 0xffffffffa01d9000 power_supply 13475 1 radeon, Live 0xffffffffa01cb000 processor 27942 8 - Live 0xffffffffa0171000 button 12930 0 - Live 0xffffffffa0169000 thermal_sys 17949 1 processor, Live 0xffffffffa0193000 ext4 318236 4 - Live 0xffffffffa011a000 mbcache 13066 1 ext4, Live 0xffffffffa003d000 jbd2 62709 1 ext4, Live 0xffffffffa0109000 crc16 12343 1 ext4, Live 0xffffffffa0060000 sg 25985 0 - Live 0xffffffffa00e7000 sr_mod 21811 0 - Live 0xffffffffa00e0000 cdrom 35093 1 sr_mod, Live 0xffffffffa00ff000 sd_mod 36259 7 - Live 0xffffffffa0096000 crc_t10dif 12348 1 sd_mod, Live 0xffffffffa002d000 usbhid 40516 0 - Live 0xffffffffa00f4000 hid 73172 1 usbhid, Live 0xffffffffa00c8000 ahci 25089 4 - Live 0xffffffffa008e000 libahci 22767 1 ahci, Live 0xffffffffa0026000 libata 149043 2 ahci,libahci, Live 0xffffffffa00a2000 scsi_mod 162442 4 sg,sr_mod,sd_mod,libata, Live 0xffffffffa0065000 xhci_hcd 68199 0 - Live 0xffffffffa004e000 r8169 42411 0 - Live 0xffffffffa0042000 mii 12675 1 r8169, Live 0xffffffffa0021000 ehci_hcd 40090 0 - Live 0xffffffffa0032000 usbcore 128338 7 snd_usb_audio,snd_usbmidi_lib,uvcvideo,usbhid,xhci_hcd,ehci_hcd, Live 0xffffffffa0000000 lspci -vvv (part of) 01:00.0 VGA compatible controller: ATI Technologies Inc Cayman XT [AMD Radeon HD 6900 Series] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 03bc 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, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 52 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fbec0000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at ee00 [size=256] [virtual] Expansion ROM at fbe00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon If there is any more information needed I would be more than happy to provide it. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 15

[Bug 38382] New: radeon: wait for empty RBBM fifo failed
by bugzilla-daemon＠bugzilla.kernel.org 24 Aug '12

24 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=38382 Summary: radeon: wait for empty RBBM fifo failed Product: Drivers Version: 2.5 Kernel Version: 3.0.0-rc4 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: stavallo(a)unina.it Regression: No Created an attachment (id=63662) --> (https://bugzilla.kernel.org/attachment.cgi?id=63662) dmesg with pageflipping disabled My system is affected by frequent oopses that makes it unusable. There are no problems when the X server is not launched, but when it starts (with KDM) something bad soon happens. If I don't login into KDM, it may freeze after few minutes. If I login, an oops happen after few minutes. Unfortunately I can't tell exactly when this behavior started to happen, but somewhere between 2.6.39 and 2.6.39.1. Yesterday I compiled the kernel from git but no luck. I tried to disable pageflipping (as suggested in bug #32402) but the oops happened again. WIth pageflipping disabled, I managed to ssh into the machine and get dmesg and Xorg.log (attached). Unfortunately, I didn't manage to ssh into the machine with pageflipping enabled. I have a Radeon X300 card and I am using mesa git from 20110616, libdrm 2.4.25 and Xorg 1.10.2. If I need to test anything, please let me know, thanks. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 7

[Bug 37502] New: Kernels oops display in X leaves screen garbled
by bugzilla-daemon＠bugzilla.kernel.org 24 Aug '12

24 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=37502 Summary: Kernels oops display in X leaves screen garbled Product: Drivers Version: 2.5 Kernel Version: 3.0.0-rc3 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: edwintorok(a)gmail.com Regression: No Created an attachment (id=62102) --> (https://bugzilla.kernel.org/attachment.cgi?id=62102) dmesg I got some BUG_ONs/warnings from the kernel, and every time it happened I ended up with a garbled screen (see attached photo). Switching to a virtual console, and back to X (twice) restored my desktop. I don't know if the kernel is trying to switch to a text console to display the Oops, or if it tries to display the oops on the graphical console, but apparently its not working well. The first time I get an Oops after a reboot I get to see the Oops text on a black background (and my mouse cursor, which makes me believe this is the graphical KMS console), but everything after that just leaves me with a garbled screen. The oops displayed is: https://lkml.org/lkml/2011/6/15/50 I don't know if this is a regression or not, I rarely get Oopses, and last time I got a panic message I was able to see it (although I was in X at the time), but then so can I for the 1st Oops message. My graphics card is: 01:00.0 VGA compatible controller: ATI Technologies Inc RV730 PRO [Radeon HD 4650] I use KMS, Xorg 1.10.2, and Mesa 7.10.2-3. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 3

[Bug 37362] New: vgaswitcheroo : switch from intel to ati impossible
by bugzilla-daemon＠bugzilla.kernel.org 24 Aug '12

24 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=37362 Summary: vgaswitcheroo : switch from intel to ati impossible Product: Drivers Version: 2.5 Kernel Version: 2.6.38 and 2.6.39 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: pub(a)ackak.fr Regression: No Created an attachment (id=61732) --> (https://bugzilla.kernel.org/attachment.cgi?id=61732) lspci -vv When i use the command "echo DIS > /sys/kernel/debug/vgaswitcheroo/switch", the screen of my laptop (HP Pavilion dv7) freeze. Impossible to switch to another tty and if i write a command in the console nothing appears. If i write "echo IGD > /sys/kernel/debug/vgaswitcheroo/swith", the screen refreshes and i can use normally my laptop. I can't disable the intel card in the bios. the result of the command "cat /sys/kernel/debug/vgaswitcheroo/swith" : 0:DIS: :Pwr:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0 The log (/var/log/messages) when i want switch to ATI : Jun 12 22:11:17 ackak-hp kernel: [ 133.005729] fbcon: Remapping primary device, fb0, to tty 1-63 Jun 12 22:11:17 ackak-hp kernel: [ 133.005976] i915: switched off -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 12

[Bug 38280] New: [bisected] regression : etqw tree/water wrong rendering
by bugzilla-daemon＠freedesktop.org 23 Aug '12

23 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=38280 Summary: [bisected] regression : etqw tree/water wrong rendering Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: pelloux(a)gmail.com Created an attachment (id=47923) --> (https://bugs.freedesktop.org/attachment.cgi?id=47923) incorrect rendering commit 9346d895e7ff6c1f01b46513694542026ffba5cc broke tree and water rendering in etqw (Island map) See attached screenshots. I'm using r600g + HD4850 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 34212] New: radeon: 3650 AGP lockup on radeon.ko load
by bugzilla-daemon＠bugzilla.kernel.org 23 Aug '12

23 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=34212 Summary: radeon: 3650 AGP lockup on radeon.ko load Product: Drivers Version: 2.5 Kernel Version: 2.6.39-rc5 + drm-next 1794d25 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: detringj(a)gmail.com Regression: No Hardware: 2x 1.7GHz Xeon (Foster) on a SuperMicro P4DC6 workstation board RadeonHD 3650 AGP (built by VisionTek) Radeon board has 1x VGA, 1x DVI, and 1x S-Video ports. A TV is attached to the S-Video port through a generic S-Video multiplexer, the others are not connected. TV is a US/NTSC standard definition CRT. System boots into a VGA text console with no problem. When attempting "modprobe radeon", the system switches to graphics mode, then prints a backtrace on the framebuffer and hangs (no keyboard response, no ping, ssh dies). A mostly-solid stripe of green pixel noise can be seen across the bottom 2 or 3 scanlines of the TV. The setup works when using the fglrx driver. An NV31+nouveau arrangement also seems to work, so I don't think the motherboard is at fault. This isn't really a "regression" per-se, as it has never worked in any vendor- or self-compiled kernel I've tried (since about July 2010). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 2

← Newer
1
...
24
25
26
27
28
29
30
...
53
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2011