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


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

Bug#908248: linux-image-amd64: udev hung due to CCP, long shutdown due to process stuck

Started byTomas Lacher <tomas.lacher@binaryx.eu>
First post2018-09-07 19:30 +0200
Last post2018-09-14 22:20 +0200
Articles 3 — 3 participants

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


Contents

  Bug#908248: linux-image-amd64: udev hung due to CCP, long shutdown due to process stuck Tomas Lacher <tomas.lacher@binaryx.eu> - 2018-09-07 19:30 +0200
    Bug#908248: Patch available but not part in mainstream tomas.lacher@binaryx.eu - 2018-09-10 22:30 +0200
      Bug#908248: Patch available but not part in mainstream Romain Perier <romain.perier@gmail.com> - 2018-09-14 22:20 +0200

#62029 — Bug#908248: linux-image-amd64: udev hung due to CCP, long shutdown due to process stuck

FromTomas Lacher <tomas.lacher@binaryx.eu>
Date2018-09-07 19:30 +0200
SubjectBug#908248: linux-image-amd64: udev hung due to CCP, long shutdown due to process stuck
Message-ID<wvsJX-2Sc-5@gated-at.bofh.it>
Package: linux-image-amd64
Version: 4.18+98
Severity: important

Issue apply to testing kernel 4.17.*, kernel 4.18 installed to proof the issue was not solved in newer kernel release.
Due to the process hung the shutdown of the system takes 5 - 10 minutes where message about "dead" udev process is printed into terminal.
No other issues currently visible.

[  242.542652] INFO: task systemd-udevd:644 blocked for more than 120 seconds.
[  242.542658]       Not tainted 4.18.0-1-amd64 #1 Debian 4.18.6-1
[  242.542660] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  242.542662] systemd-udevd   D    0   644    619 0x80000124
[  242.542665] Call Trace:
[  242.542674]  ? __schedule+0x2b7/0x880
[  242.542678]  ? __wake_up_common_lock+0x89/0xc0
[  242.542680]  schedule+0x28/0x80
[  242.542691]  __sev_do_cmd_locked+0x1f0/0x270 [ccp]
[  242.542694]  ? finish_wait+0x80/0x80
[  242.542700]  sev_do_cmd+0x2a/0x40 [ccp]
[  242.542702]  ? 0xffffffffc0880000
[  242.542707]  sev_get_api_version+0x34/0xa0 [ccp]
[  242.542713]  ? sp_get_psp_master_device+0x63/0x80 [ccp]
[  242.542717]  psp_pci_init+0x43/0x220 [ccp]
[  242.542719]  ? 0xffffffffc0880000
[  242.542724]  sp_mod_init+0x16/0x1000 [ccp]
[  242.542728]  do_one_initcall+0x46/0x1c8
[  242.542731]  ? free_unref_page_commit+0x95/0x120
[  242.542733]  ? _cond_resched+0x15/0x40
[  242.542736]  ? kmem_cache_alloc_trace+0x15d/0x1c0
[  242.542739]  ? do_init_module+0x22/0x201
[  242.542741]  do_init_module+0x5b/0x201
[  242.542743]  load_module.constprop.56+0x1649/0x1d80
[  242.542746]  ? vfs_read+0x113/0x130
[  242.542748]  ? vfs_read+0x113/0x130
[  242.542750]  ? __do_sys_finit_module+0xe9/0x110
[  242.542752]  __do_sys_finit_module+0xe9/0x110
[  242.542755]  do_syscall_64+0x55/0x110
[  242.542758]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  242.542761] RIP: 0033:0x7f45ce4f6a79
[  242.542761] Code: Bad RIP value.
[  242.542768] RSP: 002b:00007fff05345988 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[  242.542770] RAX: ffffffffffffffda RBX: 0000562209a42c80 RCX: 00007f45ce4f6a79
[  242.542771] RDX: 0000000000000000 RSI: 00007f45ce1fe0ed RDI: 0000000000000007
[  242.542772] RBP: 00007f45ce1fe0ed R08: 0000000000000000 R09: 0000000000000000
[  242.542773] R10: 0000000000000007 R11: 0000000000000246 R12: 0000000000000000
[  242.542774] R13: 0000562209a40300 R14: 0000000000020000 R15: 0000562209a5a6e0

HW info:
MSI X370 XPOWER GAMING TITANIUM (MS-7A31)
CPU: Ryzen 1700x
BIOS setting: default
BIOS release: 1.G0 / 07/12/2018 (tested with N-1 version)

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (850, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.18.0-1-amd64  4.18.6-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]


#62078 — Bug#908248: Patch available but not part in mainstream

Fromtomas.lacher@binaryx.eu
Date2018-09-10 22:30 +0200
SubjectBug#908248: Patch available but not part in mainstream
Message-ID<wwAYO-2gm-3@gated-at.bofh.it>
In reply to#62029

[Multipart message — attachments visible in raw view] — view raw

Hello team,

There seems to be patch available, but not part of upstream kernel source yet (checked against 4.18.7 git), provided by AMD employee.
Applied the patch listed from page below to 4.18.6 kernel from kernel.org and no issues visible related to udev stuck as reported before.

https://lore.kernel.org/patchwork/patch/974869/ (https://lore.kernel.org/patchwork/patch/974869/)

BRTL

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


#62145 — Bug#908248: Patch available but not part in mainstream

FromRomain Perier <romain.perier@gmail.com>
Date2018-09-14 22:20 +0200
SubjectBug#908248: Patch available but not part in mainstream
Message-ID<wy2Jj-4pa-7@gated-at.bofh.it>
In reply to#62078
On Mon, Sep 10, 2018 at 08:15:29PM +0000, tomas.lacher@binaryx.eu wrote:
> Hello team,
> 
> There seems to be patch available, but not part of upstream kernel source yet (checked against 4.18.7 git), provided by AMD employee.
> Applied the patch listed from page below to 4.18.6 kernel from kernel.org and no issues visible related to udev stuck as reported before.
> 
> https://lore.kernel.org/patchwork/patch/974869/ (https://lore.kernel.org/patchwork/patch/974869/)
> 
> BRTL

Hello,

Merge request opened, see https://salsa.debian.org/kernel-team/linux/merge_requests/62
(it depends on previous opened merge request, just focus on the HEAD commit)

Thanks,
Regards,
Romain

[toc] | [prev] | [standalone]


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


csiph-web