doom/Mu

Fork 0

fix: iseki-specific issues #7

New issue

Open

opened 2026-08-12 21:23:34 +02:00 by doom · 4 comments

doom commented

2026-08-12 21:23:34 +02:00

Owner

In this issue, 遺跡-specific issues will be analyzed and fixed.

Replace Nouveau with Proprietary Drivers #7 (comment)
Grep Issues #7 (comment)
Enable SSH for Connections coming through Tailnet & add Framework Key to authorized keys ([mostly] done in 0c67bfc029)
Make Media Keys work!
Troubleshoot Sudden Shutdown

In this issue, 遺跡-specific issues will be analyzed and fixed. - [x] Replace Nouveau with Proprietary Drivers https://git.c0mpl3x.one/doom/Mu/issues/7#issuecomment-27 - [ ] Grep Issues https://git.c0mpl3x.one/doom/Mu/issues/7#issuecomment-29 - [x] Enable SSH for Connections coming through Tailnet & add Framework Key to authorized keys ([mostly] done in 0c67bfc029) - [ ] Make Media Keys work! - [x] Troubleshoot Sudden Shutdown

doom added the

Kind/Bug

Priority

Critical

labels

2026-08-12 21:23:34 +02:00

doom self-assigned this

2026-08-12 21:23:34 +02:00

doom commented

2026-08-12 21:24:13 +02:00

Author

Owner

Nouveau appeared to cause a lot of issues, for example:

SCHED_ERROR , like here
GPC0/TPC0/MP trap, like here

as such I switched over to the proprietary legacy NVidia Driver. Modern variants are not supported anymore, and have neither modern proprietary, nor open drivers. As such this issue is fixed in d727ac8ad0.

Log Extraction:

sudo su -
cd $(mktemp -d)
journalctl --no-pager -S "2026-08-12 13:12:49" -U "2026-08-12 13:13:10" > nouveau-01.log
journalctl --no-pager -S "2026-08-12 18:21:14" -U "2026-08-12 18:21:20" > nouveau-02.log
journalctl --no-pager -S "2026-08-12 18:56:25" -U "2026-08-12 18:58:13" > nouveau-03.log
journalctl --no-pager -S "2026-08-12 20:08:02" -U "2026-08-12 20:09:25" > nouveau-04.log
chown doom -R .

Nouveau appeared to cause a lot of issues, for example: - SCHED_ERROR , like [here](https://gist.github.com/kenorb/abb9db39b04b9fd551429c79c6750883) - GPC0/TPC0/MP trap, like [here](https://askubuntu.com/questions/1046945/kernel-error-nouveau-problem-with-xorg-nv50cal-space-16#1107269) as such I switched over to the proprietary legacy NVidia Driver. Modern variants are not supported anymore, and have neither modern proprietary, nor open drivers. As such this issue is fixed in d727ac8ad0. Log Extraction: ```sh sudo su - cd $(mktemp -d) journalctl --no-pager -S "2026-08-12 13:12:49" -U "2026-08-12 13:13:10" > nouveau-01.log journalctl --no-pager -S "2026-08-12 18:21:14" -U "2026-08-12 18:21:20" > nouveau-02.log journalctl --no-pager -S "2026-08-12 18:56:25" -U "2026-08-12 18:58:13" > nouveau-03.log journalctl --no-pager -S "2026-08-12 20:08:02" -U "2026-08-12 20:09:25" > nouveau-04.log chown doom -R . ```

nouveau-01.log

122 KiB

nouveau-02.log

16 KiB

nouveau-03.log

20 KiB

nouveau-04.log

1.3 MiB

🎉 1

doom commented

2026-08-12 21:24:40 +02:00

Author

Owner

To Be Investigated:

X-Server CSI Issue (e.g.):

 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?69$p
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2026$p
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2027$p
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2031$p
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2048$p
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?u
 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[>4;2m

After some rudimentary investigation, this issue tracks down to st:

Report on the Suckless Mailing List

The responsible code is:

void
csihandle(void)
{
        char buf[40];
        int len;

        switch (csiescseq.mode[0]) {
        default:
        unknown:
                fprintf(stderr, "erresc: unknown csi ");
                csidump();
                /* die(""); */
                break;

As such the investigation on how to fix this migrates to #2

To Be Investigated: **X-Server CSI Issue** (e.g.): ``` log 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?69$p 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2026$p 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2027$p 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2031$p 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?2048$p 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[?u 8月 12 16:05:28 iseki xsession[20298]: erresc: unknown csi ESC[>4;2m ``` After some rudimentary investigation, this issue tracks down to `st`: - [Report on the Suckless Mailing List](https://lists.suckless.org/dev/2005/33935.html) The responsible code is: ```c void csihandle(void) { char buf[40]; int len; switch (csiescseq.mode[0]) { default: unknown: fprintf(stderr, "erresc: unknown csi "); csidump(); /* die(""); */ break; ``` As such the investigation on how to fix this migrates to #2

doom commented

2026-08-12 21:24:59 +02:00

Author

Owner

doom added this to the OS Maintenance project

2026-08-15 01:59:38 +02:00

doom commented

2026-08-20 19:48:17 +02:00

Author

Owner

Sudden Shutdown

On subsequent boot-up:

 8月 20 13:53:50 iseki kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
 8月 20 13:53:50 iseki kernel: microcode: Current revision: 0x00000028
 8月 20 13:53:50 iseki kernel: microcode: Updated early from: 0x0000001c
 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: be00000000800400
 8月 20 13:53:50 iseki kernel: fbcon: Taking over console
 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffb8aa2b73 MISC ffffffffb8aa2b73
 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1787226830 SOCKET 0 APIC 2 microcode 28

After some cursory investigation, I couldn't find anything. Worst of all, the absence of logs it probably a tad scary.
At the time of shutdown, as far as I can recall, there is a 40m void in logs (til the prior logs).
If there has been an intrusion, not sure how I'd know...

# Sudden Shutdown On subsequent boot-up: ``` 8月 20 13:53:50 iseki kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' 8月 20 13:53:50 iseki kernel: microcode: Current revision: 0x00000028 8月 20 13:53:50 iseki kernel: microcode: Updated early from: 0x0000001c 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: be00000000800400 8月 20 13:53:50 iseki kernel: fbcon: Taking over console 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffb8aa2b73 MISC ffffffffb8aa2b73 8月 20 13:53:50 iseki kernel: mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1787226830 SOCKET 0 APIC 2 microcode 28 ``` After some cursory investigation, I couldn't find anything. Worst of all, the absence of logs it probably a *tad* scary. At the time of shutdown, as far as I can recall, there is a 40m void in logs (til the prior logs). If there has been an intrusion, not sure how I'd know...

👍 1