Bug 279224 - [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with VT_MAXWINDOWS or SC_NO_CUTPASTE
Summary: [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with ...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 14.0-STABLE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2024-05-22 16:42 UTC by Andre Albsmeier
Modified: 2024-06-11 14:16 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Albsmeier 2024-05-22 16:42:15 UTC 
[If this is considered to be a ports issue feel free to modify the PR]

14.0-STABLE and 14.1-BETA as of today need drm-61-kmod (instead of drm-515-kmod as in earlier versions). Loading i915kms if the kernel had been built with either VT_MAXWINDOWS or SC_NO_CUTPASTE makes the system crash.

Maybe this is something similar to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241697

which had hit me as well...
Comment 1 Anton Saietskii 2024-06-11 12:37:41 UTC 
(In reply to Andre Albsmeier from comment #0)

How does crash look like? For me, it's like this (on 14.1-RELEASE amd64):
1. Screen goes black.
2. Screen turns on, displays some DRM-related messages.
3. Screen goes black again.
4. System reboots.

Note: there's no panic visible and I have PANIC_REBOOT_WAIT_TIME=-1.
Comment 2 Anton Saietskii 2024-06-11 12:52:42 UTC 
Commented VT_MAXWINDOWS, recompiled kernel -- boots fine now.
Comment 3 Andre Albsmeier 2024-06-11 14:09:12 UTC 
(In reply to Anton Saietskii from comment #1)
> How does crash look like?

1. System boots.
2. When it loads i915kms.ko, screen goes black
3. goto 1.

I can't see any messages but that doesn't mean that there are none. Maybe
the LCD needs some time to switch resolution and the crash/reboot ist faster.
Comment 4 Anton Saietskii 2024-06-11 14:16:27 UTC 
(In reply to Andre Albsmeier from comment #3)

Looks pretty similar to mine, except your steps are less. It may be related due to my systems boots in UEFI, which in turn means it's already in high-resolution graphic mode before even loader starts. This may explain why I see some DRM messages -- time for switching is saved.