On Tue, 2005-08-30 at 15:34 -0700, Daniel Walker wrote:
> Have you tried turning on
> "Non-preemptible critical section latency timing" or "Latency tracing"
I just turned on the following:
CONFIG_CRITICAL_PREEMPT_TIMING
CONFIG_CRITICAL_IRQSOFF_TIMING
CONFIG_LATENCY_TRACE
recompiled and booted. No problem here.
>
> I don't know if it's related to the PI changes, but I'm getting a crash
> with those on em64t .
>
> With both above options I get
>
> <0>init[1]: segfault at ffffffff8010ef44 rip ffffffff8010ef44 rsp 00007fffferror 5
> <0>init[1]: segfault at ffffffff8010ef44 rip ffffffff8010ef44 rsp 00007ffffffe8de8 error 5
>
> printed never ending right after init starts.
>
> If I only turn on "Non-preemptible critical section latency timing",
> then when I enter the command,
> "echo 0 > /proc/sys/kernel/preempt_max_latency"
>
> The kernel will spit out a couple of max critical section updates , then
> it will hang silently.
>
> This is all new in 2.6.13-rtX . It could have just come in with 2.6.13 ,
> but I thought I'd mention it.
Did you try the latest patches I just sent. Mainly this last one on
-rt2? There is a deadlock that is fixed wrt the BKL.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |