mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinakar Guniguntala <dino@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: david singleton <dsingleton@mvista.com>,
	"David F. Carlson" <dave@chronolytics.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PI BUG with -rt13
Date: Fri, 25 Nov 2005 01:56:37 +0530	[thread overview]
Message-ID: <20051124202637.GB9098@in.ibm.com> (raw)
In-Reply-To: <20051124145734.GA2717@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 2721 bytes --]

On Thu, Nov 24, 2005 at 03:57:34PM +0100, Ingo Molnar wrote:
> 
> * david singleton <dsingleton@mvista.com> wrote:
> 
> > Sure.  Attached is the locking fix patch. [...]
> 
> thanks, applied - it should show up in -rt15.
> 

I just noticed with the above fix, Paul's testcase completely
hangs up and when killed I hit the BUG mentioned below.
Till -rt13, this testcase just ran to completion

check_monotonic_clock: monotonic inconsistency detected!
        from       52d314a423 (355728663587) to       50a53da892 (346369665170).
pthread_cond_ma/6345[CPU#2]: BUG in check_monotonic_clock at kernel/time/timeofday.c:156
 [<c011a840>] __WARN_ON+0x60/0x80 (8)
 [<c0139972>] check_monotonic_clock+0xcc/0x109 (48)
 [<c0139dfe>] get_monotonic_clock+0x110/0x146 (68)
 [<c013100c>] ktimer_interrupt+0x54/0x2f6 (92)
 [<c010163c>] __switch_to+0x2a/0x248 (12)
 [<c037d82b>] __schedule+0x41b/0xab7 (40)
 [<c013b86e>] add_preempt_count_ti+0x1e/0xc6 (20)
 [<c013b86e>] add_preempt_count_ti+0x1e/0xc6 (8)
 [<c01393e4>] handle_nextevent_update+0xd/0x23 (20)
 [<c010caaa>] smp_apic_timer_interrupt+0x5c/0x65 (12)
 [<c01037a4>] apic_timer_interrupt+0x1c/0x24 (12)
 [<c037f39f>] __down_mutex+0x69f/0x7fd (44)
 [<c0122856>] lock_timer_base+0x19/0x33 (24)
 [<c0122856>] lock_timer_base+0x19/0x33 (76)
 [<c0122856>] lock_timer_base+0x19/0x33 (20)
 [<c03815fd>] _spin_lock_irqsave+0x1d/0x46 (12)
 [<c0122856>] lock_timer_base+0x19/0x33 (8)
 [<c0122856>] lock_timer_base+0x19/0x33 (16)
 [<c01228a8>] __mod_timer+0x38/0xdf (16)
 [<c037e86e>] schedule_timeout+0x4f/0xa2 (32)
 [<c0123773>] process_timeout+0x0/0x9 (32)
 [<c013c95d>] futex_wait+0x225/0x2b5 (24)
 [<c012e332>] add_wait_queue+0x12/0x30 (80)
 [<c013b9cb>] sub_preempt_count+0x1a/0x1e (20)
 [<c0381c34>] _raw_spin_unlock+0x12/0x2c (44)
 [<c037db39>] __schedule+0x729/0xab7 (8)
 [<c0114b4d>] default_wake_function+0x0/0x22 (12)
 [<c0114b4d>] default_wake_function+0x0/0x22 (32)
 [<c013d84f>] do_futex+0xf3/0xf8 (40)
 [<c013d949>] sys_futex+0xf5/0x101 (40)
 [<c013d951>] sys_futex+0xfd/0x101 (36)
 [<c0102ce7>] sysenter_past_esp+0x54/0x75 (24)
---------------------------
| preempt count: 00010001 ]
| 1-level deep critical section nesting:
----------------------------------------
.. [<c013b930>] .... add_preempt_count+0x1a/0x1e
.....[<00000000>] ..   ( <= stext+0x3feffd68/0x8)

------------------------------
| showing all locks held by: |  (pthread_cond_ma/6345 [f2a52120,   0]):
------------------------------

#001:             [c3888fe0] {&base->t_base.lock}
... acquired at:               lock_timer_base+0x19/0x33


I have attached the testcase below. Run it as

gcc -g  -lpthread  pthread_cond_many.c   -o pthread_cond_many
sh ./pthread_cond_many.sh --realtime


	-Dinakar




[-- Attachment #2: rt-pthread.tar.gz --]
[-- Type: application/x-gzip, Size: 2300 bytes --]

  reply	other threads:[~2005-11-24 20:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 16:18 Dinakar Guniguntala
2005-11-17 16:41 ` Dinakar Guniguntala
2005-11-17 23:03 ` David Singleton
2005-11-18  9:29   ` Ingo Molnar
2005-11-18 13:21     ` Dinakar Guniguntala
2005-11-18 13:27       ` Ingo Molnar
2005-11-18 17:05         ` david singleton
2005-11-18 17:44           ` Ingo Molnar
2005-11-21 19:48             ` David Singleton
2005-11-21 21:26               ` Ingo Molnar
2005-11-22  2:01                 ` david singleton
2005-11-24 14:57                   ` Ingo Molnar
2005-11-24 20:26                     ` Dinakar Guniguntala [this message]
2005-11-24 20:32                       ` Dinakar Guniguntala
2005-11-24 22:25                         ` david singleton
2005-11-25  4:56                         ` david singleton
2005-11-25  7:34                           ` Dinakar Guniguntala
2005-11-25  8:04                             ` Dinakar Guniguntala
2005-11-25  5:04                       ` Ingo Molnar
2005-11-25 13:27                         ` Dinakar Guniguntala
2005-11-25  8:03                   ` Ingo Molnar
2005-11-22  2:13                 ` david singleton
     [not found]                 ` <8D664A17-5B07-11DA-A840-000A959BB91E@mvista.com>
2005-11-22  9:37                   ` Dinakar Guniguntala

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=20051124202637.GB9098@in.ibm.com \
    --to=dino@in.ibm.com \
    --cc=dave@chronolytics.com \
    --cc=dsingleton@mvista.com \
    --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

all inboxes | Powered by JetHome®