Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #74411 > unrolled thread

Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces

Started byEric Valette <eric.valette@free.fr>
First post2022-02-15 19:20 +0100
Last post2022-02-16 21:10 +0100
Articles 7 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Eric Valette <eric.valette@free.fr> - 2022-02-15 19:20 +0100
    Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Eric Valette <eric.valette@free.fr> - 2022-02-15 19:40 +0100
    Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Alex Deucher <alexdeucher@gmail.com> - 2022-02-15 21:50 +0100
      Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Alex Deucher <alexdeucher@gmail.com> - 2022-02-16 21:10 +0100
        Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Eric Valette <eric.valette@free.fr> - 2022-02-16 22:40 +0100
          Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Eric Valette <eric.valette@free.fr> - 2022-04-10 12:30 +0200
      Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces Eric Valette <eric.valette@free.fr> - 2022-02-16 21:10 +0100

#74411 — Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces

FromEric Valette <eric.valette@free.fr>
Date2022-02-15 19:20 +0100
SubjectBug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
Message-ID<DRaAF-21Dp-1@gated-at.bofh.it>
Since I upgraded from 5.10 (own compiled kernel or debian kernel) to 
5.15 (own compiled from same config or debian kernel)  and even 5.16 
kernel from debian, I get this behavior :

	1) First suspend and resume works,
	2) But later suspendend always fails. I 	have kernel exceptions in amdgpu :

