mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: Re: [2.6.15-rc7-rt1] explosions in nptl mutex tests
Date: Mon, 02 Jan 2006 05:46:29 +0100	[thread overview]
Message-ID: <5.2.1.1.2.20060102052345.00be97c8@pop.gmx.net> (raw)
In-Reply-To: <5.2.1.1.2.20051231180437.00be1b20@pop.gmx.net>

At 06:10 PM 12/31/2005 +0100, Mike Galbraith wrote:
>At 05:36 PM 12/31/2005 +0100, Mike Galbraith wrote:
>
>>As luck would have it, just as I was collecting the data, there was a 
>>major explosion.  Box was slogging through glibc make check, and when it 
>>hit the mutex tests in nptl, KaBOOM.  Ding-dong-dead box... [reboot] oh 
>>my, seems repeatable.  Guess I'll see if I can find my serial console 
>>cable instead of typing make install as originally planned :)
>>
>>         -Mike
>
>Oopsen attached.  First two times it exploded on tst-mutex7, this time 
>that passed, but it exploded on tst-mutex7a.

Further datapoint: on a lark, I tried 8k stacks, and my symptoms changed - 
tst-mutex7 never failed, but running tst-mutex7a in a tight loop crashed 
the box reliably though differently.  I then recompiled with no debug 
options enabled, and ran all mutex tests in a loop for a couple of hours 
with no crash.

         -Mike 


  reply	other threads:[~2006-01-02  4:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31 15:00 [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected! Mike Galbraith
2005-12-31 15:49 ` Steven Rostedt
2005-12-31 16:36   ` Mike Galbraith
2005-12-31 17:10     ` [2.6.15-rc7-rt1] explosions in nptl mutex tests Mike Galbraith
2006-01-02  4:46       ` Mike Galbraith [this message]
2006-01-04 20:49     ` [2.6.15-rc7-rt1] check_monotonic_clock: monotonic inconsistency detected! john stultz
2006-01-04 20:53       ` Steven Rostedt

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=5.2.1.1.2.20060102052345.00be97c8@pop.gmx.net \
    --to=efault@gmx.de \
    --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®