From: Jens Axboe <axboe@suse.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: hddtemp hangs with USB SCSI disks; blk_execute_rq again
Date: Tue, 26 Oct 2004 11:10:27 +0200 [thread overview]
Message-ID: <20041026091027.GC13562@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0410260827240.8730-100000@math.ut.ee>
On Tue, Oct 26 2004, Meelis Roos wrote:
> Hi,
>
> hddtemp startup script hangs on my machine. Just the hddtemp process is
> in D state (blk_execute_rq) and unkillable, other processes run fine.
> The startup script calls hddtemp -wn /dev/sda. /dev/sda
> is a CF slot in a USB 6-in-1 memory card reader, currently empty.
> /proc/partitions shows only 2 ide disks.
>
> Since hddtemp is not converted to SG_IO yet, the kernel logs
> program hddtemp is using a deprecated SCSI ioctl, please convert it to SG_IO
> but this should not cause hddtemp to hang.
No, but it's very possible for the issue to be buggy and thus hang the
device. The old method is more risky since it lacks certain information
(such as data direction).
> This is another case of process hanging in blk_execute_rq, see the
> recent thread "readcd hangs in blk_execute_rq" (also reported by me but
> about a different computer).
Well since most user issued io goes through that path, you haven't
really discovered much else than that very fact :-)
> I have noticed it some weeks ago but didn't have time then to
> investigate and disabled hddtemp. Today I looked at it again and now I'm
> reporting it.
Report it to the hddtemp people and let them diagnose it.
--
Jens Axboe
prev parent reply other threads:[~2004-10-26 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 5:36 hddtemp hangs with USB SCSI disks; blk_execute_rq again Meelis Roos
2004-10-26 9:10 ` Jens Axboe [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=20041026091027.GC13562@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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.