All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remi Turk <remi@a2zis.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: No IRQ known for interrupt pin A of device 00:0f.0]
Date: Sat, 28 Oct 2000 21:57:04 +0200	[thread overview]
Message-ID: <39FB2F90.80A5F931@a2zis.com> (raw)
In-Reply-To: <39FB2BCF.64A80D88@mandrakesoft.com>

Jeff Garzik wrote:
> 
> Remi Turk wrote:
> >
> > Jeff Garzik wrote:
> > >
> > > Ok, after fixing a bad interaction where the Web server was trying to
> > > run dump_pirq as a CGI script, dump_pirq can be retrieved from
> > >
> > >         http://gtf.org/garzik/kernel/files/dump_pirq
> >
> > :-)
> >
> > I just posted pcmcia-cs dump_pirq's output.
> 
> Same thing :)   I posted pcmcia_cs's dump_pirq as a convenience so
> others wouldn't have to download and extract the tarball.
> 
> Attached below is a message I just sent to someone else who is having
> the same problem as you.  Would it be possible for you to try the stuff
> I suggest in the message as well?
> 
> Thanks,
> 
>         Jeff
> 
> --
> Jeff Garzik             | "Mind if I drive?"  -Sam
> Building 1024           | "Not if you don't mind me clawing at the
> MandrakeSoft            |  dash and shrieking like a cheerleader."
>                         |                     -Max
> 
>   ------------------------------------------------------------------------
> 
> Subject: Re: No IRQ known for interrupt pin A of device 00:0f.0
> Date: Sat, 28 Oct 2000 15:38:49 -0400
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> Organization: MandrakeSoft
> To: Burton Windle <burton@fint.org>
> CC: andre@linux-ide.org, Linus Torvalds <torvalds@transmeta.com>,
>      mj@ucw.cz
> References: <Pine.LNX.4.21.0010281456180.9491-100000@fint.staticky.com>
> 
> Ok, the problem is that you have an interrupt router table for your Ali
> 1533, but no interrupt router entry for your IDE device.  That's why
> pci_enable_device is failing.
> 
> Would you mind testing two kernel patches for me?  Both of these changes
> should be attempted separately in 2.4.0-test10-pre6, and -without-
> Andre's change.
> 
> The first change attempts to build an interrupt router entry for you, if
> none is available.  I am most interested if this works.
> 
> The second change simply ignores any pci_enable_device error returns,
> and assumes that the IDE subsystem will pick up the pieces.
> 
> Remember, do not apply both of these changes at the same time...
> 
> Thanks,
> 
>         Jeff

It's compiling the first kernel now, but I don't think I'll have any
results
before tomorrow. What changes from Andre do you mean?

-- 
Linux 2.4.0-test10-pre6 #1 Sat Oct 28 14:15:54 CEST 2000
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2000-10-28 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39FB2BCF.64A80D88@mandrakesoft.com>
2000-10-28 19:57 ` Remi Turk [this message]
2000-10-28 22:27 ` [Fwd: No IRQ known for interrupt pin A of device 00:0f.0] Remi Turk
2000-10-28 23:13   ` Remi Turk

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=39FB2F90.80A5F931@a2zis.com \
    --to=remi@a2zis.com \
    --cc=jgarzik@mandrakesoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.