From: Martin Dalecki <dalecki@evision-ventures.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE(?) lockups in 2.5.7pre1, 2.5.6, 2.5.6pre3
Date: Wed, 13 Mar 2002 16:38:58 +0100 [thread overview]
Message-ID: <3C8F7292.5080409@evision-ventures.com> (raw)
In-Reply-To: <200203131533.HAA09497@adam.yggdrasil.com>
Adam J. Richter wrote:
> Under 2.5.6-pre3 and 2.5.6, my desktop workstation would
> occasionally get into a state where all disk I/O would block.
> Process would run until they had to go to the disk, and then they
> would stop. Hitting ctrl-<scroll lock> shows these process in "D"
> state. The IDE controller in this machine is:
>
> 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
>
> I just built 2.5.7-pre1 and have discovered the other machne
> that has a VIA IDE controller developed the same problem just after
> printing its first "login: " prompt, although it did not have the problem
> on a subsequent reboot. This other machine did not lock up with
> 2.5.6-pre3 or 2.5.6, although that is probably just due to random
> chance, as the problem was occurring only once a day. The
> IDE controller in this second machine is:
>
> 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)
>
> I will try to track this down from the process stack traces
> when it happens next, but I thought I ought to report it in the meantime.
>
You may have noted that I'm gradually trying to replace
all cli() sti() stuff, where it's using for data structure
access by proper spin locks on ide_lock. Maybe this just
uncovered something which was hidden by the brute force used
before? (Could you possible have a look at this direction?)
next prev parent reply other threads:[~2002-03-13 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 15:33 IDE(?) lockups in 2.5.7pre1, 2.5.6, 2.5.6pre3 Adam J. Richter
2002-03-13 15:38 ` Martin Dalecki [this message]
2002-03-13 17:23 ` Vojtech Pavlik
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=3C8F7292.5080409@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox