Bug#495014: 2.6.26.3 behavior different?
I still have ide1 reset and most hdparm set to 0. However, I did not notice
that happening with hald this time around so maybe that was a false alarm.
There is a different opcode error now and a new message. Here is the log
section:
Aug 24 17:33:39 d_baron kernel: Driver 'sr' needs updating - please use
bus_type methods
Aug 24 17:33:39 d_baron kernel: lp0: using parport0 (interrupt-driven).
Aug 24 17:33:39 d_baron kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos
as rtc0
Aug 24 17:33:39 d_baron kernel: rtc0: alarms up to one day
Aug 24 17:33:39 d_baron kernel: device-mapper: ioctl: 4.13.0-ioctl
(2007-10-18) initialised: dm-devel@redhat.com
Aug 24 17:33:39 d_baron kernel: ttyS1: LSR safety check engaged!
Aug 24 17:33:39 d_baron kernel: ttyS1: LSR safety check engaged!
Aug 24 17:33:39 d_baron kernel: hdc: dma_intr: status=0x58 { DriveReady
SeekComplete DataRequest }
Aug 24 17:33:39 d_baron kernel: ide: failed opcode was: unknown
Aug 24 17:33:39 d_baron kernel: hdc: DMA disabled
Aug 24 17:33:39 d_baron kernel: hdd: DMA disabled
Aug 24 17:33:39 d_baron kernel: ide1: reset: success
That first message: What is it? Relevant?
Device mapper problem>
Now 0x058 instead of 0x0D
Reply to: