From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Finding a rogue IO source
Date: Mon, 30 Sep 2013 16:59:32 +0200 [thread overview]
Message-ID: <20130930145931.GA4095@grml> (raw)
In-Reply-To: <5243255D.2050804@ubuntu.com>
Hi!
On 14:03 Wed 25 Sep , Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have an unused disk ( no mounted filesystems ) that I put to sleep (
> hdparm -Y ) and every 10 minutes, the link is reset to process a
> request coming from a short lived process named "pool". I think it is
> a kernel work queue. I inserted a dump_stack() but it stops when it
> gets to the syscall and so doesn't trace back into what work item is
> running. How can I figure out what work item is doing this?
Maybe you could try something like this:
printk(KERN_ERR "wakeup %d", current->pid);
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
prev parent reply other threads:[~2013-09-30 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 18:03 Finding a rogue IO source Phillip Susi
2013-09-30 14:59 ` michi1 at michaelblizek.twilightparadox.com [this message]
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=20130930145931.GA4095@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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.