linux-kernel - Re: [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic Toughbook S10

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:	Sat, 7 Jul 2012 07:41:37 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bill Unruh <unruh@...sics.ubc.ca>, Jiang Liu <liuj97@...il.com>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic
 Toughbook S10

> because it is locked down by BIOS to chipset, readback should be 0xfed98004.
>
> and pci_size will return 32k for 0xfed98000.

A device with a read-only BAR doesn't conform to the PCI spec.  We
can't determine how much space the device consumes.
It's just an accident that BIOS put it at an address that we happen to
interpret as 32K.  We have no idea if the device consumes 4K, 8K, 16K,
or 32K.

> so try get one update bios that could return resource for root bus.
>
> or you could try to live with booting with pci=nocrs before your get new BIOS.

A BIOS update is not a useful answer.  The point is that we need
better reporting of the situation so we don't have to spend all this
time debugging this issue again.  We need to figure out how to
identify this as a non spec-compliant device and continue as best we
can.  We probably need to report it to the user because if there's a
device of unknown size consuming address space, we're liable to cause
a conflict by placing another device on top of it.
--
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/