I disabled CONFIG_ACPI_AC and I got the same hang with ACPI_BATTERY. I am
using 2.31. Any other suggestions? I will remove all that hang but I feer
that that is not the right way to go.
Mike
-------------- Original message ----------------------
From: Jan Kiszka <[EMAIL PROTECTED]>
--- Begin Message ---
[EMAIL PROTECTED] wrote:
> Hello,
>
> I have been working on trying to find the optimal linux kernel
> configuration and have noticed a couple problems. No matter what I
> do it seems that while cpu #2 is detected, nothing gets scheduled on
Sounds like some bug that was fixed in 2.3.1. Are you already using that
version? If not: highly recommended.
> it. Also, there is always a modprobe process running at 100%cpu that
> I can't kill. The command that is showed in top is "modprobe -s ac".
Probably due to SMI being disable. Don't know what that module precisely
does when it loops, but it may wait on SMI-backed activity of the
hardware that is now disabled. Try to switch off CONFIG_ACPI_AC in your
config.
> If I run it from the command line it hangs as well. Latencies are
> however very acceptable when running xeno-test. I do however see
> some negative values in the test output.
>
> The config file that I am using currently is the same as the one
> below just with CONFIG_XENO_HW_SMI_ALL. This seems to give me the
> best latencies.
>
> Mike
>
Jan
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
