Eject button on CD-RW locks up system

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

 



I have a system (Dell Optiplex GX270) which has both an IDE CD/DVD drive
and a CD-RW drive.  Whenever those drives have been idle for a long time,
even with no media in them, pressing the eject button on the CD-RW drive
will often lock up the system hard (mouse won't move, ctrl-alt keys don't
work, etc).  The drive door actually never opens, and the lockup can be
delayed up to about 1 minute from the time the eject button is pressed.  The
same lockup occurs if the eject command is used instead of the button too.

Except during this condition, the drives work normally, reading and writing.
The lockups often occur while both drives are empty.  This is a factory
system, all original Dell-branded components.

I have had this problem ever since FC3, but even now with FC5 it's
still happening.

The drives are:
   /dev/hdc - HL-DT-STDVD-ROM GDR8162B
   /dev/hcd - SAMSUNG CD-R/RW SW-252S

The driver is "ide-cdrom version 4.61", kernel 2.6.15-1.2054_FC5smp

During the 30-seconds to 1-minute while the system is still operational,
this shows up in the syslog messages:
  hdd: irq timeout: status=0xd0 { Busy }
  ide: failed opcode was: unknown
  hdd: DMA disabled
  hdd: ATAPI reset timed-out, status=0x80
  hdc: DMA disabled

The "unknown" opcode makes no sense to me.

The /dev/hdd settings from /proc show as:
name                    value           min             max             mode
----                    -----           ---             ---             ----
current_speed           66              0               70              rw
dsc_overlap             1               0               1               rw
init_speed              66              0               70              rw
io_32bit                0               0               3               rw
keepsettings            0               0               1               rw
nice1                   1               0               1               rw
number                  3               0               3               rw
pio_mode                write-only      0               255             w
unmaskirq               0               0               1               rw
using_dma               1               0               1               rw

And hdparm -v /dev/hdd shows:
/dev/hdd:
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 HDIO_GETGEO failed: Inappropriate ioctl for device

Any ideas on this?  I've tried searching for help but can't find anything
useful. There is no kernel panic, just a complete hard system lockup.
It's pretty bad when anybody can crash your system by just pressing
the eject button.
--
Deron Meranda


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux