From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Lange <thomas@corelatus.se>
Cc: mingo@redhat.com, peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] sched: clock wrap bug in 2.6.35-stable kills scheduling
Date: Sun, 24 Jun 2012 10:52:07 -0700 [thread overview]
Message-ID: <20120624175207.GA29455@kroah.com> (raw)
In-Reply-To: <4FE74F1B.6070803@corelatus.se>
On Sun, Jun 24, 2012 at 07:32:11PM +0200, Thomas Lange wrote:
> Commit 305e683 introduced a wrap bug that causes task scheduling to fail
> after sched_clock() wrap. On a 1000 HZ system with 32bit jiffies, this
> occurs after 49.7 days.
>
> Bug was introduced in 2.6.35.12 and is still present in linux-2.6.35.y HEAD.
Is this an issue in 3.5-rc3?
2.6.35-stable really isn't maintained anymore, I would suggest upgrading
to a more modern kernel version.
thanks,
greg k-h
next prev parent reply other threads:[~2012-06-24 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 17:32 [BUG] sched: clock wrap bug in 2.6.35-stable kills scheduling Thomas Lange
2012-06-24 17:52 ` Greg KH [this message]
2012-06-25 9:45 ` Peter Zijlstra
2012-06-25 10:38 ` Peter Zijlstra
2012-06-25 18:49 ` Thomas Lange
2012-06-25 19:33 ` Peter Zijlstra
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=20120624175207.GA29455@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=thomas@corelatus.se \
/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