All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Yannis Aribaud <bugs@d6bell.net>, linux-bcache@vger.kernel.org
Subject: Re: bcache_gc: BUG: soft lockup
Date: Fri, 13 Nov 2015 14:05:12 +0100	[thread overview]
Message-ID: <1447419912.2616.19.camel@suse.de> (raw)
In-Reply-To: <7d53afb3c7a34bb1022f0d9b6c079022@rcube.hebserv.net>

On Fri, 2015-11-13 at 12:55 +0000, Yannis Aribaud wrote:
> 13 novembre 2015 13:37 "Johannes Thumshirn" <jthumshirn@suse.de> a
> écrit:
> > Hi Yannis,
> 
> Hi Johannes,
> 
> > [...]
> > 
> > do you have a stacktrace, so we can see where it's locking up?
> 
> There is no stack trace as the kernel isn't crashed. But the system
> seems waiting for something that never happens and keep throwing the
> same message to the console (BUG: soft lockup - CPU#22 stuck for
> 23s!).
> 
> 

I see. Can you then please force a panic on soft-lockup
via softlockup_panic=1 passed to the kernel as a boot parameter or via
sysctl -w kernel.softlockup_panic=1 on a running system.

Without having any information on where it actually locked up, I see no
chance for fixing it.

Thanks,
	Johannes

  reply	other threads:[~2015-11-13 13:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 12:09 bcache_gc: BUG: soft lockup Yannis Aribaud
2015-11-13 12:37 ` Johannes Thumshirn
2015-11-13 12:55   ` Yannis Aribaud
2015-11-13 13:05     ` Johannes Thumshirn [this message]
2015-11-13 13:27       ` Yannis Aribaud
     [not found]     ` <9c96132d5fce4a5a77b1b086f7c6095d@rcube.hebserv.net>
2015-11-16  8:09       ` Johannes Thumshirn
2015-11-16 10:26         ` Yannis Aribaud
2015-11-27 12:23       ` Johannes Thumshirn
2015-11-27 12:32         ` Yannis Aribaud
2015-11-30  1:49           ` Eric Wheeler
2015-11-30  7:07             ` Johannes Thumshirn
2015-11-30  9:59               ` Yannis Aribaud
2015-12-07 10:35                 ` Yannis Aribaud
2016-01-27 14:57                   ` Yannis Aribaud
2016-01-27 15:16                     ` Johannes Thumshirn
2016-01-29 11:54                     ` Johannes Thumshirn
2016-01-29 12:54                       ` Yannis Aribaud
     [not found]                     ` <b91ce8156337b782c82317d25b3228bd@rcube.hebserv.net>
2016-05-11  1:11                       ` Eric Wheeler
2016-05-11  9:33                         ` Jens-U. Mozdzen
2016-05-11 18:26                           ` Eric Wheeler
2016-05-12 11:51                             ` Jens-U. Mozdzen
2016-05-16 11:01                         ` Yannis Aribaud
2016-05-19 23:26                           ` Eric Wheeler

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=1447419912.2616.19.camel@suse.de \
    --to=jthumshirn@suse.de \
    --cc=bugs@d6bell.net \
    --cc=linux-bcache@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.