Sample Header Ad - 728x90

Why do kernel oopses taint and prohibit reporting with ABRT?

5 votes
1 answer
812 views
I freshly installed Fedora 28 on a laptop. On boot, I get a kernel oops I would very much like to report. However, ABRT recognizes the kernel as tainted with flags GW and thus refuses to report it. If I take a look at the [abrt documentation](http://abrt.readthedocs.io/en/latest/faq.html#what-is-tainted-kernel-and-why-is-my-kernel-tainted) , it is written that W means "a warning has previously been issued by the kernel." whereas G tells me that only GPL-compatible modules are loaded (as expected, I did not install any kernel modules myself). But what exactly does this mean? Has the warning been issued by the kernel to bugzilla? This message really doesn't help me understanding why a freshly installed Linux leaves me with an error I am unable to report ... cat /proc/sys/kernel/tainted also just gives the value 512, i. e. there is only a kernel warning according to the [sysctl documentation](https://github.com/torvalds/linux/blob/master/Documentation/sysctl/kernel.txt) . So how can I find out what exactly happened and why am I not allowed to report it with ABRT? **Edit**: According to [this comment from 2012](https://bugzilla.redhat.com/show_bug.cgi?id=786280#c3) on the RedHat Bugzilla > 'w' means a warning has already occurred. We only care about the first one, which abrt should have already filed. Thus I looked to find anything in the tainted report to find out where, if at all, ABRT reported the "first one" and found [this report on FAF](http://retrace.fedoraproject.org/faf/reports/2147917/) -- however, the kernel is marked as "tainted" as well, so the report will probably not be considered for fixing and I still don't know, why.
Asked by Zollern (83 rep)
May 2, 2018, 08:10 AM
Last activity: May 4, 2018, 11:45 AM