All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Jussi Laako <jlaako@pp.htv.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA/PDC/Athlon
Date: Wed, 16 May 2001 22:05:12 +0200	[thread overview]
Message-ID: <20010516220512.A1400@suse.cz> (raw)
In-Reply-To: <3B02B824.6FAF5125@pp.htv.fi>
In-Reply-To: <3B02B824.6FAF5125@pp.htv.fi>; from jlaako@pp.htv.fi on Wed, May 16, 2001 at 08:25:56PM +0300

On Wed, May 16, 2001 at 08:25:56PM +0300, Jussi Laako wrote:

> I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand
> any load. It will deadlock (without oops) when the network/disk system faces
> any load.
> 
> There is also some new bug in VIA IDE driver. It misdetects cable as 80-w
> when it's only 40-w and causes some CRC errors and speed dropping. Some
> older kernels correctly detected the cable as 40-w and used UDMA33, this one
> tries to use UDMA100 and fails (of course). Is there any way to force cable
> detection to 40-w?

There were no changes lately in the VIA driver. Can you spot where the
problems begun?

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-05-16 20:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 17:25 VIA/PDC/Athlon Jussi Laako
2001-05-16 20:05 ` Vojtech Pavlik [this message]
2001-05-17 16:43   ` VIA/PDC/Athlon Jussi Laako
2001-05-17 16:44     ` VIA/PDC/Athlon Alan Cox
2001-05-17 20:28       ` VIA/PDC/Athlon Jussi Laako
2001-05-17 21:25         ` VIA/PDC/Athlon Alan Cox
2001-05-19 12:05           ` VIA/PDC/Athlon - IDE error theory Wilfried Weissmann
2001-05-19 12:17             ` Jussi Laako
2001-05-16 23:47 ` VIA/PDC/Athlon Alan Cox
2001-05-17  0:19 ` VIA/PDC/Athlon Zilvinas Valinskas
2001-05-17 16:46   ` VIA/PDC/Athlon Jussi Laako
  -- strict thread matches above, loose matches on Subject: below --
2001-05-18  3:52 VIA/PDC/Athlon Pavel Roskin
2001-05-18  6:33 ` VIA/PDC/Athlon Steffen Persvold
2001-05-18 12:15   ` VIA/PDC/Athlon Pavel Roskin

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=20010516220512.A1400@suse.cz \
    --to=vojtech@suse.cz \
    --cc=jlaako@pp.htv.fi \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.