Date: Sun, 19 Sep 2004 15:17:00 +0200 From: Matthias Schuendehuette <msch@snafu.de> To: Nate Lawson <nate@root.org> Cc: freebsd-current@freebsd.org Subject: Re: ISDN4BSD broken... Message-ID: <200409191517.20614.msch@snafu.de> In-Reply-To: <414620DB.9070509@root.org> References: <200408141854.38477.msch@snafu.de> <200409121046.02724.msch@snafu.de> <414620DB.9070509@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1579428.Bb0vhrAxB4 Content-Type: multipart/mixed; boundary="Boundary-01=_NbYTBPAM39DiTxn" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_NbYTBPAM39DiTxn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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] =3D=3D irq || AcpiGbl_FADT->SciInt =3D=3D irq) This didn't work, as I already mailed to you. I compared the 'boot -v'-messages of the current BETA4-kernel with the=20 messages of the last working 5.2-CURRENT kernel, and found that with the=20 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=20 0x10 type 3 at 0xd0000000 Sep 19 09:04:29 current kernel: agp0: allocating GATT for aperture of=20 size 256M Sep 19 09:04:29 current kernel: pcib1: <PCI-PCI bridge> at device 1.0 on=20 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 =20 0xe0000000-0xe1ffffff Sep 19 09:04:29 current kernel: pcib1: prefetched decode=20 0xd8000000-0xdfffffff Sep 19 09:04:29 current kernel: pci1: <PCI bus> on pcib1 Sep 19 09:04:29 current kernel: pci1: physical bus=3D1 Sep 19 09:04:29 current kernel: map[10]: type 1, range 32, base=20 e0000000, size 24, enabled Sep 19 09:04:29 current kernel: pcib1: device (null) requested decoded=20 memory range 0xe0000000-0xe0ffffff Sep 19 09:04:29 current kernel: map[14]: type 3, range 32, base=20 d8000000, size 27, enabled Sep 19 09:04:29 current kernel: pcib1: device (null) requested decoded=20 memory range 0xd8000000-0xdfffffff Sep 19 09:04:29 current kernel: pcib0: matched entry for 0.1.INTA (src=20 \_SB_.PCI0.LNKA) Sep 19 09:04:29 current kernel: pcib0: possible interrupts: 1 3 4 5 =20 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=20 175018): Sep 19 09:04:29 current kernel: interrupts: 10 5 11 7 =20 6 4 3 12 15 14 1 Sep 19 09:04:29 current kernel: penalty: 1280 1330 2720 6280 6280 =20 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=20 \_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=3D0x10de, dev=3D0x0110,=20 revid=3D0xa1 Sep 19 09:04:29 current kernel: bus=3D1, slot=3D0, func=3D0 Sep 19 09:04:29 current kernel: class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 Sep 19 09:04:29 current kernel: cmdreg=3D0x0007, statreg=3D0x02b0,=20 cachelnsz=3D0 (dwords) Sep 19 09:04:29 current kernel: lattimer=3D0x20 (960 ns), mingnt=3D0x05=20 (1250 ns), maxlat=3D0x01 (250 ns) Sep 19 09:04:29 current kernel: intpin=3Da, irq=3D10 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=20 driver attached) Sep 19 09:04:29 current kernel: isab0: <PCI-ISA bridge> at device 7.0 on=20 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=20 should have their IRQ-Line exclusively, isn't it? The IRQ 10 *is* marked in the BIOS for exclusive use for ISA and the=20 device in question is: Sep 19 09:04:29 current kernel: isic0: [GIANT-LOCKED] Sep 19 09:04:29 current kernel: isic0 at port=20 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=20 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=20 attached Sep 19 09:04:29 current kernel: i4bisppp: 2 ISDN SyncPPP device(s)=20 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=20 device(s) attached Sep 19 09:04:29 current kernel: i4btel: 2 ISDN telephony interface=20 device(s) attached Sep 19 09:04:29 current kernel: i4bipr: 2 IP over raw HDLC ISDN=20 device(s) attached (VJ header compression) I attach the whole bootlog in case there are some additional=20 informations for you... =2D-=20 Ciao/BSD - Matthias Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany) PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F --Boundary-01=_NbYTBPAM39DiTxn-- --nextPart1579428.Bb0vhrAxB4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBTYbgf1BNcN37Cl8RAr3EAJ9yFMqFkKuuir7zoXIVHIxsMpHGEACcCkgu LVfH6PkzK31j1cSvvW4l4S8= =AkNr -----END PGP SIGNATURE----- --nextPart1579428.Bb0vhrAxB4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409191517.20614.msch>