From: Andreas Schwab <schwab@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Cc: Finn Thain <fthain@telegraphics.com.au>
Subject: BUG: workqueue lockup
Date: Sun, 20 Mar 2016 16:41:14 +0100 [thread overview]
Message-ID: <87oaa9upgl.fsf@linux-m68k.org> (raw)
I'm getting this hangup with 4.5 in aranym:
[ 2.060000] scsi host0: Atari native SCSI, io_port 0x0, n_io_port 0, base 0x0, irq 15, can_queue 8, cmd_per_lun 1, sg_tablesize 0, this_id 7, flags { }, options { REAL_DMA SUPPORT_TAGS }
[ 2.110000] blk_queue_max_segments: set to minimum 1
[ 55.130000] random: nonblocking pool is initialized
[ 60.240000] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 58s!
[ 60.270000] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=-20 stuck for 52s!
[ 60.300000] Showing busy workqueues and worker pools:
[ 60.310000] workqueue events: flags=0x0
[ 60.340000] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
[ 60.340000] pending: cache_reap, do_cache_clean
[ 60.380000] workqueue events_power_efficient: flags=0x80
[ 60.410000] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
[ 60.410000] pending: fb_flashcursor, neigh_periodic_work
[ 60.450000] workqueue kblockd: flags=0x18
[ 60.470000] pwq 1: cpus=0 node=0 flags=0x0 nice=-20 active=1/256
[ 60.470000] pending: blk_mq_timeout_work
[ 60.500000] workqueue ncr5380_0: flags=0xa
[ 60.530000] pwq 2: cpus=0 node=0 flags=0x4 nice=0 active=1/1
[ 60.530000] in-flight: 6:NCR5380_main
[ 60.560000] pool 2: cpus=0 node=0 flags=0x4 nice=0 hung=58s workers=2 idle: 57
I assume that this has something to do with the ncr5380 updates.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2016-03-20 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 15:41 Andreas Schwab [this message]
2016-03-20 22:02 ` BUG: workqueue lockup Michael Schmitz
2016-03-20 22:29 ` Finn Thain
2016-03-21 0:01 ` Andreas Schwab
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=87oaa9upgl.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=fthain@telegraphics.com.au \
--cc=linux-m68k@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.