lkml.org 
[lkml]   [2001]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: VIA chipset
On Mon, 15 Oct 2001, Mark Hahn wrote:

->> RAM: 256MB pc133
->
->that's a lot of ram for an old system like this. have you scrutinized
->the bios settings/jumpers? reasonably up-to-date bios installed?

RAM is cheap :). BIOS is the latest available from Tyan for this board.

->> HD: tested with WDC AC26400R, 6149MB w/512kB Cache
->> and with IBM-DTLA-305040, 41174 MB w/380KiB Cache
->> (tested with each separately and together)
->> IBM drive tested both before and after setting it to report as
->> a PIO mode 0 drive, using IBM's "Drive Feature Tool".
->
->pio is almost never a sane setting; certainly not for a dtla.

I moved the IBM drive to another system and experienced a lockup. A
search showed that some BIOS/chipsets locked when these drives reported
as UDMA 100 and a solution is to use the IBM "dft 2.30" to cause the
drive to report itself at some lower capability. This worked in the
other system so I tried the drive in the VIA chipset system again. It
still locks.

->mixing vendors on the same cable is asking for trouble;

Tested with both and with each.

->do you see problems with just one disk per channel?

Yes.

->> Other IDE: ATAPI 4x CDROM
->
->on its own channel, I presume?

Tested as slave, master on secondary, not connected.

->also, is the ide config valid? (ie, cables <= 18", both ends plugged in,
->preferably with 80-conductor cables?)

That's an interesting point. This thing does not like 80 conductor
cables at all. I first suspected a damaged motherboard instead of a
buggy chipset/BIOS. I went through all tests at
http://www-106.ibm.com/developerworks/linux/library/l-hw1/ and
http://www-106.ibm.com/developerworks/linux/library/l-hw2/ to check the
hardware. Continuous kernel compiles overnight caused no locks using
default Debian (stable) kernel. memtest86 ran its full test (over 10
hours) with no problems.

->> CONFIG_APM is not set
->> CONFIG_ACPI is not set
->
->but how about the corresponding bios settings?

APM is disabled in BIOS.

->> Is there a way to grab kernel messages or registers or something just before
->> a lockup occurs?
->
->sure, magic sys-rq, a kernel compile option.
->

D'oh! Thanks, I will try that.

Update: system locked overnight using 2.2.19 with ext3 while doing
apt-get dist-upgrade. Some directories were mounted via NFS, but it
locks under 2.4.x whether NFS is involved or not. Will go back to 2.2.19
with ext2 and see how long it can do disk work.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:08    [W:0.069 / U:1.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site