From: Lingzhu Xiang <lxiang@redhat.com>
To: Caspar Zhang <caspar@casparzhang.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] timers: add a new test case leapsec_timer
Date: Mon, 09 Jul 2012 10:24:29 +0800 [thread overview]
Message-ID: <4FFA40DD.3030408@redhat.com> (raw)
In-Reply-To: <4FF6B720.3040705@casparzhang.com>
On 07/06/2012 06:00 PM, Caspar Zhang wrote:
> On 07/08/2012 08:23 AM, Lingzhu Xiang wrote:
>> Note that this test case might cause kernel freeze. Running with -c 5 will
>> highly increase the likelihood of that.
>
> IIRC, -c is broken, is `-i 5` able to freeze the kernel? If yes, it
> would be better to add a new entry to $LTPROOT/runtest/timers or update
> the original entry w/ `-i 5` option.
Nope. It seems the hard hang caused by concurrent leap second is unresolved
in upstream "NOTE: Some reports have been of a hard hang right at or before
the leapsecond. I've not been able to reproduce or diagnose this..." [1]
[1]: https://lkml.org/lkml/2012/7/4/78
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-07-09 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 0:09 [LTP] [PATCH] timers: add a new test case leapsec_timer Lingzhu Xiang
2012-07-08 0:23 ` Lingzhu Xiang
2012-07-06 10:00 ` Caspar Zhang
2012-07-09 2:24 ` Lingzhu Xiang [this message]
2012-10-15 12:15 ` chrubis
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=4FFA40DD.3030408@redhat.com \
--to=lxiang@redhat.com \
--cc=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
/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