linux-ext4 - [Bug 111961] ext4 umount - invalid opcode with PLEXTOR PX-128M6G-2242

lists.openwall.net		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]

Message-ID: <bug-111961-13602-n9cW1R47KG@https.bugzilla.kernel.org/>
Date:	Fri, 05 Feb 2016 23:09:52 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 111961] ext4 umount - invalid opcode with PLEXTOR
 PX-128M6G-2242

https://bugzilla.kernel.org/show_bug.cgi?id=111961

--- Comment #3 from Sebastian <info@...pages.de> ---
Thank you very much for the fast response! dmesg output from current boot
doesn't include any ext4 message. I don't have a syslog daemon running, but I
grepped for fsck and ext4 on journald, hoping that helps.

The problem just occurred once - after manual recovering from systemd recovery
shell the system boots fine again . I'll check on the logs and will provide
more information in case anything fails again. If you miss something or if I
can help you there get back to me anytime.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html