dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing
Date: Sun, 18 Mar 2018 20:31:41 +0000	[thread overview]
Message-ID: <bug-91880-502-EDN4kkYkrf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91880-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 13523 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=91880

--- Comment #186 from Chris Heald <cheald@gmail.com> ---
I've been doing a lot of experimentation, and I've found a few more things that
I feel are probably related:

* I can force a system hard-lock by doing anything which disables a monitor.
Notably, going full-screen under KDE/Xorg does this, but I can trigger it just
as easily by disabling a monitor with xrandr. Fullscreen under gnome doesn't
seem to trigger the issue, which I suspect is due to gnome's using mutter for
screen management.

* Occassioanlly, the system boots up and gets stuck with a 150MHz memory clock,
rather than clocking up to the 1500MHz state. This causes the display
corruption even if the sclk is set to 500MHz+. Setting the mclk mask manually
fixes display corruption.

* I've been experimenting with different kernels ranging from 4.4 to 4.16rc5.
Earlier kernels feel more susceptible to hard-locking, though the later kernels
aren't immune to it.

* I tried a fresh Ubuntu 16.04 LTS install, and while it did NOT exhibit the
artifacting behavior, the system hard-locked within a few minutes of light
desktop usage.

I've had a few classes of exceptions show up in kern.log:

On 4.4, my kde/wayland session hard-froze when moving a window, and produced a
log like this:

kernel: [  116.904013] radeon 0000:06:00.0: GPU fault detected: 146 0x0d8e040c
kernel: [  116.904017] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
  0x0001776C
kernel: [  116.904019] radeon 0000:06:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E10400C
kernel: [  116.904021] VM fault (0x0c, vmid 7) at page 96108, read from 'TC3'
(0x54433300) (260)
kernel: [  127.306156] radeon 0000:06:00.0: ring 0 stalled for more than
10404msec
kernel: [  127.306164] radeon 0000:06:00.0: GPU lockup (current fence id
0x0000000000002419 last fence id 0x0000000000002431 on ring 0)
kernel: [  127.357942] radeon 0000:06:00.0: Saved 2200 dwords of commands on
ring 0.
kernel: [  127.357961] radeon 0000:06:00.0: GPU softreset: 0x00000009
kernel: [  127.357963] radeon 0000:06:00.0:   GRBM_STATUS=0xF5D01028
kernel: [  127.357965] radeon 0000:06:00.0:   GRBM_STATUS2=0x50000008
kernel: [  127.357968] radeon 0000:06:00.0:   GRBM_STATUS_SE0=0xEC400002
kernel: [  127.357970] radeon 0000:06:00.0:   GRBM_STATUS_SE1=0xEC400002
kernel: [  127.357972] radeon 0000:06:00.0:   GRBM_STATUS_SE2=0x08000002
kernel: [  127.357974] radeon 0000:06:00.0:   GRBM_STATUS_SE3=0xEC000002
kernel: [  127.357976] radeon 0000:06:00.0:   SRBM_STATUS=0x20000040
kernel: [  127.357978] radeon 0000:06:00.0:   SRBM_STATUS2=0x00000000
kernel: [  127.357980] radeon 0000:06:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
kernel: [  127.357982] radeon 0000:06:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
kernel: [  127.357984] radeon 0000:06:00.0:   CP_STAT = 0x84228600
kernel: [  127.357986] radeon 0000:06:00.0:   CP_STALLED_STAT1 = 0x00000c00
kernel: [  127.357988] radeon 0000:06:00.0:   CP_STALLED_STAT2 = 0x40000000
kernel: [  127.357991] radeon 0000:06:00.0:   CP_STALLED_STAT3 = 0x00000400
kernel: [  127.357993] radeon 0000:06:00.0:   CP_CPF_BUSY_STAT = 0x00000006
kernel: [  127.357995] radeon 0000:06:00.0:   CP_CPF_STALLED_STAT1 = 0x00000003
kernel: [  127.357997] radeon 0000:06:00.0:   CP_CPF_STATUS = 0x80000063
kernel: [  127.357999] radeon 0000:06:00.0:   CP_CPC_BUSY_STAT = 0x00000000
kernel: [  127.358001] radeon 0000:06:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
kernel: [  127.358003] radeon 0000:06:00.0:   CP_CPC_STATUS = 0x00000000
kernel: [  127.358005] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR
  0x00000000
