Bug 1806747
| Summary: | [abrt] i915_active_ref: general protection fault in i915_active_ref [i915] | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Don Lindsay <redhatbugzilla> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 31 | CC: | airlied, amk, bskeggs, hdegoede, hyphen9, ichavero, itamar, jarodwilson, jeremy, jforbes, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, marek.gresko, masami256, mbukatov, mchehab, mjg59, steved, y9t7sypezp | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/2cd6fd0f23fa0cbc146a5e90b0ac0aeb912c569e | ||||||||
| Whiteboard: | abrt_hash:4e59372f747eff50b8acf90a47b7a7c1d7e0533b; | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-11-24 17:09:13 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Don Lindsay
2020-02-24 21:40:09 UTC
Created attachment 1665507 [details]
File: dmesg
Thanks for your report. The call trace looks very similar to the ones in these bug reports, although they are against 5.4 kernels: Bug 1805278 - i915: kernel NULL pointer dereference, address: 0000000000000040 appearing randomly Bug 1803372 - [abrt] i915_active_ref: BUG: kernel NULL pointer dereference, address: 0000000000000040 [i915] *** Bug 1806767 has been marked as a duplicate of this bug. *** This morning I hit the problem twice with kernel kernel-5.5.5-200.fc31.x86_64, which I upgraded to a day before (this means that I was running 5.5.5-200 for one whole day without hitting the problem). I no longer see this when I rebooted with kernel-5.4.20-200.fc31.x86_64, and neither did I see this before with other 5.4 kernel. The current "stable" kernel built for Fedora is available: kernel-5.5.6-201.fc31, kernel-headers-5.5.6-200.fc31, & 1 more https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd64d683c *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those. I no longer observe the problem with kernel 5.5.6-201.fc31.x86_64 Thanks for letting us know. kernel-5.5.7-200.fc31.x86_64 exhibited this bug, or one just like it, on my box, today. I say "or one just like it" because the problem reporting tool, run after I power cycled the box, did not detect that I'd had a crash. So I don't have an details of the crash, sorry. (In reply to Don Lindsay from comment #9) > kernel-5.5.7-200.fc31.x86_64 exhibited this bug, or one just like it, on my > box, today. Thanks for reopening this bug. This is currently in the "updates-testing" repo: kernel-5.5.8-200.fc31, kernel-headers-5.5.8-200.fc31, & 1 more https://bodhi.fedoraproject.org/updates/FEDORA-2020-d8c4450b82 > I say "or one just like it" because the problem reporting tool, run after I > power cycled the box, did not detect that I'd had a crash. So I don't have > an details of the crash, sorry. You can probably get the call trace with the journalctl "-b" option. This saves the log for the previous boot: $ journalctl -b -1 --no-hostname -k > dmesg-2.txt For a list of previous boots: $ journalctl --list-boots Created attachment 1668371 [details]
output of journalctl -b -2 --no-hostname -k (as suggested)
(In reply to Don Lindsay from comment #11) > Created attachment 1668371 [details] > output of journalctl -b -2 --no-hostname -k (as suggested) Thanks for attaching the log. It doesn't have a call trace, but it has a lot of error messages like this at the end: Mar 06 08:51:37 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=21470 end=21471) time 247 us, min 2146, max 2159, scanline start 2135, end 2168 That must be a different bug, so I suggest opening a new bug with this as the bug summary: "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A" And please attach dmesg-2.txt to that new bug. (In reply to Don Lindsay from comment #9) ... > I say "or one just like it" because the problem reporting tool, run after I > power cycled the box, did not detect that I'd had a crash. So I don't have > an details of the crash, sorry. ABRT looks for kernel call traces in the log, but there wasn't one in that case. In contrast, there is a call trace in the first attachment. Snippet from the attached dmesg: ... [14471.621232] Call Trace: [14471.621341] i915_active_ref+0x62/0x180 [i915] ... See, also: $ pgrep -fa 'abrt-dump-journal-oops' This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |