From: Jiri Olsa <olsajiri@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Nadia Derbey <Nadia.Derbey@bull.net>,
peifferp@gmail.com
Subject: Re: [BUG] soft lockup detected with ipcs
Date: Mon, 03 Mar 2008 13:19:04 +0100 [thread overview]
Message-ID: <47CBECB8.7040605@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803031305090.15209@jikos.suse.cz>
Jiri Kosina wrote:
> On Mon, 3 Mar 2008, Jiri Olsa wrote:
>
>> I'll try the patch, so far I attached the ipcs strace and adjacent kernel logs.
>
> Thanks for the strace.
>
> The kernel oopses showing the soft lockup happen at the time of the first
> segfaulting run of ipcs, or the second one that hangs?
>
> The oopses are different compared to the ones you posted previously --
> those were clearly poiting to use-after-free, these show spinlock lockup.
>
ipcs.kernel.out.1 is the kernel log from the time strace ipcs was done.
ipcs.kernel.out.2 is from the next run of ipcs that stuck,
there's no overlay between those logs.
When the kernel freeze I'm getting logs with the spinlock lockup.. and it's repeating.
next prev parent reply other threads:[~2008-03-03 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 10:46 [BUG] soft lockup detected with ipcs Jiri Olsa
2008-02-29 10:57 ` Andrew Morton
2008-02-29 11:01 ` Jiri Olsa
2008-02-29 11:29 ` Andrew Morton
2008-02-29 11:35 ` Jiri Olsa
2008-02-29 11:43 ` Jiri Kosina
2008-03-02 17:45 ` Jiri Olsa
2008-03-02 20:02 ` Andrew Morton
2008-03-02 21:23 ` Jiri Kosina
2008-03-02 21:26 ` Jiri Kosina
2008-03-03 12:00 ` Jiri Olsa
2008-03-03 12:06 ` Jiri Kosina
2008-03-03 12:19 ` Jiri Olsa [this message]
2008-03-03 12:28 ` Jiri Kosina
2008-03-03 12:38 ` Jiri Olsa
2008-03-03 14:04 ` Jiri Olsa
2008-03-03 14:45 ` Jiri Kosina
2008-03-04 9:56 ` Jiri Olsa
2008-03-04 12:57 ` Jiri Olsa
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=47CBECB8.7040605@gmail.com \
--to=olsajiri@gmail.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peifferp@gmail.com \
/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.