Hide Forgot
Description of problem: The 'nouveau' module is writing a huge number of messages to the /var/log/messages file, and causing problems when the /var filesystem fills up. Version-Release number of selected component (if applicable): kernel-3.1.6-1.fc16.x86_64 How reproducible: Usually happens in less than one week. Steps to Reproduce: 1. Use system in run-level 5 ... 2. Watch the size of the log file carefully ... 3. Actual results: System disk can fill. Expected results: I expect the system not to write more than 1GB of messages per day! Additional info: Most of the messages are of the form: Jan 1 05:58:13 hogs kernel: [292643.108503] [drm] nouveau 0000:00:05.0: PFIFO_CACHE_ERROR - Ch 3/7 Mthd 0x1efc Data 0x000001bf The system logged over 4.5GB of nouveau messages in only 12.5 hours on Jan 1.
I think this is a problem of "High" or "Urgent" severity. I'm attaching a spreadsheet which gives some more info on what kernel versions have had the problem, and how many bytes per hour are being consumed by the 'nouveau' syslog messages. Check out line #9 and #20 -- 8 GiB/hr and 7GiB/hr! So, if I want to allocate enough disk space to rotate the logs only once per week (the default configuration for /var/log/messages), then I'll need ~10GiB/hr * 24 hr/day * 7 days/week = 1,680 GiB. Over 1.5 TeraBytes just to log 'nouveau' messages!
Created attachment 562392 [details] spreadsheet w/ analysis of nouveau log message volumes (12/2011-02/2012)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.