Feb 14 15:40:58 pink-floyd3 kernel: [  830.803952] Hardware name: 
Micro-Star International Co., L
td. Bravo 17 A4DDR/MS-17FK, BIOS E17FKAMS.117 10/29/2020
Feb 14 15:40:58 pink-floyd3 kernel: [  830.803956] Workqueue: pm 
pm_runtime_work
Feb 14 15:40:58 pink-floyd3 kernel: [  830.803966] RIP: 
0010:dm_suspend+0x241/0x260 [amdgpu]
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804340] Code: 4c 89 e6 4c 89 
ef e8 ee 8a 16 00 83 f8 0
1 74 21 89 c2 48 c7 c6 a0 59 69 c1 48 c7 c7 60 83 76 c1 e8 14 ba 06 ff 
e9 6d ff ff ff <0f> 0b e9
f8 fd ff ff 4c 89 e6 4c 89 ef e8 6d ba 15 00 e9 56 ff ff
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804344] RSP: 
0018:ffffae6040647c90 EFLAGS: 00010286
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804348] RAX: 0000000000000000 
RBX: ffff973088a40000 RC
X: 0000000000000000
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804351] RDX: 000000000000000a 
RSI: 0000000000000000 RD
I: ffff973088a40000
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804353] RBP: 0000000000000000 
R08: 0000000003c0ca00 R0
9: 0000000080380002
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804356] R10: ffff9730860f25a0 
R11: 000000000000005f R1
2: ffff973088a40000
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804358] R13: ffff97308132a0d0 
R14: 0000000000000008 R1
5: 0000000000000000
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804361] FS: 
0000000000000000(0000) GS:ffff97339f68000
0(0000) knlGS:0000000000000000
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804364] CS:  0010 DS: 0000 
ES: 0000 CR0: 0000000080050
033
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804366] CR2: 00007fb8c9ce6000 
CR3: 00000001115fa000 CR
4: 0000000000350ee0
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804369] Call Trace:
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804375]  <TASK>
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804380]  ? 
nv_common_set_clockgating_state+0xa3/0xb0 [
amdgpu]
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804693] 
amdgpu_device_ip_suspend_phase1+0x63/0xc0 [am
dgpu]
Feb 14 15:40:58 pink-floyd3 kernel: [  830.804977] 
amdgpu_device_suspend+0x66/0x110 [amdgpu]
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805260] 
amdgpu_pmops_runtime_suspend+0xad/0x180 [amdg
pu]
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805542] 
pci_pm_runtime_suspend+0x5a/0x160
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805549]  ? pci_dev_put+0x20/0x20
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805553] 
__rpm_callback+0x44/0x150
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805558]  ? pci_dev_put+0x20/0x20
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805561]  rpm_callback+0x59/0x70
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805565]  ? pci_dev_put+0x20/0x20
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805568]  rpm_suspend+0x14a/0x720
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805572]  ? 
_raw_spin_unlock+0x16/0x30
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805580]  ? 
finish_task_switch.isra.0+0xc1/0x2f0
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805586]  ? 
__switch_to+0x114/0x440
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805593] 
pm_runtime_work+0x94/0xa0
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805597] 
process_one_work+0x1e8/0x3c0
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805604]  worker_thread+0x50/0x3b0
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805608]  ? 
rescuer_thread+0x370/0x370
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805611]  kthread+0x16b/0x190
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805616]  ? 
set_kthread_struct+0x40/0x40
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805621]  ret_from_fork+0x22/0x30
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805630]  </TASK>
Feb 14 15:40:58 pink-floyd3 kernel: [  830.805632] ---[ end trace 
8d77579b410d926d ]---
Feb 14 15:40:58 pink-floyd3 kernel: [  831.142133] amdgpu 0000:03:00.0: 
[drm:amdgpu_ring_test_hel
per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Feb 14 15:40:58 pink-floyd3 kernel: [  831.142444] 
[drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ d
isable failed
Feb 14 15:40:59 pink-floyd3 kernel: [  831.462157] amdgpu 0000:03:00.0: 
[drm:amdgpu_ring_test_hel
per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Feb 14 15:40:59 pink-floyd3 kernel: [  831.462465] 
[drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ d
isable failed
Feb 14 15:40:59 pink-floyd3 kernel: [  831.782375] 
[drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* faile
d to halt cp gfx
Feb 14 15:41:05 pink-floyd3 kernel: [  837.297839] amdgpu 0000:03:00.0: 
amdgpu: SMU: I'm not done
  with your previous command: SMN_C2PMSG_66:0x0000003A 
SMN_C2PMSG_82:0x00000000

[toc] | [next] | [standalone]

#74412

FromEric Valette <eric.valette@free.fr>
Date2022-02-15 19:40 +0100
Message-ID<DRaU2-21Jy-3@gated-at.bofh.it>
In reply to#74411
On 15/02/2022 19:14, Eric Valette wrote:
> Since I upgraded from 5.10 (own compiled kernel or debian kernel) to 
> 5.15 (own compiled from same config or debian kernel)  and even 5.16 
> kernel from debian, I get this behavior :
> 
>      1) First suspend and resume works,
>      2) But later suspendend always fails. I     have kernel exceptions 
> in amdgpu :


In addition when booting 5.10 I get this message :
/var/log/syslog.1:Feb 13 11:11:48 pink-floyd3 kernel: [    3.035073] 
amdgpu 0000:03:00.0: amdgpu: ACPI VFCT table present but broken (too 
short #2),skipping

and I do not see it on console with later kernels.

> 
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803952] Hardware name: 
> Micro-Star International Co., L
> td. Bravo 17 A4DDR/MS-17FK, BIOS E17FKAMS.117 10/29/2020
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803956] Workqueue: pm 
> pm_runtime_work
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803966] RIP: 
> 0010:dm_suspend+0x241/0x260 [amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804340] Code: 4c 89 e6 4c 89 
> ef e8 ee 8a 16 00 83 f8 0
> 1 74 21 89 c2 48 c7 c6 a0 59 69 c1 48 c7 c7 60 83 76 c1 e8 14 ba 06 ff 
> e9 6d ff ff ff <0f> 0b e9
> f8 fd ff ff 4c 89 e6 4c 89 ef e8 6d ba 15 00 e9 56 ff ff
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804344] RSP: 
> 0018:ffffae6040647c90 EFLAGS: 00010286
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804348] RAX: 0000000000000000 
> RBX: ffff973088a40000 RC
> X: 0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804351] RDX: 000000000000000a 
> RSI: 0000000000000000 RD
> I: ffff973088a40000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804353] RBP: 0000000000000000 
> R08: 0000000003c0ca00 R0
> 9: 0000000080380002
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804356] R10: ffff9730860f25a0 
> R11: 000000000000005f R1
> 2: ffff973088a40000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804358] R13: ffff97308132a0d0 
> R14: 0000000000000008 R1
> 5: 0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804361] FS: 
> 0000000000000000(0000) GS:ffff97339f68000
> 0(0000) knlGS:0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804364] CS:  0010 DS: 0000 
> ES: 0000 CR0: 0000000080050
> 033
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804366] CR2: 00007fb8c9ce6000 
> CR3: 00000001115fa000 CR
> 4: 0000000000350ee0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804369] Call Trace:
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804375]  <TASK>
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804380]  ? 
> nv_common_set_clockgating_state+0xa3/0xb0 [
> amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804693] 
> amdgpu_device_ip_suspend_phase1+0x63/0xc0 [am
> dgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804977] 
> amdgpu_device_suspend+0x66/0x110 [amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805260] 
> amdgpu_pmops_runtime_suspend+0xad/0x180 [amdg
> pu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805542] 
> pci_pm_runtime_suspend+0x5a/0x160
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805549]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805553] 
> __rpm_callback+0x44/0x150
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805558]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805561]  rpm_callback+0x59/0x70
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805565]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805568]  rpm_suspend+0x14a/0x720
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805572]  ? 
> _raw_spin_unlock+0x16/0x30
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805580]  ? 
> finish_task_switch.isra.0+0xc1/0x2f0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805586]  ? 
> __switch_to+0x114/0x440
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805593] 
> pm_runtime_work+0x94/0xa0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805597] 
> process_one_work+0x1e8/0x3c0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805604]  
> worker_thread+0x50/0x3b0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805608]  ? 
> rescuer_thread+0x370/0x370
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805611]  kthread+0x16b/0x190
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805616]  ? 
> set_kthread_struct+0x40/0x40
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805621]  ret_from_fork+0x22/0x30
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805630]  </TASK>
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805632] ---[ end trace 
> 8d77579b410d926d ]---
> Feb 14 15:40:58 pink-floyd3 kernel: [  831.142133] amdgpu 0000:03:00.0: 
> [drm:amdgpu_ring_test_hel
> per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
> Feb 14 15:40:58 pink-floyd3 kernel: [  831.142444] 
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ d
> isable failed
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.462157] amdgpu 0000:03:00.0: 
> [drm:amdgpu_ring_test_hel
> per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.462465] 
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ d
> isable failed
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.782375] 
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* faile
> d to halt cp gfx
> Feb 14 15:41:05 pink-floyd3 kernel: [  837.297839] amdgpu 0000:03:00.0: 
> amdgpu: SMU: I'm not done
>   with your previous command: SMN_C2PMSG_66:0x0000003A 
> SMN_C2PMSG_82:0x00000000
> 
> 
>

