Bug 452975
| Summary: | set_page_address oops (possibly i915 drm related?) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Getman <chris_getman2001> | ||||||||||||
| Component: | kernel | Assignee: | Dave Airlie <airlied> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 9 | CC: | kernel-maint | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2009-07-14 14:58:21 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
Chris Getman
2008-06-26 12:15:01 UTC
Created attachment 310324 [details]
text file from syslog
Created attachment 310325 [details]
additional information about the system
Created attachment 310357 [details]
another crash
Currently a very frequently reported oops at http://www.kerneloops.org/search.php?search=set_page_address No-one has a clue how this could happen unfortunately. Could you try adding 'Option "NoDri"' to the devices section of your /etc/X11/xorg.conf and going without 3d for a while. That would ack/nack one suspicion people seem to have that it may be related to the DRI changes. It's not happening at all in the F8 kernel, which is missing those drm patches. Output of the command 'grep kmap *drm*patch' against the kernel source is interesting... Also i915 is loaded in 142 of those reports... I have added the following: Section "Device" Identifier "Videocard0" Driver "nv" Option "NoDri" EndSection -Chris hmm. if you have an add-in card like your nvidia, the 915 drm shouldn't be getting used anyway. (It may still get loaded, but it should be completely unused). Strange. I just experienced another crash post xorg.conf modifications. I will upload the file now. Let me know if there is any other debug that I should provide. -Chris Created attachment 310685 [details]
/var/log/messages output
hmm. just to completely rule it out, move /lib/modules/2.6.25.6-55.fc9.i686/kernel/drivers/char/drm/i915.ko to your homedir, and reboot. That should prevent it from ever getting loaded. Though it's looking unlikely that it's related, which would be disappointing. Yup, it was being loaded. Here is the output from lsmod: [root@getman ~]# lsmod Module Size Used by ... i915 84484 0 ... I will move the file and reboot. I'll be sure to let you know what happens. -Chris Created attachment 310757 [details]
Another crash
The attached crash happened after the removal of the i915 module. I am up for any ideas that you might have. -Chris really clutching at straws now.. boot with agp=off too ? Before I did your recommendation, I upgraded to the 2.6.25.9-76.fc9.i686 kernel.
I ended up with the same crashes.
I then passed the agp=off, e.g. (grub.conf):
title Fedora (2.6.25.9-76.fc9.i686)
root (hd0,0)
kernel /vmlinuz-2.6.25.9-76.fc9.i686 ro root=/dev/md1 rhgb quiet agp=off
initrd /initrd-2.6.25.9-76.fc9.i686.img
The system has remained nice and stable all weekend. I've been pounding on it
for a while, and no crashes.
Is there anything I can do to assist further?
-Chris
ok, that's a very useful data point. I guess it's time to re-review the recent agp changes. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 WONTFIX if it remains open with a Fedora 'version' of '9'. 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 prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. Thank you for reporting this bug and we are sorry it could not be fixed. |