Message-ID: <3F0BA241.8020508@c-zone.net>
Date: Tue, 08 Jul 2003 22:04:01 -0700
From: jiho@c-zone.net
Organization: Kidding of Course
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?C=E9dric?= Barboiron <ced2ml@ifrance.com>
CC: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hdX lost interrupt problem
References: <3F0AE4DF.80808@ifrance.com> <3F0B6930.3080009@c-zone.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1129
Lines: 32


jiho@c-zone.net wrote:

 > I seem to recall one incident  while I was unrolling a tarball off a
 >  CD onto a hard drive, that  happened to involve a VIA chipset.

I don't have a record of it, but as I remember, when that happened I had 
APIC enabled in the BIOS.  After that, I switched to PIC.

In this machine's BIOS Setup BIOS FEATURES SETUP screen, there's the line:

   Interrupt Mode         : PIC

The other option is APIC.  Make sure it says PIC.

I think it was Alan Cox who pointed out that on single-processor systems 
you need to have PIC, and not APIC enabled.  And my kernel wasn't even 
built with APIC support ("# CONFIG_X86_UP_APIC is not set").

APIC is a newer interrupt controller type, PIC is the orginal 8259A 
type.  These chipsets can emulate either type in hardware.

I don't know if that's your problem, but you might check.


-- Jim Howard  <jiho@c-zone>

-
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/