Hello,
I installed centos 5.x 32bit.
In log messages I found this output.
Can anyone suggest me whats wrong here?
Hardware is brand new.


ar 9 06:48:17 localhost kernel: ide: failed opcode was: unknown
Mar 9 06:48:17 localhost kernel: hdc: no DRQ after issuing MULTWRITE_EXT
Mar 9 06:48:17 localhost kernel: ide1: reset: success
Mar 9 06:48:17 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Mar 9 06:48:17 localhost kernel: ide: failed opcode was: unknown
Mar 9 06:48:17 localhost kernel: hda: no DRQ after issuing MULTWRITE_EXT
Mar 9 06:48:17 localhost kernel: ide0: reset: success
Mar 9 07:28:18 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Mar 9 07:28:18 localhost kernel: ide: failed opcode was: unknown
Mar 9 07:28:18 localhost kernel: hda: no DRQ after issuing MULTWRITE_EXT
Mar 9 07:28:19 localhost kernel: ide0: reset: success
Mar 9 07:48:17 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 9 07:48:17 localhost kernel: ide: failed opcode was: unknown
Mar 9 07:48:17 localhost kernel: hdc: no DRQ after issuing MULTWRITE_EXT
Mar 9 07:48:17 localhost kernel: ide1: reset: success
Mar 9 07:48:18 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Mar 9 07:48:18 localhost kernel: ide: failed opcode was: unknown
Mar 9 07:48:18 localhost kernel: hda: no DRQ after issuing MULTWRITE_EXT
Mar 9 07:48:18 localhost kernel: ide0: reset: success
Mar 9 07:58:18 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Mar 9 07:58:18 localhost kernel: ide: failed opcode was: unknown
Mar 9 07:58:18 localhost kernel: hda: no DRQ after issuing MULTWRITE_EXT
Mar 9 07:58:18 localhost kernel: ide0: reset: success
Mar 9 08:18:18 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Mar 9 08:18:18 localhost kernel: ide: failed opcode was: unknown
Mar 9 08:18:18 localhost kernel: hdc: no DRQ after issuing MULTWRITE_EXT
Mar 9 08:18:18 localhost kernel: ide1: reset: success
Mar 9 08:38:17 localhost kernel: hda: status timeout: status=0xd0 { Busy }
Mar 9 08:38:17 localhost kernel: ide: failed opcode was: unknown
Mar 9 08:38:17 localhost kernel: hda: no DRQ after issuing MULTWRITE_EXT
Mar 9 08:38:18 localhost kernel: ide0: reset: success


Regards,
DM

Something is set wrong, or something is not compatible with something.

Hint: We cannot read your mind or see at a distance.

Question: What is you hardware set up?

HTH.
Alan.

Has anything become of this? I have the same error message in my log file. Any ideas?

Apr 1 05:25:20 dns-1 kernel: hda: status timeout: status=0xd0 { Busy }
Apr 1 05:25:20 dns-1 kernel: ide: failed opcode was: unknown
Apr 1 05:25:20 dns-1 kernel: hda: no DRQ after issuing MULTWRITE_EXT
Apr 1 05:25:20 dns-1 kernel: ide0: reset: success

Result of hdparm:

/dev/hda:
multcount = 0 (off)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 156301488, start = 0

From dmesg:

Apr 1 05:25:18 dns-1 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Apr 1 05:25:18 dns-1 kernel: hda: ST380815AS, ATA DISK drive
Apr 1 05:25:18 dns-1 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Apr 1 05:25:18 dns-1 kernel: hda: max request size: 512KiB
Apr 1 05:25:18 dns-1 kernel: hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63
Apr 1 05:25:18 dns-1 kernel: hda: cache flushes supported
Apr 1 05:25:18 dns-1 kernel: hda: hda1 hda2 hda3

