lkml.org 
[lkml]   [2003]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: PCI init issues
From
Date


Ivan,
Here is the full messages output for a system with this problem. I had
only provided part of the
messages file to him earlier. This is the entire output.

(See attached file: messages)

David




Ivan Kokshaysky
<ink@jurassic.pa To: jamal
<hadi@cyberus.ca>
rk.msu.ru> 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
03/04/2003 10:28 <Robert.Olsson@data.slu.se>,
Donald Becker <becker@scyld.com>,
AM
linux-kernel@vger.kernel.org, alexander@netintact.se,
raarts@office.netland.nl
Subject: Re: PCI init issues





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.



(See attached file: messages)
[unhandled content-type:application/octet-stream]
\
 
 \ /
  Last update: 2005-03-22 13:33    [W:1.319 / U:3.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site