dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 76559] New: screen corruption after going from VT to X
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=76559 Priority: medium Bug ID: 76559 Assignee: dri-devel(a)lists.freedesktop.org Summary: screen corruption after going from VT to X Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fabio.ped(a)libero.it Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I have a MacBook Pro with a RV530 with an external Philips 22" monitor connected (the notebook screen is disabled in X). After switching to VT and then coming back to X the screen is corrupted (like if every odd line has an offset). The same happens after suspend. A screenshot doesn't show the problem. I then usually change resolution with the Ubuntu tool (selecting a different resolution and then reapplying the previous one) and that restore the screen. Attached dmesg and Xorg log after the X -> VT -> X cycle. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 89871] nouveau diver in kernel 3.5.7 - 4.0.0-rc6 on PPC broken
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=89871 Bug ID: 89871 Summary: nouveau diver in kernel 3.5.7 - 4.0.0-rc6 on PPC broken Product: DRI Version: XOrg git Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: marvin(a)mydatex.cz Created attachment 114825 --> https://bugs.freedesktop.org/attachment.cgi?id=114825&action=edit dmesg output 3.19.3 I have PowerMac G5 machine with dual PPC. On Debian wheezy Xserver works. I upgrade to jessie with kernel 3.16 and Xserver stop working. I tested these kernels: vmlinux-3.4.106 vmlinux-3.5.7 vmlinux-3.7.9 vmlinux-3.8.13 vmlinux-3.14.37 vmlinux-3.17.8 vmlinux-3.18.10 vmlinux-3.19.3 vmlinux-4.0.0-rc6 It looks like that between 3.5.7 and 3.8.13 something change and DRM part of nouveau diver and driver stop working: I tested above kernels and problem is the same this dmesg output is from 3.19.3 [drm] Initialized drm 1.1.0 20060810 [ 10.548060] checking generic (98020000 10e000) vs hw (98000000 8000000) [ 10.548066] fb: switching to nouveaufb from OFfb NVDA,Displ [ 10.555299] Console: switching to colour dummy device 80x25 [ 10.557295] nouveau [ DEVICE][0000:0a:00.0] BOOT0 : 0x043200a4 [ 10.557310] nouveau [ DEVICE][0000:0a:00.0] Chipset: NV43 (NV43) [ 10.557316] nouveau [ DEVICE][0000:0a:00.0] Family : NV40 [ 10.557567] nouveau ![ VBIOS][0000:0a:00.0] unable to locate usable image [ 10.557575] nouveau E[ DEVICE][0000:0a:00.0] failed to create 0x10000001, -22 [ 10.557584] nouveau E[ DRM] failed to create 0x00000080, -22 [ 10.558138] nouveau: probe of 0000:0a:00.0 failed with error -22 With older kernel < 3.7.9 nouveau kernel part works but newer Xorg from jessie doesn't detect videocard. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 90079] drmSetMaster and drmDropMaster need root privileges
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=90079 Bug ID: 90079 Summary: drmSetMaster and drmDropMaster need root privileges Product: DRI Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libdrm Assignee: dri-devel(a)lists.freedesktop.org Reporter: g1938560(a)trbvm.com I run a small, user-space program that renders images in my virtual console with drmModeSetCRTC and family. I also support virtual terminal switching with ioctl() on stuff from linux/vt.h and some basic signal handling. Switching back to X server, however, just renders... nothing. Apparently I'm supposed to call drmDropMaster so that X server can pick up from there. I get -1 and errno is set to Permission Denied. When run as root, it works as expected. Is there any reason why these functions require root privileges? More importantly, is there any workaround for this so that my user space program can let X server draw its stuff once user switches back to X's virtual terminal? -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 103562] QXL driver disables IRQ and locks up when starting multihead weston, kernel 4.13
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=103562 Bug ID: 103562 Summary: QXL driver disables IRQ and locks up when starting multihead weston, kernel 4.13 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: vliaskovitis(a)suse.com Kernel 4.13.9 Weston 3.0.0-1.1 The qxl driver has its IRQ disabled (and the screen locks up not suprisingly) when trying to start weston on a VM with dual-head qxl setup. Video card config of vm: <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='2' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> Same dual-head setup works for gnome-shell/mutter though. So I am not sure if DRI/drm is the correct product/component. These are the kernel messages seen when weston is started: [ 66.719393] irq 11: nobody cared (try booting with the "irqpoll" option) [ 66.719396] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.13.9-1-default #1 [ 66.719397] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014 [ 66.719397] Call Trace: [ 66.719404] <IRQ> [ 66.719408] dump_stack+0x5c/0x85 [ 66.719423] __report_bad_irq+0x33/0xc0 [ 66.719424] note_interrupt+0x244/0x290 [ 66.719425] handle_irq_event_percpu+0x44/0x50 [ 66.719426] handle_irq_event+0x3a/0x60 [ 66.719428] handle_fasteoi_irq+0x8c/0x150 [ 66.719429] handle_irq+0x19/0x30 [ 66.719430] do_IRQ+0x41/0xc0 [ 66.719432] common_interrupt+0x8c/0x8c [ 66.719433] RIP: 0010:__do_softirq+0x6d/0x2da [ 66.719434] RSP: 0018:ffff98a4bfd03f80 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff2e [ 66.719435] RAX: 0000000000019ec0 RBX: 0000000000000000 RCX: 0000000000200042 [ 66.719436] RDX: 0000000000000047 RSI: 00000000bf861cc4 RDI: 00000000000006e0 [ 66.719436] RBP: 0000000000000002 R08: 00000023af4b5043 R09: 0000000000000020 [ 66.719437] R10: 0000000000000004 R11: 00000000000001d8 R12: 0000000000000000 [ 66.719437] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 66.719440] ? hrtimer_interrupt+0x116/0x1f0 [ 66.719442] irq_exit+0xae/0xb0 [ 66.719443] smp_apic_timer_interrupt+0x39/0x50 [ 66.719444] apic_timer_interrupt+0x8c/0xa0 [ 66.719445] </IRQ> [ 66.719446] RIP: 0010:native_safe_halt+0x2/0x10 [ 66.719447] RSP: 0018:ffffa6c0c0697ee0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff10 [ 66.719448] RAX: 0000000000000000 RBX: ffffffffb6d573e0 RCX: 0000000000000000 [ 66.719448] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 66.719448] RBP: 0000000000000002 R08: 00000023ad4d9a22 R09: ffff98a49a797f00 [ 66.719449] R10: 0000000000000000 R11: 000000dcc76ca5fb R12: 0000000000000000 [ 66.719449] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 66.719451] default_idle+0x1a/0x130 [ 66.719453] do_idle+0x167/0x1e0 [ 66.719454] cpu_startup_entry+0x5f/0x70 [ 66.719456] start_secondary+0x146/0x170 [ 66.719458] secondary_startup_64+0x9f/0xa0 [ 66.719459] handlers: [ 66.719466] [<ffffffffc01a2f60>] usb_hcd_irq [usbcore] [ 66.719468] [<ffffffffc0340870>] qxl_irq_handler [qxl] [ 66.719472] [<ffffffffc01a2f60>] usb_hcd_irq [usbcore] [ 66.719473] Disabling IRQ #11 [ 83.163774] [drm:drm_atomic_helper_swap_state [drm_kms_helper]] *ERROR* [CRTC:36:crtc-1] hw_done timed out [ 91.616818] ------------[ cut here ]------------ [ 91.616826] WARNING: CPU: 3 PID: 2176 at ../drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_commit_hw_done+0x8a/0x90 [drm_kms_helper] [ 91.616826] Modules linked in: nls_utf8 isofs fuse joydev uinput af_packet iscsi_ibft iscsi_boot_sysfs snd_hda_codec_generic crct10dif_pclmul xfs crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel snd_hda_codec libcrc32c snd_hda_core snd_hwdep snd_pcm ppdev snd_timer snd aesni_intel aes_x86_64 crypto_simd glue_helper cryptd parport_pc parport soundcore virtio_net button serio_raw virtio_balloon qemu_fw_cfg i2c_piix4 pcspkr btrfs xor sr_mod cdrom ata_generic raid6_pq floppy crc32c_intel virtio_blk ata_piix virtio_rng qxl uhci_hcd drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ehci_pci ehci_hcd drm usbcore sg [ 91.616846] CPU: 3 PID: 2176 Comm: kworker/u8:7 Not tainted 4.13.9-1-default #1 [ 91.616847] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014 [ 91.616851] Workqueue: events_unbound commit_work [drm_kms_helper] [ 91.616852] task: ffff98a43934a000 task.stack: ffffa6c0c2460000 [ 91.616855] RIP: 0010:drm_atomic_helper_commit_hw_done+0x8a/0x90 [drm_kms_helper] [ 91.616856] RSP: 0018:ffffa6c0c2463e40 EFLAGS: 00010286 [ 91.616856] RAX: ffff98a4293f7400 RBX: ffff98a422711700 RCX: ffff98a4b9ce8000 [ 91.616857] RDX: ffff98a4291b5a00 RSI: ffff98a422711700 RDI: ffff98a4b510f800 [ 91.616857] RBP: 0000000000000001 R08: 0000000000000000 R09: ffff98a4b7457000 [ 91.616858] R10: 0000000000000003 R11: 00000000f0000006 R12: ffff98a4b8cfa000 [ 91.616858] R13: ffff98a422711700 R14: ffff98a4b85f1180 R15: ffff98a422711758 [ 91.616859] FS: 0000000000000000(0000) GS:ffff98a4bfd80000(0000) knlGS:0000000000000000 [ 91.616860] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 91.616860] CR2: 00007efe00d11478 CR3: 0000000139b64000 CR4: 00000000003406e0 [ 91.616863] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 91.616863] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 91.616864] Call Trace: [ 91.616869] drm_atomic_helper_commit_tail+0x39/0x60 [drm_kms_helper] [ 91.616873] commit_tail+0x59/0x60 [drm_kms_helper] [ 91.616875] process_one_work+0x17c/0x3b0 [ 91.616876] worker_thread+0x36/0x370 [ 91.616878] ? process_one_work+0x3b0/0x3b0 [ 91.616879] kthread+0x118/0x130 [ 91.616880] ? kthread_create_on_node+0x40/0x40 [ 91.616882] ret_from_fork+0x25/0x30 [ 91.616883] Code: ed 46 f6 49 8d 7c 24 30 e8 54 4a dc f5 48 89 df e8 9c e8 46 f6 49 8b 4d 08 83 c5 01 39 a9 38 03 00 00 7f 9b 5b 5d 41 5c 41 5d c3 <0f> ff eb c5 f3 c3 0f 1f 44 00 00 48 8b 4f 08 8b 81 38 03 00 00 [ 91.616899] ---[ end trace 13e1491a20e8c564 ]--- [ 101.851625] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:36:crtc-1] flip_done timed out [ 101.851642] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:36:crtc-1] flip_done timed out -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 80683] New: EDID valid check ignores errors in CEA blocks
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=80683 Priority: medium Bug ID: 80683 Assignee: dri-devel(a)lists.freedesktop.org Summary: EDID valid check ignores errors in CEA blocks Severity: normal Classification: Unclassified OS: All Reporter: stefan.bruens(a)rwth-aachen.de Hardware: Other Status: NEW Version: DRI CVS Component: DRM/other Product: DRI in linux/drivers/gpu/drm/drm_edid.c: bool drm_edid_block_valid(u8 *raw_edid, int block, bool print_bad_edid) { ... if (csum) { if (print_bad_edid) { DRM_ERROR("EDID checksum is invalid, remainder is %d\n", csum); } /* allow CEA to slide through, switches mangle this */ if (raw_edid[0] != 0x02) goto bad; } ... return true; --- i.e. CEA blocks are always reported as valid. This occurs frequently for me with a Radeon 7750 and a Dell U2713HM connected via DisplayPort, the I2C-over-AUX seems to be buggy and swallows single bytes. If I change the "return true;" to "return !csum;" bad transfers are retried. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 98322] QXL drm driver regression in 4.7
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=98322 Bug ID: 98322 Summary: QXL drm driver regression in 4.7 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: tiwai(a)suse.de Since 4.7 kernel, qxl drm driver spews the errors when using VT: kernel: [TTM] Buffer eviction failed kernel: qxl 0000:00:02.0: object_init failed for (4026540032, 0x00000001) kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO In my test case, just install a QEMU/KVM VM with QXL interface, login GUI, and then switch to VT1. At login there, the error appears repeatedly. 4.6 kernel works fine. The git bisection spotted that it was introduced by 6819c3c2517604f979da3de773f2420e07dd4f4b drm/qxl: Use drm_fb_helper deferred_io support This was originally reported for opensuse TW: https://bugzilla.suse.com/show_bug.cgi?id=1003298 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 100375] forced EDID's can cause a amdgpu to null ptr deref
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=100375 Bug ID: 100375 Summary: forced EDID's can cause a amdgpu to null ptr deref Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: funfunctor(a)folklore1984.net [ 307.570505] [drm] Got external EDID base block and 0 extensions from "edid/768x384.bin" for connector "VGA-1" [ 445.605230] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 60 [ 445.605232] Raw EDID: [ 445.605235] 00 ff ff ff ff ff ff 00 39 f6 05 04 16 07 02 00 [ 445.605236] 10 17 01 03 81 1e 17 b4 ea c1 e5 a3 57 4e 9c 23 [ 445.605237] 1d 50 54 21 08 00 01 01 01 01 01 01 01 01 01 01 [ 445.605238] 01 01 01 07 01 01 91 26 4f ff ff ff ff ff ff ff [ 445.605239] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 445.605240] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 445.605240] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 445.605241] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 445.606369] [drm:amdgpu_connector_dvi_detect [amdgpu]] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID # reboot INIT: Sending processes the KILL signal [ 521.758143] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [ 521.765999] IP: [<ffffffff8116984d>] set_root+0x1d/0xa0 [ 521.771242] PGD 0 [ 521.773080] [ 521.774580] Oops: 0000 [#1] SMP [ 521.777717] Modules linked in: amdgpu blackmagic_io(PO) ttm backlight hid_sony led_class [ 521.785920] CPU: 2 PID: 3694 Comm: hyperflow-engin Tainted: P O 4.9.6-gentoo-r1 #1 [ 521.794610] Hardware name: BIOSTAR Group A68N-5200/A68N-5200, BIOS 4.6.5 09/03/2015 [ 521.802255] task: ffff880225698c40 task.stack: ffffc90000db8000 [ 521.808165] RIP: 0010:[<ffffffff8116984d>] [<ffffffff8116984d>] set_root+0x1d/0xa0 [ 521.815828] RSP: 0018:ffffc90000dbb688 EFLAGS: 00010202 [ 521.821133] RAX: ffff880225698c40 RBX: ffffc90000dbb7c0 RCX: ffff880225a63400 [ 521.828256] RDX: ffffffff81c56e48 RSI: 0000000000000041 RDI: ffffc90000dbb7c0 [ 521.835381] RBP: ffffc90000dbb698 R08: 000000000001a980 R09: ffff880225a63400 [ 521.842505] R10: ffff880225a80026 R11: 0000000000000010 R12: 0000000000000000 [ 521.849630] R13: ffff880225a8201c R14: 0000000000000001 R15: ffff880218826d80 [ 521.856755] FS: 00007fc3f57fa700(0000) GS:ffff88022ed00000(0000) knlGS:0000000000000000 [ 521.864834] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 521.870571] CR2: 0000000000000008 CR3: 0000000001a08000 CR4: 00000000000406e0 [ 521.877694] Stack: [ 521.879706] ffffc90000dbb7c0 0000000000000041 ffffc90000dbb6d8 ffffffff81169b89 [ 521.887160] ffff880220ead600 ffff880225a82000 ffffc90000dbb7c0 ffffc90000dbb8cc [ 521.894612] 0000000000000001 ffff880218826d80 ffffc90000dbb7b0 ffffffff8116c28a [ 521.902067] Call Trace: [ 521.904515] [<ffffffff81169b89>] path_init+0x1e9/0x330 [ 521.909740] [<ffffffff8116c28a>] path_openat+0x6a/0x1480 [ 521.915141] [<ffffffff81079bdd>] ? default_wake_function+0xd/0x10 [ 521.921319] [<ffffffff8108cddd>] ? __wake_up_common+0x4d/0x80 [ 521.927145] [<ffffffff8116f189>] do_filp_open+0x79/0xd0 [ 521.932467] [<ffffffff8134f298>] ? acpi_driver_match_device+0x3d/0x5d [ 521.938991] [<ffffffff813d67c4>] ? platform_match+0x24/0xa0 [ 521.944644] [<ffffffff81602d71>] ? klist_next+0x21/0xf0 [ 521.949957] [<ffffffff8115e5df>] file_open_name+0xdf/0x100 [ 521.955529] [<ffffffff8115e62e>] filp_open+0x2e/0x50 [ 521.960573] [<ffffffff81165561>] kernel_read_file_from_path+0x31/0x70 [ 521.967092] [<ffffffff813dffaf>] _request_firmware+0x2ef/0x5a0 [ 521.973002] [<ffffffff813e0292>] request_firmware+0x32/0x50 [ 521.978654] [<ffffffff813a9604>] drm_load_edid_firmware+0x264/0x500 [ 521.985001] [<ffffffff8139e2fc>] drm_helper_probe_single_connector_modes+0x14c/0x4d0 [ 521.992826] [<ffffffff813aa618>] drm_fb_helper_probe_connector_modes.isra.7+0x48/0x70 [ 522.000738] [<ffffffff813ac154>] drm_fb_helper_hotplug_event+0x94/0xd0 [ 522.007343] [<ffffffff813ac34c>] drm_fb_helper_restore_fbdev_mode_unlocked+0x1bc/0x2a0 [ 522.015381] [<ffffffffa00efa50>] ? amdgpu_driver_postclose_kms+0x90/0xd0 [amdgpu] [ 522.022965] [<ffffffffa01023d5>] amdgpu_fbdev_restore_mode+0x15/0x40 [amdgpu] [ 522.030199] [<ffffffffa00ef8dd>] amdgpu_driver_lastclose_kms+0xd/0x10 [amdgpu] [ 522.037505] [<ffffffff813b0286>] drm_lastclose+0x36/0xf0 [ 522.042895] [<ffffffff813b05e5>] drm_release+0x2a5/0x360 [ 522.048288] [<ffffffff81160f7a>] __fput+0xda/0x1e0 [ 522.053167] [<ffffffff811610b9>] ____fput+0x9/0x10 [ 522.058039] [<ffffffff8106e929>] task_work_run+0x79/0xa0 [ 522.063438] [<ffffffff8105731a>] do_exit+0x34a/0xaa0 [ 522.068533] [<ffffffffa00749ed>] ? _ZN10IOWorkLoop8openGateEv+0xd/0x10 [blackmagic_io] [ 522.076524] [<ffffffff810588d0>] do_group_exit+0x40/0xa0 [ 522.081916] [<ffffffff81062812>] get_signal+0x272/0x5e0 [ 522.087246] [<ffffffffa004093e>] ? _ZN15UserClientClass21getFlushedInputFramesEPcPj+0x1e/0x20 [blackmagic_io] [ 522.097233] [<ffffffff8101bfd3>] do_signal+0x23/0x5b0 [ 522.102395] [<ffffffffa003683a>] ? _ZN20UserClientClassLinux5ioctlEjm+0x8a/0xa0 [blackmagic_io] [ 522.111193] [<ffffffffa002d34c>] ? bmio_client_ioctl+0xc/0x10 [blackmagic_io] [ 522.118424] [<ffffffffa0070af5>] ? __do_global_dtors_aux+0x145/0x540 [blackmagic_io] [ 522.126251] [<ffffffff81171fab>] ? do_vfs_ioctl+0x8b/0x5a0 [ 522.131823] [<ffffffff810ab5c5>] ? ktime_get_ts64+0x45/0xf0 [ 522.137474] [<ffffffff8100222e>] exit_to_usermode_loop+0x4e/0x80 [ 522.143566] [<ffffffff81002673>] syscall_return_slowpath+0x43/0x50 [ 522.149827] [<ffffffff81608e1f>] entry_SYSCALL_64_fastpath+0x92/0x94 [ 522.156264] Code: 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 55 65 48 8b 04 25 40 c4 00 00 48 89 e5 41 54 53 f6 47 38 40 4c 8b a0 68 05 00 00 74 39 <41> 8b 4c 24 08 f6 c1 01 75 6d 49 8b 54 24 20 4 9 8b 44 24 18 48 [ 522.176216] RIP [<ffffffff8116984d>] set_root+0x1d/0xa0 [ 522.181536] RSP <ffffc90000dbb688> [ 522.185022] CR2: 0000000000000008 [ 522.188333] ---[ end trace d57bf884cf6f4e4c ]--- [ 522.192944] Fixing recursive fault but reboot is needed! -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 73624] New: AST2300 KMS EDID issue on C2750D4I
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=73624 Priority: medium Bug ID: 73624 Assignee: dri-devel(a)lists.freedesktop.org Summary: AST2300 KMS EDID issue on C2750D4I Severity: normal Classification: Unclassified OS: All Reporter: johannesobermayr(a)gmx.de Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI Created attachment 92079 --> https://bugs.freedesktop.org/attachment.cgi?id=92079&action=edit EDID issue with KMS AST2300 doesn't fetch right EDID data ... [ 10.599714] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 73 [ 10.599718] Raw EDID: [ 10.599721] 00 ff ff ff ff ff ff 00 09 d1 0b 79 45 54 00 00 [ 10.599723] 29 12 01 03 0e 2f 1a 78 2e 35 85 a6 56 48 9a 24 [ 10.599725] 12 50 54 a5 6b ba 71 00 81 0d 00 00 00 00 00 00 [ 10.599727] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599729] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 10.599731] 00 00 00 00 00 00 00 00 00 00 00 00 02 01 ff ff [ 10.599733] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 10.599734] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 89549] DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=89549 Bug ID: 89549 Summary: DisplayLink (udl) Linux kernel memory fault on USB hot unplug, proposed patch Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/other Assignee: dri-devel(a)lists.freedesktop.org Reporter: adam_richter2004(a)yahoo.com Created attachment 114235 --> https://bugs.freedesktop.org/attachment.cgi?id=114235&action=edit Add ".get_vblank_counter = drm_vblank_count," to DisplayLink drm_driver functions [This is an edit of an email that I sent yesterday to linux-fbdev at vger.kernel.org and the Linux kernel udlfb maintainer.] In Linux-4.0-rc3, the DisplayLink driver gets a kernel memory fault when its USB device is unplugged, specifically when vblank_disable_and_save in linux-4.0-rc3/drivers/gpu/drm/drm_irq.c attempts to call the NULL function pointer dev->driver_get_vblank_counter. linux-4.0-rc3/Documentation/DocBook/drm.tmpl says of that field, "Otherwise drivers can use the drm_vblank_count helper function to handle this operation." Trying that seems to have eliminated the oops when I unplug the device, although I do see these lines in the console log at device driver initialization time that I think are probably fine, but which I should mention in case the indicate that I did the wrong the thing: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. If that doesn't look like a problem, then please apply the attached patch and push it upstream. The patch just adds one line that appears in six other framebuffer drivers to initialize the driver_get_vblank_counter drm_driver function. Thanks in advance for your attention to this problem. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 28841] New: Heavy text corruption in virtual consoles using DRI
by bugzilla-daemon＠freedesktop.org 14 Oct '19

14 Oct '19

https://bugs.freedesktop.org/show_bug.cgi?id=28841 Summary: Heavy text corruption in virtual consoles using DRI Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I have a clean install of latest ubuntu lucid lynx, I added framebuffer support for g550 (matroxfb) and text in virtual consoles appears corrupted, it is made of random pixels appearing far away from the expected prompt. I can get back to clean text if I switch to xorg (ctrl+f7) then back to the virtual console, but if I type in new text, it appears ugly as usual. The only workaround for this is to disable DRI, then the text appears perfect and no switch is needed. Of course, this way the system cannot support any game. I attach my actual xorg.conf. My config: ubuntu 10.04 (Lucid) 2.6.32-22-generic i686 GNU/Linux with gnome 2.30.2 and xorg X server 1.7.6. -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019