Kernel version:
Linux version 2.6.18-53.1.14.el5 (mockbuild@builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Mar 5 11:36:49 EST 2008

Thanks in advance!

After finding a little more information on the web I was able to resolve my issue.

Using hdparm I set the multcount for my drive to the max allowable according to the drive specs:

hdparm -m 16 /dev/hda

Since this change the error messages have ceased.

I have the same problem:

/var/log/messages shows :
hda: status timeout: status=0xd0 { Busy }
May 8 11:50:41 server kernel: ide: failed opcode was: unknown
May 8 11:50:41 server kernel: hda: no DRQ after issuing MULTWRITE_EXT
May 8 11:50:41 server kernel: ide0: reset: success

hdd: Model Number: ST3160215AS

OS: CENTOS5 64 bit

changing the mult count didn't solve the problem ?

Anyone have suggestions ?

well i am still getting the errors after
hdparm -m 16 /dev/hda

Thanks

Quote:

Sorry...

Core2quad 6600
4 x 2 gigs ram
2 x500 gb sata2
supermicro mobo
CD ROM

if you need some detailed info about please do let me know.
Thanks

Quote:

I'm posting to this old issue since I need to document the probable cause and resolution (if only for myself, since I've ran into this issue twice now and ended up searching here, finding no resolution, then resolving it on my own - twice).

As the parent poster indicated in his dmesg output, the kernel was seeing his drives as IDE (hda, etc), even though he had SATA drives.

This causes all kinds of weird crap (see errors above) with performance going down the toilette, continuous errors, etc.

To fix this, reboot and go into your BIOS and change how the mobo sees the drives (*not* IDE, but AHCI). Save and reboot. The kernel will now correctly identify the SATA drives and all will be well with the world.

Presumably for compatibility reasons, some mobo BIOS' have been set to default to IDE - even for SATA drives. This has been a problem for several machines I've worked on in the past couple of months.

You may or may not need to reinstall after making this change - I just reformat/reinstall to be sure.

Cheers
Henry

Your absolutely right Henry. Thank you for resolving this issue.

I should also like to apologise to the OP, detamail, for completely missing his post of 2008/9/1 6:12:08. I do not understand how I missed it . . .

Henry: where do I find "how the mobo sees the drives" in BIOS?

I have HP ProLiant ML150 G5, Intel(R) Xeon(R) CPU E5405 @ 2.00GHz, CentOS 5.2 x86_64.

