Hide Forgot
Created attachment 534295 [details] /var/log/messages Description of problem: I saw this problem on both F15 and F16. My system will eventually lockup due to the file system being marked read-only. I initially thought it was a bad hard drive. I ran the Western Digital diagnostics, and they came back clean. So I am wondering if it is a kernel driver issue instead. I'd be happy to find out it is just an incorrect configuration on my part. Version-Release number of selected component (if applicable): Numerous kernels in Fedora 15. I also see it in Fedora 16 - 3.1.0-7.fc16.x86_64 How reproducible: Allow the system to run as normal. Issue does occur more often when the system is in runlevel 5 as opposed to runlevel 3. Actual results: File system gets marked read-only and ATA error messages are shown in /var/log/messages. Eventually the system may lock up and require a power cycle. Expected results: File systems do not get marked read-only. Additional info: First example in this log file (this was still under F15) Nov 13 16:14:30 Another example (now under F16) Nov 14 12:44:53
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Issue still occurs in kernel 3.3.0-4.fc16.x86_64. System appears to stay stable when running for long periods of time in runlevel 3 even while running CrashPlan backup software to copy data to the cloud. But system appears to have the issue more often when running in runlevel 5. The issue occurs in runlevel 5 whether or not I am actively using the system (as in, it will still happen if the system is sitting idle overnight). This may be related to some graphics issues or just a result of additional processes that gnome may run. Please let me know if I can provide any further information. I have another /var/log/messages as well as a sosreport if it will help.
Are you still seeing this with 3.4 or 3.5? Can you recreate it without any proprietary modules loaded?
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.