linux-kernel - Re: 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]

Date:	Mon, 23 May 2011 10:29:55 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	"Hornung, Michael" <mhornung@...t-ka.de>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: Kernel > 2.6.30: PCI issue causes Kernel freeze at booting

On Wed, May 18, 2011 at 7:56 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> On Wed, May 18, 2011 at 1:44 AM, Hornung, Michael <mhornung@...t-ka.de> wrote:
>>>> 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.
>
> Makes sense; that's a common way for attaching UARTs, and they are
> normally described via ACPI.  When you do that, I think it will show
> up as ttyS4 (be sure you build with CONFIG_SERIAL_8250_PNP=y), so
> you'll have to use "console=ttyS4" when you boot.  ttyS0-ttyS3 are
> taken by the hard-coded ports in serial.h, even though they may not
> exist on your platform.

Hi Michael,

Any update on this problem?  Did it make any difference to put the
UART in the ACPI namespace?

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/