public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dan Christian <dac@ptolemy.arc.nasa.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hang on mount, 2.4.2-pre4, VIA
Date: Tue, 20 Feb 2001 19:28:48 +0100	[thread overview]
Message-ID: <20010220192848.B6846@suse.cz> (raw)
In-Reply-To: <20010220101622.A18117@ptolemy.arc.nasa.gov>
In-Reply-To: <20010220101622.A18117@ptolemy.arc.nasa.gov>; from dac@ptolemy.arc.nasa.gov on Tue, Feb 20, 2001 at 10:16:22AM -0800

On Tue, Feb 20, 2001 at 10:16:22AM -0800, Dan Christian wrote:

> Hello,
>   I just tried upgrading to 2.4.2-pre4 from 2.4.1 and get a hang when
> mounting the file systems.  I have the same problem with 2.4.1-ac18.
> 
> The system is a single processor P3 and uses a VIA chipset (Tyan
> something-or-other).  DMA, multi-sector IO, and 32bit sync are enabled
> using hdparm (just before the hang).

Remove the hdparm command. It isn't needed.

> There are two Ultra-66 drives
> attached to one IDE channel and a CD-RW on a second IDE channel.
> 
> The distribution is RH7 with recent security patches and modutils
> 2.4.2.  The kernel was built with kgcc.
> 
> Has anybody else seen this?

I assume these problems weren't present before?

> I'm not on the list.  Please CC me on any replies.

What's your southbridge chip (lspci ...)? What are the drives (hdparm -i ...)?

I can send you the VIA latest drivers if you are interested in trying
whether they'll help.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-02-20 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 18:16 hang on mount, 2.4.2-pre4, VIA Dan Christian
2001-02-20 18:28 ` Vojtech Pavlik [this message]
2001-02-21 16:42   ` Dan Christian
2001-02-21  7:59 ` Tobias Ringstrom

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=20010220192848.B6846@suse.cz \
    --to=vojtech@suse.cz \
    --cc=dac@ptolemy.arc.nasa.gov \
    --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