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 1299901
Summary: | [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000060 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bryce <root> | ||||
Component: | xorg-x11-drv-mga | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 23 | CC: | clinton, edgar.hoch, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, root, xgl-maint | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/e5ff872c7f0d98e8eba2c69d485bdbdc5a4ee0bf | ||||||
Whiteboard: | abrt_hash:7a2b9ea6b2b64ede39df6ad51d68326a18018efb;VARIANT_ID=server; | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-12-20 18:00:17 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
Bryce
2016-01-19 14:06:56 UTC
Created attachment 1116182 [details]
File: dmesg
Please test this scratch build when it completes and let me know if it resolves the issue. http://koji.fedoraproject.org/koji/taskinfo?taskID=13022511 Ok,.. lets see,.. dnf update * Running transaction Installing : kernel-core-4.3.5-301.fc23.x86_64 1/10 Installing : kernel-modules-4.3.5-301.fc23.x86_64 2/10 Installing : kernel-4.3.5-301.fc23.x86_64 3/10 Installing : kernel-modules-extra-4.3.5-301.fc23.x86_64 4/10 Upgrading : kernel-headers-4.3.5-301.fc23.x86_64 5/10 Erasing : kernel-4.3.3-303.fc23.x86_64 6/10 Cleanup : kernel-headers-4.3.5-300.fc23.x86_64 7/10 Erasing : kernel-modules-extra-4.3.3-303.fc23.x86_64 8/10 Erasing : kernel-modules-4.3.3-303.fc23.x86_64 9/10 Erasing : kernel-core-4.3.3-303.fc23.x86_64 10/10 ... edit the grub to reenable rhgb quiet,.. rebuild grub2 conf,.. reboot,... yeap thats doing the right thing now. [root@ZenV ~]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.3.5-301.fc23.x86_64 root=/dev/mapper/ZenV-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=ZenV/root vconsole.font=latarcyrheb-sun16 intel_iommu=on pci_pt_e820_access=on LANG=en_GB.UTF-8 rhgb quiet Thanks. (Do I close this or do you?) Phil =--= (In reply to Bryce from comment #3) > Ok,.. lets see,.. > > dnf update * > Running transaction > Installing : kernel-core-4.3.5-301.fc23.x86_64 > 1/10 > Installing : kernel-modules-4.3.5-301.fc23.x86_64 > 2/10 > Installing : kernel-4.3.5-301.fc23.x86_64 > 3/10 > Installing : kernel-modules-extra-4.3.5-301.fc23.x86_64 > 4/10 > Upgrading : kernel-headers-4.3.5-301.fc23.x86_64 > 5/10 > Erasing : kernel-4.3.3-303.fc23.x86_64 > 6/10 > Cleanup : kernel-headers-4.3.5-300.fc23.x86_64 > 7/10 > Erasing : kernel-modules-extra-4.3.3-303.fc23.x86_64 > 8/10 > Erasing : kernel-modules-4.3.3-303.fc23.x86_64 > 9/10 > Erasing : kernel-core-4.3.3-303.fc23.x86_64 > 10/10 > ... > edit the grub to reenable rhgb quiet,.. rebuild grub2 conf,.. reboot,... > yeap thats doing the right thing now. > > [root@ZenV ~]# cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-4.3.5-301.fc23.x86_64 root=/dev/mapper/ZenV-root ro > rd.lvm.lv=fedora/swap rd.lvm.lv=ZenV/root vconsole.font=latarcyrheb-sun16 > intel_iommu=on pci_pt_e820_access=on LANG=en_GB.UTF-8 rhgb quiet > > Thanks. (Do I close this or do you?) Thanks for testing. Our update tooling will close the bug when the fix is in the stable updates repository. kernel-4.3.6-201.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e7162262b0 kernel-4.4.2-300.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ec8b4ce774 kernel-4.3.6-201.fc22 has been pushed to the Fedora 22 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-2016-e7162262b0 kernel-4.4.2-301.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7e12ae5359 I'm running into the same defect on a Dell R610 with any 4.3.x kernel. kernel-4.4.2-301.fc23 has been pushed to the Fedora 23 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-2016-7e12ae5359 kernel-4.4.3-200.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a5ac00e07c kernel-4.3.6-201.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.4.2-301.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.4.3-200.fc22 has been pushed to the Fedora 22 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-2016-a5ac00e07c kernel-4.4.3-201.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9fbe2c258b kernel-4.4.3-201.fc22 has been pushed to the Fedora 22 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-2016-9fbe2c258b kernel-4.4.3-201.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |