IDE CD problems in 2.6.13rc6

IDE CD problems in 2.6.13rc6

[Dave Jones]

I've noticed this week whilst trying to encode a bunch
of audio CDs to oggs that my boxes running the latest
kernels are having serious issues, whereas 2.6.12 seems
to cope just fine.

The symptoms vary. On some of my machines just inserting
an audio CD makes the box instantly lock up.
If I boot with the same CD in the drive, sound-juicer
can read it just fine. When I get to the next CD, I have
to reboot again, or it locks up.

On another box, it gets stuck in a loop where it
just prints out..

hdc: irq timeout: status=0xd0 { Busy }    (This line sometimes has status=0xc0)
ide: failed opcode was: unknown

The net result is that I've not got a single box that
will read audio CDs without doing something bad, and I've
tried it on several quite diverse systems.


I'll try and narrow down over the next few days when this
started happening, but IDE / CD folks may have some better
ideas about which changes were suspicious.

		Dave

Re: IDE CD problems in 2.6.13rc6

[Con Kolivas]

On Sun, 14 Aug 2005 09:29, Dave Jones wrote:
> I've noticed this week whilst trying to encode a bunch
> of audio CDs to oggs that my boxes running the latest
> kernels are having serious issues, whereas 2.6.12 seems
> to cope just fine.
>
> The symptoms vary. On some of my machines just inserting
> an audio CD makes the box instantly lock up.
> If I boot with the same CD in the drive, sound-juicer
> can read it just fine. When I get to the next CD, I have
> to reboot again, or it locks up.
>
> On another box, it gets stuck in a loop where it
> just prints out..
>
> hdc: irq timeout: status=0xd0 { Busy }    (This line sometimes has
> status=0xc0) ide: failed opcode was: unknown
>
> The net result is that I've not got a single box that
> will read audio CDs without doing something bad, and I've
> tried it on several quite diverse systems.
>
>
> I'll try and narrow down over the next few days when this
> started happening, but IDE / CD folks may have some better
> ideas about which changes were suspicious.

Ok I just started noticing unusual things on my IDE DVD-RW as well, presumably 
related, on 2.6.13-rc6. Putting in a cd and trying to read it will cause huge 
delays and then error out with:

ide-cd: cmd 0x28 timed out
hdc: DMA timeout retry
hdc: timeout waiting for DMA
hdc: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hdc: drive not ready for command
hdc: ATAPI reset complete

then it will read fine. If I start another read it goes through the same 
cycle. Forcing dma *off* with hdparm fixes the problem and all subsequent 
accesses don't have this pause, however this was never an issue on previous 
kernels with dma working fine.


relevant lspci:
00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 
UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 
UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI 
Controller (rev 02)


hdparm info of hdc:
/dev/hdc:

ATAPI CD-ROM, with removable media
        Model Number:       LITE-ON DVDRW SOHW-1653S
        Serial Number:
        Firmware Revision:  CS02
Standards:
        Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
        Supported: CD-ROM ATAPI-2
Configuration:
        DRQ response: 50us.
        Packet size: 12 bytes
Capabilities:
        LBA, IORDY(cannot be disabled)
        DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=227ns  IORDY flow control=120ns

relevant config=y info:
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_IVB=y
CONFIG_IDEDMA_AUTO=y


Cheers,
Con

Re: IDE CD problems in 2.6.13rc6

[Con Kolivas]

On Sun, 14 Aug 2005 10:26, Con Kolivas wrote:
> On Sun, 14 Aug 2005 09:29, Dave Jones wrote:
> > I've noticed this week whilst trying to encode a bunch
> > of audio CDs to oggs that my boxes running the latest
> > kernels are having serious issues, whereas 2.6.12 seems
> > to cope just fine.
> >
> > The symptoms vary. On some of my machines just inserting
> > an audio CD makes the box instantly lock up.
> > If I boot with the same CD in the drive, sound-juicer
> > can read it just fine. When I get to the next CD, I have
> > to reboot again, or it locks up.
> >
> > On another box, it gets stuck in a loop where it
> > just prints out..
> >
> > hdc: irq timeout: status=0xd0 { Busy }    (This line sometimes has
> > status=0xc0) ide: failed opcode was: unknown
> >
> > The net result is that I've not got a single box that
> > will read audio CDs without doing something bad, and I've
> > tried it on several quite diverse systems.
> >
> >
> > I'll try and narrow down over the next few days when this
> > started happening, but IDE / CD folks may have some better
> > ideas about which changes were suspicious.
>
> Ok I just started noticing unusual things on my IDE DVD-RW as well,
> presumably related, on 2.6.13-rc6. Putting in a cd and trying to read it
> will cause huge delays and then error out with:
>
> ide-cd: cmd 0x28 timed out
> hdc: DMA timeout retry
> hdc: timeout waiting for DMA
> hdc: status timeout: status=0xd0 { Busy }
> ide: failed opcode was: unknown
> hdc: drive not ready for command
> hdc: ATAPI reset complete
>
> then it will read fine. If I start another read it goes through the same
> cycle. Forcing dma *off* with hdparm fixes the problem and all subsequent
> accesses don't have this pause, however this was never an issue on previous
> kernels with dma working fine.

> hdparm info of hdc:

>         DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4

I should also point out the above *udma2 is interesting because:
hdparm /dev/hdc

/dev/hdc:
 HDIO_GET_MULTCOUNT failed: Invalid argument
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)

This *thinks* that dma is off yet querying hdc says it's in udma2 mode and the 
actual performance very much suggests to me that dma is enabled as it doesn't 
have those awful lags that dma off dvd access usually has.

Even though it apparently works fine I do get these instead though:
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec

blah...


Con

Re: IDE CD problems in 2.6.13rc6

[Alan Cox]

On Sul, 2005-08-14 at 10:30 +1000, Con Kolivas wrote:
> > presumably related, on 2.6.13-rc6. Putting in a cd and trying to read it
> > will cause huge delays and then error out with:
> >
> > ide-cd: cmd 0x28 timed out

(Thats READ_10)

> > hdc: DMA timeout retry
> > hdc: timeout waiting for DMA
> > hdc: status timeout: status=0xd0 { Busy }
> > ide: failed opcode was: unknown
> > hdc: drive not ready for command
> > hdc: ATAPI reset complete

So we asked the drive to do a read and it stayed busy - possibly from
some previous command. In a lot of cases you see the command *after* the
one that broke it. The reset then recovered the drive.


> Even though it apparently works fine I do get these instead though:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> ide: failed opcode was: 0xec

Thats somewhere between bizarre and fascinating.

Re: IDE CD problems in 2.6.13rc6

[Bartlomiej Zolnierkiewicz]

Hi Dave,

On 8/14/05, Dave Jones <davej@redhat.com> wrote:
> I've noticed this week whilst trying to encode a bunch
> of audio CDs to oggs that my boxes running the latest
> kernels are having serious issues, whereas 2.6.12 seems
> to cope just fine.
> 
> The symptoms vary. On some of my machines just inserting
> an audio CD makes the box instantly lock up.
> If I boot with the same CD in the drive, sound-juicer
> can read it just fine. When I get to the next CD, I have
> to reboot again, or it locks up.
> 
> On another box, it gets stuck in a loop where it
> just prints out..
> 
> hdc: irq timeout: status=0xd0 { Busy }    (This line sometimes has status=0xc0)
> ide: failed opcode was: unknown
> 
> The net result is that I've not got a single box that
> will read audio CDs without doing something bad, and I've
> tried it on several quite diverse systems.
> 
> 
> I'll try and narrow down over the next few days when this
> started happening, but IDE / CD folks may have some better
> ideas about which changes were suspicious.

I checked 2.6.13-rc6 patch and I see no IDE / CD changes which
could be responsible for this regression.  You can try reverting ide-cd
changes and see if this helps.  IRQ routing changes?

Bartlomiej

Re: IDE CD problems in 2.6.13rc6

[Alan Cox]

On Sul, 2005-08-14 at 13:35 +0200, Bartlomiej Zolnierkiewicz wrote:
> > The symptoms vary. On some of my machines just inserting
> > an audio CD makes the box instantly lock up.

You've got all the gnome cruft running. Start by turning that off. Then
try inserting/removing audio discs, playing them with "cdplay". I'd
expect that to be ok

Next try ripping an audio cd without all the gnome crud loaded. If that
works (it may or may not) then its practical to try and pin down the bug
and see if its error handling (the locking patterns all changed in the
base kernel recently hence all those new PIIX error reports) or
something else.

> I checked 2.6.13-rc6 patch and I see no IDE / CD changes which
> could be responsible for this regression.  You can try reverting ide-cd
> changes and see if this helps.  IRQ routing changes?

Then you'd expect to see "drive confused" methods. It could be IRQ
related - missing IRQ might do it although I'd expect that to cause
crashes during probe if we got extra IRQs (because the code to handle it
was removed from the base kernel even though it is required).

Another thing that will do this is if you bomb the drive with commands
from somewhere (say GNOME) or crash the firmware, which is why you need
to isolate all the gnome gunge for testing, and if that makes the
difference see if its a kernel or higher level change and if so what its
doing that causes problems.

Alan

Re: IDE CD problems in 2.6.13rc6

[Voluspa]

Doing a "hdparm -I /dev/hdc" (without a disk/with a ISO disk/[u]mounted/music CD):

Aug 14 19:14:33 sleipner kernel: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 14 19:14:33 sleipner kernel: hdc: drive_cmd: error=0x04 { AbortedCommand }
Aug 14 19:14:33 sleipner kernel: ide: failed opcode was: 0xec

"hdparm -i /dev/hdc" does not interfere (hdparm v6.1) and normal access like copying,
burning, playing etc works without that message emerging. Though I have seen it once...
During a session of quick mount/umount/play video file of several disks, there it was.
I attributed it to bad media.

This is a VIA motherboard (AMD64 equipped) and I run without any desktop:

root:sleipner:~# cat /proc/pci 
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: PCI device 1106:0204 (VIA Technologies, Inc.) (rev 0).
      Master Capable.  Latency=8.  
      Prefetchable 32 bit memory at 0xd0000000 [0xdfffffff].
  Bus  0, device   0, function  1:
    Host bridge: PCI device 1106:1204 (VIA Technologies, Inc.) (rev 0).
  Bus  0, device   0, function  2:
    Host bridge: PCI device 1106:2204 (VIA Technologies, Inc.) (rev 0).
  Bus  0, device   0, function  3:
    Host bridge: VIA Technologies, Inc. K8M800 (rev 0).
  Bus  0, device   0, function  4:
    Host bridge: PCI device 1106:4204 (VIA Technologies, Inc.) (rev 0).
  Bus  0, device   0, function  7:
    Host bridge: VIA Technologies, Inc. K8M800 (rev 0).
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South] (rev 0).
      Master Capable.  No bursts.  Min Gnt=12.
  Bus  0, device  10, function  0:
    Ethernet controller: Linksys, A Division of Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01) (rev 0).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=32.Max Lat=32.
      I/O at 0x1c00 [0x1c1f].
      Non-prefetchable 32 bit memory at 0xc0006000 [0xc000601f].
      Non-prefetchable 32 bit memory at 0xc0005000 [0xc00057ff].
  Bus  0, device  11, function  0:
    CardBus bridge: Texas Instruments PCI7420 CardBus Controller (rev 0).
      IRQ 16.
      Master Capable.  Latency=64.  Min Gnt=192.Max Lat=3.
      Non-prefetchable 32 bit memory at 0x88020000 [0x88020fff].
  Bus  0, device  11, function  1:
    CardBus bridge: Texas Instruments PCI7420 CardBus Controller (#2) (rev 0).
      IRQ 17.
      Master Capable.  Latency=64.  Min Gnt=192.Max Lat=3.
      Non-prefetchable 32 bit memory at 0x88021000 [0x88021fff].
  Bus  0, device  11, function  2:
    FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller (rev 0).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=2.Max Lat=4.
      Non-prefetchable 32 bit memory at 0xc0005800 [0xc0005fff].
      Non-prefetchable 32 bit memory at 0xc0000000 [0xc0003fff].
  Bus  0, device  12, function  0:
    Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 16).
      IRQ 19.
      Master Capable.  Latency=64.  Min Gnt=32.Max Lat=64.
      I/O at 0x1000 [0x10ff].
      Non-prefetchable 32 bit memory at 0xc0006400 [0xc00064ff].
  Bus  0, device  16, function  0:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 128).
      IRQ 18.
      Master Capable.  Latency=64.  
      I/O at 0x1c20 [0x1c3f].
  Bus  0, device  16, function  1:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) (rev 128).
      IRQ 18.
      Master Capable.  Latency=64.  
      I/O at 0x1c40 [0x1c5f].
  Bus  0, device  16, function  2:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3) (rev 128).
      IRQ 18.
      Master Capable.  Latency=64.  
      I/O at 0x1c60 [0x1c7f].
  Bus  0, device  16, function  3:
    USB Controller: VIA Technologies, Inc. USB 2.0 (rev 130).
      IRQ 18.
      Master Capable.  Latency=64.  
      Non-prefetchable 32 bit memory at 0xc0006800 [0xc00068ff].
  Bus  0, device  17, function  0:
    ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge (rev 0).
  Bus  0, device  17, function  1:
    IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 6).
      Master Capable.  Latency=64.  
      I/O at 0x1c80 [0x1c8f].
  Bus  0, device  17, function  5:
    Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 80).
      IRQ 19.
      I/O at 0x1400 [0x14ff].
  Bus  0, device  17, function  6:
    Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 128).
      IRQ 11.
      I/O at 0x1800 [0x18ff].
  Bus  0, device  24, function  0:
    Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration (rev 0).
  Bus  0, device  24, function  1:
    Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map (rev 0).
  Bus  0, device  24, function  2:
    Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller (rev 0).
  Bus  0, device  24, function  3:
    Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control (rev 0).
  Bus  1, device   0, function  0:
    VGA compatible controller: nVidia Corporation NV36 [GeForce FX Go5700] (rev 161).
      IRQ 20.
      Master Capable.  Latency=248.  Min Gnt=5.Max Lat=1.
      Non-prefetchable 32 bit memory at 0xc1000000 [0xc1ffffff].
      Prefetchable 32 bit memory at 0xe0000000 [0xefffffff].

Mvh
Mats Johannesson
--

Re: IDE CD problems in 2.6.13rc6

[Voluspa]

The "hdparm -I /dev/hdc"

hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
de: failed opcode was: 0xec

Is present on all kernels that I have locally (oldest 2.6.11.11)
so it is not related to the threadstarters problems, it seems.

root:sleipner:~# hdparm -I /dev/hdc

/dev/hdc:

ATAPI CD-ROM, with removable media
        Model Number:       TSSTcorpCD/DVDW TS-L532A                
        Serial Number:      254A204626          
        Firmware Revision:  TI50    
Standards:
        Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
        Supported: CD-ROM ATAPI-2 
Configuration:
        DRQ response: 50us.
        Packet size: 12 bytes
Capabilities:
        LBA, IORDY(can be disabled)
        Buffer size: 2048.0kB
        DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    NOP cmd
           *    DEVICE RESET cmd
           *    PACKET command feature set
           *    Power Management feature set
           *    Mandatory FLUSH CACHE command 
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by CSEL

root:sleipner:~# hdparm -i /dev/hdc

/dev/hdc:

 Model=TSSTcorpCD/DVDW TS-L532A, FwRev=TI50, SerialNo=254A204626
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=2048kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 *udma2 
 AdvancedPM=no
 Drive conforms to: Reserved: 

 * signifies the current active mode

root:sleipner:~# hdparm /dev/hdc

/dev/hdc:
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 HDIO_GETGEO failed: Invalid argument

root:sleipner:~# grep VIA /usr/src/testing/my-2.6.13-rc6-.config 
[edited]
CONFIG_BLK_DEV_VIA82CXXX=y

root:sleipner:~# grep IDE /usr/src/testing/my-2.6.13-rc6-.config 
[edited]
# CONFIG_PARIDE is not set
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
# Please see Documentation/ide.txt for help/info on IDE drives
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# IDE chipset support/bugfixes
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y

Mvh
Mats Johannesson
--

Re: IDE CD problems in 2.6.13rc6

[Nick Warne]

Voluspa wrote:

> 
> The "hdparm -I /dev/hdc"
> 
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> de: failed opcode was: 0xec
> 
> Is present on all kernels that I have locally (oldest 2.6.11.11)
> so it is not related to the threadstarters problems, it seems.

Hi all,

Maybe teaching you all to suck eggs here, but I used to get this a lot on my 
CD's - KDE ran some probe and as the CD[s] where empty logs filled up rapidly 
with that error.  I thought the[a] drive was duff, so bought a new CD-RW.

Made no difference :-/  I then investigated further, and read that instead of 
the SCSI emulation, it was superceded by IDE-CD.

kernel 2.6.12.3

Kernel command line: BOOT_IMAGE=Nicks ro root=303 hdc=ide-cd hdd=ide-cd

Fixed the issue for me.  But as I say, teaching to suck eggs, but I thought I 
would mention it.

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

Re: IDE CD problems in 2.6.13rc6

[Nick Warne]

I just remember a path I took when resolving the issue further to my post 
below.

Here is what man hdparm says on -i and -I:

       -i     Display  the  identification info that was obtained from the 
drive at boot time,
              if available.  This is a feature of modern IDE drives, and may 
not be  supported
              by  older  devices.   The  data returned may or may not be 
current, depending on
              activity since booting the system.  However, the current  
multiple  sector  mode
              count is always shown.  For a more detailed interpretation of 
the identification
              info, refer to AT Attachment Interface for Disk Drives (ANSI ASC 
X3T9.2  working
              draft, revision 4a, April 19/93).

       -I     Request identification info directly from the drive, which is 
displayed in a new
              expanded format with considerably more detail  than  with  the  
older  -i  flag.
              There is a special "no seatbelts" variation on this option, 
-Istdin which cannot
              be combined with any other options, and which  accepts  a  drive  
identification
              block  as  standard  input instead of using a /dev/hd* 
