dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 28426] New: hardware cursor corruption with radeon+kms
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28426 Summary: hardware cursor corruption with radeon+kms Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: maillist(a)pnpitalia.it please see also bug #19215, may be related After some days the xorg server is up and running the cursor get corrupted. This is a kde4 desktop on a dual 1920x1080 screen powered by an ATI Radeon HD 4670. The bug happens often, having played a game like Aquaria (in windowed mode) help a lot, but it does not guarantees an immediate trigger. This time xorg was up and running for about four days (not totally sure), yesterday I've played with the already mentioned Aquaria. please feel free to request further information since I don't know where to start I've tried to be broad on covering the system information, here is what the attached zip file contain: - "cursor-gimp.jpeg" cursor as it should be (after a reboot) - "VGA-0-cursor-broken.jpeg" cursor as it's shown in the left monitor VGA-0 - "DVI-0-cursor-broken.jpeg" cursor as it's shown in the right monitor DVI-0 - "Xorg.0.log" log for the server on vt7 whit kde running - "Xorg.1.log" tentative to start another X server on vt8, it also had a broken cursor - "xorg.conf" "SWcursor" is commented out - "radeontool--debug-regs.log" `radeontool debug regs` output - "installed-software.log" radeon and x11 related software installed on this pc - "modinfo-radeon.log" `modinfo radeon` output - "lsmod.log" `lsmod` output - "xrandr--verbose.log" `xrandr -q --verbose` output - "lspci-vvv.log" `lspci -vvv` output - "lshw.log" `lshw` output, it's an hardware lister - "dmesg.log" `dmesg` output -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 28373] New: DRM lockup on X startup
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28373 Summary: DRM lockup on X startup Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: mattias.nissler(a)gmx.de I've tried to get the DRM/KMS stuff going on my Ati X800 Pro R423 PCIE. Here are theversions I've tried with: drm-2.6.git at 9e67e5b Merge tag 'v2.6.34' into drm-radeon-testing libdrm git at 607e228 Enable silent automake rules. xf86-video-ati git at 428125c r3xx-r5xx: enable color tiling by default on KMS mesa git at b202c78 r300: fix blits for textures of width/height greater than 2048 on r5xx The kernel boots up just fine and the text console switches to the drm framebuffer device as expected. When starting the X server, the VT switch occurs, but the display just freezes (presumably at modesetting time). The kernel doesn't crash, but graphics become unusable (no VT switching, modesetting whatsoever possible from the command line). In my kernel logs, I see the following: Jun 3 17:51:06 kea kernel: INFO: task X:3245 blocked for more than 120 seconds. Jun 3 17:51:06 kea kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 3 17:51:06 kea kernel: X D ffffffff8175c820 0 3245 3243 0x00400004 Jun 3 17:51:06 kea kernel: ffff88007c515788 0000000000000046 0000000000000000 ffffffff00000000 Jun 3 17:51:06 kea kernel: ffff88007c515fd8 ffff88007c515fd8 ffff88007a961040 0000000000014000 Jun 3 17:51:06 kea kernel: ffff88007c515fd8 0000000000014000 ffffffff81a67020 ffff88007a961040 Jun 3 17:51:06 kea kernel: Call Trace: Jun 3 17:51:06 kea kernel: [<ffffffff81743bc3>] mutex_lock_nested+0x183/0x370 Jun 3 17:51:06 kea kernel: [<ffffffff813bfb5b>] ? radeon_ring_lock+0x2b/0x60 Jun 3 17:51:06 kea kernel: [<ffffffff813bfb5b>] radeon_ring_lock+0x2b/0x60 Jun 3 17:51:06 kea kernel: [<ffffffff8174519b>] ? _raw_write_unlock_irqrestore+0x3b/0x60 Jun 3 17:51:06 kea kernel: [<ffffffff813d36a1>] r300_gpu_is_lockup+0x71/0x190 Jun 3 17:51:06 kea kernel: [<ffffffff813a8aee>] radeon_fence_wait+0x32e/0x3c0 Jun 3 17:51:06 kea kernel: [<ffffffff810926b0>] ? autoremove_wake_function+0x0/0x40 Jun 3 17:51:06 kea kernel: [<ffffffff813a82a5>] ? radeon_fence_emit+0xe5/0x130 Jun 3 17:51:06 kea kernel: [<ffffffff814074c8>] radeon_pm_set_clocks+0x428/0x670 Jun 3 17:51:06 kea kernel: [<ffffffff81407742>] ? radeon_pm_compute_clocks+0x32/0x280 Jun 3 17:51:06 kea kernel: [<ffffffff814077f0>] radeon_pm_compute_clocks+0xe0/0x280 Jun 3 17:51:06 kea kernel: [<ffffffff813ac42c>] radeon_crtc_mode_fixup+0x2c/0x50 Jun 3 17:51:06 kea kernel: [<ffffffff81358958>] drm_crtc_helper_set_mode+0x138/0x3c0 Jun 3 17:51:06 kea kernel: [<ffffffff81359657>] drm_crtc_helper_set_config+0x837/0x8e0 Jun 3 17:51:06 kea kernel: [<ffffffff8136be00>] drm_mode_setcrtc+0x170/0x3c0 Jun 3 17:51:06 kea kernel: [<ffffffff8135e79a>] drm_ioctl+0x33a/0x4c0 Jun 3 17:51:06 kea kernel: [<ffffffff8136bc90>] ? drm_mode_setcrtc+0x0/0x3c0 Jun 3 17:51:06 kea kernel: [<ffffffff810973de>] ? up_read+0x1e/0x40 Jun 3 17:51:06 kea kernel: [<ffffffff81114a98>] vfs_ioctl+0x38/0xd0 Jun 3 17:51:06 kea kernel: [<ffffffff81114c7a>] do_vfs_ioctl+0x8a/0x640 Jun 3 17:51:06 kea kernel: [<ffffffff8111527a>] sys_ioctl+0x4a/0x80 Jun 3 17:51:06 kea kernel: [<ffffffff81032f42>] system_call_fastpath+0x16/0x1b Jun 3 17:51:06 kea kernel: 6 locks held by X/3245: Jun 3 17:51:06 kea kernel: #0: (&dev->mode_config.mutex){......}, at: [<ffffffff8136bcca>] drm_mode_setcrtc+0x3a/0x3c0 Jun 3 17:51:06 kea kernel: #1: (&rdev->pm.mutex){......}, at: [<ffffffff81407742>] radeon_pm_compute_clocks+0x32/0x280 Jun 3 17:51:06 kea kernel: #2: (&dev->struct_mutex){......}, at: [<ffffffff814070d1>] radeon_pm_set_clocks+0x31/0x670 Jun 3 17:51:06 kea kernel: #3: (&rdev->vram_mutex){......}, at: [<ffffffff814070db>] radeon_pm_set_clocks+0x3b/0x670 Jun 3 17:51:06 kea kernel: #4: (&rdev->cp.mutex){......}, at: [<ffffffff814070e5>] radeon_pm_set_clocks+0x45/0x670 Jun 3 17:51:06 kea kernel: #5: (&rdev->cp.mutex){......}, at: [<ffffffff813bfb5b>] radeon_ring_lock+0x2b/0x60 I've had a quick look at the code, seems radeon_ring_lock cannot acquire the lock, since it's already taken by radeon_pm_set_clocks? But maybe the 300_gpu_is_lockup call indicates there's a bigger problem occurring before? You see, I don't know the code ;) If you want me to try patches, different versions etc. I'm happy to help. Keep up the good work! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 28217] New: Black screen and crash on r600 with radeon module not loaded
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28217 Summary: Black screen and crash on r600 with radeon module not loaded Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: kilobug(a)freesurf.fr If the radeon kernel module isn't loaded, starting Xorg gives me a black screen and I need to do a hard reboot (reset). I've a HD4650 radeon, so it's r600 driver. This didn't happen with my old Radeon 9250, but I did upgrade X and kernel at the same time (to have r600 support), so not sure if it's related to hardware or to more recent X. I'm using Debian GNU/Linux with 64-bits kernel and 32-bits userland and : - xserver-xorg-video-radeon version 1:6.13.0-2 - xserver-xorg version 1:7.5+6 - libgl1-mesa-dri version 7.8.1-1 - kernel 2.6.33-2-amd64 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 13

[Bug 28069] New: maniadrive - smooth play with LIBGL_ALWAYS_INDIRECT=true, (almost) unplayable otherwise
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28069 Summary: maniadrive - smooth play with LIBGL_ALWAYS_INDIRECT=true, (almost) unplayable otherwise Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: pcpa(a)mandriva.com.br The problem described in https://bugs.freedesktop.org/show_bug.cgi?id=28002 actually also happens with the ati driver. Just that with the ati driver, it is less visible (the car position jumps less), but with LIBGL_ALWAYS_INDIRECT it also becomes a lot more smooth. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 28030] New: HDMI audio does not work with HD4200 IGP but does work with radeonhd
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=28030 Summary: HDMI audio does not work with HD4200 IGP but does work with radeonhd Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: seanius(a)debian.org I've been using the radeonhd driver for some time due to the fact that it supports audio over HDMI, so i can have everything routed to my HDMI receiver over one cable. I read that recently the radeon driver was supposed to offer support for this as well, and since it's otherwise a better driver i thought i'd give it a go. unfortunately, i am greeted with the sound of silence, and not hte simon and garfunkel version (which would equally be surprising, but...). if i switch my xorg config to use the radonhd driver audio still works on this machine, but without running x or with x running and radeon driver loaded, nothing. alsa sees the devices, and I can play to it via sox, but I don't hear anything. here's some info that might be useful, please let me know if you need anything else. lspci: 01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200] 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] kernel: Linux htpc 2.6.34-rc6 #1 SMP Fri Apr 30 18:58:36 CEST 2010 x86_64 GNU/Linux dmesg | grep -i radeon: [ 28.209345] [drm] radeon kernel modesetting enabled. [ 28.209617] radeon 0000:01:05.0: setting latency timer to 64 [ 28.216607] [drm] radeon: power management initialized [ 28.216623] radeon 0000:01:05.0: VRAM: 256M 0xC0000000 - 0xCFFFFFFF (256M used) [ 28.216630] radeon 0000:01:05.0: GTT: 512M 0xA0000000 - 0xBFFFFFFF [ 28.219976] [drm] radeon: 256M of VRAM memory ready [ 28.219980] [drm] radeon: 512M of GTT memory ready. [ 28.220065] [drm] radeon: irq initialized. [ 28.221688] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 28.273545] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 28.280034] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 28.320843] [drm] radeon: ib pool ready. [ 28.321217] [drm] Radeon Display Connectors [ 28.650110] fb0: radeondrmfb frame buffer device [ 28.650115] [drm] Initialized radeon 2.3.0 20080528 for 0000:01:05.0 on minor 0 kernel options: options radeon modeset=1 audio=1 (also tried with modeset=0) aplay -L: null Discard all samples (playback) or generate zero samples (capture) front:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog Front speakers surround40:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=SB,DEV=0 HDA ATI SB, ALC889A Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=SB,DEV=0 HDA ATI SB, ALC889A Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=HDMI HDA ATI HDMI, ATI HDMI HDMI Audio Output lsmod: Module Size Used by nls_utf8 1240 0 nls_cp437 5825 0 btrfs 375614 0 zlib_deflate 17634 1 btrfs crc32c 2584 1 libcrc32c 986 1 btrfs ufs 57094 0 qnx4 6345 0 hfsplus 64974 0 hfs 37094 0 minix 21517 0 ntfs 158011 0 vfat 7832 0 msdos 6265 0 fat 39741 2 vfat,msdos jfs 137530 0 xfs 736926 0 exportfs 3066 1 xfs reiserfs 193312 0 ext4 273039 0 jbd2 61357 1 ext4 crc16 1311 1 ext4 ext2 53155 0 cryptd 5422 0 aes_x86_64 7380 2 aes_generic 26090 1 aes_x86_64 ppdev 5299 0 lp 8078 0 parport 25598 2 ppdev,lp acpi_cpufreq 5673 0 cpufreq_stats 2649 0 cpufreq_conservative 7886 0 cpufreq_powersave 926 0 cpufreq_userspace 1904 0 binfmt_misc 6446 1 uinput 6654 1 fuse 50041 5 loop 12218 0 joydev 8344 0 snd_hda_codec_idt 44345 1 arc4 1314 2 snd_hda_intel 19402 1 ecb 1865 2 snd_hda_codec 64924 2 snd_hda_codec_idt,snd_hda_intel snd_hwdep 5468 1 snd_hda_codec snd_pcm_oss 31980 0 snd_mixer_oss 12687 1 snd_pcm_oss pcmcia 29415 0 snd_pcm 61553 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi 4454 0 snd_rawmidi 15945 1 snd_seq_midi snd_seq_midi_event 4738 1 snd_seq_midi iwl3945 51692 0 snd_seq 42374 2 snd_seq_midi,snd_seq_midi_event iwlcore 84262 1 iwl3945 nouveau 366209 3 snd_timer 16288 2 snd_pcm,snd_seq snd_seq_device 4515 3 snd_seq_midi,snd_rawmidi,snd_seq mac80211 148124 2 iwl3945,iwlcore dell_wmi 2579 0 ttm 39325 1 nouveau drm_kms_helper 19995 1 nouveau cfg80211 114001 3 iwl3945,iwlcore,mac80211 yenta_socket 18897 0 rsrc_nonstatic 6873 1 yenta_socket psmouse 44995 0 dell_laptop 5040 0 video 18189 0 tpm_tis 7349 0 tpm 9843 1 tpm_tis tpm_bios 4629 1 tpm dcdbas 4992 1 dell_laptop evdev 7426 24 pcmcia_core 11412 3 pcmcia,yenta_socket,rsrc_nonstatic serio_raw 3726 0 snd 46659 13 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device wmi 5443 1 dell_wmi i2c_i801 7822 0 rfkill 13314 3 cfg80211,dell_laptop output 1732 1 video battery 5518 0 ac 2200 0 drm 143465 5 nouveau,ttm,drm_kms_helper i2c_algo_bit 4297 1 nouveau rng_core 3166 0 processor 28802 3 acpi_cpufreq i2c_core 15804 5 nouveau,drm_kms_helper,i2c_i801,drm,i2c_algo_bit button 4706 1 nouveau soundcore 4726 1 snd snd_page_alloc 6097 2 snd_hda_intel,snd_pcm intel_agp 25635 0 dm_snapshot 24498 0 dm_mirror 11626 0 dm_region_hash 6640 1 dm_mirror dm_log 7645 2 dm_mirror,dm_region_hash ext3 105714 3 jbd 36203 1 ext3 mbcache 5152 3 ext4,ext2,ext3 dm_mod 54789 9 dm_snapshot,dm_mirror,dm_log raid1 18423 0 md_mod 76980 1 raid1 sg 19029 0 sr_mod 12711 0 sd_mod 30243 5 crc_t10dif 1284 1 sd_mod cdrom 29769 1 sr_mod ata_generic 3023 0 ata_piix 20556 5 libata 132830 2 ata_generic,ata_piix uhci_hcd 18218 0 scsi_mod 124407 4 sg,sr_mod,sd_mod,libata tg3 104200 0 ide_pci_generic 2828 0 ehci_hcd 29920 0 libphy 14000 1 tg3 ide_core 76791 1 ide_pci_generic usbcore 124669 3 uhci_hcd,ehci_hcd nls_base 6369 9 nls_utf8,nls_cp437,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore thermal 12046 0 thermal_sys 12036 3 video,processor,thermal -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 27609] New: Regression: r600 CS checker rejects narrow FBO renderbuffers.
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=27609 Summary: Regression: r600 CS checker rejects narrow FBO renderbuffers. Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nbowler(a)draconx.ca Created an attachment (id=34944) --> (https://bugs.freedesktop.org/attachment.cgi?id=34944) Full kernel log including failure message. The R600 CS checker recently merged into the mainline kernel breaks rendering to FBOs with renderbuffers of width <= 48. The height does not matter. Attempting to run such a program terminates with drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info. and in dmesg: radeon 0000:03:00.0: r600_cs_track_validate_cb:198 cb pitch (32 x 4 = 128) invalid radeon 0000:03:00.0: r600_packet3_check:1109 invalid cmd stream 514 [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Please see the test case attached to bug 27590 for a program which triggers this issue. The program works on Linux 2.6.33 and with the software rasterizer. The problem is reproducible with both mesa 7.8.1 and git master, against latest Linus git kernel. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 51042] New: Turning off connector polling in drm_kms_helper inhibits HDMI hot plug
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=51042 Bug #: 51042 Summary: Turning off connector polling in drm_kms_helper inhibits HDMI hot plug Classification: Unclassified Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: dargllun(a)gmail.com When turning off connector polling in drm_kms_helper using the poll=N module parameter HDMI hot plugging does not work anymore. Quoting Alex Deucher: See this discussion for details and some logs: http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/22107 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 71083] New: (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=71083 Priority: medium Bug ID: 71083 Assignee: dri-devel(a)lists.freedesktop.org Summary: (struct drm_encoder_helper_funcs)->mode_set not re-called after display (and EDID) change Severity: normal Classification: Unclassified OS: All Reporter: zajec5(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: DRM/other Product: DRI I use my DCE5 Barts (HD69xx) with AV-receiver Onkyo TX-SR605 and one of the following displays: 1) TV Sony Bravia KDL-52X3500 2) Projector Epson EH-TW6100 My problem is that when I change display connected to the Onkyo's output EDID changes, but drm doesn't call mode_set as long as I use the same resolution. To force drm to call mode_set I've to change resolution (xrandr --output HDMI-0 --mode X) and then swtich back to the mode I want. While the display seems to be working fine without that mode_set call, the audio engine doesn't. As part of the modesetting handler we read ELD-related info from EDID and write it to the audio engine of the GPU. Without this happening I can't play correctly audio (because also sees info about previous device, not the current one). I think mode_set should be called every time EDID changes. Is that right? In case someone's curious: 1) EDID with Onkyo + Sony TV: 00ffffffffffff003dcb610700000000 0011010380a05a780a0dc9a057479827 12484c21080081800101010101010101 010101010101023a801871382d40582c 450040846300001e011d007251d01e20 6e28550040846300001e000000fc0054 582d53523630350a20202020000000fd 00303e0e460f000a2020202020200185 02034c705c1f03041213051420071610 15110206010f1e0b1a191d0e0a242625 2335097f070f7f071707503f06c05706 005f7e01671e00834f00006c030c0012 00b82dc000000000e3050301023a80d0 72382d40102c458040846300001e011d 00bc52d01e20b828554040846300001e 00000000000000000000000000000078 2) EDID with Onkyo + Epson projector: 00ffffffffffff004ca333d000000000 0c150104952616780aa0558d515a962a 1c505400000001010101010101010101 0101010101016a4d80a07038fc413020 36007ed710000018d49a80a07038fc41 302036007ed710000038000000fc0053 414d53554e470a2020202020000000fc 00313733485430322d4330310a200035 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 69675] New: audio broken in 24Hz/24p since 3.11 (regression)
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=69675 Priority: medium Bug ID: 69675 Assignee: dri-devel(a)lists.freedesktop.org Summary: audio broken in 24Hz/24p since 3.11 (regression) Severity: normal Classification: Unclassified OS: All Reporter: pierre-bugzilla(a)ossman.eu Hardware: Other Status: NEW Version: unspecified Component: DRM/other Product: DRI Bug 64503 is back again, but this time it isn't a case of PEBKAC. Instead it is commit e6e792092e816bea0797995c886fb057c91d4546 that breaks things. With 3.10 I have just this 24p mode in Xorg: [ 47.361] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) With 3.11 I have two: Xorg.0.log:[ 56.189] (II) RADEON(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Xorg.0.log:[ 56.189] (II) RADEON(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) And although the second one gives me an image, audio is royally screwed up. Please revert, or at least give us a knob to disable these extra modes. -- You are receiving this mail because: You are the assignee for the bug.

1 56

[Bug 80628] New: The way KMS works doesn't support HDMI/DP well
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=80628 Priority: medium Bug ID: 80628 Assignee: dri-devel(a)lists.freedesktop.org Summary: The way KMS works doesn't support HDMI/DP well Severity: enhancement Classification: Unclassified OS: Linux (All) Reporter: tom.ty89(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI If the machine has no monitor attached at all before boot, KMS couldn't probe the monitor and make it goes into native resolution afterwards. This issue is not very obvious when DVI/VGA are the only connectors available because of their mechanism. When it comes to HDMI/DP, the monitor is considered disconnected when it's powered off. Then the issue become annoying, while we have to make sure that one monitor is connected and switched on before boot. Moreover, display managers have to be started manually under such situation after you turn on your monitor. Not even all DM can start X in optimal resolution without some "xrandr hack" By the way, it's funny that if you got one attached, you can power on others later without getting into the problem. Just that I am not sure if it's because all my monitors have the same optimal resolution. -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014