Bug 1010002
Summary: | invalid opcode 0xaa | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fahad Alduraibi <fadnix> | ||||
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 19 | CC: | accounts, airlied, ajax, ashes-iontach, bskeggs, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa, ohadlevy, tpelka | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:336ac49c3f43a3469f67ed98a38050d2fdcff57a | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1063947 (view as bug list) | Environment: | |||||
Last Closed: | 2015-02-17 17:15: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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1063947 | ||||||
Attachments: |
|
Description
Fahad Alduraibi
2013-09-19 16:43:44 UTC
Created attachment 800037 [details]
File: dmesg
I have the same problem: Hardware: ASUS N750JV Notebook OS: Fedora 19 x64 No problems during installation or use with default kernel 3.9.5-301. After installation i updated to kernel 3.11.1-200 using "yum update". Booting this kernel causes the above kernel panic during boot. Today i updated to kernel 3.11.2-201. This kernel has the same problem. I also have this problem: Hardware: Clevo W350STQ, i7-4700MQ, NVIDIA GTX 765M (N14E-GE) OS: Fedora 19 x64 Similarly, doesn't crash on kernels 3.9 and 3.10, but does with 3.11. I was getting the invalid opcode 0xAA before though, so although it is probably related (card not being POSTed, from what I read on the nouveau irc log), it might not directly be the cause of this crash. This error message was only ever visible on the screen for a short time, so perhaps other people were getting it and not seeing it? NB this commit deals with the opcode somewhat, so it will be interesting to see if it fixes this and several other issues with the card: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau/core/subdev/bios/init.c?id=5495e39fb3695182b9f2a72fe4169056cada37a1 This issue is fixed for me with kernel 3.11.6-200. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |