Linux boot crash due to ramoops module NPE

Open
#2,548 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux
Domain
operating-systems

Research direction

Start by reproducing the SteamOS installer boot from a USB stick on the reported hardware, using ignore_loglevel to inspect the ramoops crash shown in the attached image. Compare the normal boot with module_blacklist=ramoops; done means SteamOS and its installer boot without manually modifying the Linux boot arguments.

Written by the indexing model from the issue text.

Description

Your system information
  • Steam client version:
  • SteamOS version: 3.8.12
  • Opted into Steam client beta?: [Yes/No] No
  • Opted into SteamOS beta?: [Yes/No] No
  • Have you checked for updates in Settings > System?: [Yes/No] Yes

CPU: Intel i7-13700K
Motherboard: AORUS ELITE AX/Z790 AORUS ELITE AX, BIOS FE 07/24/2023
RAM: 32GB
GPU: AMD Radeon RX6800XT

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen.

**What's expected **
SteamOS and SteamOS installer should boot without manually modifying linux boot args

** What happened **
StteamOS and installer bootstrap silently panic all the time

Steps for reproducing this issue:
  1. burn SteamOS image to usb stick and use the usb stick to boot OS
  2. after a few silent crashes and reboots, start to see "Current OS + Boot Menu" screen and enter grub
  3. press e to edit linux boot arg and add ignore_loglevel and start seeing dmesg crash messages as below:
Image
Warkaround:

add module_blacklist=ramoops to linux boot arg

Dominant language
No language data
Stars
2.6k
Forks
83
Avg merge
4m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ValveSoftware/SteamOS

All issues in ValveSoftware/SteamOS

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.