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: <CAE9FiQWbtByxJopU_SHLpiAJt_91qTs_=9dBFTYDHFh5OQQydg@mail.gmail.com>
Date:	Sat, 14 Jan 2012 13:05:54 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Rogério Brito <rbrito@....usp.br>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	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

On Fri, Jan 13, 2012 at 11:09 PM, Rogério Brito <rbrito@....usp.br> wrote:
> Dear Yinghai and other people,
>
> On Sat, Jan 14, 2012 at 00:01, Rogério Brito <rbrito@....usp.br> wrote:
>> On Fri, Jan 13, 2012 at 15:29, Yinghai Lu <yinghai@...nel.org> wrote:
>>> On Fri, Jan 13, 2012 at 3:59 AM, Rogério Brito <rbrito@....usp.br> wrote:
>>>> If it applies (and newer kernels don't have things which your patch needs),
>>>> I will keep working with Linus's v3.2 tag.
>>>
>>> No problem, I will put that patch into for-pci2 for your conveniences.
>>
>> Thanks. That's definitely easier for me. I'm grabbing it to compile
>> and will report in a moment.
>
> Just to clarify, my "definitely easier for me" means "I know what to
> do (or, at least, I'm closer this way not doing wrong things)".
>
>>>> When I compiled from your branch for-pci2 from linux-yinghai.git (without
>>>> any extra patches), it *did* boot, but noticed one thing weird: using htop
>>>> and in single user mode, it reported 100% of CPU in use. With regular top, a
>>>> more fine grained output revealed that no processes were using the CPU, but
>>>> that almost all of the time was spent in kernel mode.
>>>>
>>>> Anyway, as you asked, I put the log of what I see at
>>>>
>>>>    http://www.ime.usp.br/~rbrito/linux/clevo/2012-01-13-0951-yanghai-for-pci2-branch/
>>>
>>> [    0.165615] pci 0000:05:07.0: CardBus bridge to [bus 06-09]
>>> [    0.165682] pci 0000:05:07.0:   bridge window [io  0x0001-0x0000]
>>> [    0.165751] pci 0000:05:07.0:   bridge window [io  0x0001-0x0000]
>>> [    0.165821] pci 0000:05:07.0:   bridge window [mem
>>> 0x00000001-0x00000000 pref]
>>> [    0.165904] pci 0000:05:07.0:   bridge window [mem 0x00000001-0x00000000]
>>> [    0.165975] pci 0000:00:10.0: PCI bridge to [bus 05-06]
>>> [    0.166043] pci 0000:00:10.0:   bridge window [mem 0xb3200000-0xb32fffff]
>>> [    0.166259] pci 0000:00:10.0: setting latency timer to 64
>>> [    0.166329] pci 0000:05:07.0: device not available (can't reserve
>>> [io  0x0001-0x0000])
>>> [    0.166412] pci 0000:05:07.0: Error enabling bridge (-22), continuing
>>>
>>> We have some problems with handling cardbus bridge as optional resources.
>>>
>>> will produce some patches and update for-pci2 branch for your test.
>>
>> OK. Will try that as soon as my download completes.
>
> Just for the record, I have grabbed your for-pci2 branch with HEAD
> being 5db4211 and this is what I get:
>
>    http://www.ime.usp.br/~rbrito/linux/clevo/boot-yinghai-for-pci2-g5db4211.m4v
>
> A warning, though is that there were some options regarding PCI buses
> which I did not know exactly how to answer. I can post my config here
> if you are interested in that. Well, actually, I can give you ssh
> access to this notebook if you want to hack on it. Just let me know
> what times you (or anyone else) are online and I will try to arrange
> everything.
>

Please enable CONFIG_BOOT_PRINTK_DELAY in your .config

and boot with "boot_delay=1000" or even "boot_delay=5000"

then video capture could help.

Thanks

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