Re: PATA DMA problem leading to kernel panic on reading movie DVDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Sun, May 17, 2009 at 21:35:09 +0200, Bartlomiej Zolnierkiewicz wrote:
> > > The error message with 2.6.23.14 was:
> > > 
> > >   hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > >   hdc: drive_cmd: error=0x04 { AbortedCommand }
> > >   ide: failed opcode was: 0xec
> 
> This is more-or-less innocent -- some user-space utility wrongly uses
> ATA IDENTIFY command on ATAPI devices and it gets logged as an error...

thanks; that's a load off my mind :-).

> > > This is correct: the drive is only capable of Ultra DMA mode 2 33.3 MB/s
> > > (see manufacturer's documentation) and is attached with a standard 40-wire
> > > ATA cable (black connectors for master and slave).
> 
> Martin, this is one of ATAPI drives which support UDMA66 but have broken
> cable detection.

Are you sure? Compare this:

  http://downloadcenter.samsung.com/content/UM/200709/20070928095126750_SH-S202N_Eng.pdf

> Please:
> 
> * send 'hdparm --Istdout /dev/hdc' output

Here it is:

  /dev/hdc:
  85c0 0000 0000 0000 0000 0000 0000 0000
  0000 0000 2020 2020 2020 2020 2020 2020
  2020 2020 2020 2020 0000 0000 0000 5342
  3031 2020 2020 5453 5354 636f 7270 2043
  4444 5644 5720 5348 2d53 3230 324e 2020
  2020 2020 2020 2020 2020 2020 2020 0000
  0000 0b00 0000 0200 0200 0006 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0007
  0003 0078 0078 017f 0078 0000 0000 0000
  0000 00f8 0210 0000 0000 0000 0000 0000
  00f8 0210 0210 0000 0000 0000 0000 0000
  041f 0000 8005 3200 005b 2000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 a3a5

> * try 2.6.30-rc6 (maybe 2.6.29.3 oops has been fixed already and we just
>   need to backport it)

That'll have to wait until tomorrow -- I have a low-bandwidth connection
here.

> also connecting the drive using 80-wires cable and getting another hdparm
> output (+ seeing if it helps the other problems) would be very useful.

I'll try that too, but that also will have to wait until tommorrow.

Thanks for the help,
Martin Lottermoser
-- 
Martin Lottermoser             Martin.Lottermoser at _REMOVE_t-online.de
Greifswaldstrasse 28
38124 Braunschweig             http://home.vrweb.de/martin.lottermoser
Germany
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux