From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Aron Lentsch <lentsch@nal.go.jp>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IRQ problems on new Toshiba Libretto
Date: Sun, 10 Jun 2001 23:24:21 -0400 [thread overview]
Message-ID: <3B2439E5.493B0472@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106111107270.1065-100000@triton.nal.go.jp>
Aron,
Can you also include your kernel .config?
Looking at your dmesg output, there is no mention of a PCI BIOS at all.
That either implies there is no kernel support for PCI BIOS built in
(ok) or your BIOS doesn't support PCI BIOS (ug).
Further, there is no PCI interrupt routing table found by direct scan of
memory, so it looks like your BIOS is not providing interrupt routing
info at all. Without that, we can only route irqs on "a wing and a
prayer"
Suggestions:
* Build kernel with CONFIG_PCI_GOANY config option.
* Do not build an SMP kernel (CONFIG_SMP) unless you are really using a
multiprocessor machine.
* Go through BIOS setup. Check for and enable "PNP OS" setting, and
similar settings which reflect an automatically assignment of machine
resources.
It is also possible that this machine's interrupt routing info is in
ACPI tables.. though I do not believe the Linux ACPI can make use of
this yet.
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-11 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200106091737.KAA26056@penguin.transmeta.com>
2001-06-11 2:51 ` IRQ problems on new Toshiba Libretto Aron Lentsch
2001-06-11 3:24 ` Jeff Garzik [this message]
2001-06-11 6:28 ` Aron Lentsch
2001-06-11 3:29 ` Linus Torvalds
2001-06-11 6:30 ` Aron Lentsch
2001-06-09 15:01 Aron Lentsch
2001-06-09 19:14 ` Alan Cox
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=3B2439E5.493B0472@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=lentsch@nal.go.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.