From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218006] [ext4] system panic when ext4_writepages:2918: Journal has aborted
Date: Mon, 16 Oct 2023 08:25:59 +0000 [thread overview]
Message-ID: <bug-218006-13602-f3bOGp3vrm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218006-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218006
--- Comment #3 from Gary (fengchunguo@126.com) ---
(In reply to Theodore Tso from comment #2)
> Also, note the panic message:
>
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
>
> This indicates that the init process received a SIGBUS (signal number 7).
> Given all of the large number of mmc0 / sdhci errors, it's pretty clear that
> the storage device is *very* unhappy.
>
>
> The most common cause, as Artem as stated, is that it's a hardware problem,
> It's possible that forcing a factory reset might work. If the SD card is
> removable, you could just to see if reseating the SD card, or if that
> doesn't work, replacing the SD card. If the eMMC flash device is soldered
> onto the mainboard, then probably solution is complete hardware replacement.
Hi Theodore,
Thanks for your suggestion.
Uesed cpuburn and memtest tool test 7*24 hours, not found mmc issue, included
stroage part.
We need use kernel 4.14, could you please kindly offer the debugging way?
Thanks,
BRs,
Gary
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-10-16 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 8:48 [Bug 218006] New: [ext4] system panic when ext4_writepages:2918: Journal has aborted bugzilla-daemon
2023-10-13 22:44 ` [Bug 218006] " bugzilla-daemon
2023-10-14 21:44 ` bugzilla-daemon
2023-10-16 8:25 ` bugzilla-daemon [this message]
2023-10-16 8:27 ` bugzilla-daemon
2023-10-16 8:44 ` bugzilla-daemon
2023-10-16 15:41 ` bugzilla-daemon
2023-10-17 1:41 ` bugzilla-daemon
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=bug-218006-13602-f3bOGp3vrm@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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).