kernel: [  127.358007] radeon 0000:06:00.0:  
VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
kernel: [  127.404670] radeon 0000:06:00.0: GRBM_SOFT_RESET=0x00010001
kernel: [  127.404725] radeon 0000:06:00.0: SRBM_SOFT_RESET=0x00000100
kernel: [  127.405874] radeon 0000:06:00.0:   GRBM_STATUS=0x00003028
kernel: [  127.405876] radeon 0000:06:00.0:   GRBM_STATUS2=0x00000008
kernel: [  127.405878] radeon 0000:06:00.0:   GRBM_STATUS_SE0=0x00000006
kernel: [  127.405880] radeon 0000:06:00.0:   GRBM_STATUS_SE1=0x00000006
kernel: [  127.405882] radeon 0000:06:00.0:   GRBM_STATUS_SE2=0x00000006
kernel: [  127.405884] radeon 0000:06:00.0:   GRBM_STATUS_SE3=0x00000006
kernel: [  127.405885] radeon 0000:06:00.0:   SRBM_STATUS=0x20000A40
kernel: [  127.405887] radeon 0000:06:00.0:   SRBM_STATUS2=0x00000000
kernel: [  127.405889] radeon 0000:06:00.0:   SDMA0_STATUS_REG   = 0x46CEE557
kernel: [  127.405891] radeon 0000:06:00.0:   SDMA1_STATUS_REG   = 0x46CEE557
kernel: [  127.405893] radeon 0000:06:00.0:   CP_STAT = 0x00000000
kernel: [  127.405893] radeon 0000:06:00.0:   CP_STAT = 0x00000000
kernel: [  127.405895] radeon 0000:06:00.0:   CP_STALLED_STAT1 = 0x00000000
kernel: [  127.405896] radeon 0000:06:00.0:   CP_STALLED_STAT2 = 0x00000000
kernel: [  127.405898] radeon 0000:06:00.0:   CP_STALLED_STAT3 = 0x00000000
kernel: [  127.405900] radeon 0000:06:00.0:   CP_CPF_BUSY_STAT = 0x00000000
kernel: [  127.405902] radeon 0000:06:00.0:   CP_CPF_STALLED_STAT1 = 0x00000000
kernel: [  127.405903] radeon 0000:06:00.0:   CP_CPF_STATUS = 0x00000000
kernel: [  127.405905] radeon 0000:06:00.0:   CP_CPC_BUSY_STAT = 0x00000000
kernel: [  127.405907] radeon 0000:06:00.0:   CP_CPC_STALLED_STAT1 = 0x00000000
kernel: [  127.405909] radeon 0000:06:00.0:   CP_CPC_STATUS = 0x00000000
kernel: [  127.405929] radeon 0000:06:00.0: GPU reset succeeded, trying to
resume
kernel: [  127.658172] [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
kernel: [  127.658189] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm
resume failed
kernel: [  127.658194] [drm] probing gen 2 caps for device 1022:1453 = 733903/e
kernel: [  127.658197] [drm] PCIE gen 3 link speeds already enabled
kernel: [  127.664213] [drm] PCIE GART of 2048M enabled (table at
0x0000000000326000).
kernel: [  127.664341] radeon 0000:06:00.0: WB enabled
kernel: [  127.664344] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr
0x0000000200000c00 and cpu addr 0xffff8807f3799c00
kernel: [  127.664346] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr
0x0000000200000c04 and cpu addr 0xffff8807f3799c04
kernel: [  127.664347] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr
0x0000000200000c08 and cpu addr 0xffff8807f3799c08
kernel: [  127.664349] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr
0x0000000200000c0c and cpu addr 0xffff8807f3799c0c
kernel: [  127.664350] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr
0x0000000200000c10 and cpu addr 0xffff8807f3799c10
kernel: [  127.664772] radeon 0000:06:00.0: fence driver on ring 5 use gpu addr
0x0000000000078b30 and cpu addr 0xffffc90003c38b30
kernel: [  127.664933] radeon 0000:06:00.0: fence driver on ring 6 use gpu addr
0x0000000200000c18 and cpu addr 0xffff8807f3799c18
kernel: [  127.664934] radeon 0000:06:00.0: fence driver on ring 7 use gpu addr
0x0000000200000c1c and cpu addr 0xffff8807f3799c1c
kernel: [  127.666482] [drm] ring test on 0 succeeded in 2 usecs
kernel: [  127.666568] [drm] ring test on 1 succeeded in 2 usecs
kernel: [  127.666586] [drm] ring test on 2 succeeded in 2 usecs
kernel: [  127.666735] [drm] ring test on 3 succeeded in 3 usecs
kernel: [  127.666745] [drm] ring test on 4 succeeded in 3 usecs
kernel: [  127.692636] [drm] ring test on 5 succeeded in 1 usecs
kernel: [  127.712543] [drm] UVD initialized successfully.
kernel: [  127.813896] [drm] ring test on 6 succeeded in 708 usecs
kernel: [  127.813920] [drm] ring test on 7 succeeded in 3 usecs
kernel: [  127.813921] [drm] VCE initialized successfully.
kernel: [  127.814029] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm
resume failed

On 4.15.10-041510-generic, I left my computer running overnight and came back
to it frozen with this in kern.log:

Mar 18 04:25:10 Gaia kernel: [  559.092721] BUG: stack guard page was hit at
000000001ecd1fa8 (stack is 0000000020941864..00000000cf703fbf)
Mar 18 04:25:10 Gaia kernel: [  559.092729] kernel stack overflow (page fault):
0000 [#1] SMP NOPTI
Mar 18 04:25:10 Gaia kernel: [  559.092733] Modules linked in:
nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter overlay xfrm_user
xfrm4_tunnel tunnel4 l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel ipcomp
xfrm_ipcomp udp_tunnel esp4 pppox ah4 af_key xfrm_algo xt_CHECKSUM
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables
ip6table_filter ip6_tables devlink iptable_filter binfmt_misc
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel
edac_mce_amd snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib kvm_amd
snd_hwdep kvm uvcvideo snd_seq_midi irqbypass snd_seq_midi_event snd_rawmidi
crct10dif_pclmul videobuf2_vmalloc crc32_pclmul
Mar 18 04:25:10 Gaia kernel: [  559.092784]  videobuf2_memops videobuf2_v4l2
snd_seq ghash_clmulni_intel videobuf2_core snd_pcm pcbc videodev snd_seq_device
media snd_timer joydev aesni_intel aes_x86_64 snd crypto_simd input_leds
glue_helper serio_raw soundcore cryptd ccp k10temp shpchp mac_hid wmi_bmof
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic
usbhid hid amdkfd amd_iommu_v2 amdgpu chash radeon i2c_algo_bit ttm
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm i2c_piix4
r8169 ahci mii libahci wmi gpio_amdpt gpio_generic
Mar 18 04:25:10 Gaia kernel: [  559.092832] CPU: 5 PID: 7352 Comm: tail
Tainted: G        W        4.15.10-041510-generic #201803152130
Mar 18 04:25:10 Gaia kernel: [  559.092834] Hardware name: Gigabyte Technology
Co., Ltd. AB350-Gaming 3/AB350-Gaming 3-CF, BIOS F10 12/01/2017
Mar 18 04:25:10 Gaia kernel: [  559.092881] RIP:
0010:amdgpu_get_pp_num_states+0x88/0x120 [amdgpu]
Mar 18 04:25:10 Gaia kernel: [  559.092884] RSP: 0018:ffffb3cb8a837ca8 EFLAGS:
00010282
Mar 18 04:25:10 Gaia kernel: [  559.092888] RAX: 00000000000000d4 RBX:
ffffb3cb8a837cac RCX: 0000000000000001
Mar 18 04:25:10 Gaia kernel: [  559.092890] RDX: 0000000000000000 RSI:
ffffffffc087a88c RDI: 0000000000000000
Mar 18 04:25:10 Gaia kernel: [  559.092893] RBP: ffffb3cb8a837d20 R08:
ffffffffc087a865 R09: ffff88c9ecebd98b
Mar 18 04:25:10 Gaia kernel: [  559.092895] R10: 0000000000000000 R11:
ffff88c9ecebd98a R12: ffff88c9ecebd000
Mar 18 04:25:10 Gaia kernel: [  559.092898] R13: ffffffffc087a858 R14:
00000000000000d4 R15: 0000000000000993
Mar 18 04:25:10 Gaia kernel: [  559.092901] FS:  00007fccb1787540(0000)
GS:ffff88c9fe740000(0000) knlGS:0000000000000000
Mar 18 04:25:10 Gaia kernel: [  559.092904] CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Mar 18 04:25:10 Gaia kernel: [  559.092906] CR2: ffffb3cb8a838000 CR3:
00000004a30d0000 CR4: 00000000003406e0
Mar 18 04:25:10 Gaia kernel: [  559.092909] Call Trace:
Mar 18 04:25:10 Gaia kernel: [  559.092918]  ?
tty_insert_flip_string_fixed_flag+0x86/0xe0
Mar 18 04:25:10 Gaia kernel: [  559.092925]  dev_attr_show+0x23/0x60
Mar 18 04:25:10 Gaia kernel: [  559.092931]  sysfs_kf_seq_show+0xa3/0x130
Mar 18 04:25:10 Gaia kernel: [  559.092935]  kernfs_seq_show+0x27/0x30
Mar 18 04:25:10 Gaia kernel: [  559.092939]  seq_read+0xe5/0x430
Mar 18 04:25:10 Gaia kernel: [  559.092943]  kernfs_fop_read+0x137/0x180
Mar 18 04:25:10 Gaia kernel: [  559.092948]  __vfs_read+0x3a/0x170
Mar 18 04:25:10 Gaia kernel: [  559.092954]  ?
security_file_permission+0xa1/0xc0
Mar 18 04:25:10 Gaia kernel: [  559.092958]  vfs_read+0x8e/0x130
Mar 18 04:25:10 Gaia kernel: [  559.092962]  SyS_read+0x55/0xc0
Mar 18 04:25:10 Gaia kernel: [  559.092967]  do_syscall_64+0x73/0x130
Mar 18 04:25:10 Gaia kernel: [  559.092973] 
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Mar 18 04:25:10 Gaia kernel: [  559.092976] RIP: 0033:0x7fccb12b5081
Mar 18 04:25:10 Gaia kernel: [  559.092978] RSP: 002b:00007ffc17d84d68 EFLAGS:
00000246 ORIG_RAX: 0000000000000000
Mar 18 04:25:10 Gaia kernel: [  559.092982] RAX: ffffffffffffffda RBX:
0000000000002000 RCX: 00007fccb12b5081
Mar 18 04:25:10 Gaia kernel: [  559.092984] RDX: 0000000000002000 RSI:
00007ffc17d84db0 RDI: 0000000000000003
Mar 18 04:25:10 Gaia kernel: [  559.092986] RBP: 0000000000000000 R08:
0000000000000000 R09: 00007fccb1313b40
Mar 18 04:25:10 Gaia kernel: [  559.092988] R10: 00000000fffffff3 R11:
0000000000000246 R12: 00007ffc17d84db0
Mar 18 04:25:10 Gaia kernel: [  559.092991] R13: 0000000000000003 R14:
ffffffffffffffff R15: 000055e8f3b747e0
Mar 18 04:25:10 Gaia kernel: [  559.092994] Code: c7 c2 7a a8 87 c0 be 00 10 00
00 4c 89 e7 e8 d0 08 90 d1 41 89 c7 8b 45 8c 85 c0 74 72 48 8d 5d 8c 45 31 f6
49 c7 c5 58 a8 87 c0 <42> 8b 44 b3 04 44 89 f1 4d 89 e8 83 f8 0a 74 2d 83 f8 02
49 c7
Mar 18 04:25:10 Gaia kernel: [  559.093080] RIP:
amdgpu_get_pp_num_states+0x88/0x120 [amdgpu] RSP: ffffb3cb8a837ca8
Mar 18 04:25:10 Gaia kernel: [  559.093084] ---[ end trace dbba232a9ca4c5c7
]---

Possibly related, if I `cat pp_num_states` from a terminal, I get a
segmentation fault:

root@Gaia:~# cat /sys/class/drm/card0/device/pp_num_states
Segmentation fault

I'm going to continue to dig. Let me know what logs/tests/whatnot I can provide
that would be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 14392 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-18 20:31 UTC|newest]

Thread overview: 213+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 15:00 [Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing bugzilla-daemon
2015-09-04 15:03 ` bugzilla-daemon
2015-09-04 18:40 ` bugzilla-daemon
2015-09-04 18:46 ` bugzilla-daemon
2015-09-04 18:50 ` bugzilla-daemon
2015-09-04 19:05 ` bugzilla-daemon
2015-09-04 19:08 ` bugzilla-daemon
2015-09-08 13:13 ` bugzilla-daemon
2015-10-16 15:01 ` bugzilla-daemon
2015-10-16 15:13 ` bugzilla-daemon
2015-10-16 21:20 ` bugzilla-daemon
2015-10-16 22:04 ` bugzilla-daemon
2015-10-16 22:17 ` bugzilla-daemon
2015-10-17 11:17 ` bugzilla-daemon
2015-10-17 14:06 ` bugzilla-daemon
2015-10-18 11:59 ` bugzilla-daemon
2015-10-19 11:16 ` bugzilla-daemon
2015-11-18 14:35 ` bugzilla-daemon
2015-11-18 14:36 ` bugzilla-daemon
2015-11-26 20:06 ` bugzilla-daemon
2015-11-26 20:07 ` bugzilla-daemon
2015-12-01 19:07 ` bugzilla-daemon
2015-12-01 19:08 ` bugzilla-daemon
2015-12-09 11:58 ` bugzilla-daemon
2015-12-09 12:27 ` bugzilla-daemon
2015-12-09 12:28 ` bugzilla-daemon
2015-12-09 15:05 ` bugzilla-daemon
2015-12-09 16:23 ` bugzilla-daemon
2015-12-09 16:28 ` bugzilla-daemon
2015-12-09 16:30 ` bugzilla-daemon
2015-12-09 16:35 ` bugzilla-daemon
2015-12-10  1:08 ` bugzilla-daemon
2015-12-10  5:40 ` bugzilla-daemon
2015-12-12 16:11 ` bugzilla-daemon
2015-12-12 16:12 ` bugzilla-daemon
2015-12-14 15:35 ` bugzilla-daemon
2015-12-14 17:36 ` bugzilla-daemon
2015-12-14 17:39 ` bugzilla-daemon
2015-12-18 19:42 ` bugzilla-daemon
2015-12-20 18:29 ` bugzilla-daemon
2015-12-21 13:34 ` bugzilla-daemon
2015-12-21 17:45 ` bugzilla-daemon
2015-12-25 22:50 ` bugzilla-daemon
2015-12-26  9:06 ` bugzilla-daemon
2015-12-27  0:32 ` bugzilla-daemon
2015-12-27  2:34 ` bugzilla-daemon
2015-12-27 10:46 ` bugzilla-daemon
2015-12-28 17:13 ` bugzilla-daemon
2016-01-12 15:39 ` bugzilla-daemon
2016-01-14  6:46 ` bugzilla-daemon
2016-01-14  6:52 ` bugzilla-daemon
2016-01-14 13:34 ` bugzilla-daemon
2016-01-14 20:47 ` bugzilla-daemon
2016-01-14 20:49 ` bugzilla-daemon
2016-01-14 20:49 ` bugzilla-daemon
2016-01-15  1:47 ` bugzilla-daemon
2016-01-15 12:13 ` bugzilla-daemon
2016-01-15 12:30 ` bugzilla-daemon
2016-01-16 14:00 ` bugzilla-daemon
2016-01-18  4:23 ` bugzilla-daemon
2016-01-19 15:13 ` bugzilla-daemon
2016-01-20  1:13 ` bugzilla-daemon
2016-01-20  4:32 ` bugzilla-daemon
2016-01-20 15:29 ` bugzilla-daemon
2016-01-20 17:12 ` bugzilla-daemon
2016-01-20 17:37 ` bugzilla-daemon
2016-01-20 17:51 ` bugzilla-daemon
2016-01-20 17:53 ` bugzilla-daemon
2016-01-20 18:11 ` bugzilla-daemon
2016-01-20 18:15 ` bugzilla-daemon
2016-01-20 18:31 ` bugzilla-daemon
2016-01-20 19:17 ` bugzilla-daemon
2016-01-20 20:48 ` bugzilla-daemon
2016-01-21 19:40 ` bugzilla-daemon
2016-01-22 17:01 ` bugzilla-daemon
2016-01-25 22:10 ` bugzilla-daemon
2016-01-25 23:12 ` bugzilla-daemon
2016-01-26  0:22 ` bugzilla-daemon
2016-01-26  2:21 ` bugzilla-daemon
2016-01-29 18:15 ` bugzilla-daemon
2016-01-29 21:40 ` bugzilla-daemon
2016-01-29 23:12 ` bugzilla-daemon
2016-01-29 23:12 ` bugzilla-daemon
2016-01-30  8:56 ` bugzilla-daemon
2016-01-31 13:33 ` bugzilla-daemon
2016-03-15 17:57 ` bugzilla-daemon
2016-03-15 18:12 ` bugzilla-daemon
2016-03-18 11:44 ` bugzilla-daemon
2016-03-21 17:31 ` bugzilla-daemon
2016-03-27 19:47 ` bugzilla-daemon
2016-03-31 18:01 ` bugzilla-daemon
2016-03-31 18:03 ` bugzilla-daemon
2016-03-31 18:34 ` bugzilla-daemon
2016-03-31 18:37 ` bugzilla-daemon
2016-04-03 17:34 ` bugzilla-daemon
2016-04-14  6:43 ` bugzilla-daemon
2016-04-20 18:59 ` bugzilla-daemon
2016-04-23 13:48 ` bugzilla-daemon
2016-05-02  4:05 ` bugzilla-daemon
2016-05-04 22:38 ` bugzilla-daemon
2016-05-04 23:36 ` bugzilla-daemon
2016-05-09  2:40 ` bugzilla-daemon
2016-05-09  2:53 ` bugzilla-daemon
2016-06-02  7:23 ` bugzilla-daemon
2016-06-02 14:54 ` bugzilla-daemon
2016-06-30  0:41 ` bugzilla-daemon
2016-07-17  6:26 ` bugzilla-daemon
2016-07-17 19:00 ` bugzilla-daemon
2016-07-17 20:18 ` bugzilla-daemon
2016-07-19 21:39 ` bugzilla-daemon
2016-07-20  1:39 ` bugzilla-daemon
2016-07-20  3:22 ` bugzilla-daemon
2016-07-20  3:28   ` Bridgman, John
2016-07-20 10:01 ` bugzilla-daemon
2016-07-23  1:57 ` bugzilla-daemon
2016-07-25 10:22 ` bugzilla-daemon
2016-08-02 19:19 ` bugzilla-daemon
2016-08-04  6:29 ` bugzilla-daemon
2016-08-11  9:03 ` bugzilla-daemon
2016-08-31 11:07 ` bugzilla-daemon
2016-09-19  2:36 ` bugzilla-daemon
2016-10-14 21:20 ` bugzilla-daemon
2016-10-28 19:25 ` bugzilla-daemon
2016-10-31 19:47 ` bugzilla-daemon
2016-10-31 19:49 ` bugzilla-daemon
2016-11-01 18:53 ` bugzilla-daemon
2016-11-02  9:52 ` bugzilla-daemon
2016-11-03  5:52 ` bugzilla-daemon
2016-11-03  9:45 ` bugzilla-daemon
2016-11-03 22:46 ` bugzilla-daemon
2016-11-30 13:42 ` bugzilla-daemon
2016-11-30 14:12 ` bugzilla-daemon
2016-12-04 23:11 ` bugzilla-daemon
2016-12-08 22:59 ` bugzilla-daemon
2016-12-08 23:25 ` bugzilla-daemon
2016-12-08 23:27 ` bugzilla-daemon
2016-12-09  1:15 ` bugzilla-daemon
2016-12-09  4:36 ` bugzilla-daemon
2016-12-10 21:13 ` bugzilla-daemon
2016-12-11  5:55 ` bugzilla-daemon
2016-12-11 11:12 ` bugzilla-daemon
2016-12-11 19:39 ` bugzilla-daemon
2016-12-11 21:39 ` bugzilla-daemon
2016-12-19 14:07 ` bugzilla-daemon
2016-12-20  2:13 ` bugzilla-daemon
2017-01-11  9:55 ` bugzilla-daemon
2017-01-14 14:36 ` bugzilla-daemon
2017-01-17 12:10 ` bugzilla-daemon
2017-03-16 11:37 ` bugzilla-daemon
2017-03-16 11:49 ` bugzilla-daemon
2017-04-18  7:58 ` bugzilla-daemon
2017-04-28 18:49 ` bugzilla-daemon
2017-05-19 22:25 ` bugzilla-daemon
2017-05-20 18:21 ` bugzilla-daemon
2017-05-30 20:50 ` bugzilla-daemon
2017-06-10 17:28 ` bugzilla-daemon
2017-07-08 18:29 ` bugzilla-daemon
2017-07-08 19:56 ` bugzilla-daemon
2017-08-13 15:57 ` bugzilla-daemon
2017-09-09 11:29 ` bugzilla-daemon
2017-09-09 12:01 ` bugzilla-daemon
2017-09-09 16:33 ` bugzilla-daemon
2017-09-09 18:47 ` bugzilla-daemon
2017-09-09 23:55 ` bugzilla-daemon
2017-09-10  0:00 ` bugzilla-daemon
2017-09-10  3:45 ` bugzilla-daemon
2017-09-10  3:50 ` bugzilla-daemon
2017-09-10  5:13 ` bugzilla-daemon
2017-09-10  5:39 ` bugzilla-daemon
2017-09-10  8:11 ` bugzilla-daemon
2017-09-10 11:47 ` bugzilla-daemon
2017-09-10 16:16 ` bugzilla-daemon
2017-09-13 22:41 ` bugzilla-daemon
2017-09-14  5:13 ` bugzilla-daemon
2017-09-14 13:08 ` bugzilla-daemon
2017-09-14 15:14 ` bugzilla-daemon
2017-09-14 15:18 ` bugzilla-daemon
2017-09-18 23:06 ` bugzilla-daemon
2017-09-25 13:19 ` bugzilla-daemon
2017-09-26 20:36 ` bugzilla-daemon
2018-01-11 14:56 ` bugzilla-daemon
2018-03-03  4:44 ` bugzilla-daemon
2018-03-13  5:49 ` bugzilla-daemon
2018-03-13  5:50 ` bugzilla-daemon
2018-03-13  5:50 ` bugzilla-daemon
2018-03-13 14:47 ` bugzilla-daemon
2018-03-18 20:31 ` bugzilla-daemon [this message]
2018-03-19 16:23 ` bugzilla-daemon
2018-05-03 23:11 ` bugzilla-daemon
2018-05-04  3:08 ` bugzilla-daemon
2018-05-06 18:29 ` bugzilla-daemon
2018-05-07 15:02 ` bugzilla-daemon
2018-05-07 18:23 ` bugzilla-daemon
2018-05-07 22:31 ` bugzilla-daemon
2018-05-11 21:36 ` bugzilla-daemon
2018-05-11 21:38 ` bugzilla-daemon
2018-05-11 22:13 ` bugzilla-daemon
2018-05-11 22:15 ` bugzilla-daemon
2018-05-12 13:11 ` bugzilla-daemon
2018-05-13 20:21 ` bugzilla-daemon
2018-05-13 20:40 ` bugzilla-daemon
2018-05-13 20:49 ` bugzilla-daemon
2018-05-14 18:54 ` bugzilla-daemon
2018-06-01 23:11 ` bugzilla-daemon
2018-08-04  0:50 ` bugzilla-daemon
2018-08-16 22:46 ` bugzilla-daemon
2018-08-18  8:34 ` bugzilla-daemon
2018-08-18 10:09 ` bugzilla-daemon
2018-08-18 10:13 ` bugzilla-daemon
2018-08-19  4:29 ` bugzilla-daemon
2018-08-19 17:23 ` bugzilla-daemon
2018-08-19 19:03 ` bugzilla-daemon
2019-09-25 17:53 ` 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-91880-502-EDN4kkYkrf@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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).