From: "Joao S Veiga" <jsveiga_lkml@rf.com.br>
To: linux-kernel@vger.kernel.org
Subject: Re: Hangs in 2.4.19 and 2.4.20-pre5 (IDE-related?)
Date: Thu, 26 Sep 2002 17:37:10 -0300 [thread overview]
Message-ID: <200209262037.g8QKbAIt008284@rf.com.br> (raw)
Hi,
I started getting similar hangs with a PII4X board and an old QUANTUM
Pioneer SG 2.1A, around 2.4.18-10 (RH). Didn't happen with vanilla 2.4.18
& before, still happened with vanilla 2.4.19.
I could reproduce it by writing big files to the disk (consistently if
transfering them from the network - RTL8139, 100BaseT). Like you've
described, the HDD LED remained lit.
Strangely, the machine kept "some" functionality: It's a firewall/NAT
machine, and this kept working, hitting Return on an already opened shell
brought the next line prompt, etc. Trying anything requiring disk access
would hang. No core dumped, no log messages (of course, since the disk
couldn't be written).
I ended up changing a BIOS setting : PCI Latency timer from 32 to 128 PCI
clocks. (I've loaded the BIOS defaults, and "0" came up. Things got really
worse, so just went the other way - didn't try intermediate values though).
It's working fine now. I'd just like to understand why. I suppose
something got slower, but I couldn't notice (it's just a
firewall/NAT/web/mailserver, and the outside link is just 64k).
If you have this setting on the BIOS, give it a try.
Joao
next reply other threads:[~2002-09-26 20:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 20:37 Joao S Veiga [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 14:08 Jan-Hinnerk Reichert
2002-10-06 16:25 ` Alan Cox
2002-10-06 19:56 ` Jan-Hinnerk Reichert
2002-10-06 21:38 ` Alan Cox
2002-08-29 18:26 Meelis Roos
2002-08-29 19:37 ` Andre Hedrick
2002-08-29 20:18 ` Meelis Roos
2002-08-29 20:46 ` Vojtech Pavlik
2002-08-30 3:04 ` Andre Hedrick
2002-08-30 5:51 ` Vojtech Pavlik
2002-08-30 6:31 ` Andre Hedrick
2002-08-30 6:51 ` Vojtech Pavlik
2002-08-30 14:34 ` Meelis Roos
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=200209262037.g8QKbAIt008284@rf.com.br \
--to=jsveiga_lkml@rf.com.br \
--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
all inboxes | Powered by JetHome®