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

[RogÃrio Brito]

Hi, people.

Sorry about the delay, but I have gathered a bunch of information
about the machine.

For the record, I tried to put some order on the subdirectory at:

    http://www.ime.usp.br/~rbrito/linux/clevo/

On Sat, Jan 14, 2012 at 19:05, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Fri, Jan 13, 2012 at 11:09 PM, RogÃrio Brito <rbrito@xxxxxxxxxx> wrote:
>> 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.

Regarding these options, Yinghai, the options which I enabled once I
typed "make oldconfig" were:

CONFIG_PCI_PRI
CONFIG_PCI_PASID

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

I did just that and uploaded a video from Linus's git tree with the
options above to:

    http://youtu.be/_dYhkWHfep0

It took a long time to boot (about 7 minutes), but all details are
there, I hope.  I can repeat the same steps for your for-pci2 branch,
if you want me to.

Bjorn wrote:
> 1) Your M5X0JE is horribly broken, but I couldn't find any similar
> reports on the web, so I wonder if there's a BIOS setting or something
> that's unique to your system.

After searching, and searching, and searching, I could find this
thread (in Portuguese) of some people with this computer, all of them
having problems with multiple distributions (which is not a surprise,
as the kernel has problems with these machines):

    http://www.forumdebian.com.br/topico-notebook-amazon-pc-amz-a-101-resolvido

Just for the record, this Clevo was rebranded by a company called
Amazon PC (the model is A101). Amazon PC has disappeared from Earth.

> Can you (a) capture the current BIOS
> settings (photos of SETUP screens or something) and (b) reset to
> factory defaults and see if anything changes?  If things work better
> with the defaults, knowing what the difference is might help us fix
> Linux.

I took pictures of the few setup screens, and I reset everything to
factory defaults, but still no luck. You can see the photos at:

    http://www.ime.usp.br/~rbrito/linux/clevo/photos/

> 2) Can you use a Windows tool like AIDA64 (free trial version at
> http://www.aida64.com/downloads) to collect information about how
> Windows configures the box?

Sure, I downloaded it an generated some reports. Two of them with this
tool that you mentioned and one with lshw. They are at:

    http://www.ime.usp.br/~rbrito/linux/clevo/hardware-description/

--- Comment #16 from Zhang Rui <rui.zhang@xxxxxxxxx>  2012-01-18 05:39:52 ---
hmm, what's the status of this bug?
does the problem still exist in the latest upstream kernel?

Yes, Zhang. Both bugs:

    https://bugzilla.kernel.org/show_bug.cgi?id=41622
    https://bugzilla.kernel.org/show_bug.cgi?id=41722

are still reproducible with the latest kernels. Please, don't close them.

OK. I'm going to bed right now, but I will be happy to provide any
further information or test any patches/trees.


Thanks for all the help,

-- 
RogÃrio Brito : rbrito@{ime.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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/