Am 22.11.2017 um 18:51 schrieb Michael Lyle:

Hi Coly, Stefan--

On 11/22/2017 05:14 AM, Stefan Priebe - Profihost AG wrote:

quoted

quoted

Hi Stefan,

Hmm, I don't have idea here. Anyway, is the cache mode set as writeback?
Recently I post a patch to fix a potential deadlock between writeback
rate update kworker and register code, I am not sure whether it is
relative to your issue, but at least we can have a try. the patch title is:
 [RFC] bcache: fix a circular dead locking with dc->writeback_lock and
bch_register_lock

Just for your information.

i can try that one - can you please resend? I can't find that mail and
don't know how to grab that one our of the web html archives to apply
correctly.

Stefan

I don't think there's any chance this patch will do anything.  If
there's a deadlock, the whole thing will become stuck forever and never
allow registration or progress on the device again-- which doesn't match
the symptoms here.

No it does not ;-)

This probably relates to udev configuration in your environment somehow.

Default debian udev - nothing special. Works on 50 other systems
perfectly only one where it does not... but udev debugging just sucks.

Stefan

Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html