Re: stop "dmesg.boot" from being overwritten on each boot-up
- In reply to: Greg 'groggy' Lehey : "Re: stop "dmesg.boot" from being overwritten on each boot-up"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 03 May 2024 05:09:20 UTC
On Mon, Apr 29, 2024 at 5:56 PM Greg 'groggy' Lehey <grog@freebsd.org> wrote: > [Trimmed, resequenced for clarity] > > On Monday, 29 April 2024 at 5:21:51 -0400, Gerard E. Seibert wrote: > > On Mon, 29 Apr 2024 08:46:27 +1000, Greg 'groggy' Lehey < > grog@freebsd.org> stated: > >> When replying to this message, please copy the original recipients. > >> If you don't, I may ignore the reply or reply to the original > >> recipients. For more information, see > >> http://www.lemis.com/questions.html Sent from my desktop computer. > > You didn't copy questions@ on your last message. > > >> On Sunday, 28 April 2024 at 16:42:58 -0400, Gerard E. Seibert wrote: > >>> I want to get a copy of what happens when the system locks up while > >>> booting with the i915ms.ko module. Is there any setting I can use to > >>> stop overwriting that file or perhaps append the output to it? > >> > >> Not that I know of. But while you're in single user, you can rename > >> the file. It would be better to copy it elsewhere in case the entire > >> contents of the /var/run directory gets removed. > > > > The problem with moving the file is that it has already been > > overwritten by the new boot-up process. > > Not when you're in single user. The file systems are mounted > read-only, and it's not even sure that /var is accessible. To rename > the file you first need to mount -u / and maybe mount the file system > on which /var is located. I assumed you knew that, since you did > other things in single user. > > > I might make a suggestion that a mechanism be put in place to allow > > a user to not automatically overwrite that file. Something like > > letsencrypt does with its log files. > > Sure, that's what the bugs system is for. And in that connection, > > >> Have you checked the bug reports for your i915ms problem? > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original recipients. > For more information, see http://www.lemis.com/questions.html > Sent from my desktop computer. > See complete headers for address and phone numbers. > This message is digitally signed. If your Microsoft mail program > reports problems, please read http://lemis.com/broken-MUA.php > A few questions... What processor do you have? What version of FreeBSD? What version of drm-kmod (drm-*-kmod)? Which version is between the 'drm' and 'kmod'? There is a known problem with drm-515-kmod on 14.0 on Alder Lake. The problem should be fixed on 14.1 and drm-61-kmod which is getting close. If you install 14-STABLE, the fix is there. If your system does not match, you really should open a trouble report. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683