I have 3 OQOs with Centos and I frequently get the following error messages:
Jan 28 13:18:07 oqo3 kernel: hdc: status timeout: status=0xd0 { Busy }
Jan 28 13:18:07 oqo3 kernel: ide: failed opcode was: unknown
Jan 28 13:18:07 oqo3 kernel: hdc: no DRQ after issuing MULTWRITE
Jan 28 13:18:07 oqo3 kernel: ide1: reset: success
I have Fedora 10 on a fourth unit and it NEVER gets this message. I
should point out that originally I had Centos on this unit as well and
it got these errors, so this seems to be something that Centos is having
problems with that has been 'fixed' by FC10.
Any idea what can be done? They seem to be more nuance that not, but if
I am in init 3 mode and in VI and get one of these messages in the
middle of editing some file, well, I typically :q! out and start over.....
Robert Moskowitz wrote:> Any idea what can be done? They seem to be more nuance that not, but if > I am in init 3 mode and in VI and get one of these messages in the > middle of editing some file, well, I typically :q! out and start over..... >you can use ctl-L to refresh a vim edit screen... (if you're in insert mode, hit <ESC> first)... beats quitting and starting over. do these errors always occur on /dev/hdc or random devices? if always /dev/hdc, is that a CD/DVD or a HD ? that OQO thing is some kinda VIA C7 or whatever? you might try disabling DMA on the /dev/hdc, like... /sbin/hdparm -d0 /dev/hdc [this would have to be put in a init file, maybe /etc/rc.d/rc.local ]
> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Robert Moskowitz > Sent: Thursday, 29 January 2009 5:30 AM > To: CentOS mailing list > Subject: [CentOS] hdc: no DRQ after issuing MULTWRITE > > Any idea what can be done? They seem to be more nuance that not, but > if > I am in init 3 mode and in VI and get one of these messages in the > middle of editing some file, well, I typically :q! out and start > over..... >man dmesg suggests that running the command `dmesg -n1' should stop you getting messages on the console other than panic messages! But all in all, you probably want to fix the issue to avoid filling up your logs with crap messages; for that, I have no solution! Cheers, AK.
John R Pierce wrote:> Robert Moskowitz wrote: > >> Any idea what can be done? They seem to be more nuance that not, but if >> I am in init 3 mode and in VI and get one of these messages in the >> middle of editing some file, well, I typically :q! out and start over..... >> >> > > you can use ctl-L to refresh a vim edit screen... (if you're in insert > mode, hit <ESC> first)... beats quitting and starting over. >Now I just have to remember that when I am using vi. I actually use vi a lot, but just for simple editing...> > do these errors always occur on /dev/hdc or random devices? if always > /dev/hdc, is that a CD/DVD or a HD ? that OQO thing is some kinda > VIA C7 or whatever? you might try disabling DMA on the /dev/hdc, like... >hdc is the ONLY media regularly in the unit. Only used CD for the install, and only occationally a usb drive. And yes it is a VIA-based system. And disabling DMA results in what? No dma errors, slower seek/write times, bad things on kernel panics?> > /sbin/hdparm -d0 /dev/hdc > > [this would have to be put in a init file, maybe /etc/rc.d/rc.local ]