Re: HP/Compaq NC6120 ACPI problems

[Andrej Prsa <andrej.prsa-zs/Xt9NzJtxxh+DGd0HQrg@public.gmane.org>]

Hi!

> > Hmm. Yes, I can now repeat this with a 6220, though most of the time
> > I manage it it seems to be linked to a suspend to disk beforehand. I
> > suspect this /may/ be linked to the fact that on the 6120, only the
> > first lid event is received. I'll see if I can track this down over
> > the weekend.
> 
> Ha. Yes, progress, of sorts. On the 6120, you need to do
> 
> setpci -s 1f.0 bb.b=84
> 
> after every lid event in order to get any more. I /think/ this is a
> bug with the HP BIOS (the 6220 doesn't do this) - I'm in touch with HP
> over it now.

I see; please let me know when you get any additional information and of
course if there's anything I can do to help! If it's not too much
trouble, could you (or anyone else of course) please explain what
exactly does this setpci do?

> As for the high kacpid load, I'm only able to trigger this after
> a suspend to disk, and using the platform option (to ensure the _WAK
> methods are called) /seems/ to avoid it. Could you try building a
> kernel with acpi debug support, set the output level fairly high (echo
> -n 0x0000ffff >/proc/acpi/debug_level) and see what sort of output you
> get?

Intriguingly, I recompiled the kernel with ACPI support built in (in
contrast to having a modular ACPI support) and this time kacpid
doesn't overload the processor and the fan is working!

Determined to come to the bottom of the problem, I recompiled the kernel
again, this time with ACPI support modular and voila - the same
malfunctioning behavior popped up. I 'tail -f'd both syslog and
messages; before kacpid blowup there was no significant output, but at
the time of kacpid blowup both logs started filling up like crazy to the
point that even init 0 didn't work anymore - all I got was a console
with ACPI debug messages filling screen after screen and I had to force
computer to a halt.

> Warning - there'll be huge amounts of it. Really huge amounts. The
> stuff we're interested in is whatever appears after kacpid has begun
> taking up all the processor time.

Please find the messages.gz file at (3.1MB compressed size!):

	http://www.fiz.uni-lj.si/~prsa/messages.gz

(sorry for the enormous size (~50MB uncompressed), but I didn't want to
cut out anything relevant!) The start of the messages file is the start
of kacpid going crazy.


The solution for me is of course ACPI built into the kernel, for it
seems that the fan is working that way. Still, I would like to help
out in resolving this issue, so let me know if there's anything else I
could do!

Thanks & best wishes,

Andrej


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click