> I have gotten the same thing from one one of my boxes, wiht
> kernal 2.0.35+.
> It turned out to be the IDE controller. Upon boot up I got a
> message about a
> "buggy interface" after IDE synch. It was an older Packard Hell, but this
> controller was used a lot back in the day. Could you have a bad Cable? or
> other 'bad connection' ?
Thanks for the help.
I've tried changing the cables. I've tried single-channel cables, and dual
channel, I've tried attaching the hdd to the either channel as well. What's
funny is that I can't seem to make the error happens, it's almost random.
Sometimes I can do a
$ls -R /
and I still don't get any errors. But 5 minutes later the error might rear
it's ugly head. I'm downloading the 2.2.13 kernel now, so I'll see if that
helps. I'm checking the linux-kernel archives for relevant information. It
doesn't seem to cause any problems, however (all my daemons are running
great, and services aren't lagging a bit--it's pretty snappy).
Bootup logs only record a normal IDE initialization, no "buggy interface"
warnings. But speaking of which, here is some relevent bootup info.
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1060-0x1067, BIOS settings hda:DMA, hdb:pio
ide1: BM-DMA at 0x1068-0x106f, BIOS settings hdc:DMA, hdd:pio
hda: ST36421A, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-6502B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: ST36421A, 6150MB w/256kB Cache, CHS=784/255/63
hdc: ATAPI 40X CD-ROM drive, 256kB Cache
Uniform CDROM driver Revision: 2.56
Might it be related to the PIIX4 chipset? I've searched the system for
core-dumps and nothing has crashed so far on my system. I'm really stumped
on this one.
> Dan Browning wrote:
>
> The following error shows up on the console every once and a while (not
>
> > necesarily linked with any system action that I can discern--but happens
> > when I run linuxconf), it also logs to var/log/messages
> >
> > hda: status timeout: status=0xd0 { Busy }
> > hda: no DRQ after issuing WRITE
> > ide0: reset: success
> > This is on Redhat 6.1, 2.2.12, intel etherexpress pro/100+ management
> > adapter, p2-400, 128mb ram, w/ 1 6gb seagate ide hdd (udma33)
> on an intel
> > se-440bx mb.
> >
> > linux-net mailing list had a simliar question to which there
> was just one
> > reply: "you have a bad hard drive." I find that hard to
> believe because:
> > On the same machine, 2.0.x kernels don't display such behavior, and I've
> > gotten this message with about a half-dozen redhat boxes (6.x).
> >
> > This subject may have been broached before, but http://vger.rutgers.edu
> > doesn't have an archive for it's mail, so where is the list archive?
> >
> > Also, what is a way to cat all files recursively? I've
> forgotten, look at
> > the sillies things I'm trying:
> >
> > $ cat `ls -R` (doesn't work because ls puts a ":" on the end
> of the file
> > name)
> > $ cat -R (bad switch)
> > $ ls -R | cat (just shows file names, not contents)
> >
> > Thanks for the help guys,
> >
> > Dan Browning
> > Network Administrator
> > Cyclone Computer Systems
>
>
>
> --
> ~P~
>
> "What we do is never really understood,
> but always merely praised and blamed."
>
> Neitzche
>
>
>
