The following was filed automatically by anaconda: anaconda 11.5.0.59 exception report Traceback (most recent call first): File "<string>", line 68, in __iter__ File "/usr/lib/yum-plugins/whiteout.py", line 46, in postreposetup_hook for event, elem in iterparse(infile): File "/usr/lib/python2.6/site-packages/yum/plugins.py", line 179, in run func(conduitcls(self, self.base, conf, **kwargs)) File "/usr/lib/python2.6/site-packages/yum/repos.py", line 79, in doSetup self.ayum.plugins.run('postreposetup') File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 452, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 444, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/anaconda/yuminstall.py", line 1078, in <lambda> self.__withFuncDo(anaconda, lambda r: self.ayum.doRepoSetup(thisrepo=r.id), File "/usr/lib/anaconda/yuminstall.py", line 1109, in __withFuncDo fn(repo) File "/usr/lib/anaconda/yuminstall.py", line 1079, in doRepoSetup thisrepo=thisrepo, fatalerrors=fatalerrors) File "/usr/lib/anaconda/yuminstall.py", line 1036, in doBackendSetup self.doRepoSetup(anaconda) File "/usr/lib/anaconda/backend.py", line 271, in doBackendSetup if anaconda.backend.doBackendSetup(anaconda) == DISPATCH_BACK: File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1339, in nextClicked self.anaconda.dispatch.gotoNext() SyntaxError: no element found: line 1, column 0
Created attachment 350122 [details] Attached traceback automatically from anaconda.
The following error messages from your syslog indicate either hardware problems or a kernel driver error. That'd explain why you are getting a pretty odd error that we haven't seen from anyone else. If this were really a bug, we would be getting a ton of reports from it. <3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 <3>ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 <3> cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <3> res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error) <3>ata2.00: status: { DRDY ERR } <4>ata2.00: qc timeout (cmd 0xa0)
Try adding "pci=nomsi" to the boot options.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.