[toc] | [prev] | [next] | [standalone]

#74413

FromAlex Deucher <alexdeucher@gmail.com>
Date2022-02-15 21:50 +0100
Message-ID<DRcVP-22Vo-7@gated-at.bofh.it>
In reply to#74411
What chip is this?  Can you provide the full dmesg output?

Alex

On Tue, Feb 15, 2022 at 1:15 PM Eric Valette <eric.valette@free.fr> wrote:
>
> Since I upgraded from 5.10 (own compiled kernel or debian kernel) to
> 5.15 (own compiled from same config or debian kernel)  and even 5.16
> kernel from debian, I get this behavior :
>
>         1) First suspend and resume works,
>         2) But later suspendend always fails. I         have kernel exceptions in amdgpu :
>
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803952] Hardware name:
> Micro-Star International Co., L
> td. Bravo 17 A4DDR/MS-17FK, BIOS E17FKAMS.117 10/29/2020
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803956] Workqueue: pm
> pm_runtime_work
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.803966] RIP:
> 0010:dm_suspend+0x241/0x260 [amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804340] Code: 4c 89 e6 4c 89
> ef e8 ee 8a 16 00 83 f8 0
> 1 74 21 89 c2 48 c7 c6 a0 59 69 c1 48 c7 c7 60 83 76 c1 e8 14 ba 06 ff
> e9 6d ff ff ff <0f> 0b e9
> f8 fd ff ff 4c 89 e6 4c 89 ef e8 6d ba 15 00 e9 56 ff ff
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804344] RSP:
> 0018:ffffae6040647c90 EFLAGS: 00010286
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804348] RAX: 0000000000000000
> RBX: ffff973088a40000 RC
> X: 0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804351] RDX: 000000000000000a
> RSI: 0000000000000000 RD
> I: ffff973088a40000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804353] RBP: 0000000000000000
> R08: 0000000003c0ca00 R0
> 9: 0000000080380002
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804356] R10: ffff9730860f25a0
> R11: 000000000000005f R1
> 2: ffff973088a40000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804358] R13: ffff97308132a0d0
> R14: 0000000000000008 R1
> 5: 0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804361] FS:
> 0000000000000000(0000) GS:ffff97339f68000
> 0(0000) knlGS:0000000000000000
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804364] CS:  0010 DS: 0000
> ES: 0000 CR0: 0000000080050
> 033
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804366] CR2: 00007fb8c9ce6000
> CR3: 00000001115fa000 CR
> 4: 0000000000350ee0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804369] Call Trace:
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804375]  <TASK>
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804380]  ?
> nv_common_set_clockgating_state+0xa3/0xb0 [
> amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804693]
> amdgpu_device_ip_suspend_phase1+0x63/0xc0 [am
> dgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.804977]
> amdgpu_device_suspend+0x66/0x110 [amdgpu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805260]
> amdgpu_pmops_runtime_suspend+0xad/0x180 [amdg
> pu]
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805542]
> pci_pm_runtime_suspend+0x5a/0x160
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805549]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805553]
> __rpm_callback+0x44/0x150
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805558]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805561]  rpm_callback+0x59/0x70
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805565]  ? pci_dev_put+0x20/0x20
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805568]  rpm_suspend+0x14a/0x720
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805572]  ?
> _raw_spin_unlock+0x16/0x30
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805580]  ?
> finish_task_switch.isra.0+0xc1/0x2f0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805586]  ?
> __switch_to+0x114/0x440
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805593]
> pm_runtime_work+0x94/0xa0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805597]
> process_one_work+0x1e8/0x3c0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805604]  worker_thread+0x50/0x3b0
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805608]  ?
> rescuer_thread+0x370/0x370
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805611]  kthread+0x16b/0x190
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805616]  ?
> set_kthread_struct+0x40/0x40
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805621]  ret_from_fork+0x22/0x30
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805630]  </TASK>
> Feb 14 15:40:58 pink-floyd3 kernel: [  830.805632] ---[ end trace
> 8d77579b410d926d ]---
> Feb 14 15:40:58 pink-floyd3 kernel: [  831.142133] amdgpu 0000:03:00.0:
> [drm:amdgpu_ring_test_hel
> per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
> Feb 14 15:40:58 pink-floyd3 kernel: [  831.142444]
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ d
> isable failed
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.462157] amdgpu 0000:03:00.0:
> [drm:amdgpu_ring_test_hel
> per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.462465]
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ d
> isable failed
> Feb 14 15:40:59 pink-floyd3 kernel: [  831.782375]
> [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* faile
> d to halt cp gfx
> Feb 14 15:41:05 pink-floyd3 kernel: [  837.297839] amdgpu 0000:03:00.0:
> amdgpu: SMU: I'm not done
>   with your previous command: SMN_C2PMSG_66:0x0000003A
> SMN_C2PMSG_82:0x00000000
>
>
>

[toc] | [prev] | [next] | [standalone]

#74418

FromAlex Deucher <alexdeucher@gmail.com>
Date2022-02-16 21:10 +0100
Message-ID<DRyMF-2gNz-5@gated-at.bofh.it>
In reply to#74413
On Wed, Feb 16, 2022 at 2:56 PM Eric Valette <eric.valette@free.fr> wrote:
>
> On Tue, 15 Feb 2022 15:42:27 -0500 Alex Deucher <alexdeucher@gmail.com>
> wrote:
> > What chip is this?  Can you provide the full dmesg output?
>
> Its a a renoir chip with a second gpu : [Radeon RX 5500/5500M / Pro 5500M].

Thanks.  Can you attach the dmesg output?  Can you bisect?

Alex


>
>
> Processor Information
>          Socket Designation: FP6
>          Type: Central Processor
>          Family: Zen
>          Manufacturer: Advanced Micro Devices, Inc.
>          ID: 01 0F 86 00 FF FB 8B 17
>          Signature: Family 23, Model 96, Stepping 1
>          Flags:
>                  FPU (Floating-point unit on-chip)
>                  VME (Virtual mode extension)
>                  DE (Debugging extension)
>                  PSE (Page size extension)
>                  TSC (Time stamp counter)
>                  MSR (Model specific registers)
>                  PAE (Physical address extension)
>                  MCE (Machine check exception)
>                  CX8 (CMPXCHG8 instruction supported)
>                  APIC (On-chip APIC hardware supported)
>                  SEP (Fast system call)
>                  MTRR (Memory type range registers)
>                  PGE (Page global enable)
>                  MCA (Machine check architecture)
>                  CMOV (Conditional move instruction supported)
>                  PAT (Page attribute table)
>                  PSE-36 (36-bit page size extension)
>                  CLFSH (CLFLUSH instruction supported)
>                  MMX (MMX technology supported)
>                  FXSR (FXSAVE and FXSTOR instructions supported)
>                  SSE (Streaming SIMD extensions)
>                  SSE2 (Streaming SIMD extensions 2)
>                  HTT (Multi-threading)
>          Version: AMD Ryzen 7 4800H with Radeon Graphics
>          Voltage: 1.2 V
>          External Clock: 100 MHz
>          Max Speed: 4300 MHz
>          Current Speed: 2900 MHz
>          Status: Populated, Enabled
>          Upgrade: None
>          L1 Cache Handle: 0x000D
>          L2 Cache Handle: 0x000E
>          L3 Cache Handle: 0x000F
>          Serial Number: Unknown
>          Asset Tag: Unknown
>          Part Number: Unknown
>          Core Count: 8
>          Core Enabled: 8
>          Thread Count: 16
>          Characteristics:
>                  64-bit capable
>                  Multi-Core
>                  Hardware Thread
>                  Execute Protection
>                  Enhanced Virtualization
>                  Power/Performance Control

[toc] | [prev] | [next] | [standalone]

#74420

FromEric Valette <eric.valette@free.fr>
Date2022-02-16 22:40 +0100
Message-ID<DRAbL-2hyq-3@gated-at.bofh.it>
In reply to#74418
On 16/02/2022 21:01, Eric Valette wrote:
> On 16/02/2022 20:58, Alex Deucher wrote:
>> On Wed, Feb 16, 2022 at 2:56 PM Eric Valette <eric.valette@free.fr> 
>> wrote:
>>>

> Here is the dmesg. For bisecting, I'm not home and the Intrenet 
> connection is just too slow.

In order to help a bit, I started to build kernel with the kernel 
patches set I had on my laptop so here it is:

5.11 suspend/resume is ok
5.12 suspend/resume is ok
5.13 suspend OK, resume KO, PC is dead I have to reboot.
5.14 suspend/resume is ok multiple times but I do have the exceptions at 
various places
sudo dmesg | grep RIP
[   19.918769] RIP: 0010:ieee80211_reconfig+0x9a/0x1300
[   19.918976] RIP: 0010:drv_remove_interface+0xd8/0xe0
[   19.919086] RIP: 0010:drv_stop+0xb8/0xc0
[   20.320553] RIP: 0010:iwl_mvm_mac_ctxt_init+0x1e2/0x220 [iwlmvm]
[   20.320801] RIP: 0033:0x7f0d4632536d

5.15 you have the result with latest one 5.15.24. RIP is at a given place.


Sorry to be unable to do more.

--eric

[toc] | [prev] | [next] | [standalone]

#75000

FromEric Valette <eric.valette@free.fr>
Date2022-04-10 12:30 +0200
Message-ID<EaCZr-7MxD-1@gated-at.bofh.it>
In reply to#74420
On 16/02/2022 22:36, Eric Valette wrote:
> On 16/02/2022 21:01, Eric Valette wrote:
>> On 16/02/2022 20:58, Alex Deucher wrote:
>>> On Wed, Feb 16, 2022 at 2:56 PM Eric Valette <eric.valette@free.fr> 
>>> wrote:
>>>>
> 
>> Here is the dmesg. For bisecting, I'm not home and the Intrenet 
>> connection is just too slow.
> 
> In order to help a bit, I started to build kernel with the kernel 
> patches set I had on my laptop so here it is:
> 
> 5.11 suspend/resume is ok
> 5.12 suspend/resume is ok
> 5.13 suspend OK, resume KO, PC is dead I have to reboot.
> 5.14 suspend/resume is ok multiple times but I do have the exceptions at 
> various places
> sudo dmesg | grep RIP
> [   19.918769] RIP: 0010:ieee80211_reconfig+0x9a/0x1300
> [   19.918976] RIP: 0010:drv_remove_interface+0xd8/0xe0
> [   19.919086] RIP: 0010:drv_stop+0xb8/0xc0
> [   20.320553] RIP: 0010:iwl_mvm_mac_ctxt_init+0x1e2/0x220 [iwlmvm]
> [   20.320801] RIP: 0033:0x7f0d4632536d
> 
> 5.15 you have the result with latest one 5.15.24. RIP is at a given place.
> 
> 
> Sorry to be unable to do more.


As a follow up : 5.17.1 from debian fixes the problem. Unfortunately it 
is not a long term kernel...

-- eric

[toc] | [prev] | [next] | [standalone]

#74419

FromEric Valette <eric.valette@free.fr>
Date2022-02-16 21:10 +0100
Message-ID<DRyMF-2gNz-7@gated-at.bofh.it>
In reply to#74413
On Tue, 15 Feb 2022 15:42:27 -0500 Alex Deucher <alexdeucher@gmail.com> 
wrote:
> What chip is this?  Can you provide the full dmesg output?

Its a a renoir chip with a second gpu : [Radeon RX 5500/5500M / Pro 5500M].


Processor Information
         Socket Designation: FP6
         Type: Central Processor
         Family: Zen
         Manufacturer: Advanced Micro Devices, Inc.
         ID: 01 0F 86 00 FF FB 8B 17
         Signature: Family 23, Model 96, Stepping 1
         Flags:
                 FPU (Floating-point unit on-chip)
                 VME (Virtual mode extension)
                 DE (Debugging extension)
                 PSE (Page size extension)
                 TSC (Time stamp counter)
                 MSR (Model specific registers)
                 PAE (Physical address extension)
                 MCE (Machine check exception)
                 CX8 (CMPXCHG8 instruction supported)
                 APIC (On-chip APIC hardware supported)
                 SEP (Fast system call)
                 MTRR (Memory type range registers)
                 PGE (Page global enable)
                 MCA (Machine check architecture)
                 CMOV (Conditional move instruction supported)
                 PAT (Page attribute table)
                 PSE-36 (36-bit page size extension)
                 CLFSH (CLFLUSH instruction supported)
                 MMX (MMX technology supported)
                 FXSR (FXSAVE and FXSTOR instructions supported)
                 SSE (Streaming SIMD extensions)
                 SSE2 (Streaming SIMD extensions 2)
                 HTT (Multi-threading)
         Version: AMD Ryzen 7 4800H with Radeon Graphics
         Voltage: 1.2 V
         External Clock: 100 MHz
         Max Speed: 4300 MHz
         Current Speed: 2900 MHz
         Status: Populated, Enabled
         Upgrade: None
         L1 Cache Handle: 0x000D
         L2 Cache Handle: 0x000E
         L3 Cache Handle: 0x000F
         Serial Number: Unknown
         Asset Tag: Unknown
         Part Number: Unknown
         Core Count: 8
         Core Enabled: 8
         Thread Count: 16
         Characteristics:
                 64-bit capable
                 Multi-Core
                 Hardware Thread
                 Execute Protection
                 Enhanced Virtualization
                 Power/Performance Control

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web