From: Greg KH <greg@kroah.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: platform_shutdown crasher reaches LTS v5.10
Date: Tue, 29 Apr 2025 14:28:36 +0200 [thread overview]
Message-ID: <2025042924-trembling-backward-9436@gregkh> (raw)
In-Reply-To: <707a42f7-09c7-48e7-9b87-4e4dd1dfbde4@oracle.com>
On Mon, Apr 28, 2025 at 02:51:44PM -0400, Chuck Lever wrote:
> Howdy -
>
> My queue/5.10 CI test runners have hit this crash on shutdown:
>
> [ 42.547410] RIP: 0010:platform_shutdown+0x9/0x20
> [ 42.547955] Code: b7 46 08 c3 cc cc cc cc 31 c0 83 bf a8 02 00 00 ff
> 75 ec c3 cc cc cc cc 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8b 47
> 68 <48> 8b 40 e8 48 85 c0 74 09 48 83 ef 10 e9 35 2c 80 00 c3 cc cc cc
> [ 42.550016] RSP: 0018:ffffc2ff80013de0 EFLAGS: 00010246
> [ 42.550630] RAX: 0000000000000000 RBX: ffff9e6805d2ec18 RCX:
> 0000000000000000
> [ 42.551444] RDX: 0000000000000001 RSI: ffff9e6805d2ec18 RDI:
> ffff9e6805d2ec10
> [ 42.552263] RBP: ffffffff9be79420 R08: ffff9e6805d2f408 R09:
> ffffffff9bc5c698
> [ 42.553081] R10: 0000000000000000 R11: 0000000000000000 R12:
> ffff9e6805d2ec10
> [ 42.553900] R13: ffff9e6805d2ec90 R14: 00000000fee1dead R15:
> 0000000000000000
> [ 42.554717] FS: 00007f05a6960b80(0000) GS:ffff9e6b6fc00000(0000)
> knlGS:0000000000000000
> [ 42.555633] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 42.556291] CR2: ffffffffffffffe8 CR3: 000000010960a006 CR4:
> 0000000000370ef0
> [ 42.557105] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [ 42.557919] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> 0000000000000400
> [ 42.558733] Call Trace:
> [ 42.559044] device_shutdown+0x15b/0x1c0
> [ 42.559512] __do_sys_reboot.cold+0x2f/0x5b
> [ 42.560015] ? vfs_writev+0x9b/0x110
> [ 42.560444] ? do_writev+0x57/0xf0
> [ 42.560859] do_syscall_64+0x33/0x40
> [ 42.561289] entry_SYSCALL_64_after_hwframe+0x67/0xd1
>
>
> It's likely due to this recently applied commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=queue/5.10&id=09dc7a2708efc8eaa3efcbb1d50b2d8232b41114
>
> Maybe commit 46e85af0cc53 ("driver core: platform: don't oops in
> platform_shutdown() on unbound devices") fixes this issue, but I didn't
> test it.
Thanks, I'll go fix this up again.
greg k-h
prev parent reply other threads:[~2025-04-29 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 18:51 platform_shutdown crasher reaches LTS v5.10 Chuck Lever
2025-04-29 12:28 ` Greg KH [this message]
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=2025042924-trembling-backward-9436@gregkh \
--to=greg@kroah.com \
--cc=chuck.lever@oracle.com \
--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