ISDN4BSD broken...

Matthias Schuendehuette msch at snafu.de
Sun Sep 19 06:17:33 PDT 2004


Hello Nate,

On Tuesday 14 September 2004 00:36, Nate Lawson wrote:
> It's probably IRQ routing related.  Try changing the check in
> acpi_pci_link_is_valid_irq() to this:
>
> if (link->interrupts[i] == irq || AcpiGbl_FADT->SciInt == irq)

This didn't work, as I already mailed to you.

I compared the 'boot -v'-messages of the current BETA4-kernel with the 
messages of the last working 5.2-CURRENT kernel, and found that with the 
BETA4-kernel IRQ 10 *is* used for pcib0 and pcib1:

Sep 19 09:04:29 current kernel: agp0: <VIA 82C8363 (Apollo KT133A) host
 to PCI bridge> mem 0xd0000000-0xd7ffffff at device 0.0 on pci0
Sep 19 09:04:29 current kernel: agp0: Reserved 0x8000000 bytes for rid 
 0x10 type 3 at 0xd0000000
Sep 19 09:04:29 current kernel: agp0: allocating GATT for aperture of 
 size 256M
Sep 19 09:04:29 current kernel: pcib1: <PCI-PCI bridge> at device 1.0 on 
 pci0
Sep 19 09:04:29 current kernel: pcib1:   secondary bus     1
Sep 19 09:04:29 current kernel: pcib1:   subordinate bus   1
Sep 19 09:04:29 current kernel: pcib1:   I/O decode        0xf000-0xfff
Sep 19 09:04:29 current kernel: pcib1:   memory decode     
 0xe0000000-0xe1ffffff
Sep 19 09:04:29 current kernel: pcib1:   prefetched decode 
 0xd8000000-0xdfffffff
Sep 19 09:04:29 current kernel: pci1: <PCI bus> on pcib1
Sep 19 09:04:29 current kernel: pci1: physical bus=1
Sep 19 09:04:29 current kernel: map[10]: type 1, range 32, base 
 e0000000, size 24, enabled
Sep 19 09:04:29 current kernel: pcib1: device (null) requested decoded 
 memory range 0xe0000000-0xe0ffffff
Sep 19 09:04:29 current kernel: map[14]: type 3, range 32, base 
 d8000000, size 27, enabled
Sep 19 09:04:29 current kernel: pcib1: device (null) requested decoded 
 memory range 0xd8000000-0xdfffffff
Sep 19 09:04:29 current kernel: pcib0: matched entry for 0.1.INTA (src 
 \_SB_.PCI0.LNKA)
Sep 19 09:04:29 current kernel: pcib0: possible interrupts:  1  3  4  5  
 6  7 10 11 12 14 15
Sep 19 09:04:29 current kernel: ACPI PCI link arbitrated settings:
Sep 19 09:04:29 current kernel: \_SB_.PCI0.LNKA (references 8, priority 
 175018):
Sep 19 09:04:29 current kernel: interrupts:     10     5    11     7     
 6     4     3    12    15    14     1
Sep 19 09:04:29 current kernel: penalty:   1280  1330  2720  6280  6280  
 6280  6280  6360 51280 51280101280
Sep 19 09:04:29 current kernel: atpic: Programming IRQ10 as level/low
Sep 19 09:04:29 current kernel: pcib0: slot 1 INTA routed to irq 10 via 
 \_SB_.PCI0.LNKA
Sep 19 09:04:29 current kernel: pcib1: slot 0 INTA is routed to irq 10
Sep 19 09:04:29 current kernel: found-> vendor=0x10de, dev=0x0110, 
 revid=0xa1
Sep 19 09:04:29 current kernel: bus=1, slot=0, func=0
Sep 19 09:04:29 current kernel: class=03-00-00, hdrtype=0x00, mfdev=0
Sep 19 09:04:29 current kernel: cmdreg=0x0007, statreg=0x02b0, 
 cachelnsz=0 (dwords)
Sep 19 09:04:29 current kernel: lattimer=0x20 (960 ns), mingnt=0x05 
 (1250 ns), maxlat=0x01 (250 ns)
Sep 19 09:04:29 current kernel: intpin=a, irq=10
Sep 19 09:04:29 current kernel: powerspec 2  supports D0 D3  current D0
Sep 19 09:04:29 current kernel: pci1: <display, VGA> at device 0.0 (no 
 driver attached)
Sep 19 09:04:29 current kernel: isab0: <PCI-ISA bridge> at device 7.0 on 
 pci0
Sep 19 09:04:29 current kernel: isa0: <ISA bus> on isab0



I think that that should not happen - as far as I know, ISA-Devices 
should have their IRQ-Line exclusively, isn't it?

The IRQ 10 *is* marked in the BIOS for exclusive use for ISA and the 
device in question is:



Sep 19 09:04:29 current kernel: isic0: [GIANT-LOCKED]
Sep 19 09:04:29 current kernel: isic0 at port 
0x580-0x59f,0x180-0x19f,0x980-0x99f,0xd80-0xd9f irq 10 flags 0x3
 on isa0
Sep 19 09:04:29 current kernel: isic0: passive stack unit 0
Sep 19 09:04:29 current kernel: isic0: Teles S0/16.3
Sep 19 09:04:29 current kernel: isic0: ISAC 2085 Version A1/A2 or 
 2086/2186 Version 1.1 (IOM-2)
Sep 19 09:04:29 current kernel: isic0: HSCX 82525 or 21525 Version 2.1
[...]
Sep 19 09:04:29 current kernel: i4bctl: ISDN system control port 
 attached
Sep 19 09:04:29 current kernel: i4bisppp: 2 ISDN SyncPPP device(s) 
 attached
Sep 19 09:04:29 current kernel: isp0: bpf attached
Sep 19 09:04:29 current kernel: isp1: bpf attached
Sep 19 09:04:29 current kernel: i4b: ISDN call control device attached
Sep 19 09:04:29 current kernel: i4btrc: 1 ISDN trace device(s) attached
Sep 19 09:04:29 current kernel: i4brbch: 2 raw B channel access 
 device(s) attached
Sep 19 09:04:29 current kernel: i4btel: 2 ISDN telephony interface 
 device(s) attached
Sep 19 09:04:29 current kernel: i4bipr: 2 IP over raw HDLC ISDN 
 device(s) attached (VJ header compression)



I attach the whole bootlog in case there are some additional 
informations for you...

-- 
Ciao/BSD - Matthias

Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany)
PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040919/f41795ab/attachment.bin


More information about the freebsd-current mailing list