mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Joel K. Greene" <joel.greene@catapult.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Timer interrupt stops, causes soft lockup
Date: Fri, 14 Mar 2008 09:38:14 -0700	[thread overview]
Message-ID: <20080314093814.3147f250@laptopd505.fenrus.org> (raw)
In-Reply-To: <1205510009.29658.83.camel@linuxdt036.nc.catapult.com>

On Fri, 14 Mar 2008 11:53:29 -0400
"Joel K. Greene" <joel.greene@catapult.com> wrote:

> We originally saw this on the SLED10 kernel - SuSE's version of
> 2.6.16.21 - where the issue would occur in a matter of weeks or
> months.

Hi,

this is roughly a 3 year old kernel; and the thing is, this code has been
revamped entirely several times since then. Do you see this behavior with,
say the 2.6.24 kernel? That's a twofold question, since it has with-tickless 
and without-tickless as option. (tickless doesn't tend to use the PIT at all
so would just avoid the entire issue; without-tickless still uses the PIT)

It's really better to use your support contract with Novell to get them to fix
it for SLE(S/D)10 if you are not in a position to test or diagnose with new
kernels; they're there to support you for their old kernel. In general, the folks
on this list are working on current kernels and don't tend to spend time working
on such old kernels. The probability of this bug being fixed since then, or the fix
being totally not applicable to current kernels, is quite high (given the several rewrites
of the timer code) so it'd be a waste of the time of the people on this list.

Now, if you can see the behavior on 2.6.24 (or better, the latest 2.6.25-rc), then
suddenly you'll find a lot more people who're going to be interested....


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-03-14 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1204653133.718.14.camel@linuxdt036.nc.catapult.com>
     [not found] ` <47CD634E.2828.00B3.0@novell.com>
     [not found]   ` <1204722318.6578.12.camel@linuxdt036.nc.catapult.com>
     [not found]     ` <47CE45D8.2828.00B3.0@novell.com>
     [not found]       ` <1204728175.6578.23.camel@linuxdt036.nc.catapult.com>
     [not found]         ` <47D3DC53.2828.00B3.0@novell.com>
     [not found]           ` <1205152374.18463.17.camel@linuxdt036.nc.catapult.com>
     [not found]             ` <1205235450.18463.45.camel@linuxdt036.nc.catapult.com>
     [not found]               ` <47D6423D.1E6F.00AA.0@novell.com>
     [not found]                 ` <1205255048.18463.60.camel@linuxdt036.nc.catapult.com>
     [not found]                   ` <1205260328.18463.67.camel@linuxdt036.nc.catapult.com>
     [not found]                     ` <47D68B9D.1E6F.00AA.0@novell.com>
     [not found]                       ` <1205265642.18463.82.camel@linuxdt036.nc.catapult.com>
     [not found]                         ` <1205322793.20205.9.camel@linuxdt036.nc.catapult.com>
     [not found]                           ` <1205326713.20205.27.camel@linuxdt036.nc.catapult.com>
     [not found]                             ` <1205332212.20205.33.camel@linuxdt036.nc.catapult.com>
2008-03-14 15:53                               ` Joel K. Greene
2008-03-14 16:38                                 ` Arjan van de Ven [this message]
2008-03-14 17:21                                   ` Joel K. Greene
2008-03-15  5:30                                     ` Arjan van de Ven
2008-03-17 15:46                                 ` Pavel Machek
2008-03-18 14:40                                   ` Joel K. Greene

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=20080314093814.3147f250@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=joel.greene@catapult.com \
    --cc=linux-kernel@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 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®