File corruption when using kernels 2.6.18+

I am using kernel 2.6.17.14, and would like to use newer versions for the wireless code but I get file corruption with any kernel more recent than this. My system uses a SiS645DX chipset (it is a rebadged CLEVO D400E) with 5513 IDE.

I get this corruption with read/writes, i.e using "cp", "dd", when compiling software, writing to CD, etc etc. An example:

cp ../Changelog-2.6.18 .
diff Changelog-2.6.18 ../Changelog-2.6.18

16377c16377
< LD .top_vmlinux1
---
> LD .tmp_vmlinux1
23954c23954
< Date: Mon Jul 1% 04:45:11 2006 -0700
---
> Date: Mon Jul 10 04:45:11 2006 -0700
24955c24955
< This is generally useful, but partacularly helps see if it is the same sector
---
> This is generally useful, but particularly helps see if it is the same sector
31879c31879
< [MMC] sdhci: version bump cdhci
---
> [MMC] sdhci: version bump sdhci
42955c42955
< Replace `he temp makefile hacks with proper CONFIG entries, which are also
---
> Replace the temp makefile hacks with proper CONFIG entries, which are also
49050c49050
< and this task is(already holding:
---
> and this task is already holding:
[output clipped]

I would suspect a memory problem but memtest86+ gives no errors despite numerous passes, and I get no errors in older kernels. Does anyone have any idea what changed in 2.6.18 to cause such an error?

I have tried some obvious things (see thread on linuxquestions.org: http://www.linuxquestions.org/questions/showthread.php?t=578200), but I don't understand enough about the kernel to get any further.

Neil.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: FreeBSD 7.0 crashed when running super-smack upon PostgreSQL
    ... Is there any chance I can get remote access to a box holding the synchronized kernel, kernel debugging symbols, source code, and core dump? ... It sounds like TCP in a user thread is stumbling over a violation of system invariants (don't sleep while holding a mutex) performed by another thread. ... We need to track down the original thread and figure out why it's sleeping while holding that lock -- perhaps it's a user thread performing a copyin/copyout holding the lock, or perhaps an ithread or other software interrupt thread acquiring a lock of an inappropriate type while holding the lock. ... kgdb has its own thread ID scheme so you'll need to use info threads to track down the right kgdb thread id before you can select the identified kernel thread/process. ...
    (freebsd-stable)
  • RE: Used Memory Not Clearing Down On Redhat Machines.
    ... > Pages in the inactive dirty state ought to be getting flushed ... > causing the kernel not to properly launder the inactive dirty ... > don't have any hung processes that could be holding the ... > memory open, you should check to see if there is a newer ...
    (RedHat)
  • Re: splice/tee bugs?
    ... maybe the test found a way to exit the kernel previously while holding ... the lock? ...
    (Linux-Kernel)
  • RE: Used Memory Not Clearing Down On Redhat Machines.
    ... > You have an awful lot of memory in the in_d state. ... > causing the kernel not to properly launder the inactive dirty ... > and holding all of this memory open. ... Unix Systems Administrator ...
    (RedHat)
  • Re: Writing a plain text file to disk from kernel space
    ... Any good tutorials/pointers on how to get started with kernel ... I found what looks to be a very comprehensive kernel debugging reference here: http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf ... do that while holding a non-sleepable lock. ...
    (freebsd-hackers)