All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Stark <stark@enterprisedb.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: soft lockup detected
Date: Thu, 16 Aug 2007 14:36:17 +0100	[thread overview]
Message-ID: <874pizwqi6.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <1187270275.6114.87.camel@twins> (Peter Zijlstra's message of "Thu\, 16 Aug 2007 15\:17\:55 +0200")

"Peter Zijlstra" <peterz@infradead.org> writes:

> On Thu, 2007-08-16 at 09:54 +0100, Gregory Stark wrote:
>
>> This is on 2.6.21-1.3194.fc7. I've been trying different kernels but this is
>> the first point where I've narrowed down the symptoms to something
>> reproducible.
>
> That is a very old kernel, and a vendor kernel at that.

I'm sorry? The original kernel to exhibit the problem was 2.6.5 -- *that* was
a very old kernel and I insisted we upgrade before trying to report any
problems. However 2.6.21 is only one version out of date and it's about 3
months old. None of the changelog entries since then have mentioned any semop
or ipc related changes (aside from a hugetlb change but we're not using
hugetlb). It's more recent than most distributions have as their current
release.

I do share your feelings about vendor kernels. We've seen these problems with
SUSE 2.6.5 and 2.6.16 kernels though. This was the most recently released
kernel we've tried.

> Did any of the different kernels you tried include a recent upstream
> one?

Still working on it.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

      reply	other threads:[~2007-08-16 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16  8:54 soft lockup detected Gregory Stark
2007-08-16 13:17 ` Peter Zijlstra
2007-08-16 13:36   ` Gregory Stark [this message]

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=874pizwqi6.fsf@oxford.xeocode.com \
    --to=stark@enterprisedb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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.