Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Clark Williams <[email protected]>
Subject: Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
From: Steven Rostedt <[email protected]>
Date: Fri, 13 Jan 2006 18:08:28 -0500 (EST)
Cc: lkml <[email protected]>, Ingo Molnar <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Sender: [email protected]

On Fri, 13 Jan 2006, Clark Williams wrote:

>
> Have you tried booting your system with a up kernel?
>

Not a x86_64 up.  But serveral up i386 boxes.

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

Follow-Ups:
- Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
  - From: Mikael Andersson <[email protected]>

References:
- Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
  - From: Steven Rostedt <[email protected]>
- Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
  - From: Clark Williams <[email protected]>
- Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
  - From: Steven Rostedt <[email protected]>
- Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
  - From: Clark Williams <[email protected]>

Prev by Date: Re: wireless: recap of current issues (stack)
Next by Date: Re: [patch] kobject: don't oops on null kobject.name
Previous by thread: Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
Next by thread: Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]

Powered by Linux