public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: lost interrupt hell - Plea for Help
Date: Fri, 10 May 2002 14:28:48 -0700	[thread overview]
Message-ID: <3CDC3B90.AADE1835@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020509132713.1987A-100000@pioneer> <200205101112.g4ABCoX29098@Port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:
> 
> On 9 May 2002 09:34, Tomasz Rola wrote:
> > > I have tried every combination of master / slave between the two drives,
> > > the drives on their own, scsi emulation through ide-scsi, purely as IDE
> > > drives, ommitting ide cdrom support from teh kernel completely and only
> > > using ide-scsi... every time I try to get a track ripped, dmesg fills up
> > > with hdX: lost interrupt.
> > >
> > > If I try to rip from the DVD drive, the system hangs and its reset
> > > button time.
> > >
> > > Can anyone tell me where I'm going wrong? Is there anything from my
> > > system you need to see to help me?

  I have same problem (see some other emails from me, I haven't posted
about anything else), via motherboard, audio cd ripping doesn't work (I
get lost interrupt messages).

  I am pretty sure it's kernel problem (or motherboard design issue,
which is sort of kernel problem as well), I tried (none of it makes any
difference):

  - different cd-rom drivers (same situation),
  - dma on/off
  - 32 bit access on/off
  
  everything else except of audio ripping works (burning, data cd
reading, HD connected instead of cdrom drive etc.)

  PCI IDE card works (in same conmputer, same cdrom drive, same IDE
cables).

  the IRQ works ok, as long as the activity is something else than audio
ripping - the numbers in /proc/interrupts go up, there doesn't seem to
be any interrupt conflict (it's assigned by BIOS, IRQ 15, nothing else
seems to be using 15, at least nothing that would be visible on bios
bootup screen (it prints irq assignments) or linux (/proc/interupts
doesn't list 15 at all if the cdrom drive is not there, it lists hdc if
the drive is in).

  there are other people who have the same problem, it looks like all
are via chipsets related (I just got email from another guy who cannot
find a solution either).

  this is with stable kernel (I tried 2.4.17 and 2.4.18), via config
option compiled in (I haven't tried without via support in kernel yet,
I'll try that).

  any ideas? TIA

	erik

  reply	other threads:[~2002-05-10 21:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 18:01 lost interrupt hell - Plea for Help mikeH
2002-05-09 11:34 ` Tomasz Rola
2002-05-10 16:15   ` Denis Vlasenko
2002-05-10 21:28     ` Erik Steffl [this message]
2002-05-11  8:32       ` mikeH
2002-05-11  8:38         ` Rudmer van Dijk
2002-05-11  8:53           ` mikeH
2002-05-11  8:48             ` Rudmer van Dijk
2002-05-16 20:50           ` Rudmer van Dijk
2002-05-17  8:49             ` Mike
2002-05-19  7:14               ` Erik Steffl
2002-05-19 18:43                 ` Kevin P. Fleming
2002-05-11  8:48         ` Erik Steffl
2002-05-09 11:42 ` Tomasz Rola
  -- strict thread matches above, loose matches on Subject: below --
2002-05-19 12:25 Mikael Pettersson
2002-05-20  8:42 ` Erik Steffl
2002-05-19 20:26 Mikael Pettersson
2002-05-19 22:19 ` Kevin P. Fleming
2002-05-20  0:35 ` Kevin P. Fleming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CDC3B90.AADE1835@bigfoot.com \
    --to=steffl@bigfoot.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox