| 1 |
On Wed, 12 May 2021 22:44:56 -0400 |
| 2 |
"Walter Dnes" <waltdnes@××××××××.org> wrote: |
| 3 |
|
| 4 |
> On Wed, May 12, 2021 at 11:16:56AM -0700, Mark Knecht wrote |
| 5 |
> > |
| 6 |
> > Is there nothing in the system logs? What's near the end before whatever |
| 7 |
> > you get from booting after this issue? |
| 8 |
> |
| 9 |
> Where would those logfiles be? "dmesg" starts off with... |
| 10 |
> |
| 11 |
> [ 0.000000] Linux version 5.10.27-gentoo (root@i3) (gcc (Gentoo 10.2.0-r5 p6) 10.2.0, GNU ld (Gentoo 2.34 p6) 2.34.0) #1 SMP Mon Apr 19 20:56:52 EDT 2021 |
| 12 |
> [ 0.000000] Command line: BOOT_IMAGE=Experimental ro root=801 noexec=on net.ifnames=0 intel_pstate=disable ipv6.disable=1 |
| 13 |
> [ 0.000000] x86/fpu: x87 FPU will use FXSAVE |
| 14 |
> [ 0.000000] BIOS-provided physical RAM map: |
| 15 |
> |
| 16 |
> etc. This has happened with various kernels. Note that "Experimental" |
| 17 |
> is the latest kernel version. "Production" is the previous working |
| 18 |
> kernel I've compiled. It serves as a fallback in case I screw things up |
| 19 |
> on the "make menuconfig" step. It also saved me years ago on the switch |
| 20 |
> from /dev/hdx to /dev/sdx. |
| 21 |
> |
| 22 |
|
| 23 |
Maybe you can set in /etc/conf.d/bootmisc the variable |
| 24 |
previous_dmesg="YES" |
| 25 |
That should preserve the last dmesg after a reboot, i.e. |
| 26 |
/var/log/dmesg.old would be the file you want to look at after hard |
| 27 |
reset. |
| 28 |
|
| 29 |
Cheers |
| 30 |
Andreas |
Archives