lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 14 Oct 2023 21:44:47 +0000
Subject: [Bug 218006] [ext4] system panic when ext4_writepages:2918: Journal
 has aborted

Theodore Tso ( changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #2 from Theodore Tso ( ---
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