GNOME Abrt thinks that my kernel is tainted, but it doesn't appear to be

Ask Fedora
, , ,
1

When I invoke gnome-abrt-1.4.3-3.fc41.x86_64 to report discussion.fedoraproject.org/t/146166/1, I see:

Screenshot_20250227_003224
Screenshot_20250227_0032241280×690 62.4 KB

A kernel problem occurred, but your kernel has been tainted (flags:GBDL). Explanation:
B - Bad page referenced or some unexpected page flags.
D - Kernel has oopsed before.
L - A soft lockup has previously occurred.
Kernel maintainers are unable to diagnose tainted reports.

However, the undermentioned commands appear to demonstrate otherwise: [1]

    1. #!/usr/bin/env sh
cat /proc/sys/kernel/tainted

    2. 0

    1. #!/usr/bin/env sh
sudo dmesg | grep -i taint

    2. $Null

    1. #!/usr/bin/env sh
for i in $(seq 18); do echo $(($i-1)) $(($(cat /proc/sys/kernel/tainted)>>($i-1)&1)); done

    2. 0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
14 0
15 0
16 0
17 0

Consequently, how can I ascertain what it considers to be taint?

  1. discussion.fedoraproject.org/t/92303/4 ↩︎

1 Like
2

That image shows the message may be a result of a soft lockup which is being discussed here.

3

@computersavvy, certainly the report is due to the cited problem, but do you mean that the taint message is also caused by the lockup?

If so, doesn’t that render Abrt fairly useless for kernel reports, if it gets confused about whether the kernel is tainted when it crashes merely because it’s… crashed?

4

I’ve reported this upstream: