NetBSD Problem Report #4464

Received: (qmail 12190 invoked from network); 10 Nov 1997 23:29:03 -0000
Message-Id: <>
Date: Mon, 10 Nov 1997 18:28:05 -0500 (EST)
From: "Eric S. Hvozda" <>
Subject: disable selection of irq 9 for pcmcia subsystem?
X-Send-Pr-Version: 3.95

>Number:         4464
>Category:       kern
>Synopsis:       irq 9 causes problems on the Sager NP7500A
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 10 15:35:04 +0000 1997
>Last-Modified:  Sun Oct 26 21:33:37 +0000 2008
>Originator:     Eric S. Hvozda
>Release:        1.3_ALPHA


System: NetBSD 1.3_ALPHA NetBSD 1.3_ALPHA (HELIOS) #4: Mon Nov 10 17:46:11 EST 1997 root@:/usr/src/sys/arch/i386/compile/HELIOS i386


	On Sager NP7500A and look alikes (this particular notebook
	is marketed under various names by VARs), irq 9 causes problems
	if the pcmcia subsystem attempts to use it.

	These problems range anywhere to configured, but unusable
	devices (with a D-Link DE-650 ethernet card and a
	Megahertz V.34 modem) to drivers hanging (with an Adaptec
	SlimSCSI card).  In all cases one can get to DDB and cleanly
	reboot however.
	Try to use the pcmcia subsystem on a Sager NP7500A or lookalike
	and observe odd behavior and note that the subsystem is
	attempting to use irq 9 from the messages on the console.  

	If the system isn't using irq 9 (perhaps you don't have a 
	builtin sound blaster consuming irq 7, or only one pcmcia
	card) use PCIC_ISA_INTR_ALLOC_MASK appropriately in a
	kernel config file to force use of irq 9.

	Perhaps the best idea is to disable selection of irq 9
	in the pcmcia subsystem.  This could be done by altering the
	default value of PCIC_ISA_INTR_ALLOC_MASK in
	/sys/dev/isa/i82365_isa.c.  Currently it is set to 0xfbff, but
	a setting of 0xf9ff will disable both irq 9 and 10 (interestingly
	irq 10 is safe to use on the Sager NP7500A unlike the NEC
	Versa series).

	It's a toss up from my POV; if it's clearly documented how
	to change the behavior, perhaps we don't care.  However it could
	be a show stopper for installs.  Also it can also have the
	appearance that NetBSD doesn't support the Sager if someone
	is unlikely enough to have the pcmcia subsystem try to use irq 9.

	At any rate, the diabling of this irq isn't an issue on the
	Sager since 11 and 15 are still left for selection.

From: "Chris G. Demetriou" <>
Subject: Re: kern/4464: disable selection of irq 9 for pcmcia subsystem? 
Date: Tue, 11 Nov 97 08:42:23 -0800

 > 	At any rate, the diabling of this irq isn't an issue on the
 > 	Sager since 11 and 15 are still left for selection.

 Of course, by the nature of PC hardware, at least one of will
 undoubtedly cause problems for anothre notebook, and the other for
 another...  8-)

 "There's gotta be a better way to do this."  Isn't there some way to
 query the BIOS, or something?

 Data point: on my ThinkPad 760EL, IRQ 7 seems to be used for my PCMCIA
 modem (gee, looking at things, i guess i don't have my parallel port
 configured), and IRQ 9 seems to be used for my PCMCIA ethernet.  At
 home I've got a docking station with a (built-in) PCI SCSI adapter, a
 PCI slot, and two more PCMCIA slots (that I don't know the IRQ #s for
 off-hand 8-).

State-Changed-From-To: open->feedback
State-Changed-When: Tue, 13 May 2008 13:21:28 +0000
Is this still a problem?

State-Changed-From-To: feedback->open
State-Changed-When: Sun, 26 Oct 2008 21:33:37 +0000
Feedback timeout. Anyone else still have this hardware?


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.