Bug 212255 - WARNING: at arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask
Summary: WARNING: at arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-12 17:38 UTC by Felice Tufo
Modified: 2021-03-18 08:21 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.11.3
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (93.16 KB, text/plain)
2021-03-12 17:38 UTC, Felice Tufo 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Felice Tufo 2021-03-12 17:38:42 UTC 
Created attachment 295819 [details]
dmesg

Hello,
i get two warnings booting kernel 5.11.3. The warning is present on later 5.11.x kernels (included 5.11.6) too, but does not show on 5.11.2.

------------[ cut here ]------------
[    6.099356] WARNING: CPU: 6 PID: 366 at arch/x86/kernel/fpu/core.c:129 kernel_fpu_begin_mask+0xa3/0xb0
 ---[ end trace 4cbc711ff0b0578b ]---

[    6.102354] ------------[ cut here ]------------
[    6.102354] WARNING: CPU: 6 PID: 366 at arch/x86/kernel/fpu/core.c:155 kernel_fpu_end+0x1e/0x30
Comment 2 Felice Tufo 2021-03-12 19:18:50 UTC 
Thanks Alex,
it seems that Linus merged those patches (just today) for the next -rc release, am I right?
If so, I'll do a quick test and let you know as soon as Ubuntu team will release the next mainline kernel (usually just 1 or 2 days after -rc is out).
Comment 3 Alex Deucher 2021-03-12 19:28:43 UTC 
(In reply to Felice Tufo from comment #2)
> Thanks Alex,
> it seems that Linus merged those patches (just today) for the next -rc
> release, am I right?

correct.
Comment 4 Felice Tufo 2021-03-15 09:24:41 UTC 
I confirm that the fix solves the bug on kernel 5.12.0-rc3 (at least on my test system).
Comment 5 Felice Tufo 2021-03-18 08:21:27 UTC 
Tested also on 5.11.7
Note You need to log in before you can comment on or make changes to this bug.