[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-218006-13602-qesp1hcWNM@https.bugzilla.kernel.org/>
Date: Sat, 14 Oct 2023 21:44:47 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 218006] [ext4] system panic when ext4_writepages:2918: Journal
has aborted
https://bugzilla.kernel.org/show_bug.cgi?id=218006
Theodore Tso (tytso@....edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@....edu
--- Comment #2 from Theodore Tso (tytso@....edu) ---
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.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists