[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOtrxKMH2iyWOOtYTYCsK5eH_ZZm9zrJyh30H_7HG-36+8k_iA@mail.gmail.com>
Date: Tue, 10 Jan 2012 00:41:17 -0200
From: Rogério Brito <rbrito@....usp.br>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
bugzilla-daemon@...zilla.kernel.org,
Edward Donovan <edward.donovan@...ble.net>,
Thomas Gleixner <tglx@...utronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
linux-kernel@...r.kernel.org,
Márcia Coutinho de Brito <mcbrito@...il.com>,
Ram Pai <linuxram@...ibm.com>
Subject: Re: [Bug 41722] Clevo M5X0JE hangs in ACPI init
Dear Yinghai,
On Mon, Jan 9, 2012 at 23:32, Yinghai Lu <yinghai@...nel.org> wrote:
> in pci_bus_alloc_resource(), we already have
>
> /* don't allocate too high if the pref mem doesn't support 64bit*/
> if (!(res->flags & IORESOURCE_MEM_64))
> max = PCIBIOS_MAX_MEM_32;
>
> So it should allocate to range below 4G to unassigned children devices.
>
> but need to make sure (peer) root bus does have valid resource range at first.
>
> Rogério,
>
> Do you have bootlog with "debug ignore_loglevel pci=earlydump" ?
I have posted some information to bugzilla (see [0]), but not with
pci=earlydump. It seems that bugzilla doesn't want to mail me a reset
e-mail, but while I am waiting, I posted this on my homepage (see
[1]).
Please, note that this boot log was taken with the patch that I
e-mailed earlier (i.e., the one that makes things work). If you want
me to send a log with a vanilla kernel, just let me know and I will
grab more information.
Thanks,
Rogério.
[0]: https://bugzilla.kernel.org/show_bug.cgi?id=41622
[1]: http://www.ime.usp.br/~rbrito/linux/clevo/clevo-dmesg-with-earlydump-2012-01-10.txt
--
Rogério Brito : rbrito@...e.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
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