Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1749949
Summary: | iwlwifi FW error in SYNC CMD GEO_TX_POWER_LIMIT | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 31 | CC: | airlied, bskeggs, bugzilla, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, pbrobinson, steved | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | kernel-5.3.1-300.fc31 kernel-5.3.2-300.fc31 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2019-09-26 00:02:08 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 1269538 | ||||||||||
Attachments: |
|
Description
Paul Whalen
2019-09-06 20:30:15 UTC
Created attachment 1612558 [details]
dmesg
Spoke too soon, this also affects vanilla f31. Created attachment 1612565 [details]
lsusb
Created attachment 1612566 [details]
lspci
Could be a dup of bug 1745766. Possible related upstream bugs, in particular the first which directly refers to https://bugzilla.kernel.org/show_bug.cgi?id=204151 https://bugzilla.kernel.org/show_bug.cgi?id=204153 I'm not sure at what point this is a legitimate complaint to ask for a revert for whatever caused the regression. Is anyone else seeing performance regressions coinciding with these splats? I'm seeing 8x performance reduction consistently on 5.3.0 kernel, but only intermittantly on 5.2.x kernel, and no regression at all with 5.1.x. So I guess it's complicated. (In reply to Chris Murphy from comment #5) > Could be a dup of bug 1745766. Nope, there were two distinct problems. One was fixed some time ago, this one just got a patch. I hit both bugs at the same time, first the firmware splat with this bug's complaint, and then I get the kernel backtrace in 1745766. I don't know if they're related, but the other one is definitely not fixed in either 5.2 or 5.3 series. FEDORA-2019-43830aa346 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-43830aa346 Verified fixed with 5.3.1-300.fc31.x86_64. kernel-5.3.1-300.fc31, kernel-headers-5.3.1-100.fc31, kernel-tools-5.3.1-100.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. FEDORA-2019-fbcb04143f has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-fbcb04143f kernel-5.3.2-300.fc31, kernel-headers-5.3.2-300.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-fbcb04143f kernel-5.3.2-300.fc31, kernel-headers-5.3.2-300.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |