From: eso@self.rodeo
To: 9front <9front@9front.org>
Subject: [9front] panic on hjfs fshalt
Date: Thu, 28 Dec 2023 18:35:54 -0800 [thread overview]
Message-ID: <abae85abadd9e8f690d197a58e7406de@self.rodeo> (raw)
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
Thinkpad x230, behavior began after a sysupdate. I can't say the exact
date it was updating from, but some time during the "Golden Age of
Ballooning" period. Now every time I use fshalt I get a panic. The disk
is an mSATA SSD running hjfs.
Below is my sysinfo, attached is a picture of the error output on
screen.
http://okturing.com/src/18019/body
[-- Attachment #2: IMG_3362.jpg --]
[-- Type: image/jpeg, Size: 1550571 bytes --]
next reply other threads:[~2023-12-29 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 2:35 eso [this message]
2023-12-29 3:26 ` Thaddeus Woskowiak
2023-12-29 4:11 ` cinap_lenrek
2023-12-29 4:41 ` Thaddeus Woskowiak
2023-12-29 6:38 ` eso
2023-12-29 6:54 ` Jacob Moody
2023-12-29 21:38 ` eso
2023-12-29 3:39 ` Thaddeus Woskowiak
2023-12-29 5:22 ` ori
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=abae85abadd9e8f690d197a58e7406de@self.rodeo \
--to=eso@self.rodeo \
--cc=9front@9front.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).