Blank message during boot is interpreted as an error

[pallaswept]

NVIDIA Open GPU Kernel Modules Version

595 but this is an old bug

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

openSUSE Tumbleweed

Kernel Release

Linux Pallas 6.19.10-1-default #1 SMP PREEMPT_DYNAMIC Wed Mar 25 11:02:57 UTC 2026 (a439317) x86_64 x86_64 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

RTX 3090

Describe the bug

During boot, a single empty line is logged. It is not logged as an error, but because it is empty, it is interpreted as an error, and generates a false positive when when testing for errors at boot. It appears to be coming from this module. Here's an example (it's the second line):

Apr 04 00:24:42 Pallas kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Apr 04 00:24:42 Pallas kernel: 
Apr 04 00:24:42 Pallas kernel: nvidia 0000:07:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Apr 04 00:24:42 Pallas kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  595.58.03  Release Build  (abuild@OBS)  Tue Mar 24 18:36:04 UTC 2026

And here it is showing up as an error:

> journalctl -b0 -p3
Apr 04 00:24:42 Pallas kernel:

To Reproduce

Boot

Bug Incidence

Always

nvidia-bug-report.log.gz

I'm sorry I don't have the time to make sure that script is something I'm OK with running or to check its output to see if it's something I'm OK with sharing. I'm sure you can reproduce this, every system seems to do it.

More Info

I've seen users postulate that this empty line is intended as a separator. Perhaps it could be just a hyphen or something, so it's not a truly empty line, and is not misinterpreted as an error?

[harsh01blr]

A fix to align the module’s build flags with the newer kernel checks, patch the failing macro to restore compatibility. Happy to help if this can be assigned.