All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: Carsten Emde <C.Emde@osadl.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: timerfd read does not return - was probably fixed in 3.4.38
Date: Mon, 29 Apr 2013 10:43:27 +0200	[thread overview]
Message-ID: <517E32AF.8080907@meduna.org> (raw)
In-Reply-To: <517D0DD0.6040307@osadl.org>

On 28.04.2013 13:53, Carsten Emde wrote:

Hi Carsten,

> We, therefore, configure and enable continuous latency
> monitoring histograms (CONFIG_WAKEUP_LATENCY_HIST and
> CONFIG_MISSED_TIMER_OFFSETS_HIST) by default in all our farm systems
> since more than two years (https://www.osadl.org/?id=864), and we are
> not aware of any problem that might be related to them.

The problem is our systems that started to exhibit this problem
did have just these enabled :( Many more were compiled in.

Your continuous test farm is impressive! A suggestion: would it
be possible to also add a dmesg and more of the /proc/timer_list
output to the profile pages? This would make comparing with
the own system even easier.

For example the Geode system at https://www.osadl.org/?id=948 :
how did you convince it to use highres timers? In my environment
the Geode LX / CS5536 needs tsc=reliable, but your kernel command
line does not contain it.

Thanks
-- 
                                        Stano


  reply	other threads:[~2013-04-29  8:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 11:02 hrtimer: interrupt took 6742 ns, then RT throttling and hung machine for nearly 2 seconds Stanislav Meduna
2013-04-15 11:54 ` Stanislav Meduna
2013-04-15 12:22 ` Thomas Gleixner
2013-04-15 12:56   ` Stanislav Meduna
2013-04-17 15:46     ` timerfd and softirqd [Was: Re: hrtimer: interrupt took 6742 ns, then RT throttling and hung machine for nearly 2 seconds] Stanislav Meduna
2013-04-18  9:11       ` timerfd read does not return [Was: Re: timerfd and softirqd] Stanislav Meduna
2013-04-19 19:53         ` Stanislav Meduna
2013-04-22  7:35           ` [PATCH] Re: timerfd read does not return Stanislav Meduna
2013-04-22  8:55             ` Stanislav Meduna
2013-04-27  8:34         ` timerfd read does not return - was probably fixed in 3.4.38 Stanislav Meduna
2013-04-28 11:53           ` Carsten Emde
2013-04-29  8:43             ` Stanislav Meduna [this message]
2013-05-02 20:02           ` Steven Rostedt
2013-05-10 12:42           ` timerfd read does not return - some traces Stanislav Meduna
2013-05-12 17:31             ` Stanislav Meduna
2013-05-12 23:20             ` timerfd read does not return - hangs inside put_user Stanislav Meduna
2013-05-13  8:05               ` timerfd read does not return - caused by MM fault Stanislav Meduna
2013-05-14  8:31                 ` Livelock in handle_pte_fault [Was: Re: timerfd read does not return] Stanislav Meduna
2013-11-25 10:36                   ` Vijay Katoch

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=517E32AF.8080907@meduna.org \
    --to=stano@meduna.org \
    --cc=C.Emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.