From alsa-user-owner@alsa.jcu.cz  Mon Nov  9 10:50:09 1998
Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id KAA05120
	for <alsa-user@jcu.cz>; Mon, 9 Nov 1998 10:48:45 +0100
Received: from oemcomputer (207-172-91-14.s14.as1.nyb.erols.com [207.172.91.14])
	by smtp3.erols.com (8.8.8/8.8.5) with SMTP id EAA02059
	for <alsa-user@jcu.cz>; Mon, 9 Nov 1998 04:48:40 -0500 (EST)
Message-ID: <3646A129.9FE@erols.com>
Date: Mon, 09 Nov 1998 03:00:41 -0500
From: Paul Winkler <zarmzarm@erols.com>
MIME-Version: 1.0
To: alsa-user@jcu.cz
Subject: Lockups: Yes, it's the mainboard!
References: <19981027120923.261.qmail@io.nu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

A while ago, we were discussing system lockups caused by full-duplex
recording, and the possibility that this might be caused by a problem
with the motherboard rather than with software.

I've just upgraded my version of OSS/Linux to 3.91h and the problem
seems to have completely gone away! (At least so far.)

According to 4front's tech support:
> Some PC chipsets such as VIA and Intel VX have somehow broken ISA DMA.
> We have made a simple fix to the next version which is reported
> to work with the VIA chipset [ and may work with the VX] ...
> This kind of problems are usually some kind of timing problems. Some
> chipsets just lock if certain operations are performed too quickly
> after each other.

Well, the fix seems to have worked on my system, which is based on Intel
VX.

I hope this information will be useful to ALSA developers! I wish I knew
more about the details of the problem...

regards,

PW