parameter.  The format of
              this block must be exactly the same as that found in  
the  /proc/ide/*/hd*/iden­
              tify  "files".   This  variation  is  designed for use with 
"libraries" of drive
              identification information, and can also be used on ATAPI drives 
which may  give
              media errors with the standard mechanism.

Note the last sentence:

' This  variation  is  designed for use with "libraries" of drive 
identification information, and can also be used on ATAPI drives which may  
give  media errors with the standard mechanism.

Nick

Voluspa wrote:
> The "hdparm -I /dev/hdc"
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> de: failed opcode was: 0xec
>
> Is present on all kernels that I have locally (oldest 2.6.11.11)
> so it is not related to the threadstarters problems, it seems.

Hi all,

Maybe teaching you all to suck eggs here, but I used to get this a lot on my
CD's - KDE ran some probe and as the CD[s] where empty logs filled up rapidly
with that error.  I thought the[a] drive was duff, so bought a new CD-RW.

Made no difference :-/  I then investigated further, and read that instead of
the SCSI emulation, it was superceded by IDE-CD.

kernel 2.6.12.3

Kernel command line: BOOT_IMAGE=Nicks ro root=303 hdc=ide-cd hdd=ide-cd

Fixed the issue for me.  But as I say, teaching to suck eggs, but I thought I
would mention it.

Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

-------------------------------------------------------

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

Re: IDE CD problems in 2.6.13rc6

[Voluspa]

On 2005-08-14 20:10:49 Nick Warne wrote:

>Note the last sentence:
>
>' This  variation  is  designed for use with "libraries" of drive 
>identification information, and can also be used on ATAPI drives which may  
>give  media errors with the standard mechanism.

My jaw just clonked on the table. And the media error at hand made you
buy a new CD-RW. There is precedence for this (remember the blaming X and
other programs in the keyboard driver?) so perhaps the kernel people could
amend the error like:

hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec
ide: Did you just run "hdparm -I" or do you use a nosy desktop?

Mvh
Mats Johannesson
--

Re: IDE CD problems in 2.6.13rc6

[Alan Cox]

On Llu, 2005-08-15 at 00:51 +0200, Voluspa wrote:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> ide: failed opcode was: 0xec
> ide: Did you just run "hdparm -I" or do you use a nosy desktop?

We certainly could interpret 0x51, 0x04 specifically. Its not an "error"
in the usual spew at the user case generally speaking but a "do this"
"no" sequence. Its useful to log because sending unknown commands to an
IDE device is something we want to catch (some drives hang if you do it,
others do really *crazy* things).

Would

hdc: command not supported by drive
ide: failed opcode was: 0xec

have been more helpful 

Alan

Re: IDE CD problems in 2.6.13rc6

[Voluspa]

On Mon, 15 Aug 2005 01:37:08 +0100 Alan Cox wrote:
> 
> We certainly could interpret 0x51, 0x04 specifically. Its not an "error"
> in the usual spew at the user case generally speaking but a "do this"
> "no" sequence. Its useful to log because sending unknown commands to an
> IDE device is something we want to catch (some drives hang if you do it,
> others do really *crazy* things).
> 
> Would
> 
> hdc: command not supported by drive
> ide: failed opcode was: 0xec
> 
> have been more helpful 

If it was clearly marked as "This is INFO, not a Warning". Most users
I've met (myself included) are always expecting their hardware to crash and
burn at the drop of a hat. Scary messages just confirm our anguish - 
especially when it's coming by way of the CD/HD system.

Mvh
Mats Johannesson
--

Re: IDE CD problems in 2.6.13rc6

[Nick Warne]

Voluspa wrote:
 
> On 2005-08-14 20:10:49 Nick Warne wrote:
> 
>>Note the last sentence:
>>
>>' This  variation  is  designed for use with "libraries" of drive
>>identification information, and can also be used on ATAPI drives which may
>>give  media errors with the standard mechanism.
> 
> My jaw just clonked on the table. And the media error at hand made you
> buy a new CD-RW. There is precedence for this (remember the blaming X and
> other programs in the keyboard driver?) 

Just for the record, it was a KDE service daemon that caused these errors for 
me, like a 24MB log in 12 hours:

KDED Media Manager

Also trying to remember, I had a CD-RW on /dev/hdc and a CD-R on /dev/hdd.  It 
was /dev/hdd that give those errors, but I only passed the SCSI emulation on 
kernel line for the CD-RW.

So I suppose it uses similar code (of sorts) as HDPARM.  I dunno.

The old drive was 6 years old anyway - so after I sussed the issue I pretend I 
did an upgrade ;-)

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."