Summary: | install-amd64-minimal-20240630T170408Z.iso: Terminal permanently stops responding to input (freezes) | ||
---|---|---|---|
Product: | Gentoo Release Media | Reporter: | Cam Spiers <camspiers> |
Component: | InstallCD | Assignee: | Gentoo Release Team <releng> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | bkohler, camspiers, genkernel, immoloism |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cam Spiers
2024-07-02 13:27:12 UTC
To add some notes to this, I originally became suspicious of genkernel being the issue when the livegui had trouble but the installcd was freezing. Running through all the troubleshooting steps to narrow it down to a genkernel issue with a 7950x3d but as it's only confirmed in the installcd I've marked it as a releng bug and cc the genkernel project in. to clarify again, livegui (dist-kernel) - works fine installcd with genkernel - hard locks after 30 minutes installcd with dist-kernel - works fine Are you able to ssh in from another machine and see if it's otherwise responsive, and if there are any errors in dmesg? As discussed with Ben on IRC this is a full lock which suggested it could be a powermgmt issue. I can't see anything missing in releng kconfig from a quick look at https://github.com/gentoo/releng/blob/master/releases/kconfig/amd64/amd64-6.6.30.config (I forgot to check this before CCing genkernel so apologises if unneeded.) For users hitting this right now please use the latest version of the livegui when using a 7000x3d CPU which affected by this bug as that will allow you get around the issue and install Gentoo as normal. Anyone that wish to help provide more info to solve this fully then please can you mount a second storage device to the system which won't wipe at shutdown and run "tail -f /var/log/dmesg > /mnt/<2nddrv>" on a 7950x3d for the full 30 minutes until it hard locks then tar.xz the log file and attach it to this bug report so we can all look further into it. I should be able to provide the output of dmesg during a crash within the next 10hrs. Running the following after booting into live CD: ``` mount /dev/nvme2n1p2 /mnt/ubuntu-root tail -f /var/log/dmesg > /mnt/ubuntu-root/dmesg.log ``` I captured the following: ``` [ 15.985254] Loading firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin [ 15.988903] mt7921e 0000:09:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240219110958a [ 15.998642] Loading firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 15.998739] mt7921e 0000:09:00.0: WM Firmware Version: ____010000, Build Time: 20240219111038 [ 16.030756] Loading firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 16.081037] wl: loading out-of-tree module taints kernel. [ 16.081040] wl: module license 'MIXED/Proprietary' taints kernel. [ 16.081041] Disabling lock debugging due to kernel taint [ 16.081042] wl: module license taints kernel. ``` However I will note that this output happened right after boot. There was nothing more added when the freeze occurred. (I confirmed this because I catted the dmesg.log after boot, and took a photo of it). |