linux-kernel - AW: Kernel > 2.6.30: PCI issue causes Kernel freeze at booting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <334319B2EBE0B144BAE1402B79D82DC5CE13B05A@srvpegasus>
Date:	Wed, 18 May 2011 09:44:22 +0200
From:	"Hornung, Michael" <mhornung@...t-ka.de>
To:	'Bjorn Helgaas' <bhelgaas@...gle.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: AW: Kernel > 2.6.30: PCI issue causes Kernel freeze at booting

Hello Bjorn,

>[added linux-pci]

>> On Tue, May 17, 2011 at 1:01 AM, Hornung, Michael <mhornung@...t-ka.de> wrote:
>> the system from which I'm talking about is a Menlow XL (Intel Atom Z510PT and SCH US15WPT) platform with 512 megabyte RAM.
>> There is one PCIe-switch (PI7C9X20404SL) attached to each of both PCIe-ports of the US15WPT (see attached 2.6.30-lspci.txt for details).

>I think you forgot to attach the lspci.

Sorry for that, I attached it to this mail.

>> With both switches enabled, all Kernel versions (vanilla) above 2.6.30 refuse to boot. With only one switch active
>> (the other one with no supply voltage ), all Kernel versions boot properly. It does not matter which switch is removed, it
>> is sufficient just to remove one of the two.
>>
>> There is an UART (FPGA IP Core) in that system located at address 1900h using interrupt 3. In order to get Kernel messages at boot time,
>> I changed file arch/x86/include/asm/serial.h as follows:
>>
>> -        { 0, BASE_BAUD, 0x3F8, 4, STD_COM_FLAGS },      /* ttyS0 */     \
>> +        { 0, BASE_BAUD, 0x1900, 3, STD_COM_FLAGS },     /* ttyS0 */    \
>>
>> that is the only change I made to the kernel sources.

> Is this UART connected via PCI?  I don't think so, because I don't see
> any I/O BARs that include 0x1900. 

The UART is connected via LPC bus.

> However, I don't see any ACPI
> devices that mention that address either (none of the "pnp 00:xx"
> devices include that range).

> Since there's no PCI-enumerable device that uses 0x1900, and ACPI
> doesn't mention it, we think it's available, and I notice the 2.6.38.6
> kernel does assign the [io  0x1000-0x1fff] range to the 00:1c.1 bridge
> I/O window.  Now we probably have two devices claiming accesses to
> 0x1900 (the bridge and the UART).  I don't know whether this is
> causing the problem, but it can't be good.

> I think the best way to fix this would be to change your BIOS to
> include a PNP0501 ACPI device with the appropriate _CRS to tell us
> what resources it uses (then you could drop your serial.h change,
> too).

I do have the BIOS sources so I'll try do to it that way, thank you very
much!

> If changing the BIOS is impossible, you could at least find out if
> this is the problem by adding a quirk in drivers/pnp/quirks.c to
> reserve the 0x1900 region by adding an I/O resource to the PNP0c02
> device.

> Bjorn


Thank you very much again for your help!

With best regards


Michael Hornung


------------------------------------------------------------
Michael Hornung
Hardware
Mobile Telematic and Fare Collection Systems

Phone +49-(0)721-6100-305
Fax +49-(0)721-6100-399
E-Mail mhornung@...t-ka.de

INIT Innovative Informatikanwendungen
in Transport-, Verkehrs- und Leitsystemen GmbH 
Käppelestrasse 4-6
76131 Karlsruhe
Germany
http://www.init-ka.de  
 
Geschäftsführer:
Dr.-Ing. Gottfried Greschner, Dipl.-Inform. Achim Becker, Dipl.-Ing. (FH) Wolfgang Degen, Dipl.-Kfm. Dr. Jürgen Greschner
 
Amtsgericht Mannheim HRB 103679 . Internationale Registrierungen: 988055689MVA (Norwegen), FC027220 (UK)  
 
Vertraulichkeitshinweis:
Der Inhalt dieser E-Mail ist vertraulich zu behandeln. Das Schreiben ist nur zur Kenntnis des oben genannten Empfängers bestimmt. Wenn Sie nicht der richtige Adressat sind, informieren Sie bitte sofort den Absender und vernichten diese Nachricht. Unerlaubte Kopien sowie unbefugte Weitergabe sind nicht gestattet.
Bitte beachten Sie, dass durch diese E-Mail keine rechtsverbindlichen Willenserklärungen abgegeben werden.
 
Privacy Notice:
Content of this e-mail must be treated as strictly confidential. This writing is intended only for the knowledge of the above-mentioned addressee. If you are not the correct recipient please inform the sender immediately and permanently erase this message. Illegal copies as well as unauthorized passing is not permitted and strictly forbidden.
Please note that by sending this mail INIT does not make any commitment and is under no obligation.


View attachment "2.6.30-lspci.txt" of type "text/plain" (54751 bytes)