[Bug 14757] New: Data Corruption on AMD64 SATA System with Breezy Badger
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Mon Sep 5 20:17:26 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14757
Ubuntu | kernel-package
Summary: Data Corruption on AMD64 SATA System with Breezy Badger
Product: Ubuntu
Version: unspecified
Platform: amd64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel-package
AssignedTo: ben.collins at ubuntu.com
ReportedBy: c-t-b at gmx.de
QAContact: kernel-bugs at lists.ubuntu.com
Dear all,
writing data on SATA harddisk (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 espeacially 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 harddisk 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 suprising,
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.
Greetings.
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
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list