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-next>] [day] [month] [year] [list]
Date:	Mon, 10 Nov 2008 10:12:22 +0100
From:	"GARCIA DE SORIA LUCENA, JUAN JESUS" <juanj.g_soria@...pobbva.com>
To:	<linux-kernel@...r.kernel.org>
Subject: Regression: Boot hang sizing transparent PCI-to-PCI bridge since after 2.6.25-r7.

Hello.

Time ago I bisected a commit that was making my OKI Anima 3300 laptop
hang during boot.

The offending commit was:

------------
commit 12c22d6ef299ccf0955e5756eb57d90d7577ac68
Author: Linus Torvalds <torvalds@...ux-foundation.org>
Date:   Wed Mar 26 11:22:40 2008 -0700

    Revert "PCI: remove transparent bridge sizing"

    This reverts commit 8fa5913d54f3b1e09948e6a0db34da887e05ff1f, which
    caused various interesting problems for people, including wrong
resource
    allocations.  See for example bugzilla entry "2.6.25-rc2: ohci1394
    problem (MMIO broken)" at

        http://bugzilla.kernel.org/show_bug.cgi?id=10080

[...]
------------

It happenend sometime fter 2.6.25-rc7; since then I've been living on
hand-patched kernels; I can't boot any official kernel from Ubuntu or
Gentoo without patching them. For Ubuntu this would mean rebuilding the
LiveCD and then manually patching every kernel update and restricted
modules distribution...


I filled this bug:

http://bugzilla.kernel.org/show_bug.cgi?id=11054

that seems to be getting no attention at all. It includes detailed lspci
output.


The specific bridge that fails (as far as I can tell from putting
kprintf()'s into the kernel) is:

00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
(prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=04, subordinate=08, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: c3000000-c30fffff
	Prefetchable memory behind bridge: fff00000-000fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
	Capabilities: [b8] Subsystem: Gammagraphx, Inc. Device 0000
	Capabilities: [8c] HyperTransport: MSI Mapping Enable- Fixed-
		Mapping Address Base: 00000000fee00000


A specific weird detail of the machine (I don't know whether it's
related at all) is that the onboard ethernet controller is recognized as
some kind of bridge??? :

00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
	Subsystem: CLEVO/KAPOK Computer Device 5403
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (250ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at c0007000 (32-bit, non-prefetchable)
[size=4K]
	Region 1: I/O ports at 30b8 [size=8]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable+ DSel=0 DScale=0 PME-
	Kernel driver in use: forcedeth


Since this issue means that either I scrap my laptop or suffer a forced
live of kernel micromanagement no matter the distro I choose, I'm very
interested in helping with this. I'll try to find the problem myself if
someone directs me about what to look for.


Regards, and thanks in advance,

   Juan Jesus.


--
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/

Powered by blists - more mailing lists