public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Nick Koston" <nick@burst.net>
To: John Cavan <johnc@damncats.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Asus CUV4X-DLS
Date: Wed, 27 Jun 2001 23:35:41 -0400	[thread overview]
Message-ID: <20010627233541.A32271@burst.net> (raw)
In-Reply-To: <20010627215304.D28795@burst.net> <3B3AA1DE.E4419FA8@damncats.org>
In-Reply-To: <3B3AA1DE.E4419FA8@damncats.org>; from johnc@damncats.org on Wed, Jun 27, 2001 at 11:17:50PM -0400

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

Thanks for the tips, however it doesn't help :-(

Anyways in case anyone is curious the i/o problem still happens
with an aic7xxx card put in and the onboard scsi disabled.

[snip] 
> "J. Nick Koston" wrote:
> > 
> > There seems to be a major problem with this board and 2.4.x kernels.
> > I consistantly get SCSI Input/Output errors on multiple drives that I
> > know are good when running a SMP kernel.  These errors do no happen
> > with a UP kernel.  This is happening on multiple systems and with
> > multiple know good scsi drives of all speeds and sizes.
> 
> Make sure you have the latest BIOS upgrade and set the MPS revision in
> the BIOS to 1.1 rather than 1.4. This cured a similar issue for me and
> USB on the CUV4X-D motherboard, but as your board is different, your
> mileage may vary.

Already set at 1.1
> 
> Also, try passing "noapic" to the kernel on boot if the problem still
> persists. The downside is that all interrupts will be handled by a
> single CPU. There is a definite problem with VIA chipsets.
> 
Tried this as well (mentioned in my original email)

> John

-- 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-06-28  3:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28  1:53 Asus CUV4X-DLS J. Nick Koston
     [not found] ` <3B3AA1DE.E4419FA8@damncats.org>
2001-06-28  3:35   ` J. Nick Koston [this message]
2001-06-28 12:14     ` John Cavan
2001-06-28 12:27       ` John Cavan
2001-06-28 19:32         ` J. Nick Koston
2001-07-02  6:14 ` Asus CUV4X-DLS apic fun (pre8/ac22) Justin Guyett
     [not found] <mail.linux.kernel/20010627233541.A32271@burst.net>
     [not found] ` <01Jun28.041132edt.62285@gpu.utcc.utoronto.ca>
2001-07-01  6:47   ` Asus CUV4X-DLS J. Nick Koston

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=20010627233541.A32271@burst.net \
    --to=nick@burst.net \
    --cc=johnc@damncats.org \
    --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