CentOS 5.2. x64
#uname -a
Linux bjnat 2.6.18-92.el5 #1 SMP Tue Jun 10 18:51:06 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
#tail -f /var/log/messages
Dec 29 16:12:20 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:22 bjnat last message repeated 2 times
Dec 29 16:12:22 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:22 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:22 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:24 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:24 bjnat last message repeated 4 times
Dec 29 16:12:24 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:24 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:24 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:26 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:26 bjnat last message repeated 3 times
Dec 29 16:12:26 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:26 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:26 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:28 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:30 bjnat last message repeated 4 times
Dec 29 16:12:30 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:30 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:30 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:30 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:32 bjnat last message repeated 3 times
Dec 29 16:12:32 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:32 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:32 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:34 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:34 bjnat last message repeated 4 times
Dec 29 16:12:34 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:34 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:34 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:36 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:40 bjnat last message repeated 9 times
Dec 29 16:12:40 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:40 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:40 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:40 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:44 bjnat last message repeated 3 times
Dec 29 16:12:44 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:44 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:44 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:44 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:12:58 bjnat last message repeated 10 times
Dec 29 16:12:58 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:12:58 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:12:58 bjnat kernel: hde: drive not ready for command
Dec 29 16:12:58 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:04 bjnat last message repeated 6 times
Dec 29 16:13:04 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:04 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:04 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:06 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:06 bjnat last message repeated 5 times
Dec 29 16:13:06 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:06 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:06 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:06 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:10 bjnat last message repeated 4 times
Dec 29 16:13:10 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:10 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:10 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:12 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:16 bjnat last message repeated 5 times
Dec 29 16:13:16 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:16 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:16 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:16 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:18 bjnat last message repeated 4 times
Dec 29 16:13:18 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:18 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:18 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:18 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:20 bjnat last message repeated 3 times
Dec 29 16:13:20 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:20 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:20 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:20 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:22 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:22 bjnat last message repeated 4 times
Dec 29 16:13:22 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:22 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:22 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:24 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:28 bjnat last message repeated 11 times
Dec 29 16:13:28 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:28 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:28 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:28 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:53 bjnat last message repeated 21 times
Dec 29 16:13:53 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:53 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:53 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:53 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:13:55 bjnat last message repeated 5 times
Dec 29 16:13:55 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:13:55 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:13:55 bjnat kernel: hde: drive not ready for command
Dec 29 16:13:55 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:01 bjnat last message repeated 10 times
Dec 29 16:14:01 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:01 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:01 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:07 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:07 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:07 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:11 bjnat last message repeated 7 times
Dec 29 16:14:11 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:11 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:11 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:13 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:21 bjnat last message repeated 11 times
Dec 29 16:14:25 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:33 bjnat last message repeated 15 times
Dec 29 16:14:33 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:33 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:33 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:33 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:37 bjnat last message repeated 5 times
Dec 29 16:14:37 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:37 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:37 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:37 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:45 bjnat last message repeated 5 times
Dec 29 16:14:45 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:14:45 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:14:45 bjnat kernel: hde: drive not ready for command
Dec 29 16:14:45 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:14:53 bjnat last message repeated 9 times
Dec 29 16:14:55 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:01 bjnat last message repeated 11 times
Dec 29 16:15:01 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:01 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:01 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:03 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:05 bjnat last message repeated 3 times
Dec 29 16:15:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:15 bjnat last message repeated 4 times
Dec 29 16:15:15 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:15 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:15 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:15 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:17 bjnat last message repeated 3 times
Dec 29 16:15:17 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:17 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:17 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:17 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:21 bjnat last message repeated 9 times
Dec 29 16:15:21 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:21 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:21 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:23 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:23 bjnat last message repeated 4 times
Dec 29 16:15:23 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:23 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:23 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:23 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:31 bjnat last message repeated 10 times
Dec 29 16:15:31 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:31 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:31 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:33 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:35 bjnat last message repeated 5 times
Dec 29 16:15:35 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:35 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:35 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:37 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:43 bjnat last message repeated 9 times
Dec 29 16:15:43 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:43 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:43 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:45 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:15:59 bjnat last message repeated 13 times
Dec 29 16:15:59 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:15:59 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:15:59 bjnat kernel: hde: drive not ready for command
Dec 29 16:15:59 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:01 bjnat last message repeated 3 times
Dec 29 16:16:03 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:05 bjnat last message repeated 3 times
Dec 29 16:16:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:07 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:07 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:07 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:09 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:11 bjnat last message repeated 4 times
Dec 29 16:16:11 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:11 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:11 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:11 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:15 bjnat last message repeated 6 times
Dec 29 16:16:15 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:15 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:15 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:17 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:17 bjnat last message repeated 2 times
Dec 29 16:16:17 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:17 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:17 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:19 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:31 bjnat last message repeated 12 times
Dec 29 16:16:32 bjnat kernel: ip_conntrack: table full, dropping packet.
Dec 29 16:16:32 bjnat last message repeated 9 times
Dec 29 16:16:33 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:37 bjnat last message repeated 8 times
Dec 29 16:16:37 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:37 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:37 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:39 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:49 bjnat last message repeated 12 times
Dec 29 16:16:49 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:49 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:49 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:49 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:55 bjnat last message repeated 11 times
Dec 29 16:16:55 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:55 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:55 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:55 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:16:57 bjnat last message repeated 3 times
Dec 29 16:16:57 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:16:57 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:16:57 bjnat kernel: hde: drive not ready for command
Dec 29 16:16:57 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:01 bjnat last message repeated 6 times
Dec 29 16:17:01 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:01 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:01 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:03 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:03 bjnat last message repeated 4 times
Dec 29 16:17:03 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:03 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:03 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:05 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:07 bjnat last message repeated 5 times
Dec 29 16:17:07 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:07 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:07 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:07 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:11 bjnat last message repeated 5 times
Dec 29 16:17:11 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:11 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:11 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:13 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:13 bjnat last message repeated 2 times
Dec 29 16:17:13 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:13 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:13 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:15 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:15 bjnat last message repeated 2 times
Dec 29 16:17:15 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:15 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:15 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:15 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:23 bjnat last message repeated 8 times
Dec 29 16:17:23 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:23 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:23 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:23 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:25 bjnat last message repeated 3 times
Dec 29 16:17:25 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:25 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:25 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:25 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:31 bjnat last message repeated 11 times
Dec 29 16:17:31 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:31 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:31 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:33 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:37 bjnat last message repeated 5 times
Dec 29 16:17:37 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:37 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:37 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:37 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:39 bjnat last message repeated 4 times
Dec 29 16:17:39 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:39 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:39 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:41 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:41 bjnat last message repeated 5 times
Dec 29 16:17:41 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:41 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:41 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:43 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:43 bjnat last message repeated 2 times
Dec 29 16:17:43 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:43 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:43 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:43 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:53 bjnat last message repeated 14 times
Dec 29 16:17:53 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:53 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:53 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:53 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:55 bjnat last message repeated 2 times
Dec 29 16:17:55 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:55 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:55 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:57 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:17:57 bjnat last message repeated 2 times
Dec 29 16:17:57 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:17:57 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:17:57 bjnat kernel: hde: drive not ready for command
Dec 29 16:17:57 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:17 bjnat last message repeated 9 times
Dec 29 16:18:17 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:17 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:17 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:21 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:23 bjnat last message repeated 3 times
Dec 29 16:18:23 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:23 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:23 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:27 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:27 bjnat last message repeated 3 times
Dec 29 16:18:27 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:27 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:27 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:29 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:29 bjnat last message repeated 3 times
Dec 29 16:18:29 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:29 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:29 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:31 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:35 bjnat last message repeated 8 times
Dec 29 16:18:35 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:35 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:35 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:35 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:37 bjnat last message repeated 2 times
Dec 29 16:18:37 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:37 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:37 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:39 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:49 bjnat last message repeated 8 times
Dec 29 16:18:49 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:49 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:49 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:51 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:53 bjnat last message repeated 3 times
Dec 29 16:18:53 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:53 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:53 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:53 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:57 bjnat last message repeated 6 times
Dec 29 16:18:57 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:57 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:57 bjnat kernel: hde: drive not ready for command
Dec 29 16:18:59 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:59 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:18:59 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:18:59 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:18:59 bjnat kernel: hde: drive not ready for command
Dec 29 16:19:01 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:19:01 bjnat last message repeated 2 times
Dec 29 16:19:01 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:19:01 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:19:01 bjnat kernel: hde: drive not ready for command
Dec 29 16:19:01 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:19:22 bjnat kernel: printk: 49 messages suppressed.
Dec 29 16:19:22 bjnat kernel: ip_conntrack: table full, dropping packet.
Dec 29 16:20:27 bjnat kernel: SKB BUG: Invalid truesize (496) len=264, sizeof(sk_buff)=240
Dec 29 16:20:27 bjnat kernel: SKB BUG: Invalid truesize (496) len=264, sizeof(sk_buff)=240
Dec 29 16:20:27 bjnat kernel: SKB BUG: Invalid truesize (1264) len=1038, sizeof(sk_buff)=240
Dec 29 16:20:27 bjnat kernel: SKB BUG: Invalid truesize (1264) len=1038, sizeof(sk_buff)=240
Dec 29 16:20:28 bjnat kernel: SKB BUG: Invalid truesize (496) len=264, sizeof(sk_buff)=240
Dec 29 16:20:28 bjnat kernel: SKB BUG: Invalid truesize (496) len=264, sizeof(sk_buff)=240
Dec 29 16:20:29 bjnat kernel: SKB BUG: Invalid truesize (752) len=526, sizeof(sk_buff)=240
Dec 29 16:20:29 bjnat kernel: SKB BUG: Invalid truesize (752) len=526, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=648, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=648, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (1008) len=773, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (1008) len=773, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=646, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=646, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (1008) len=774, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (1008) len=774, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=650, sizeof(sk_buff)=240
Dec 29 16:20:30 bjnat kernel: SKB BUG: Invalid truesize (880) len=650, sizeof(sk_buff)=240
Dec 29 16:20:31 bjnat kernel: SKB BUG: Invalid truesize (1008) len=772, sizeof(sk_buff)=240
Dec 29 16:20:31 bjnat kernel: SKB BUG: Invalid truesize (1008) len=772, sizeof(sk_buff)=240
Dec 29 16:20:31 bjnat kernel: SKB BUG: Invalid truesize (880) len=645, sizeof(sk_buff)=240
Dec 29 16:20:31 bjnat last message repeated 3 times
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=769, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=769, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=772, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=772, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=778, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1008) len=778, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1136) len=902, sizeof(sk_buff)=240
Dec 29 16:20:32 bjnat kernel: SKB BUG: Invalid truesize (1136) len=902, sizeof(sk_buff)=240
Dec 29 16:20:33 bjnat kernel: SKB BUG: Invalid truesize (880) len=654, sizeof(sk_buff)=240
Dec 29 16:20:33 bjnat kernel: SKB BUG: Invalid truesize (880) len=654, sizeof(sk_buff)=240
Dec 29 16:20:33 bjnat kernel: SKB BUG: Invalid truesize (880) len=651, sizeof(sk_buff)=240
Dec 29 16:20:33 bjnat kernel: SKB BUG: Invalid truesize (880) len=651, sizeof(sk_buff)=240
Dec 29 16:20:34 bjnat kernel: SKB BUG: Invalid truesize (1136) len=906, sizeof(sk_buff)=240
Dec 29 16:20:34 bjnat kernel: SKB BUG: Invalid truesize (1136) len=906, sizeof(sk_buff)=240
Dec 29 16:20:34 bjnat kernel: SKB BUG: Invalid truesize (1008) len=779, sizeof(sk_buff)=240
Dec 29 16:20:34 bjnat kernel: SKB BUG: Invalid truesize (1008) len=779, sizeof(sk_buff)=240
Dec 29 16:20:53 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:21:50 bjnat yum-updatesd-helper: error getting update info: failure: repodata/primary.xml.gz from rpmforge: [Errno 256] No more mirrors to try.
Dec 29 16:21:54 bjnat kernel: Xvnc[8215]: segfault at 0000000000000008 rip 000000000044eeb4 rsp 00007fffcb5e4d30 error 4
Dec 29 16:21:54 bjnat scim-bridge: Panel client has not yet been prepared
Dec 29 16:21:54 bjnat last message repeated 67 times
Dec 29 16:21:54 bjnat scim-bridge: The lockfile is destroied
Dec 29 16:21:54 bjnat scim-bridge: Cleanup, done. Exitting...
Dec 29 16:22:52 bjnat gconfd (root-8250): GConf 服务器不在使用，正在关闭。
Dec 29 16:22:52 bjnat gconfd (root-8250): 退出
Dec 29 16:23:15 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:24:15 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:25:19 bjnat kernel: hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
Dec 29 16:25:19 bjnat kernel: hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec 29 16:25:19 bjnat kernel: ide: failed opcode was: unknown
Dec 29 16:25:19 bjnat kernel: hde: drive not ready for command

CentOS 5.2 (as implied by the kernel that you currently have running) is severely out of date and usage of that point release is deprecated.

Please read the CentOS 5.4 Release Notes, paying particular attention to the details at the end of Section #4, and update your system to the current point release, which is (at the date of this posting) 5.4, with kernel-2.6.18-164.9.1.el5.

Once that has been done, please check again.