mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: jamal <hadi@cyberus.ca>
Cc: Greg KH <greg@kroah.com>, Linus Torvalds <torvalds@transmeta.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	kuznet@ms2.inr.ac.ru, david.knierim@tekelec.com,
	Robert Olsson <Robert.Olsson@data.slu.se>,
	Donald Becker <becker@scyld.com>,
	linux-kernel@vger.kernel.org, alexander@netintact.se,
	raarts@office.netland.nl
Subject: Re: PCI init issues
Date: Tue, 4 Mar 2003 18:28:15 +0300	[thread overview]
Message-ID: <20030304182815.A3829@jurassic.park.msu.ru> (raw)
In-Reply-To: <20030303203540.F67734@shell.cyberus.ca>; from hadi@cyberus.ca on Mon, Mar 03, 2003 at 08:48:16PM -0500

On Mon, Mar 03, 2003 at 08:48:16PM -0500, jamal wrote:
> Mar  3 18:01:39 localhost kernel: PCI->APIC IRQ transform: (B6,I4,P0) ->
> 96
> Mar  3 18:01:39 localhost kernel: PCI->APIC IRQ transform: (B6,I5,P1) ->
> 96
> Mar  3 18:01:39 localhost kernel: PCI->APIC IRQ transform: (B6,I6,P2) ->
> 96
> Mar  3 18:01:39 localhost kernel: PCI->APIC IRQ transform: (B6,I7,P3) ->
> 96
...
> BIOS irq assignments i suppose are validated.

No, this means that mp tables are broken in a way I didn't expect...
Also, it's unclear whether or not the IOxAPIC routing is broken as well.
Probably full dmesg output (especially things related to IO_APICs setup
and irq<->pin mapping) could shed some light on this.

> I have a feeling the reason it works in windows is because of a
> functional ACPI.

Perhaps.

Ivan.

  reply	other threads:[~2003-03-04 15:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-02 17:44 jamal
2003-03-03 12:14 ` Ivan Kokshaysky
2003-03-03 16:01   ` David S. Miller
2003-03-04  1:51     ` jamal
2003-03-04  1:48   ` jamal
2003-03-04 15:28     ` Ivan Kokshaysky [this message]
2003-03-04 18:16   ` Donald Becker
2003-03-04 22:30     ` Ivan Kokshaysky
2003-03-04 22:59       ` kuznet
2003-03-04 23:36       ` Donald Becker
2003-03-04 16:26 david.knierim
2003-03-04 16:41 ` Linus Torvalds
2003-03-04 17:54 ` Ron Arts
2003-03-04 18:26   ` Ivan Kokshaysky
2003-03-04 18:54     ` Linus Torvalds
2003-03-04 19:37       ` Ron Arts
2003-03-04 22:46         ` Zwane Mwaikambo
2003-03-04 23:22           ` Ron Arts
2003-03-04 23:58             ` Zwane Mwaikambo
2003-03-04 22:46       ` Ivan Kokshaysky
2003-03-04 23:12         ` kuznet
2003-03-05 11:06           ` Ivan Kokshaysky
2003-03-05 13:54       ` Ron Arts
2003-03-04 21:50 david.knierim

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=20030304182815.A3829@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=Robert.Olsson@data.slu.se \
    --cc=alexander@netintact.se \
    --cc=becker@scyld.com \
    --cc=david.knierim@tekelec.com \
    --cc=greg@kroah.com \
    --cc=hadi@cyberus.ca \
    --cc=jgarzik@pobox.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raarts@office.netland.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®