public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Esben Stien <b0ef@esben-stien.name>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.15-rt1
Date: Tue, 10 Jan 2006 22:09:01 -0500	[thread overview]
Message-ID: <1136948941.6197.76.camel@localhost.localdomain> (raw)
In-Reply-To: <87hd8bk9sy.fsf@esben-stien.name>

On Tue, 2006-01-10 at 23:17 +0100, Esben Stien wrote:
> Ingo Molnar <mingo@elte.hu> writes:
> 
> > i have released the 2.6.15-rt1 tree
> 
> Didn't see any release announcement for 2.6.15-rt3, so I post here. 

If you want Ingo to see this, then please CC him (as I added him).

> 
> I've booted up rt3 and got this: 
> 
> [drm] Loading R200 Microcode
> check_monotonic_clock: monotonic inconsistency detected!
>         from      157c03cbfc9 (1476398989257) to      157c03ca8f6 (1476398983414).
> softirq-hrtimer/8[CPU#0]: BUG in check_monotonic_clock at kernel/time/timeofday.c:160
>  [<c0112555>] __WARN_ON+0x40/0x5f (8)
>  [<c012701a>] check_monotonic_clock+0x64/0x9a (48)
>  [<c01273c7>] get_monotonic_clock+0xb5/0xe8 (32)
>  [<c0124d95>] hrtimer_forward+0x2b/0xd6 (64)
>  [<c011ae6a>] group_send_sig_info+0xb1/0xd3 (12)
>  [<c0114e88>] it_real_fn+0x0/0x42 (40)
>  [<c0114ec2>] it_real_fn+0x3a/0x42 (4)
>  [<c01253c2>] run_hrtimer_softirq+0x7d/0xe8 (24)
>  [<c01161e3>] ksoftirqd+0xce/0x139 (32)
>  [<c0116115>] ksoftirqd+0x0/0x139 (40)
>  [<c01223f2>] kthread+0x79/0xa3 (4)
>  [<c0122379>] kthread+0x0/0xa3 (24)
>  [<c0100db9>] kernel_thread_helper+0x5/0xb (16)

Is this AMD or Intel?

> 
> I'm also, for some reason, unable to get my Logitech MX1000 mouse to
> work in xorg-6.8.1 here, through evdev. I changed my config file to
> use normal /dev/psaux as a temporary solution. I'm coming from
> linux-2.6.14-rt22 where everything related is working fine. No
> software has changed.

Does vanilla 2.6.15 (without -rt) work?

> 
> I run my own distro. 

Cool.

-- Steve



  reply	other threads:[~2006-01-11  3:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03  9:47 2.6.15-rt1 Ingo Molnar
2006-01-03 11:21 ` 2.6.15-rt1 Michal Piotrowski
2006-01-03 11:27   ` 2.6.15-rt1 Ingo Molnar
2006-01-03 11:34     ` 2.6.15-rt1 Michal Piotrowski
2006-01-03 14:33 ` 2.6.15-rt1 Florian Schmidt
2006-01-03 15:13   ` 2.6.15-rt1 Florian Schmidt
2006-01-03 18:40     ` 2.6.15-rt1 Steven Rostedt
2006-01-03 18:56       ` 2.6.15-rt1 Steven Rostedt
2006-01-04  0:01         ` 2.6.15-rt1 Florian Schmidt
2006-01-04  0:24           ` 2.6.15-rt1 Steven Rostedt
2006-01-04 14:31             ` 2.6.15-rt1 Steven Rostedt
2006-01-03 23:12 ` 2.6.15-rt1 David Brown
2006-01-03 23:29   ` 2.6.15-rt1 David Brown
2006-01-04  2:24   ` 2.6.15-rt1 YOSHIFUJI Hideaki / 吉藤英明
2006-01-04  7:16     ` 2.6.15-rt1 David Brown
2006-01-04  7:43       ` 2.6.15-rt1 YOSHIFUJI Hideaki / 吉藤英明
2006-01-04  7:50         ` 2.6.15-rt1 David Brown
2006-01-04 21:01           ` 2.6.15-rt1 Willy Tarreau
2006-01-05 20:52 ` 2.6.15-rt1 James Cloos
2006-01-05 21:00   ` 2.6.15-rt1 David Brown
2006-01-10 22:17 ` 2.6.15-rt1 Esben Stien
2006-01-11  3:09   ` Steven Rostedt [this message]
2006-01-11 10:16 ` 2.6.15-rt1 Esben Stien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1136948941.6197.76.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=b0ef@esben-stien.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox