[olug] RE: HDC: Lost Interrupt Error
CM Miller
cmmiller1973 at yahoo.com
Fri Apr 18 17:13:03 UTC 2003
I did this, tried it but still keep getting this
dmesg | grep hdc: lost interrupt>hdc_error_output
ide1: BM-DMA at 0x4008-0x400f, BIOS settings:
hdc:DMA, hdd:pio
hdc: SAMSUNG CD-ROM SC-148F, ATAPI CD/DVD-ROM drive
hdc: ATAPI 48X CD-ROM drive, 128kB Cache
hdc: command error: status=0x59 { DriveReady
SeekComplete DataRequest
Error }
hdc: command error: error=0x54
hdc: status error: status=0x59 { DriveReady
SeekComplete DataRequest
Error }
hdc: status error: error=0x54
hdc: drive not ready for command
hdc: status timeout: status=0xd1 { Busy }
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: command error: status=0x59 { DriveReady
SeekComplete DataRequest
Error }
hdc: command error: error=0x54
hdc: status error: status=0x59 { DriveReady
SeekComplete DataRequest
Error }
hdc: status error: error=0x54
hdc: drive not ready for command
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
hdc: lost interrupt
I then commented out what I put in for
/etc/sysconfig/harddisk and so far it was worked ok...
-Chris
--- Adam Haeder <adamh at omaha.org> wrote:
> Put these lines at the end of you /etc/rc.d/rc.local
> file:
>
> hdparm -c 1 /dev/hda
> hdparm -d 1 /dev/hda
>
> The first one turns on 32bit io, the second turns on
> dma.
>
> Verify with:
> hdparm /dev/hda
>
> Repeat for each hard drive.
>
> --
> Adam Haeder
> Assistant Vice President of Information Technology
> AIM Institute
> adamh at omaha.org
> (402) 345-5025 x115
> PGP Public key: http://www.omaha.org/~adamh/pgp.html
>
> On Thu, 17 Apr 2003, CM Miller wrote:
>
> >
> >
> > I don't remember seeing Adam post that...?
> >
> > So where would I add hdparm -d 1 /dev/hda? Under
> > /etc/sysconfig/harddisk where USE_DMA = 1 is?
> >
> > Since I've changed that, it has had a few delays,
> but
> >
> > nothing like it was doing.
> >
> > Also, it isn't a very old hard drive, I got it in
> Nov
> > of '01.
> >
> > thanks
> >
> > -Chris
> >
> >
> > --- Brian Wiese <bwiese at cotse.com> wrote:
> > > Perhaps youre hard drive is very old and doesnt
> > > support DMA? Adam
> > > mentioned using "hdparm -d 1 /dev/hda" I
> believe.
> > > Hrmm... if this seems
> > > to have solved it, no errors for days, thats
> good to
> > > know.
> > >
> > > On Thu, 17 Apr 2003 11:06:37 -0700 (PDT)
> > > CM Miller <cmmiller1973 at yahoo.com> wrote:
> > >
> > > |
> > > |
> > > |I generally don't give up so easily, so after
> not
> > > |getting an my problem answer here I posted to
> > > |
> > > |
> > > |http://www.linuxjunior.org
> > > |
> > > |
> > > |Someone advised that I modify
> > > /etc/sysconfig/harddisk
> > > |and uncomment the following:
> > > |
> > > |USE_DMA = 1
> > > |
> > > |It works, but now I want to know, why?
> > > |
> > > |DMA, I suspect is Direct Memory Access and here
> are
> > > |some of the comments above this line
> > > |
> > > |
> > > |# These options are used to tune the hard
> drives -
> > > |# read the hdparm man page for more information
> > > |
> > > |# Set this to 1 to enable DMA. This might cause
> > > some
> > > |# data corruption on certain chipset / hard
> drive
> > > |# combinations. This is used with the "-d"
> option
> > > |
> > > |
> > > |thanks
> > > |
> > > |
> > > |
> > > |
> > > |>>Thanks Brian for the help, see my comments
> below.
> > >
> > > |
> > > |
> > > |--- Brian Wiese <bwiese at cotse.com> wrote:
> > > |> On Sat, 12 Apr 2003 20:24:01 -0700 (PDT)
> > > |> CM Miller <cmmiller1973 at yahoo.com> wrote:
> > > |>
> > > |>
> > > |> |Whenever using XMMS to play oggs/mp3s from a
> > > |> mounted
> > > |> |cdrom, XMMS will stop playing and do
> nothing. I
> > > |> |cannot kill the process, or umount. I have
> to
> > > |> reboot
> > > |> |to fix it.
> > > |>
> > > |> When does it the music stop/xmms die?
> > > |>Do you play
> > > |> music for awhile, then
> > > |> hours later it just stops or hangs and you
> can't
> > > |> kill it?
> > > |
> > > |
> > > |It varies, sometimes right away, sometimes 5 or
> 10
> > > |minutes later.
> > > |
> > > |
> > > |>I've had
> > > |> something like this before, after playing
> mp3s
> > > from
> > > |> a networked drive over
> > > |> many hours/days - it seemed like xmms would
> lock
> > > up
> > > |> and the system needed
> > > |> to be rebooted, again - I couldnt kill the
> xmms
> > > |> process. I think it had
> > > |> something to do with tying up my sound device
> > > |> /dev/dsp or something, it
> > > |> was locked up too if I recall - or still in
> use
> > > by
> > > |> xmms.
> > > |>
> > > |> |Using clt+alt and F1, I get out of the GUI,
> get
> > > a
> > > |> |login screen, login in and get this error:
> > > |> |
> > > |> |HDC: Lost Interrupt.
> > > |>
> > > |> You get this on reboots/boot ups? Just when
> you
> > > are
> > > |> playing music from
> > > |> xmms? This doesn't seem like an error that
> xmms
> > > |> would spit out.
> > > |
> > > |
> > > |Nah, I don't think it is an error with XMMS, my
> > > |research on this points to two things: Either
> > > |conflict with ides or enable multi-mode for my
> > > kernel,
> > > |which I have never heard of before.
> > > |
> > > |
> > > |>
> > > |> |Google the output and get this website
> > > |> |
> > > |>
> > >
> >
>
||http://www.greenend.org.uk/rjk/2002/02/lostinterrupt.html
> > > |> |
> > > |> |
> > > |> |I check my /proc/interrupts
> > > |> |
> > > |> |
> > > |> | CPU0
> > > |> | 0: 10307351 XT-PIC timer
> > > |> | 1: 12545 XT-PIC keyboard
> > > |> | 2: 0 XT-PIC cascade
> > > |> | 3: 123161 XT-PIC SiS 7018
> PCI
> > > |> Audio,
> > > |> |EMU10K1
> > > |> | 5: 13429 XT-PIC eth0
> > > |> | 6: 22 XT-PIC floppy
> > > |> | 8: 1 XT-PIC rtc
> > > |> | 11: 0 XT-PIC usb-ohci,
> > > usb-ohci
> > > |> | 12: 213315 XT-PIC PS/2 Mouse
> > > |> | 14: 82148 XT-PIC ide0
> > > |> | 15: 115332 XT-PIC ide1
> > > |> |NMI: 0
>
=== message truncated ===
=====
*****************
*********************
GAIM ID: cmmiller1973
*********************
******************
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
More information about the OLUG
mailing list