From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201957] amdgpu: ring gfx timeout
Date: Mon, 01 Apr 2019 18:20:39 +0000 [thread overview]
Message-ID: <bug-201957-2300-6NRZ8gEKTO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201957-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #6 from Dev Bazilio (anode.dev@gmail.com) ---
tried linux-amd-staging-drm-next-git-5.1.811103.2acb851ad43b and dmes is still
has a lot of warnings. Tested also youtube in chrome with UVD, got a minor
freeze and long freeze ~30sec of system
Apr 01 21:01:03 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper
[amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 21:01:03 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR*
resume of IP block <uvd_v6_0> failed -110
Apr 01 21:01:03 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_device_ip_resume failed (-110).
Apr 01 20:26:59 kernel: [drm] amdgpu kernel modesetting enabled.
Apr 01 20:26:59 kernel: vga_switcheroo: detected switching method
\_SB_.PCI0.VGA_.ATPX handle
Apr 01 20:26:59 kernel: [drm] initializing kernel modesetting (CARRIZO
0x1002:0x9874 0x1025:0x1201 0xCA).
Apr 01 20:26:59 kernel: [drm] register mmio base: 0xD1500000
Apr 01 20:26:59 kernel: [drm] register mmio size: 262144
Apr 01 20:26:59 kernel: [drm] add ip block number 0 <vi_common>
Apr 01 20:26:59 kernel: [drm] add ip block number 1 <gmc_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 2 <cz_ih>
Apr 01 20:26:59 kernel: [drm] add ip block number 3 <gfx_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 4 <sdma_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 5 <powerplay>
Apr 01 20:26:59 kernel: [drm] add ip block number 6 <dm>
Apr 01 20:26:59 kernel: [drm] add ip block number 7 <uvd_v6_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 8 <vce_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 9 <acp_ip>
Apr 01 20:26:59 kernel: [drm] UVD is enabled in physical mode
Apr 01 20:26:59 kernel: [drm] VCE enabled in physical mode
Apr 01 20:26:59 kernel: ATOM BIOS: 113-C91400-007
Apr 01 20:26:59 kernel: [drm] RAS INFO: ras initialized successfully, hardware
ability[0] ras_mask[0]
Apr 01 20:26:59 kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit,
fragment size is 9-bit
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 -
0x000000F41FFFFFFF (512M used)
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 -
0x000000FF3FFFFFFF
Apr 01 20:26:59 kernel: [drm] Detected VRAM RAM=512M, BAR=512M
Apr 01 20:26:59 kernel: [drm] RAM width 64bits UNKNOWN
Apr 01 20:26:59 kernel: [TTM] Zone kernel: Available graphics memory: 3804974
KiB
Apr 01 20:26:59 kernel: [TTM] Zone dma32: Available graphics memory: 2097152
KiB
Apr 01 20:26:59 kernel: [TTM] Initializing pool allocator
Apr 01 20:26:59 kernel: [TTM] Initializing DMA pool allocator
Apr 01 20:26:59 kernel: [drm] amdgpu: 512M of VRAM memory ready
Apr 01 20:26:59 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Apr 01 20:26:59 kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
Apr 01 20:26:59 kernel: [drm] PCIE GART of 1024M enabled (table at
0x000000F4007E9000).
Apr 01 20:26:59 kernel: [drm] Found UVD firmware Version: 1.91 Family ID: 11
Apr 01 20:26:59 kernel: [drm] UVD ENC is disabled
Apr 01 20:26:59 kernel: [drm] Found VCE firmware Version: 52.4 Binary ID: 3
Apr 01 20:26:59 kernel: smu version 27.17.00
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Engine clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 480000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 533340
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 576000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 626090
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 685720
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 720000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 757900
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: level : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Display clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 400000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 496560
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 626090
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 685720
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 757900
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 800000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 847060
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: level : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Memory clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 667000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 933000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: engine_max_clock: 75790
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: level : 8
Apr 01 20:26:59 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid
Connector ObjectID from Adapter Service for connector index:2! type 0 expected
3
Apr 01 20:26:59 kernel: [drm] Display Core initialized with v3.2.24!
Apr 01 20:26:59 kernel: [drm] SADs count is: -2, don't need to read it
Apr 01 20:26:59 kernel: [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
Apr 01 20:26:59 kernel: [drm] Driver supports precise vblank timestamp query.
Apr 01 20:26:59 kernel: [drm] UVD initialized successfully.
Apr 01 20:26:59 kernel: [drm] VCE initialized successfully.
Apr 01 20:26:59 kernel: kfd kfd: Allocated 3969056 bytes on gart
Apr 01 20:26:59 kernel: Topology: Add APU node [0x9874:0x1002]
Apr 01 20:26:59 kernel: kfd kfd: added device 1002:9874
Apr 01 20:26:59 kernel: [drm] fb mappable at 0x21FDCD000
Apr 01 20:26:59 kernel: [drm] vram apper at 0x21F000000
Apr 01 20:26:59 kernel: [drm] size 8294400
Apr 01 20:26:59 kernel: [drm] fb depth is 24
Apr 01 20:26:59 kernel: [drm] pitch is 7680
Apr 01 20:26:59 kernel: fbcon: amdgpudrmfb (fb0) is primary device
Apr 01 20:26:59 kernel: Console: switching to colour frame buffer device 240x67
Apr 01 20:26:59 kernel: amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer
device
Apr 01 20:26:59 kernel: [drm] Initialized amdgpu 3.31.0 20150101 for
0000:00:01.0 on minor 0
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: enabling device (0002 -> 0003)
Apr 01 20:26:59 kernel: [drm] initializing kernel modesetting (POLARIS12
0x1002:0x699F 0x1025:0x1210 0xC3).
Apr 01 20:26:59 kernel: [drm] register mmio base: 0xD1200000
Apr 01 20:26:59 kernel: [drm] register mmio size: 262144
Apr 01 20:26:59 kernel: [drm] add ip block number 0 <vi_common>
Apr 01 20:26:59 kernel: [drm] add ip block number 1 <gmc_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 2 <tonga_ih>
Apr 01 20:26:59 kernel: [drm] add ip block number 3 <gfx_v8_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 4 <sdma_v3_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 5 <powerplay>
Apr 01 20:26:59 kernel: [drm] add ip block number 6 <dm>
Apr 01 20:26:59 kernel: [drm] add ip block number 7 <uvd_v6_0>
Apr 01 20:26:59 kernel: [drm] add ip block number 8 <vce_v3_0>
Apr 01 20:26:59 kernel: kfd kfd: skipped device 1002:699f, PCI rejects atomics
Apr 01 20:26:59 kernel: [drm] UVD is enabled in VM mode
Apr 01 20:26:59 kernel: [drm] UVD ENC is enabled in VM mode
Apr 01 20:26:59 kernel: [drm] VCE enabled in VM mode
Apr 01 20:26:59 kernel: vga_switcheroo: enabled
Apr 01 20:26:59 kernel: ATOM BIOS: SWBRT23054.001
Apr 01 20:26:59 kernel: [drm] GPU posting now...
Apr 01 20:26:59 kernel: [drm] RAS INFO: ras initialized successfully, hardware
ability[0] ras_mask[0]
Apr 01 20:26:59 kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit,
fragment size is 9-bit
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 -
0x000000F47FFFFFFF (2048M used)
Apr 01 20:26:59 kernel: amdgpu 0000:03:00.0: GART: 256M 0x000000FF00000000 -
0x000000FF0FFFFFFF
Apr 01 20:26:59 kernel: [drm] Detected VRAM RAM=2048M, BAR=256M
Apr 01 20:26:59 kernel: [drm] RAM width 128bits GDDR5
Apr 01 20:26:59 kernel: [drm] amdgpu: 2048M of VRAM memory ready
Apr 01 20:26:59 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Apr 01 20:26:59 kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Apr 01 20:26:59 kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400000000).
Apr 01 20:26:59 kernel: [drm] Chained IB support enabled!
Apr 01 20:26:59 kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Apr 01 20:26:59 kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage
ID but it's not patched
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Engine clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 214000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 551000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 734000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 921000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 980000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 1046000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: engine_max_clock: 104600
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: memory_max_clock: 125000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: level : 8
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: values for Memory clock
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 300000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 625000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: 1250000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: Validation clocks:
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: engine_max_clock: 104600
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: memory_max_clock: 125000
Apr 01 20:26:59 kernel: [drm] DM_PPLIB: level : 8
Apr 01 20:26:59 kernel: [drm] Display Core initialized with v3.2.24!
Apr 01 20:26:59 kernel: [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
Apr 01 20:26:59 kernel: [drm] Driver supports precise vblank timestamp query.
Apr 01 20:26:59 kernel: [drm] UVD and UVD ENC initialized successfully.
Apr 01 20:26:59 kernel: [drm] VCE initialized successfully.
Apr 01 20:26:59 kernel: [drm] Initialized amdgpu 3.31.0 20150101 for
0000:03:00.0 on minor 1
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
failed to send message 15b ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
failed to send message 15a ret is 0
Apr 01 20:26:59 kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]]
*ERROR* ib ring test failed (-110).
Apr 01 20:26:59 kernel: EXT4-fs (sda3): mounted filesystem with ordered data
mode. Opts: (null)
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
failed to send message 155 ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:26:59 kernel: amdgpu: [powerplay]
failed to send message 15b ret is 0
Apr 01 20:27:48 kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400000000).
Apr 01 20:27:48 kernel: amdgpu: [powerplay]
failed to send message 154 ret is 0
Apr 01 20:27:49 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper
[amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:27:49 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR*
resume of IP block <uvd_v6_0> failed -110
Apr 01 20:27:49 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_device_ip_resume failed (-110).
Apr 01 20:27:50 kernel: amdgpu: [powerplay]
Apr 01 20:28:30 kernel: amdgpu: [powerplay]
failed to send message 261 ret is 0
Apr 01 20:28:31 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:31 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:32 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:32 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:33 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:33 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:34 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:34 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:35 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:35 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:36 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:36 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:37 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:37 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:38 kernel: [drm] Fence fallback timer expired on ring sdma0
Apr 01 20:28:39 kernel: amdgpu: [powerplay]
Apr 01 20:29:12 kernel: amdgpu: [powerplay]
failed to send message 154 ret is 0
Apr 01 20:29:13 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper
[amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:29:13 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR*
resume of IP block <uvd_v6_0> failed -110
Apr 01 20:29:13 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_device_ip_resume failed (-110).
Apr 01 20:30:06 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:30:06 kernel: amdgpu: [powerplay]
failed to send message 135 ret is 0
Apr 01 20:30:07 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:30:07 kernel: amdgpu: [powerplay]
failed to send message 190 ret is 0
Apr 01 20:30:08 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:30:08 kernel: amdgpu: [powerplay]
failed to send message 63 ret is 0
Apr 01 20:30:09 kernel: amdgpu: [powerplay]
last message was failed ret is 0
Apr 01 20:30:09 kernel: amdgpu: [powerplay]
failed to send message 84 ret is 0
Apr 01 20:30:09 kernel: amdgpu 0000:03:00.0: GPU pci config reset
Apr 01 20:34:17 kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400000000).
Apr 01 20:34:18 kernel: amdgpu: [powerplay]
failed to send message 154 ret is 0
Apr 01 20:34:18 kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper
[amdgpu]] *ERROR* ring uvd_enc0 test failed (-110)
Apr 01 20:34:18 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR*
resume of IP block <uvd_v6_0> failed -110
Apr 01 20:34:18 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR*
amdgpu_device_ip_resume failed (-110).
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-01 18:20 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 4:52 [Bug 201957] New: amdgpu: ring gfx timeout bugzilla-daemon
2018-12-11 14:57 ` [Bug 201957] " bugzilla-daemon
2018-12-11 18:18 ` bugzilla-daemon
2019-03-07 5:20 ` bugzilla-daemon
2019-03-07 5:24 ` bugzilla-daemon
2019-03-12 13:15 ` bugzilla-daemon
2019-04-01 18:20 ` bugzilla-daemon [this message]
2019-04-01 18:44 ` bugzilla-daemon
2019-08-20 15:06 ` bugzilla-daemon
2019-09-11 8:36 ` bugzilla-daemon
2019-09-20 11:37 ` bugzilla-daemon
2019-10-02 10:39 ` bugzilla-daemon
2019-10-11 22:00 ` bugzilla-daemon
2019-10-14 17:18 ` bugzilla-daemon
2019-10-24 16:39 ` bugzilla-daemon
2019-10-24 16:40 ` bugzilla-daemon
2019-10-27 18:44 ` bugzilla-daemon
2019-11-10 7:11 ` bugzilla-daemon
2019-11-25 9:43 ` bugzilla-daemon
2019-12-03 15:53 ` bugzilla-daemon
2019-12-03 16:07 ` bugzilla-daemon
2019-12-03 21:34 ` bugzilla-daemon
2019-12-04 9:54 ` bugzilla-daemon
2019-12-08 17:32 ` bugzilla-daemon
2020-01-02 8:30 ` bugzilla-daemon
2020-01-02 9:11 ` bugzilla-daemon
2020-01-19 17:03 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:04 ` bugzilla-daemon
2020-01-19 17:13 ` bugzilla-daemon
2020-04-04 21:54 ` bugzilla-daemon
2020-05-01 9:03 ` bugzilla-daemon
2020-05-01 19:52 ` bugzilla-daemon
2020-05-25 12:21 ` bugzilla-daemon
2020-06-19 19:11 ` bugzilla-daemon
2020-08-10 23:49 ` bugzilla-daemon
2020-09-01 14:00 ` bugzilla-daemon
2020-09-13 11:14 ` bugzilla-daemon
2020-11-23 16:27 ` bugzilla-daemon
2021-01-24 19:37 ` bugzilla-daemon
2021-01-24 22:26 ` bugzilla-daemon
2021-01-24 22:51 ` bugzilla-daemon
2021-01-24 22:56 ` bugzilla-daemon
2021-01-25 22:24 ` bugzilla-daemon
2021-01-26 3:22 ` bugzilla-daemon
2021-02-14 19:48 ` bugzilla-daemon
2021-02-28 12:35 ` bugzilla-daemon
2021-03-28 13:19 ` bugzilla-daemon
2021-08-22 20:01 ` bugzilla-daemon
2021-11-17 7:14 ` bugzilla-daemon
2021-11-26 2:09 ` bugzilla-daemon
2021-12-12 21:59 ` bugzilla-daemon
2021-12-22 20:33 ` bugzilla-daemon
2022-01-01 4:29 ` bugzilla-daemon
2022-01-09 18:06 ` bugzilla-daemon
2022-01-22 23:54 ` bugzilla-daemon
2022-01-22 23:56 ` bugzilla-daemon
2022-01-24 23:17 ` bugzilla-daemon
2022-01-25 8:56 ` bugzilla-daemon
2022-01-25 18:19 ` bugzilla-daemon
2022-01-25 18:49 ` bugzilla-daemon
2022-02-02 11:39 ` bugzilla-daemon
2022-02-03 1:37 ` bugzilla-daemon
2022-02-03 1:39 ` bugzilla-daemon
2022-02-03 3:42 ` bugzilla-daemon
2022-02-11 12:23 ` bugzilla-daemon
2022-02-24 23:40 ` bugzilla-daemon
2022-02-25 14:20 ` bugzilla-daemon
2022-05-05 15:19 ` bugzilla-daemon
2022-05-05 19:14 ` bugzilla-daemon
2022-06-11 22:06 ` bugzilla-daemon
2022-06-13 1:20 ` bugzilla-daemon
2022-06-20 12:03 ` bugzilla-daemon
2022-06-20 12:06 ` bugzilla-daemon
2022-06-22 12:56 ` bugzilla-daemon
2022-06-23 10:04 ` bugzilla-daemon
2022-06-23 10:26 ` bugzilla-daemon
2022-06-23 11:05 ` bugzilla-daemon
2022-06-23 11:44 ` bugzilla-daemon
2022-06-23 22:12 ` bugzilla-daemon
2022-06-29 2:58 ` bugzilla-daemon
2022-07-14 10:17 ` bugzilla-daemon
2022-07-17 10:28 ` bugzilla-daemon
2022-07-17 20:08 ` bugzilla-daemon
2022-08-11 2:59 ` bugzilla-daemon
2023-01-11 1:13 ` bugzilla-daemon
2023-05-23 10:27 ` bugzilla-daemon
2023-05-24 8:55 ` bugzilla-daemon
2023-08-15 12:33 ` bugzilla-daemon
2023-08-24 15:52 ` bugzilla-daemon
2023-09-21 22:38 ` bugzilla-daemon
2023-09-23 1:52 ` bugzilla-daemon
2023-09-30 10:25 ` bugzilla-daemon
2023-09-30 18:57 ` bugzilla-daemon
2023-09-30 19:08 ` bugzilla-daemon
2023-09-30 19:35 ` bugzilla-daemon
2023-09-30 19:47 ` bugzilla-daemon
2023-10-21 14:29 ` bugzilla-daemon
2023-10-22 17:35 ` bugzilla-daemon
2023-10-23 17:22 ` bugzilla-daemon
2024-06-04 8:00 ` bugzilla-daemon
2024-06-04 14:27 ` bugzilla-daemon
2024-06-05 9:02 ` bugzilla-daemon
2024-06-05 9:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-201957-2300-6NRZ8gEKTO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).