-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trace_printk() is used in kernel #2615
Comments
Same here. Same kernel, apparently happens super early, before any module has the opportunity to be loaded. [ 0.133935] printk: log_buf_len individual max cpu contribution: 4096 bytes |
is there anything weird else in the logs?
…On Sun, Apr 10, 2022, 06:50 Matteo Morini ***@***.***> wrote:
Same here. Same kernel, apparently happens super early, before any module
has the opportunity to be loaded.
—
Reply to this email directly, view it on GitHub
<#2615 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ54FKRPHPS74QLV54U4HDVELMD7ANCNFSM5SSNSMIA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
By the naked eye, nothing. Days later, though, a couple
appeared. I became confused by the successive Not tainted -> taint[ed] transition (no kernel modules were loaded in between)
btrfs seems somehow implied:
|
Fixed in 36150 - 5.16.18-1138.native #1 SMP Wed Apr 6 08:55:53 PDT 2022 x86_64 GNU/Linux |
When i was debugging an issue, in the
dmesg
I found the notice shown above in the output.I'm not kernel expert but just sending the output here. Maybe some switch needs to be turned off.
Oh, I just updated manually, and the kernel version is:
The text was updated successfully, but these errors were encountered: