From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] panic on hjfs fshalt
Date: Fri, 29 Dec 2023 05:11:53 +0100 [thread overview]
Message-ID: <6CFB6A4CE8CBE02161DE369AC6A9B3A6@felloff.net> (raw)
In-Reply-To: <CAG3JMtbSc5cFcgpo=34rs+kEDOQjaGQc+J+Ucty_MyXOoCZr-Q@mail.gmail.com>
it very much sounds like the issue that has been
fixed before the last release in the kernel.
9e8a7578f063f4caa5ceae9b997ff72a88dbaa58 devsd: Fix memory leaks, wstst check, cleanup
Hash: 9e8a7578f063f4caa5ceae9b997ff72a88dbaa58
Date: Sat Jun 3 18:58:13 CES 2023
Author: cinap_lenrek <cinap_lenrek@felloff.net>
Message: devsd: Fix memory leaks, wstst check, cleanup
0d34984734c0feceaab774d401a09e9333f81991 sdiahci, sdodin, sdide, devsd: get it right...
Hash: 0d34984734c0feceaab774d401a09e9333f81991
Date: Sat May 27 00:08:53 CES 2023
Author: cinap_lenrek <cinap_lenrek@felloff.net>
Message: sdiahci, sdodin, sdide, devsd: get it right...
the bug is triggered by the following code in fshalt:
# turn off disk drives
for(i in $s)
echo config spec $i switch off >>'#S/sdctl'
i highly suspect you'r *NOT* running the new kernel.
note that mk install is not enougth. you need to
copy it to 9fat for your bootloader to find it
if you boot off a disk.
otherwise, comment it out in fshalt to avoid the crash.
--
cinap
next prev parent reply other threads:[~2023-12-29 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 2:35 eso
2023-12-29 3:26 ` Thaddeus Woskowiak
2023-12-29 4:11 ` cinap_lenrek [this message]
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=6CFB6A4CE8CBE02161DE369AC6A9B3A6@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).