This could still be a memory issue which is showing up in Gusty, but not
in Feisty or memtest86+. However, it could also be a kernel module
randomly corrupting pagecache kernel memory. Both of these will cause
the issues you mention. Incidently, the issue that it only occurs with
file writing rather than reading is a red-herring and is caused by file
caching behaviour in Linux. When Linux reads and writes a file the data
is cached in memory (page cache) for later reuse. If you read a file for
the first time (i.e. it is not already in the cache), there is no
opportunity for the data to become corrupted before it is read by the
program, with writing the data isn't immediately written to disk, but
kept in the cache for sometime where is being randomly corrupted before
being flushed to disk.
These issues are extremely hard to track down. If it is a kernel module
corrupting memory, the first thing is to determine if you have any
different modules loaded running on Gutsy than you have running Feisty.
If so, one of the additional/different modules may be the culprit.
Please attach the output you attached previously (dmesg, /proc/modules)
for the Feisty kernel. Also it would be helpful if you're aware of any
differences between hardware recognition in Feisty/Gutsy yourself.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New => Incomplete
--
Regression: File corruption on amd64/nVidia with 2.6.22-14-generic
https://bugs.launchpad.net/bugs/162478
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
