mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: linux-kernel@vger.kernel.org
Subject: task kworker / kloopd blocked for more than 120 seconds
Date: Thu, 28 May 2015 11:37:59 +0200	[thread overview]
Message-ID: <20150528113759.03088f57@leda.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

Hello everybody,

I am experiencing issues on a live system based on Arch Linux [0][1] with
Linux kernel 4.0.x when booted in RAM mode (parameter 'copytoram') [2].
Probably the problem exists some time longer, I am not sure when this first
happened and what versions are effected.

The boot sequence looks like this:

-> boot kernel
-> start initramfs
-> get the squashfs image file (there is no difference with loop mount,
   nbd or http)
-> root filesystem is set up with loop devices and device mapper
-> boot continues

The root filesystem is accessed as follows:

-> ext4 filesystem
  -> device mapper snapshot target
    -> /dev/loop1: r/o ext4 image
      -> mounted squashfs
        -> /dev/loop0: squashfs image
    -> /dev/loop2: r/w COW image (sparse file)

    
Assembling the root filesystem stack always succeeds, but sometimes boot hangs
with a lot of:

INFO: task kworker/u#:#:### blocked for more than 120 seconds

and a single:

INFO: task kloopd/### blocked for more than 120 seconds

Any idea what goes wrong? Looks like a race condition or deadlock.

[0] https://wiki.archlinux.org/index.php/Archiso
[1] https://projects.archlinux.org/archiso.git/
[2] https://projects.archlinux.org/archiso.git/tree/docs/README.bootparams
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Chris           get my mail address:    */=0;b=c[a++];)
putchar(b-1/(/*               gcc -o sig sig.c && ./sig    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2015-05-28  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  9:37 Christian Hesse [this message]
2015-05-28 12:20 ` Ming Lei
2015-05-29 12:15   ` Christian Hesse
2015-05-29 12:45     ` Ming Lei

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=20150528113759.03088f57@leda.localdomain \
    --to=list@eworm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®