Data Corruption on AMD64 SATA System

Bug #63815 reported by Linus van Pelt
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Dear all,

unfortunately you close Bug #20988 due to inactivity. Sorry for that but I was a little short in time. Nevertheless the problem still exists and I will give you some more information today.

With success I tested the following kernels:

Knoppix 4.0.1 Linux Knoppix 2.6.12 #2 SMP Tue Aug 9 23:20:52 CEST 2005 i686 GNU/Linux

KNOPPIX 4.0.2 Linux Knoppix 2.6.12 #2 SMP Tue Aug 9 23:20:52 CEST 2005 i686 GNU/Linux

Ubuntu 5.04 AMD64 Linux 2.6.10-6-amd64-generic #1 Mon Jan 16 19:04:15 UTC 2006 x86_64 GNU/Linux

Ubuntu 5.04 AMD64 Linux 2.6.10-6-amd64-generic #1 Fri Sep 15 12:24:24 UTC 2006 x86_64 GNU/Linux

I tested the following configuration without success:

Ubuntu 6.04 Linux 2.6.15-18-amd64-generic #1 SMP PREEMPT Thu Mar 9 14:37:22 UTC 2006 x86_64 GNU/Linux

Ubuntu 6.06 AMD64 Linux 2.6.15-26-amd64-k8 #1 SMP PREEMPT Fri Sep 8 20:14:40 UTC 2006 x86_64 GNU/Linux

Ubuntu 6.10 AMD64 Linux 2.6.17-10-generic #2 SMP Tue Sep 26 15:43:28 UTC 2006 x86_64 GNU/Linux

Ever when a precompiled kernel failed a build-from-sources kernel fails as well.

I build also a kernel from the sources at kernel.org (libata version 2.00;sata_sil 0000:01:07.0: version 2.0) without success:
kernel.org AMD64 Linux gecko 2.6.18 #1 SMP PREEMPT Tue Oct 3 16:58:22 CEST 2006 x86_64 GNU/Linux

Beside the mentioned working Live-CD-Systems (Knoppix) I tested without sucess the live distribution of Ubuntu 5.10 (i386 and AMD64 ) and some other live distributions

KANTONIX 2005-04 AMD64 Linux Kanotix 2.6.14-kanotix64-9 #1 SMP PREEMPT Wed Dec 28 10:20:07 GMT 2005 x86_64 GNU/Linux

KANTONIX 2005-04 386 Linux Kanotix 2.6.14-kanotix-9 #1 PREEMPT Wed Dec 28 10:17:53 CET 2005 i686 GNU/Linux

SuSE 93 Linux linux 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC 2005 i686 athlon i386 GNU/Linux

Just to be secure thats there's no hardware defect I changed main memory and hard disk including cables without success.

In the Internet I found some other people with same or similar problems but finally none of there hints helped. Some of which mentioned a timing problem which may be solved by some BIOS settings but my BIOS don' t give me the opportunity to set some time. Is there a software solution?

I hope I will be able to support you much more in future and help solving this problems.

Best regards.

- - - - -
Here a short review of the former report:
writing data on SATA hard disk (Silicon Image 3512A Onboard-RAID) under Breezy
Badger (kernel version 2.6.12-7-amd64-k8, libata version 1.11 loaded; sata_sil
version 0.9) cause sometimes errors in md5sum check especially when large files
are copied or moved.

The same problem occurs under Fedora Core 4 or SuSE 9.3 with different kernel
versions.

Memory and hard disk have been checked without any evidence.

With Hoary Hedgehog kernel 2.6.10-5-amd64-k8 everything work fine (libata
version 1.10 loaded; sata_sil version 0.8). Some x86 kernels (e.g. Knoppix) also
works without problems as well as Debian Sarge AMD64 (not really surprising,
isn't it?).

The modules loaded in Breezy seem not to differ relevantly from Hoary except of
some versions (of cause).

I guess I have tried nearly everything to figure out where the problem is
located - so I may give any additional information on request.

So maybe anybody out there has any idea and find help before I go mad.

System description:
  Shuttle XPC SN85Gv2
  Motherboard FN85
  NVIDIA nForce3

  AMD Athlon(tm) 64 Processor 2800+

  RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI
3512 (rev 1)
  Harddisk
  Vendor: ATA Model: SAMSUNG SP1614C Rev: SW10
  Type: Direct-Access ANSI SCSI revision: 05

Linus van Pelt (c-t-b)
description: updated
Linus van Pelt (c-t-b)
description: updated
Revision history for this message
towsonu2003 (towsonu2003) wrote :

I am closing this one (I re-opened the older one) so the work can goon on the other bug report. When a bug is closed because there was no response and you will respond, you can reopen it. thanks :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.