From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] latest code crashes thinkpad x1 yoga 3rd gen on fshalt
Date: Thu, 25 May 2023 22:00:20 -0400 [thread overview]
Message-ID: <D727244FD8E9ED75774C60747BC02D30@gaff.inri.net> (raw)
In-Reply-To: <5EE27AD5-BC82-4641-9D59-D94A4AAB9494@ftrv.se>
> It's because I added nvme shutdown via fshalt, and apparently shutting
> down *ram* disks uncovered this bug. Because sdram seems to be only
> present on pc and pc64 (read: none that I have here) I haven't noticed
> it before pushing my change. I think you can just replace xalloc back
> with malloc in sdram.c. Sorry.
no problem at all. s/xalloc/malloc/ in port/sdram.c fixes the issue for
my machine.
anybody else seen this?
sl
next prev parent reply other threads:[~2023-05-26 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 3:31 Stanley Lieber
2023-05-25 3:33 ` Stanley Lieber
2023-05-25 4:47 ` unobe
2023-05-25 5:05 ` Stanley Lieber
2023-05-25 11:42 ` mia soweli
2023-05-25 13:51 ` Stanley Lieber
2023-05-25 15:16 ` Sigrid Solveig Haflínudóttir
2023-05-26 0:50 ` sl
2023-05-26 1:06 ` Sigrid Solveig Haflínudóttir
2023-05-26 2:00 ` sl [this message]
2023-05-26 15:36 ` Tobias Heinicke
2023-05-26 15:42 ` Jacob Moody
2023-05-26 15:56 ` Stanley Lieber
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=D727244FD8E9ED75774C60747BC02D30@gaff.inri.net \
--to=sl@stanleylieber.com \
--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).