From: Mario Limonciello <mario.limonciello@amd.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>, casteyde.christian@free.fr
Cc: stable@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
regressions@lists.linux.dev,
alexander deucher <alexander.deucher@amd.com>,
gregkh@linuxfoundation.org
Subject: Re: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3)
Date: Tue, 17 May 2022 21:19:49 -0500 [thread overview]
Message-ID: <4dc0d1e4-7e74-f85a-d8af-fdcd862d8a4a@amd.com> (raw)
In-Reply-To: <CAAd53p69LqeH7pD2S4T-D4i_+PEaejb12kx7rbapPrPCfQ9-iQ@mail.gmail.com>
On 5/17/22 21:08, Kai-Heng Feng wrote:
> On Wed, May 18, 2022 at 1:38 AM <casteyde.christian@free.fr> wrote:
>>
>> dmesg logs
>
> Actually, the "good" is still no good:
> [ 43.375323] PM: suspend entry (deep)
> ...
> [ 43.695342] PM: late suspend of devices failed
> ...
> [ 44.554108] PM: suspend exit
> [ 44.554168] PM: suspend entry (s2idle)
>
> So we need to find out why the suspend failed at first place.
>
I noticed that too; but the patch I suggested will completely avoid the
GPU reset for the APU, which is my guess at why this suspend fails in
the first place even in "good" scenario.
> Kai-Heng
>
>>
>> ----- Mail original -----
>> De: "Kai-Heng Feng" <kai.heng.feng@canonical.com>
>> À: "Christian Casteyde" <casteyde.christian@free.fr>
>> Cc: stable@vger.kernel.org, "Thorsten Leemhuis" <regressions@leemhuis.info>, regressions@lists.linux.dev, "alexander deucher" <alexander.deucher@amd.com>, gregkh@linuxfoundation.org, "Mario Limonciello" <mario.limonciello@amd.com>
>> Envoyé: Mardi 17 Mai 2022 08:58:30
>> Objet: Re: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3)
>>
>> On Tue, May 17, 2022 at 2:36 PM Christian Casteyde
>> <casteyde.christian@free.fr> wrote:
>>>
>>> No, the problem is there even without acpicall. Fyi I use it to shutdown the NVidia card that eats the battery otherwise.
>>>
>>> I managed to get a dmesg output with 2.18rc7 I will post it this evening (basically exact same behavior as 2.17.4).
>>
>> Can you please also attach dmesg without the offending commit (i.e.
>> when it's working)?
>>
>> Kai-Heng
>>
>>>
>>> CC
>>>
>>> Télécharger BlueMail pour Android
>>>
>>> Le 17 mai 2022 à 04:03, à 04:03, Kai-Heng Feng <kai.heng.feng@canonical.com> a écrit:
>>>> On Tue, May 17, 2022 at 1:23 AM Christian Casteyde
>>>> <casteyde.christian@free.fr> wrote:
>>>>>
>>>>> I've tried with 5.18-rc7, it doesn't work either. I guess 5.18 branch
>>>> have all
>>>>> commits.
>>>>>
>>>>> full dmesg appended (not for 5.18, I didn't manage to resume up to
>>>> the point
>>>>> to get a console for now).
>>>>
>>>> Interestingly, I found you are using acpi_call:
>>>> [ 30.667348] acpi_call: loading out-of-tree module taints kernel.
>>>>
>>>> Does removing the acpi_call solve the issue?
>>>>
>>>> Kai-Heng
>>>>
>>>>>
>>>>> CC
>>>>>
>>>>> Le lundi 16 mai 2022, 04:47:25 CEST Kai-Heng Feng a écrit :
>>>>>> [+Cc Mario]
>>>>>>
>>>>>> On Sun, May 15, 2022 at 1:34 AM Christian Casteyde
>>>>>>
>>>>>> <casteyde.christian@free.fr> wrote:
>>>>>>> I've applied the commit a56f445f807b0276 on 5.17.7 and tested.
>>>>>>> This does not fix the problem on my laptop.
>>>>>>
>>>>>> Maybe some commits are still missing?
>>>>>>
>>>>>>> For informatio, here is a part of the log around the suspend
>>>> process:
>>>>>> Is it possible to attach full dmesg?
>>>>>>
>>>>>> Kai-Heng
>>>>>>
>>>>>>> May 14 19:21:41 geek500 kernel: snd_hda_intel 0000:01:00.1: can't
>>>> change
>>>>>>> power state from D3cold to D0 (config space inaccessible)
>>>>>>> May 14 19:21:41 geek500 kernel: PM: late suspend of devices
>>>> failed
>>>>>>> May 14 19:21:41 geek500 kernel: ------------[ cut here
>>>> ]------------
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_designware AMDI0010:03:
>>>> Transfer while
>>>>>>> suspended
>>>>>>> May 14 19:21:41 geek500 kernel: pci 0000:00:00.2: can't derive
>>>> routing for
>>>>>>> PCI INT A
>>>>>>> May 14 19:21:41 geek500 kernel: pci 0000:00:00.2: PCI INT A: no
>>>> GSI
>>>>>>> May 14 19:21:41 geek500 kernel: WARNING: CPU: 9 PID: 1972 at
>>>> drivers/i2c/
>>>>>>> busses/i2c-designware-master.c:570 i2c_dw_xfer+0x3f6/0x440
>>>>>>> May 14 19:21:41 geek500 kernel: Modules linked in: [last
>>>> unloaded:
>>>>>>> acpi_call] May 14 19:21:41 geek500 kernel: CPU: 9 PID: 1972 Comm:
>>>>>>> kworker/u32:18 Tainted: G O 5.17.7+ #7
>>>>>>> May 14 19:21:41 geek500 kernel: Hardware name: HP HP Pavilion
>>>> Gaming
>>>>>>> Laptop
>>>>>>> 15-ec1xxx/87B2, BIOS F.25 08/18/2021
>>>>>>> May 14 19:21:41 geek500 kernel: Workqueue: events_unbound
>>>>>>> async_run_entry_fn May 14 19:21:41 geek500 kernel: RIP:
>>>>>>> 0010:i2c_dw_xfer+0x3f6/0x440
>>>>>>> May 14 19:21:41 geek500 kernel: Code: c6 05 db 31 45 01 01 4c 8b
>>>> 67 50 4d
>>>>>>> 85 e4 75 03 4c 8b 27 e8 fc e1 e9 ff 4c 89 e2 48 c7 c7 00 01 cc
>>>>>>>
>>>>>>> ab 48 89 c6 e8 b3 4f 45 00 <0f> 0b 41 be 94 ff ff ff e9 cc fc ff
>>>> ff e9 2d
>>>>>>> 9c>
>>>>>>> 4b 00 83 f8 01 74
>>>>>>> May 14 19:21:41 geek500 kernel: RSP: 0018:ffff8dbfc31e7c68
>>>> EFLAGS:
>>>>>>> 00010286
>>>>>>> May 14 19:21:41 geek500 kernel: RAX: 0000000000000000 RBX:
>>>>>>> ffff888540f170e8
>>>>>>> RCX: 0000000000000be5
>>>>>>> May 14 19:21:41 geek500 kernel: RDX: 0000000000000000 RSI:
>>>>>>> 0000000000000086
>>>>>>> RDI: ffffffffac858df8
>>>>>>> May 14 19:21:41 geek500 kernel: RBP: ffff888540f170e8 R08:
>>>>>>> ffffffffabe46d60
>>>>>>> R09: 00000000ac86a0f6
>>>>>>> May 14 19:21:41 geek500 kernel: R10: ffffffffffffffff R11:
>>>>>>> ffffffffffffffff
>>>>>>> R12: ffff888540f5c070
>>>>>>> May 14 19:21:41 geek500 kernel: R13: ffff8dbfc31e7d70 R14:
>>>>>>> 00000000ffffff94
>>>>>>> R15: ffff888540f17028
>>>>>>> May 14 19:21:41 geek500 kernel: FS: 0000000000000000(0000)
>>>>>>> GS:ffff88885f640000(0000) knlGS:0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>>>>>>> 0000000080050033
>>>>>>> May 14 19:21:41 geek500 kernel: CR2: 00007f1984067028 CR3:
>>>>>>> 0000000045e0c000
>>>>>>> CR4: 0000000000350ee0
>>>>>>> May 14 19:21:41 geek500 kernel: Call Trace:
>>>>>>> May 14 19:21:41 geek500 kernel: <TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ? dequeue_entity+0xd4/0x250
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> newidle_balance.constprop.0+0x1f7/0x3b0
>>>>>>> May 14 19:21:41 geek500 kernel: __i2c_transfer+0x16d/0x520
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_transfer+0x7a/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: __i2c_hid_command+0x106/0x2d0
>>>>>>> May 14 19:21:41 geek500 kernel: ? amd_gpio_irq_enable+0x19/0x50
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_hid_set_power+0x4a/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_hid_core_resume+0x60/0xb0
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> acpi_subsys_resume_early+0x50/0x50
>>>>>>> May 14 19:21:41 geek500 kernel: dpm_run_callback+0x1d/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: device_resume+0x122/0x230
>>>>>>> May 14 19:21:41 geek500 kernel: async_resume+0x14/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: async_run_entry_fn+0x1b/0xa0
>>>>>>> May 14 19:21:41 geek500 kernel: process_one_work+0x1d3/0x3a0
>>>>>>> May 14 19:21:41 geek500 kernel: worker_thread+0x48/0x3c0
>>>>>>> May 14 19:21:41 geek500 kernel: ? rescuer_thread+0x380/0x380
>>>>>>> May 14 19:21:41 geek500 kernel: kthread+0xd3/0x100
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> kthread_complete_and_exit+0x20/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ret_from_fork+0x22/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: </TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ---[ end trace 0000000000000000
>>>> ]---
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_hid_acpi i2c-ELAN0718:00:
>>>> failed to
>>>>>>> change power setting.
>>>>>>> May 14 19:21:41 geek500 kernel: PM: dpm_run_callback():
>>>>>>> acpi_subsys_resume+0x0/0x50 returns -108
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_hid_acpi i2c-ELAN0718:00: PM:
>>>> failed
>>>>>>> to
>>>>>>> resume async: error -108
>>>>>>> May 14 19:21:41 geek500 kernel: amdgpu 0000:05:00.0:
>>>>>>> [drm:amdgpu_ring_test_helper] *ERROR* ring gfx test failed (-110)
>>>>>>> May 14 19:21:41 geek500 kernel:
>>>> [drm:amdgpu_device_ip_resume_phase2]
>>>>>>> *ERROR* resume of IP block <gfx_v9_0> failed -110
>>>>>>> May 14 19:21:41 geek500 kernel: amdgpu 0000:05:00.0: amdgpu:
>>>>>>> amdgpu_device_ip_resume failed (-110).
>>>>>>> May 14 19:21:41 geek500 kernel: PM: dpm_run_callback():
>>>>>>> pci_pm_resume+0x0/0x120 returns -110
>>>>>>> May 14 19:21:41 geek500 kernel: amdgpu 0000:05:00.0: PM: failed
>>>> to resume
>>>>>>> async: error -110
>>>>>>> May 14 19:21:41 geek500 kernel: ------------[ cut here
>>>> ]------------
>>>>>>> May 14 19:21:41 geek500 kernel: AMDI0010:03 already disabled
>>>>>>> May 14 19:21:41 geek500 kernel: WARNING: CPU: 6 PID: 1091 at
>>>> drivers/clk/
>>>>>>> clk.c:971 clk_core_disable+0x80/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Modules linked in: [last
>>>> unloaded:
>>>>>>> acpi_call] May 14 19:21:41 geek500 kernel: CPU: 6 PID: 1091 Comm:
>>>>>>> kworker/6:3 Tainted: G W O 5.17.7+ #7
>>>>>>> May 14 19:21:41 geek500 kernel: Hardware name: HP HP Pavilion
>>>> Gaming
>>>>>>> Laptop
>>>>>>> 15-ec1xxx/87B2, BIOS F.25 08/18/2021
>>>>>>> May 14 19:21:41 geek500 kernel: Workqueue: pm pm_runtime_work
>>>>>>> May 14 19:21:41 geek500 kernel: RIP:
>>>> 0010:clk_core_disable+0x80/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Code: 10 e8 e4 4a d1 00 0f 1f 44
>>>> 00 00 48
>>>>>>> 8b 5b 30 48 85 db 74 b6 8b 43 7c 85 c0 75 a4 48 8b 33 48 c7 c7 7d
>>>> 87 c4
>>>>>>> ab e8 79 7a 9a 00 <0f> 0b 5b 5d c3 65 8b 05 5c a1 92 55 89 c0 48
>>>> 0f a3 05
>>>>>>> 4a 61 9d 01 May 14 19:21:41 geek500 kernel: RSP:
>>>> 0018:ffff8dbfc1c47d50
>>>>>>> EFLAGS: 00010082 May 14 19:21:41 geek500 kernel:
>>>>>>> May 14 19:21:41 geek500 kernel: RAX: 0000000000000000 RBX:
>>>>>>> ffff8885401b6300
>>>>>>> RCX: 0000000000000027
>>>>>>> May 14 19:21:41 geek500 kernel: RDX: ffff88885f59f468 RSI:
>>>>>>> 0000000000000001
>>>>>>> RDI: ffff88885f59f460
>>>>>>> May 14 19:21:41 geek500 kernel: RBP: 0000000000000283 R08:
>>>>>>> ffffffffabf26da8
>>>>>>> R09: 00000000ffffdfff
>>>>>>> May 14 19:21:41 geek500 kernel: R10: ffffffffabe46dc0 R11:
>>>>>>> ffffffffabe46dc0
>>>>>>> R12: ffff8885401b6300
>>>>>>> May 14 19:21:41 geek500 kernel: R13: ffff888540fc30f4 R14:
>>>>>>> 0000000000000008
>>>>>>> R15: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: FS: 0000000000000000(0000)
>>>>>>> GS:ffff88885f580000(0000) knlGS:0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>>>>>>> 0000000080050033
>>>>>>> May 14 19:21:41 geek500 kernel: CR2: 00000000010fa990 CR3:
>>>>>>> 0000000102956000
>>>>>>> CR4: 0000000000350ee0
>>>>>>> May 14 19:21:41 geek500 kernel: Call Trace:
>>>>>>> May 14 19:21:41 geek500 kernel: <TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: clk_disable+0x24/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_dw_prepare_clk+0x74/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: dw_i2c_plat_suspend+0x2e/0x40
>>>>>>> May 14 19:21:41 geek500 kernel:
>>>> acpi_subsys_runtime_suspend+0x9/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: __rpm_callback+0x3f/0x150
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_callback+0x54/0x60
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_suspend+0x142/0x720
>>>>>>> May 14 19:21:41 geek500 kernel: pm_runtime_work+0x8f/0xa0
>>>>>>> May 14 19:21:41 geek500 kernel: process_one_work+0x1d3/0x3a0
>>>>>>> May 14 19:21:41 geek500 kernel: worker_thread+0x48/0x3c0
>>>>>>> May 14 19:21:41 geek500 kernel: ? rescuer_thread+0x380/0x380
>>>>>>> May 14 19:21:41 geek500 kernel: kthread+0xd3/0x100
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> kthread_complete_and_exit+0x20/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ret_from_fork+0x22/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: </TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ---[ end trace 0000000000000000
>>>> ]---
>>>>>>> May 14 19:21:41 geek500 kernel: ------------[ cut here
>>>> ]------------
>>>>>>> May 14 19:21:41 geek500 kernel: AMDI0010:03 already unprepared
>>>>>>> May 14 19:21:41 geek500 kernel: WARNING: CPU: 6 PID: 1091 at
>>>> drivers/clk/
>>>>>>> clk.c:829 clk_core_unprepare+0xb1/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Modules linked in: [last
>>>> unloaded:
>>>>>>> acpi_call] May 14 19:21:41 geek500 kernel: CPU: 6 PID: 1091 Comm:
>>>>>>> kworker/6:3 Tainted: G W O 5.17.7+ #7
>>>>>>> May 14 19:21:41 geek500 kernel: Hardware name: HP HP Pavilion
>>>> Gaming
>>>>>>> Laptop
>>>>>>> 15-ec1xxx/87B2, BIOS F.25 08/18/2021
>>>>>>> May 14 19:21:41 geek500 kernel: Workqueue: pm pm_runtime_work
>>>>>>> May 14 19:21:41 geek500 kernel: RIP:
>>>> 0010:clk_core_unprepare+0xb1/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Code: 40 00 66 90 48 8b 5b 30 48
>>>> 85 db 74
>>>>>>> a2 8b 83 80 00 00 00 85 c0 0f 85 79 ff ff ff 48 8b 33 48 c7 c7 35
>>>> 87 c4
>>>>>>> ab e8 18 7c 9a 00 <0f> 0b 5b c3 65 8b 05 fc a2 92 55 89 c0 48 0f
>>>> a3 05 ea
>>>>>>> 62 9d 01 73 May 14 19:21:41 geek500 kernel: RSP:
>>>> 0018:ffff8dbfc1c47d60
>>>>>>> EFLAGS: 00010286 May 14 19:21:41 geek500 kernel: RAX:
>>>> 0000000000000000
>>>>>>> RBX: ffff8885401b6300 RCX: 0000000000000027
>>>>>>> May 14 19:21:41 geek500 kernel: RDX: ffff88885f59f468 RSI:
>>>>>>> 0000000000000001
>>>>>>> RDI: ffff88885f59f460
>>>>>>> May 14 19:21:41 geek500 kernel: RBP: ffff8885401b6300 R08:
>>>>>>> ffffffffabf26da8
>>>>>>> R09: 00000000ffffdfff
>>>>>>> May 14 19:21:41 geek500 kernel: R10: ffffffffabe46dc0 R11:
>>>>>>> ffffffffabe46dc0
>>>>>>> R12: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: R13: ffff888540fc30f4 R14:
>>>>>>> 0000000000000008
>>>>>>> R15: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: FS: 0000000000000000(0000)
>>>>>>> GS:ffff88885f580000(0000) knlGS:0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>>>>>>> 0000000080050033
>>>>>>> May 14 19:21:41 geek500 kernel: CR2: 00000000010fa990 CR3:
>>>>>>> 0000000102956000
>>>>>>> CR4: 0000000000350ee0
>>>>>>> May 14 19:21:41 geek500 kernel: Call Trace:
>>>>>>> May 14 19:21:41 geek500 kernel: <TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: clk_unprepare+0x1f/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_dw_prepare_clk+0x7c/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: dw_i2c_plat_suspend+0x2e/0x40
>>>>>>> May 14 19:21:41 geek500 kernel:
>>>> acpi_subsys_runtime_suspend+0x9/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: __rpm_callback+0x3f/0x150
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: done.
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_callback+0x54/0x60
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_suspend+0x142/0x720
>>>>>>> May 14 19:21:41 geek500 kernel: pm_runtime_work+0x8f/0xa0
>>>>>>> May 14 19:21:41 geek500 kernel: process_one_work+0x1d3/0x3a0
>>>>>>> May 14 19:21:41 geek500 kernel: worker_thread+0x48/0x3c0
>>>>>>> May 14 19:21:41 geek500 kernel: ? rescuer_thread+0x380/0x380
>>>>>>> May 14 19:21:41 geek500 kernel: kthread+0xd3/0x100
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> kthread_complete_and_exit+0x20/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ret_from_fork+0x22/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: </TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ---[ end trace 0000000000000000
>>>> ]---
>>>>>>> May 14 19:21:41 geek500 kernel: ------------[ cut here
>>>> ]------------
>>>>>>> May 14 19:21:41 geek500 kernel: AMDI0010:03 already disabled
>>>>>>> May 14 19:21:41 geek500 kernel: WARNING: CPU: 6 PID: 1091 at
>>>> drivers/clk/
>>>>>>> clk.c:971 clk_core_disable+0x80/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Modules linked in: [last
>>>> unloaded:
>>>>>>> acpi_call] May 14 19:21:41 geek500 kernel: CPU: 6 PID: 1091 Comm:
>>>>>>> kworker/6:3 Tainted: G W O 5.17.7+ #7
>>>>>>> May 14 19:21:41 geek500 kernel: Hardware name: HP HP Pavilion
>>>> Gaming
>>>>>>> Laptop
>>>>>>> 15-ec1xxx/87B2, BIOS F.25 08/18/2021
>>>>>>> May 14 19:21:41 geek500 kernel: Workqueue: pm pm_runtime_work
>>>>>>> May 14 19:21:41 geek500 kernel: RIP:
>>>> 0010:clk_core_disable+0x80/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Code: 10 e8 e4 4a d1 00 0f 1f 44
>>>> 00 00 48
>>>>>>> 8b 5b 30 48 85 db 74 b6 8b 43 7c 85 c0 75 a4 48 8b 33 48 c7 c7 7d
>>>> 87 c4
>>>>>>> ab e8 79 7a 9a 00 <0f> 0b 5b 5d c3 65 8b 05 5c a1 92 55 89 c0 48
>>>> 0f a3 05
>>>>>>> 4a 61 9d 01 May 14 19:21:41 geek500 kernel: RSP:
>>>> 0018:ffff8dbfc1c47d50
>>>>>>> EFLAGS: 00010082 May 14 19:21:41 geek500 kernel: RAX:
>>>> 0000000000000000
>>>>>>> RBX: ffff8885401b6300 RCX: 0000000000000027
>>>>>>> May 14 19:21:41 geek500 kernel: RDX: ffff88885f59f468 RSI:
>>>>>>> 0000000000000001
>>>>>>> RDI: ffff88885f59f460
>>>>>>> May 14 19:21:41 geek500 kernel: RBP: 0000000000000287 R08:
>>>>>>> ffffffffabf26da8
>>>>>>> R09: 00000000ffffdfff
>>>>>>> May 14 19:21:41 geek500 kernel: R10: ffffffffabe46dc0 R11:
>>>>>>> ffffffffabe46dc0
>>>>>>> R12: ffff8885401b6300
>>>>>>> May 14 19:21:41 geek500 kernel: R13: ffff888540fc30f4 R14:
>>>>>>> 0000000000000008
>>>>>>> R15: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: FS: 0000000000000000(0000)
>>>>>>> GS:ffff88885f580000(0000) knlGS:0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>>>>>>> 0000000080050033
>>>>>>> May 14 19:21:41 geek500 kernel: CR2: 00000000010fa990 CR3:
>>>>>>> 0000000102956000
>>>>>>> CR4: 0000000000350ee0
>>>>>>> May 14 19:21:41 geek500 kernel: Call Trace:
>>>>>>> May 14 19:21:41 geek500 kernel: <TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: clk_disable+0x24/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_dw_prepare_clk+0x88/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: dw_i2c_plat_suspend+0x2e/0x40
>>>>>>> May 14 19:21:41 geek500 kernel:
>>>> acpi_subsys_runtime_suspend+0x9/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: __rpm_callback+0x3f/0x150
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_callback+0x54/0x60
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_suspend+0x142/0x720
>>>>>>> May 14 19:21:41 geek500 kernel: pm_runtime_work+0x8f/0xa0
>>>>>>> May 14 19:21:41 geek500 kernel: process_one_work+0x1d3/0x3a0
>>>>>>> May 14 19:21:41 geek500 kernel: worker_thread+0x48/0x3c0
>>>>>>> May 14 19:21:41 geek500 kernel: ? rescuer_thread+0x380/0x380
>>>>>>> May 14 19:21:41 geek500 kernel: kthread+0xd3/0x100
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> kthread_complete_and_exit+0x20/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ret_from_fork+0x22/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: </TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ---[ end trace 0000000000000000
>>>> ]---
>>>>>>> May 14 19:21:41 geek500 kernel: ------------[ cut here
>>>> ]------------
>>>>>>> May 14 19:21:41 geek500 kernel: AMDI0010:03 already unprepared
>>>>>>> May 14 19:21:41 geek500 kernel: WARNING: CPU: 6 PID: 1091 at
>>>> drivers/clk/
>>>>>>> clk.c:829 clk_core_unprepare+0xb1/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Modules linked in: [last
>>>> unloaded:
>>>>>>> acpi_call] May 14 19:21:41 geek500 kernel: CPU: 6 PID: 1091 Comm:
>>>>>>> kworker/6:3 Tainted: G W O 5.17.7+ #7
>>>>>>> May 14 19:21:41 geek500 kernel: Hardware name: HP HP Pavilion
>>>> Gaming
>>>>>>> Laptop
>>>>>>> 15-ec1xxx/87B2, BIOS F.25 08/18/2021
>>>>>>> May 14 19:21:41 geek500 kernel: Workqueue: pm pm_runtime_work
>>>>>>> May 14 19:21:41 geek500 kernel: RIP:
>>>> 0010:clk_core_unprepare+0xb1/0x1a0
>>>>>>> May 14 19:21:41 geek500 kernel: Code: 40 00 66 90 48 8b 5b 30 48
>>>> 85 db 74
>>>>>>> a2 8b 83 80 00 00 00 85 c0 0f 85 79 ff ff ff 48 8b 33 48 c7 c7 35
>>>> 87 c4
>>>>>>> ab e8 18 7c 9a 00 <0f> 0b 5b c3 65 8b 05 fc a2 92 55 89 c0 48 0f
>>>> a3 05 ea
>>>>>>> 62 9d 01 73 May 14 19:21:41 geek500 kernel: RSP:
>>>> 0018:ffff8dbfc1c47d60
>>>>>>> EFLAGS: 00010286 May 14 19:21:41 geek500 kernel: RAX:
>>>> 0000000000000000
>>>>>>> RBX: ffff8885401b6300 RCX: 0000000000000027
>>>>>>> May 14 19:21:41 geek500 kernel: RDX: ffff88885f59f468 RSI:
>>>>>>> 0000000000000001
>>>>>>> RDI: ffff88885f59f460
>>>>>>> May 14 19:21:41 geek500 kernel: RBP: ffff8885401b6300 R08:
>>>>>>> ffffffffabf26da8
>>>>>>> R09: 00000000ffffdfff
>>>>>>> May 14 19:21:41 geek500 kernel: R10: ffffffffabe46dc0 R11:
>>>>>>> ffffffffabe46dc0
>>>>>>> R12: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: R13: ffff888540fc30f4 R14:
>>>>>>> 0000000000000008
>>>>>>> R15: 0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: FS: 0000000000000000(0000)
>>>>>>> GS:ffff88885f580000(0000) knlGS:0000000000000000
>>>>>>> May 14 19:21:41 geek500 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
>>>>>>> 0000000080050033
>>>>>>> May 14 19:21:41 geek500 kernel: CR2: 00000000010fa990 CR3:
>>>>>>> 0000000102956000
>>>>>>> CR4: 0000000000350ee0
>>>>>>> May 14 19:21:41 geek500 kernel: Call Trace:
>>>>>>> May 14 19:21:41 geek500 kernel: <TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: clk_unprepare+0x1f/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: i2c_dw_prepare_clk+0x90/0xd0
>>>>>>> May 14 19:21:41 geek500 kernel: dw_i2c_plat_suspend+0x2e/0x40
>>>>>>> May 14 19:21:41 geek500 kernel:
>>>> acpi_subsys_runtime_suspend+0x9/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: __rpm_callback+0x3f/0x150
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_callback+0x54/0x60
>>>>>>> May 14 19:21:41 geek500 kernel: ? acpi_dev_suspend+0x160/0x160
>>>>>>> May 14 19:21:41 geek500 kernel: rpm_suspend+0x142/0x720
>>>>>>> May 14 19:21:41 geek500 kernel: pm_runtime_work+0x8f/0xa0
>>>>>>> May 14 19:21:41 geek500 kernel: process_one_work+0x1d3/0x3a0
>>>>>>> May 14 19:21:41 geek500 kernel: worker_thread+0x48/0x3c0
>>>>>>> May 14 19:21:41 geek500 kernel: ? rescuer_thread+0x380/0x380
>>>>>>> May 14 19:21:41 geek500 kernel: kthread+0xd3/0x100
>>>>>>> May 14 19:21:41 geek500 kernel: ?
>>>> kthread_complete_and_exit+0x20/0x20
>>>>>>> May 14 19:21:41 geek500 kernel: ret_from_fork+0x22/0x30
>>>>>>> May 14 19:21:41 geek500 kernel: </TASK>
>>>>>>> May 14 19:21:41 geek500 kernel: ---[ end trace 0000000000000000
>>>> ]---
>>>>>>> May 14 19:21:59 geek500 kernel: snd_hda_codec_hdmi hdaudioC1D0:
>>>> Unable to
>>>>>>> sync register 0x4f0800. -5
>>>>>>> May 14 19:21:59 geek500 kernel: (elapsed 0.175 seconds) done.
>>>>>>> May 14 19:21:59 geek500 kernel: amdgpu 0000:05:00.0: amdgpu:
>>>> Power
>>>>>>> consumption will be higher as BIOS has not been configured for
>>>>>>> suspend-to-idle. To use suspend-to-idle change the sleep mode in
>>>> BIOS
>>>>>>> setup.
>>>>>>> May 14 19:21:59 geek500 kernel: snd_hda_intel 0000:01:00.1: can't
>>>> change
>>>>>>> power state from D3cold to D0 (config space inaccessible)
>>>>>>> May 14 19:21:59 geek500 kernel: pci 0000:00:00.2: can't derive
>>>> routing for
>>>>>>> PCI INT A
>>>>>>> May 14 19:21:59 geek500 kernel: pci 0000:00:00.2: PCI INT A: no
>>>> GSI
>>>>>>> May 14 19:21:59 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:21:59 geek500 kernel: Bluetooth: hci0: command
>>>> 0xfc20 tx
>>>>>>> timeout May 14 19:21:59 geek500 kernel: [drm] Fence fallback
>>>> timer
>>>>>>> expired on ring sdma0
>>>>>>> May 14 19:21:59 geek500 kernel: Bluetooth: hci0: RTL: download fw
>>>> command
>>>>>>> failed (-110)
>>>>>>> May 14 19:21:59 geek500 kernel: done.
>>>>>>> May 14 19:22:00 geek500 kernel: snd_hda_codec_hdmi hdaudioC1D0:
>>>> Unable to
>>>>>>> sync register 0x4f0800. -5
>>>>>>> May 14 19:22:00 geek500 dnsmasq[2079]: no servers found in
>>>> /etc/dnsmasq.d/
>>>>>>> dnsmasq-resolv.conf, will retry
>>>>>>> May 14 19:22:01 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> sdma0
>>>>>>> May 14 19:22:01 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:01 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:02 geek500 last message buffered 2 times
>>>>>>> May 14 19:22:03 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:03 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:03 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:03 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:04 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:04 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:04 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:04 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:05 geek500 last message buffered 2 times
>>>>>>> May 14 19:22:05 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:06 geek500 kernel: [drm] Fence fallback timer
>>>> expired on
>>>>>>> ring sdma0
>>>>>>> May 14 19:22:06 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> gfx May 14 19:22:06 geek500 last message buffered 1 times
>>>>>>> ...
>>>>>>> May 14 19:22:18 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> sdma0
>>>>>>> May 14 19:22:18 geek500 kernel:
>>>> [drm:amdgpu_dm_atomic_commit_tail] *ERROR*
>>>>>>> Waiting for fences timed out!
>>>>>>> May 14 19:22:18 geek500 kernel: [drm] Fence fallback timer
>>>> expired on ring
>>>>>>> sdma0
>>>>>>>
>>>>>>> CC
>>>>>>>
>>>>>>> Le samedi 14 mai 2022, 17:12:33 CEST Thorsten Leemhuis a écrit :
>>>>>>>> Hi, this is your Linux kernel regression tracker. Thanks for
>>>> the report.
>>>>>>>>
>>>>>>>> On 14.05.22 16:41, Christian Casteyde wrote:
>>>>>>>>> #regzbot introduced v5.17.3..v5.17.4
>>>>>>>>> #regzbot introduced: 001828fb3084379f3c3e228b905223c50bc237f9
>>>>>>>>
>>>>>>>> FWIW, that's commit 887f75cfd0da ("drm/amdgpu: Ensure HDA
>>>> function is
>>>>>>>> suspended before ASIC reset") upstream.
>>>>>>>>
>>>>>>>> Recently a regression was reported where 887f75cfd0da was
>>>> suspected as
>>>>>>>> the culprit:
>>>>>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F2008&data=05%7C01%7Cmario.limonciello%40amd.com%7C9f81b636194e44c69fb908da387358f3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637884365323647690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Np%2FMfai9ObN6w3RncSlT3%2FjQNJtzzmY0LL4qK0hVo2k%3D&reserved=0
>>>>>>>>
>>>>>>>> And a one related to it:
>>>>>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1982&data=05%7C01%7Cmario.limonciello%40amd.com%7C9f81b636194e44c69fb908da387358f3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637884365323647690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=kJXaC7bE3TSphzokMt4sG7xUd3Pi7VrNFYPr9DKrBrk%3D&reserved=0
>>>>>>>>
>>>>>>>> You might want to take a look if what was discussed there might
>>>> be
>>>>>>>> related to your problem (I'm not directly involved in any of
>>>> this, I
>>>>>>>> don't know the details, it's just that 887f75cfd0da looked
>>>> familiar to
>>>>>>>> me). If it is, a fix for these two bugs was committed to master
>>>> earlier
>>>>>>>> this week:
>>>>>>>>
>>>>>>>>
>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git%2Fcommi&data=05%7C01%7Cmario.limonciello%40amd.com%7C9f81b636194e44c69fb908da387358f3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637884365323647690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZD%2BXimGGTHtXIvQfHwSh4kwIln6oJxe4ppjwcrBncHY%3D&reserved=0
>>>>>>>> t/?i d=a56f445f807b0276
>>>>>>>>
>>>>>>>> It will likely be backported to 5.17.y, maybe already in the
>>>> over-next
>>>>>>>> release. HTH.
>>>>>>>>
>>>>>>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression
>>>> tracker' hat)
>>>>>>>>
>>>>>>>> P.S.: As the Linux kernel's regression tracker I deal with a
>>>> lot of
>>>>>>>> reports and sometimes miss something important when writing
>>>> mails like
>>>>>>>> this. If that's the case here, don't hesitate to tell me in a
>>>> public
>>>>>>>> reply, it's in everyone's interest to set the public record
>>>> straight.
>>>>>>>>
>>>>>>>>> Hello
>>>>>>>>> Since 5.17.4 my laptop doesn't resume from suspend anymore.
>>>> At resume,
>>>>>>>>> symptoms are variable:
>>>>>>>>> - either the laptop freezes;
>>>>>>>>> - either the screen keeps blank;
>>>>>>>>> - either the screen is OK but mouse is frozen;
>>>>>>>>> - either display lags with several logs in dmesg:
>>>>>>>>> [ 228.275492] [drm] Fence fallback timer expired on ring gfx
>>>>>>>>> [ 228.395466] [drm:amdgpu_dm_atomic_commit_tail] *ERROR*
>>>> Waiting for
>>>>>>>>> fences timed out!
>>>>>>>>> [ 228.779490] [drm] Fence fallback timer expired on ring gfx
>>>>>>>>> [ 229.283484] [drm] Fence fallback timer expired on ring
>>>> sdma0
>>>>>>>>> [ 229.283485] [drm] Fence fallback timer expired on ring gfx
>>>>>>>>> [ 229.787487] [drm] Fence fallback timer expired on ring gfx
>>>>>>>>> ...
>>>>>>>>>
>>>>>>>>> I've bisected the problem.
>>>>>>>>>
>>>>>>>>> Please note this laptop has a strange behaviour on suspend:
>>>>>>>>> The first suspend request always fails (this point has never
>>>> been
>>>>>>>>> fixed
>>>>>>>>> and
>>>>>>>>> plagues us when trying to diagnose another regression on
>>>> touchpad not
>>>>>>>>> resuming in the past). The screen goes blank and I can get it
>>>> OK when
>>>>>>>>> pressing the power button, this seems to reset it. After that
>>>> all
>>>>>>>>> suspend/resume works OK.
>>>>>>>>>
>>>>>>>>> Since 5.17.4, it is not possible anymore to get the laptop
>>>> working
>>>>>>>>> again
>>>>>>>>> after the first suspend failure.
>>>>>>>>>
>>>>>>>>> HW : HP Pavilion / Ryzen 4600H with AMD graphics integrated +
>>>> NVidia
>>>>>>>>> 1650Ti
>>>>>>>>> (turned off with ACPI call in order to get more battery, I'm
>>>> not using
>>>>>>>>> NVidia driver).
>>>>>
>>>
next prev parent reply other threads:[~2022-05-18 2:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 14:41 [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) Christian Casteyde
2022-05-14 15:12 ` Thorsten Leemhuis
2022-05-14 17:34 ` Christian Casteyde
2022-05-16 2:47 ` Kai-Heng Feng
2022-05-16 3:06 ` Mario Limonciello
2022-05-16 17:23 ` Christian Casteyde
2022-05-17 2:03 ` Kai-Heng Feng
2022-05-17 6:36 ` Christian Casteyde
2022-05-17 6:58 ` Kai-Heng Feng
2022-05-17 17:37 ` casteyde.christian
2022-05-18 5:52 ` Thorsten Leemhuis
2022-05-18 5:54 ` Kai-Heng Feng
2022-05-18 6:37 ` Thorsten Leemhuis
2022-05-18 20:15 ` Limonciello, Mario
2022-05-23 13:02 ` Christian Casteyde
2022-05-23 14:00 ` Limonciello, Mario
2022-05-23 17:03 ` Christian Casteyde
2022-05-23 22:01 ` Limonciello, Mario
2022-05-24 20:54 ` Christian Casteyde
2022-05-25 7:29 ` Thorsten Leemhuis
2022-05-17 17:38 ` casteyde.christian
2022-05-17 18:13 ` Limonciello, Mario
2022-05-18 11:02 ` casteyde.christian
2022-05-19 17:31 ` Limonciello, Mario
2022-05-19 18:07 ` Limonciello, Mario
2022-05-18 2:08 ` Kai-Heng Feng
2022-05-18 2:19 ` Mario Limonciello [this message]
2022-05-18 7:15 ` Christian Casteyde
2022-05-18 10:53 ` casteyde.christian
2022-05-27 9:51 ` [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) #forregzbot Thorsten Leemhuis
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=4dc0d1e4-7e74-f85a-d8af-fdcd862d8a4a@amd.com \
--to=mario.limonciello@amd.com \
--cc=alexander.deucher@amd.com \
--cc=casteyde.christian@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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).