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:   Mon, 16 Oct 2023 08:25:59 +0000
Subject: [Bug 218006] [ext4] system panic when ext4_writepages:2918: Journal
 has aborted

--- Comment #3 from Gary ( ---
(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?



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