From: Jens Axboe <[email protected]>
To: Changhui Zhong <[email protected]>, [email protected]
Subject: Re: [bug report] Kernel panic - not syncing: Fatal hardware error!
Date: Mon, 18 Mar 2024 20:20:58 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGVVp+WOLnr9Hxd10Xwa8YpJ=W5Re9csPCMtNF8Ux0_zbg0ktA@mail.gmail.com>
On 3/18/24 3:50 AM, Changhui Zhong wrote:
> Hello,
>
> found a kernel panic issue after add io_uring parameters to kernel
> cmdline and then reboot,
> please help check,
>
> repo:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> branch: master
> commit HEAD:f6cef5f8c37f58a3bc95b3754c3ae98e086631ca
>
> grubby --args='io_uring.enable=y' --update-kernel=/boot/vmlinuz-6.8.0+
> grubby --args='sysctl.kernel.io_uring_disabled=0'
> --update-kernel=/boot/vmlinuz-6.8.0+
> reboot
Pretty dubious on that, should have no bearing or impact on that at
all. Does the same sha boot just fine multiple times without the
added parameters?
--
Jens Axboe
prev parent reply other threads:[~2024-03-19 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:50 [bug report] Kernel panic - not syncing: Fatal hardware error! Changhui Zhong
2024-03-19 2:20 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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