linux-kernel - Re: [Bug 41722] Clevo M5X0JE hangs in ACPI init

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: <CAErSpo6CEfSC=--Tkn2LofZuJ-TXPAMCO9qMcwovzj_k_rMiig@mail.gmail.com>
Date:	Sun, 8 Jan 2012 21:20:50 -0700
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Rogério Brito <rbrito@....usp.br>
Cc:	Edward Donovan <edward.donovan@...ble.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	bugzilla-daemon@...zilla.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Márcia Coutinho de Brito <mcbrito@...il.com>
Subject: Re: [Bug 41722] Clevo M5X0JE hangs in ACPI init

On Sun, Jan 8, 2012 at 3:27 PM, Rogério Brito <rbrito@....usp.br> wrote:
> I bisected the PCI stuff and ended up with a bad commit 12c22d6ef299ccf0955,
> which was made by Linus:
>
> ,----[ git show 12c22d6ef299ccf0955e5756eb57d90d7577ac68 ]
> | commit 12c22d6ef299ccf0955e5756eb57d90d7577ac68
> | Author: Linus Torvalds <torvalds@...ux-foundation.org>
> | Date:   Wed Mar 26 11:22:40 2008 -0700
> |
> |     Revert "PCI: remove transparent bridge sizing"
> | (...)
> `----
>
> The patch that I am using to make this laptop boot at least is essentially a
> revert of that commit.
>
> Just for the sake of documentation, I am attaching here the patch that makes
> things work (at least partially).

Your patch avoids sizing transparent bridges.  I don't have an opinion
on whether that's a good idea in general.

However, I am curious about what breaks on your system when we do size
the transparent bridge.  It seems like sizing it should *work*, even
if it's not strictly necessary, so I wonder if this hang is telling us
about some other PCI allocation issue we should fix.  Would you mind
opening a bugzilla for this, since the current tree is broken for you,
and attaching a log or digital photo of the hang?

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/