Your message dated Tue, 23 Jan 2001 07:27:40 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#83154: Teles 16.3 in AXP noname
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Jan 2001 16:38:18 +0000
>From [EMAIL PROTECTED] Mon Jan 22 10:38:15 2001
Return-path: <[EMAIL PROTECTED]>
Received: from baghira.han.de [::ffff:212.63.63.2] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14Kjys-0005bm-00; Mon, 22 Jan 2001 10:38:11 -0600
Received: from kalahari.UUCP (uucp@localhost)
        by baghira.han.de (8.9.3/8.9.3) with UUCP id RAA30499
        for bugs.debian.org!submit; Mon, 22 Jan 2001 17:33:24 +0100
Received: by kalahari
        id m14KNJX-0001zUC
        (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 21 Jan 2001 17:25:59 +0100 (CET)
Message-Id: <m14KNJX-0001zUC@kalahari>
Date: Sun, 21 Jan 2001 17:25:59 +0100 (CET)
To: [EMAIL PROTECTED]
Subject: Teles 16.3 in AXP noname
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
From: [EMAIL PROTECTED] (Andreas Buschmann)
Delivered-To: [EMAIL PROTECTED]


Package: kernel? modconf?
Version: 2.2.17  0.2.26.14?
Architecture: alpha


When trying to add a Teles 16.3 ISDN card to my Alpha noname, modconf
hangs my computer after entering the configuration.

The ISA configuration from the SRM console:

>>>isacfg -slot 3 -dev 0

=============================================================
handle: Teles-16.3
etyp: 1
slot: 3
dev: 0
enadev: 1
totdev: 1
iobase0: 180   iobase1: 8000000000000000
iobase2: 8000000000000000   iobase3: 8000000000000000
iobase4: 8000000000000000   iobase5: 8000000000000000
membase0: 8000000000000000   memlen0: 8000000000000000
membase1: 8000000000000000   memlen1: 8000000000000000
membase2: 8000000000000000   memlen2: 8000000000000000
rombase: 8000000000000000   romlen:   8000000000000000
dma0: 80000000          irq0: a
dma1: 80000000          irq1: 80000000
dma2: 80000000          irq2: 80000000
dma3: 80000000          irq3: 80000000
=============================================================

The actual hangup:

root@atacama> modconf

...

mtype=3 io=0x180 irq=10 protocol=2 id=isdn0

...

Installing module hisax. If the device isn't there, or isn't configured correctly, 
this could cause your system to pause for up to a minute.

ISDN subsystem Rev: 1.100/1.84/1.114/1.63/none/1.4 loaded
Teles 16.3: IRQ(10) getting no interrupts during init 1

And now the computer hangs, and needs a reset.



I have found, that this hangup resulted from an interrupt conflict
between the Teles ISA card on irq 10, and the PCI VGA card which also
takes irq 10. It can be resolved by removing one of the two cards or
finding an interrupt of the set (5, 9, 10, 12, 15), which can be
reassigned to the Teles card.

The irq of the VGA card does not show up in /proc/interrupts:
root@atacama> cat /proc/interrupts 
  1:          0    keyboard
  4:       2033   +serial
  5:          8   +serial
  8:    2581088    timer
 11:       8279    ncr53c8xx
 15:      11052    DE200 (eth0)
but in /proc/pci 
root@atacama> cat /proc/pci 
PCI devices found:
  Bus  0, device   6, function  0:
    Non-VGA device: NCR 53c810 (rev 1).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=255.  
      I/O at 0x8000 [0x8001].
      Non-prefetchable 32 bit memory at 0x4200000 [0x4200000].
  Bus  0, device   7, function  0:
    Non-VGA device: Intel 82378IB (rev 3).
      Medium devsel.  Master Capable.  No bursts.  
  Bus  0, device   8, function  0:
    VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 84).
      Medium devsel.  IRQ 10.  
      Non-prefetchable 32 bit memory at 0x14000000 [0x14000000].


This seems like a bug in the design of the PC hardware.

It might be possible test for this sort of conflict.
If it is not possible a warning should be added to the documentation
of the ISDN cards to watch out for interrupt conflicts.


Anyway, it seems very difficult to add an ISA ISDN card to a PCI + ISA
PC like motherboard as there are usually no free interrupts:

IRQ:    Device:
  0     reserved
  1     keyboard
  2     same as IRQ 9
  3     COM2
  4     COM1
  5     COM3    or other, sometimes available
  6     floppy
  7     LPT1              sometimes reasignable
  8     timer
  9     COM4    or other, sometimes available
 10     VGA               often not assignable
 11     SCSI (NCR or Adaptec)
 12     mouse             often not assignable, was free in old ISA PCs
 13     math error
 14     IDE hd
 15     IDE hd or ethernet



                                        Tschuess
                                                Andreas

---------------------------------------
Received: (at 83154-done) by bugs.debian.org; 22 Jan 2001 20:27:53 +0000
>From [EMAIL PROTECTED] Mon Jan 22 14:27:53 2001
Return-path: <[EMAIL PROTECTED]>
Received: from gondor.apana.org.au [::ffff:203.14.152.114] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 14KnZ8-0003Tc-00; Mon, 22 Jan 2001 14:27:52 -0600
Received: (from herbert@localhost)
        by gondor.apana.org.au (8.11.1/8.11.1/Debian 8.11.0-6) id f0MKReB24563
        for [EMAIL PROTECTED]; Tue, 23 Jan 2001 07:27:40 +1100
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Tue, 23 Jan 2001 07:27:40 +1100
To: [EMAIL PROTECTED]
Subject: Re: Bug#83154: Teles 16.3 in AXP noname
Message-ID: <[EMAIL PROTECTED]>
References: <m14KNJX-0001zUC@kalahari>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <m14KNJX-0001zUC@kalahari>; from [EMAIL PROTECTED] on Sun, Jan 21, 
2001 at 05:25:59PM +0100
Delivered-To: [EMAIL PROTECTED]

On Sun, Jan 21, 2001 at 05:25:59PM +0100, Andreas Buschmann wrote:
> 
> It might be possible test for this sort of conflict.

That is best done in user space.

> If it is not possible a warning should be added to the documentation
> of the ISDN cards to watch out for interrupt conflicts.

modconf should already warn you about the possibility of a system hang
when installing a module.
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to