Bug 6253 - sd 0:0:0:0: SCSI error: return code = 0x8000002
Summary: sd 0:0:0:0: SCSI error: return code = 0x8000002
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: i386 Linux
: P2 blocking
Assignee: Tejun Heo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-20 04:22 UTC by Bill Strig
Modified: 2007-08-08 20:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.15.2
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bill Strig 2006-03-20 04:22:35 UTC 
Most recent kernel where this bug did not occur:
Distribution: Debian Testing
Hardware Environment:

Samsung HD160JJ - 160 GB SATA
Asus p4p800s-X
Intel Pentium 3.0 GHz HT
768 MB DDRAM
WriteMaster DVD +/- R/RW
Nvidia GeForce2 64MB

Software Environment:
Windows XP(/dev/sda1(fat32) and /dev/sda2(Ntfs))
Debian GNU/Linux Testing(/dev/sda3(swap) and /dev/sda4(reiserfs -root))
Problem Description:
Blocking computer with following error message:

ata1: command 0x35 timeout, stat 0xd0 host_stat 0x21
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC ASCQ 0xb/47/00
ata1: status=0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Aborted Command
     Additional sense: Scsi parity error
end_request: I/O error, dev sda, sector $some_sector
ATA: abnormal status 0xD0 on port 0xEFF7
ATA: abnormal status 0xD0 on port 0xEFF7
ATA: abnormal status 0xD0 on port 0xEFF7

Steps to reproduce:

Mostly when disk is busy(writing).
Comment 1 Bill Strig 2006-03-21 04:11:19 UTC 
I tried slackware 10.2 with all kernels and it didn't work.
Comment 2 Natalie Protasevich 2007-07-08 17:17:24 UTC 
Have you tested lately with recent kernels from kernel.org?
Thanks.
Comment 3 Tejun Heo 2007-08-08 20:49:45 UTC 
Closing for now.  Please reopen if the problem persists on newer kernels.  It sounds a lot like hardware problem tho.
Note You need to log in before you can comment on or make changes to this bug.