Issue #580: [kernel] [abrt] dma_alloc_noncontiguous: WARNING: CPU: 0 PID: 1429 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x32a/0x380 | rhbz#2020759 - blocker-review

fedora-qa / blocker-review

#580 [kernel] [abrt] dma_alloc_noncontiguous: WARNING: CPU: 0 PID: 1429 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x32a/0x380 | rhbz#2020759

Closed 2 years ago by blockerbot. Opened 3 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2020759
Information from BlockerBugs App:

Current vote summary

Rejected FinalBlocker (+0, 0, -3)
- -1 by adamwill, nielsenb, lruzicka

Commented but haven't voted yet: coremodule

The votes have been last counted at 2022-02-21 16:33 UTC and the last processed comment was #comment-782626

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)

nielsenb commented 3 years ago

Violation of the "There must be no SELinux denial notifications or crash notifications on boot of or during installation" part of the SELinux and crash notifications criteria.

FinalBlocker +1

coremodule commented 3 years ago

AGREED AcceptedFinalBlocker

Discussed during the 2022-02-07 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:

"There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-07/f36-blocker-review.2022-02-07-17.00.txt

blockerbot commented 3 years ago

The following votes have been closed:

Accepted FinalBlocker (+1, 0, -0)
- +1 by nielsenb

adamwill commented 3 years ago

So as mentioned on the bug report, we found out that this likely happens only with debug kernels, and we do not ship Beta or Final releases with debug kernels. So I think it makes sense to re-vote this one, and have cleared the AcceptedBlocker tag from the bug. So:

REVOTE FinalBlocker

adamwill commented 3 years ago

To support the notion that this only happens on debug kernels, I'm currently running a non-debug kernel and I do not have this trace in my system logs. When I run a debug kernel I do get it. So I now vote:
FinalBlocker -1

nielsenb commented 3 years ago

FinalBlocker -1

If it appears in a regular kernel, we can vote again.