Re: Re: making progress with ACPI was: ACPI small patch up date

[Ernst Herzberg <earny-euM3SP4ZHrg@public.gmane.org>]

On Mittwoch, 30. Oktober 2002 00:50, Grover, Andrew wrote:

>
> We can fix bugs, the problem is *diagnosing* the issue. There's only so
> much diagnosis that can be done without the hardware. If you say "line 444
> of ec.c is acquiring a semaphore at interrupt level" that's probably
> enough. If you post a patch, we'll apply it. If you just say "my system
> hangs" then it's a lot harder. Sometimes the dmesg or DSDT are enough that
> other people can suss out what might be the problem -- sometimes not.
>

Hm. Give me some debugging hints. I'm not a kernel hacker, and i see the need 
for ACPI, but this stuff is complex. I have not the time and i am not willing 
to understand every line in the code. But i'm willing to help you to help you 
to fix problems in the code. 

ACPI_FUNCTION_TRACE looks for me like a function that can help.  Should it 
work if i change acpi_set_debug(..) to ACPI_DEBUG_HIGH in acpi_init(void)?  
Last try i get a kernel that don't start or was not able to send any 
printk-message.
(clean 2.4.20-pre11, newest patched ACPI patch, compiled into, not modules, 
gcc3.2)

Problem is, that thermal and processor doesn't work anymore, no error message, 
no warning... no hint ;-)

<Earny>


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf