From: Brad Campbell <brad@wasp.net.au>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: htejun@gmail.com, linux-ide@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
Date: Mon, 18 Jun 2007 15:40:55 +0400 [thread overview]
Message-ID: <46766F47.1080405@wasp.net.au> (raw)
In-Reply-To: <200706181129.l5IBT0Sa002063@harpo.it.uu.se>
Mikael Pettersson wrote:
>>> I don't think sata_promise is the guilty party here. Looks like some
>>> layer above sata_promise got confused about the state of the interface.
>> But locking up hard after hardreset is a problem of sata_promise, no?
>
> Maybe, maybe not. The original report doesn't specify where/how
> the machine hung.
It hangs in the process of trying to power it off. Unmount everything and halt the machine.
I've tried halt with and without the -h.
With the -h you can hear the drives spin down, then it tries to spin them up again and hangs.
Without the -h it just hangs hard where you see in the photo.
> Brad: can you enable sysrq and check if the kernel responds to
> sysrq when it appears to hang, and if so, where it's executing?
All my kernels have sysrq enabled. Once the hard reset is displayed on the screen everything locks.
> sata_promise just passes sata_std_hardreset to ata_do_eh.
> I've certainly seen EH hardresets work before, so I'm assuming
> that something in this particular situation (PHY offlined,
> kernel close to shutting down) breaks things.
That is my thought. I thought on a .22-rc kernel if I used halt -h and it spun the disks down that
the kernel would detect that and not try to flush the caches on them, or have I read something
incorrectly?
> FWIW, I'm seeing scsi layer accesses (cache flushes) after things
> like rmmod sata_promise. They error out and don't seem to cause
> any harm, but the fact that they occur at all makes me nervous.
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2007-06-18 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 11:29 Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678] Mikael Pettersson
2007-06-18 11:33 ` Tejun Heo
2007-06-18 11:40 ` Brad Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-16 19:09 Mikael Pettersson
2007-06-18 7:09 ` Tejun Heo
2007-06-16 11:52 Brad Campbell
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=46766F47.1080405@wasp.net.au \
--to=brad@wasp.net.au \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).