From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14765 invoked from network); 26 May 2023 02:06:16 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 May 2023 02:06:16 -0000 Received: from gaff.inri.net ([168.235.71.243]) by 9front; Thu May 25 22:00:20 -0400 2023 Message-ID: Date: Thu, 25 May 2023 22:00:20 -0400 From: sl@stanleylieber.com To: 9front@9front.org In-Reply-To: <5EE27AD5-BC82-4641-9D59-D94A4AAB9494@ftrv.se> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: webscale shared SSL over AJAX engine NoSQL frontend Subject: Re: [9front] latest code crashes thinkpad x1 yoga 3rd gen on fshalt Reply-To: 9front@9front.org Precedence: bulk > 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