From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: Eric Wheeler <ewheeler@ewheeler.net>,
Kent Overstreet <kmo@daterainc.com>
Cc: "linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
Ross Anderson <rosander@dsotm.net>,
Stefan Priebe <s.priebe@profihost.ag>
Subject: Re: 3.17-rc6: bcache_gc: BUG: soft lockup - CPU#2 stuck for 23s!
Date: Sat, 22 Nov 2014 13:46:03 +0100 [thread overview]
Message-ID: <5470858B.9090900@message-id.googlemail.com> (raw)
In-Reply-To: <1416615728.4084.325.camel@geekdesk.ewheeler.net>
Hi Eric,
Am 22.11.2014 um 01:22 schrieb Eric Wheeler:
>> Before the patch goes upstream I need it tested so I know if it fixes
>> the actual issue or not.
>
> We have been using the rcu_sched patch and the cond_resched patch together
> (both attached) since November 3rd on 3.17.2 without any bcache
> backtraces. bcache is running in writeback mode. The server is
> predominantly write-only with relatively few reads.
Is the rcu_sched patch supposed to help the same or a totally different
problem? Means: should I also apply it, rebuild the module and reboot
(resetting the test time to zero :-)
I had the "deadly" soft lockup once per week since updating to
3.16/3.17, so I can only tell if it might help in two weeks earliest.
> To sum up, the attached two patches (plus the for-jens pull) have fixed all
> of our bcache problems since 3.14.y. These patches on 3.17.2 seem quite stable.
That's good to hear :-)
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
next prev parent reply other threads:[~2014-11-22 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 0:25 3.17-rc6: bcache_gc: BUG: soft lockup - CPU#2 stuck for 23s! Eric Wheeler
2014-10-27 2:52 ` 3.17: bcache_gc: BUG: soft lockup - CPU#2 stuck for 22s! Eric Wheeler
2014-10-31 9:20 ` Zhu Yanhai
2014-10-31 10:35 ` Re[2]: " Pavel Goran
2014-11-01 2:35 ` Eric Wheeler
2014-11-01 20:44 ` 3.17-rc6: bcache_gc: BUG: soft lockup - CPU#2 stuck for 23s! Kent Overstreet
2014-11-21 22:54 ` Stefan Seyfried
2014-11-21 23:20 ` Kent Overstreet
2014-11-22 0:22 ` Eric Wheeler
2014-11-22 12:46 ` Stefan Seyfried [this message]
2014-11-24 18:52 ` Eric Wheeler
2014-12-03 9:32 ` Stefan Seyfried
2014-12-03 11:25 ` Thomas Stein
2014-11-23 11:17 ` Thomas Stein
2014-11-24 18:49 ` 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=5470858B.9090900@message-id.googlemail.com \
--to=stefan.seyfried@googlemail.com \
--cc=ewheeler@ewheeler.net \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=rosander@dsotm.net \
--cc=s.priebe@profihost.ag \
/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.