From: Jiri Olsa <olsajiri@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] soft lockup detected with ipcs
Date: Fri, 29 Feb 2008 12:35:00 +0100 [thread overview]
Message-ID: <47C7EDE4.9040909@gmail.com> (raw)
In-Reply-To: <20080229032902.a1a235df.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 29 Feb 2008 12:01:27 +0100 Jiri Olsa <olsajiri@gmail.com> wrote:
>
>> Andrew Morton wrote:
>>> On Fri, 29 Feb 2008 11:46:24 +0100 Jiri Olsa <olsajiri@gmail.com> wrote:
>>>
>>>> when I run 'ipcs' my system freeze up immediatelly.
>>>> I was able to get kernel BUG message once, I think it is not
>>>> printed out all the time it freeze.
>>>>
>>>> I tried on 2.6.24, 2.6.20 and 2.6.18.
>>>> I attached screenshot from 2.6.18 freeze and config.
>>> how weird. Lots of people are surely running ipcs and not seeing this.
>>>
>>> Can you suggest what's different about your setup?
>> no idea :) I noticed like 2 weeks ago... I probably changed some config,
>> but I dont remember what it was, I'll try to figure out.
>>
>> Anyway I can reproduce this immediatelly, so I can run any diag you'd need to see.
>>
>
> (reversed top-posting - please don't do that ;))
>
> Strange. I guess as a first step it would be good if you can get a full
> backtrace - can you set up netconsole
> (Documentation/networking/netconsole.txt) and grab that?
>
> We have your config. Can you tell us how you're triggering it? Does a
> particular workload have to be run, or is it triggerable straight after
> bootup?
>
> Thanks.
I'll try to get the netconsole..
The trigger is simple just type ipcs and press enter :)
I noticed that running from xterm freeze all the time.
It wont freeze up sometimes running directly from terminal.
I also tried to reproduce it in qemu but with no luck.
next prev parent reply other threads:[~2008-02-29 11:35 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 [this message]
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
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=47C7EDE4.9040909@gmail.com \
--to=olsajiri@gmail.com \
--cc=akpm@linux-foundation.org \
--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 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.