Bug 11029 - md5sum counts wrong and data corruption on copy
Summary: md5sum counts wrong and data corruption on copy
Status: REJECTED INVALID
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 high
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-03 03:25 UTC by Anton Arapov
Modified: 2008-09-11 23:57 UTC (History)
1 user (show)

See Also:
Kernel Version: kernel-2.6.25-14.fc9
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
dmesg output in Fedora (23.40 KB, text/plain)
2008-07-03 03:29 UTC, Anton Arapov
Details
dmesg output in RHEL (20.97 KB, text/plain)
2008-07-03 03:31 UTC, Anton Arapov
Details
hdparm output (1.42 KB, text/plain)
2008-07-03 03:32 UTC, Anton Arapov
Details
lspci output (7.38 KB, text/plain)
2008-07-03 03:33 UTC, Anton Arapov
Details

Description Anton Arapov 2008-07-03 03:25:29 UTC
Failing kernels version: 
  RHEL5.1+, kernel-2.6.18-53.el5
  Fedora9, kernel-2.6.25-14.fc9

Distribution: 
  Fedora/RHEL

Hardware Environment:
  mboard: GigaByte nForce4 SLI Intel Edition with latest stable BIOS
  2xhdd: seagate and maxtor

Problem Description:
  local or over ssh file copy produce corrupted file
  md5sum wrong for original non-corrupted files

Notice:
  mem=3072M and iommu=soft does not help
  tested with different SATA cables.
  
  following in RHEL5.2's dmesg. No problems in Fedora9.
ata1.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
ata1.00: CPB resp_flags 0x11: , CMD error
ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
         res 51/04:00:0b:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata2.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
ata2.00: CPB resp_flags 0x11: , CMD error
ata2.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
         res 51/04:00:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata2.00: status: { DRDY ERR }
ata2.00: error: { ABRT }
Comment 1 Anton Arapov 2008-07-03 03:27:47 UTC
correct md5sum:
 5390f9f703e083cf1470fb438ea49082  rhel-5.2-server-x86_64-dvd.iso

md5sum's, which I getting in RHEL5
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso
 [root@pepe tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 ffeb4fe9997771500a825a0ad1e6a322  rhel-5.2-server-x86_64-dvd.iso

in Fedora9:
 [root@fedorasrv tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 8d712c92acbd9878098a3dccb7da4845  rhel-5.2-server-x86_64-dvd.iso
 [root@fedorasrv tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 8d712c92acbd9878098a3dccb7da4845  rhel-5.2-server-x86_64-dvd.iso
 [root@fedorasrv tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 8d712c92acbd9878098a3dccb7da4845  rhel-5.2-server-x86_64-dvd.iso
 [root@fedorasrv tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 8d712c92acbd9878098a3dccb7da4845  rhel-5.2-server-x86_64-dvd.iso
 [root@fedorasrv tmp]# md5sum rhel-5.2-server-x86_64-dvd.iso 
 8d712c92acbd9878098a3dccb7da4845  rhel-5.2-server-x86_64-dvd.iso
Comment 2 Anton Arapov 2008-07-03 03:29:38 UTC
Created attachment 16711 [details]
dmesg output in Fedora
Comment 3 Anton Arapov 2008-07-03 03:31:02 UTC
Created attachment 16712 [details]
dmesg output in RHEL
Comment 4 Anton Arapov 2008-07-03 03:32:40 UTC
Created attachment 16713 [details]
hdparm output
Comment 5 Anton Arapov 2008-07-03 03:33:45 UTC
Created attachment 16714 [details]
lspci output
Comment 6 Anton Arapov 2008-07-03 03:36:53 UTC
Host freezes from time to time on file copy.
No problems at all in M$ environment.
Comment 7 Thomas Gleixner 2008-09-11 07:17:17 UTC
Is this still a problem on latest mainline kernel (2.6.27-rc6) ?
Comment 8 Anton Arapov 2008-09-11 23:57:48 UTC
has been solved by changing RAM modules. sorry for not letting you know.

Note You need to log in before you can comment on or make changes to this bug.