From: Tejun Heo <htejun@gmail.com>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Freeze after disabling write cache with hdparm -W0 /dev/sda
Date: Wed, 11 Jul 2007 14:11:58 +0900 [thread overview]
Message-ID: <4694669E.7060600@gmail.com> (raw)
In-Reply-To: <46935C4D.40003@onelan.co.uk>
Simon Farnsworth wrote:
> Hello,
>
> We're trying to consistently disable write caching on our systems (one
> PATA disk on /dev/sda), by running the following command during boot:
>
> hdparm -W0 /dev/sda
>
> However, on some disks, we see a freeze of between 30 seconds and 2
> minutes after issuing this command. How do we avoid this freeze? We're
> happy to write our own userspace utility, or change the kernel.
>
> We're using the pata_via driver, with a kernel that's the same code as
> the Fedora 3189 kernel, but with CONFIG_DEBUG_STACKOVERFLOW set to n.
>
> From a machine that's just done this freeze:
[--snip--]
> BUG: warning at kernel/softirq.c:138/local_bh_enable() (Not tainted)
> [<c042afff>] local_bh_enable+0x45/0x96
> [<c0603cde>] cond_resched_softirq+0x2d/0x43
> [<c05d55bf>] established_get_first+0x17/0xac
> [<c05d8f93>] tcp_seq_next+0x71/0x86
> [<c048c004>] seq_read+0x181/0x268
> [<c048be83>] seq_read+0x0/0x268
> [<c0476651>] vfs_read+0xab/0x15a
> [<c0476fb7>] sys_read+0x41/0x67
> [<c0404ecc>] syscall_call+0x7/0xb
> =======================
Hmmmm.. This is the only suspicious looking part of the kernel log and
doesn't have too much to do with ATA freeze. 30sec - 2min delay sounds
awfully like something caused by ATA commands timing out but libata
always complains verbosely about those. Can you check dmesg again after
the freeze?
--
tejun
next prev parent reply other threads:[~2007-07-11 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 10:15 Freeze after disabling write cache with hdparm -W0 /dev/sda Simon Farnsworth
2007-07-11 5:11 ` Tejun Heo [this message]
2007-07-11 8:31 ` Simon Farnsworth
2007-07-11 8:36 ` Tejun Heo
2007-07-11 8:54 ` Simon Farnsworth
2007-07-11 8:57 ` Tejun Heo
2007-07-11 12:25 ` Simon Farnsworth
2007-07-13 7:45 ` Tejun Heo
2007-07-17 8:57 ` Simon Farnsworth
2007-07-11 18:46 ` Mark Lord
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=4694669E.7060600@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=simon.farnsworth@onelan.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).