From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 08:46:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3984916A4CE; Sun, 12 Sep 2004 08:46:13 +0000 (GMT) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2E3D43D5A; Sun, 12 Sep 2004 08:46:12 +0000 (GMT) (envelope-from msch@snafu.de) Received: from dial-76-045.de.inter.net ([213.73.76.45] helo=current.best-eng.de) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1C6Pzt-0000Wt-00; Sun, 12 Sep 2004 10:46:10 +0200 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.13.1/8.13.1) with ESMTP id i8C8k8qi054688; Sun, 12 Sep 2004 10:46:09 +0200 (CEST) (envelope-from matthias@current.best-eng.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.13.1/8.13.1/Submit) id i8C8k31V054450; Sun, 12 Sep 2004 10:46:03 +0200 (CEST) (envelope-from matthias) From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-current@freebsd.org Date: Sun, 12 Sep 2004 10:46:02 +0200 User-Agent: KMail/1.6.2 References: <200408141854.38477.msch@snafu.de> <200408211927.36948.msch@snafu.de> In-Reply-To: <200408211927.36948.msch@snafu.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200409121046.02724.msch@snafu.de> X-Mailman-Approved-At: Sun, 12 Sep 2004 14:21:58 +0000 cc: njl@freebsd.org cc: andre@freebsd.org Subject: Re: ISDN4BSD broken... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2004 08:46:13 -0000 Hello all, there's still no change - ISDN4BSD still does not work with my TELES S0 16.3 ISA-Card (no PnP). I tried with 6-CURRENT from Sep 10, which has the new commits for ISDN4BSD from andre@freebsd.org, but this did not change anything. (thanks for the hint, Gary!) The last working Version is from Aug 11, 14:00 UTC - at 16:00 UTC it's broken. The kernel files which changed in between are: src/sys/dev/acpica/acpi_pci_link.c (-> 1.19) src/sys/dev/acpica/acpi_pcib.c (-> 1.47) src/sys/dev/acpica/acpi_pcib_acpi.c (-> 1.39) src/sys/dev/acpica/acpi_pcib_pci.c (-> 1.10) src/sys/dev/acpica/acpi_pcibvar.h (-> 1.3) That's all I can do for now - if additional informations are required, please contact me and tell me how to retrieve them... Ciao/BSD - Matthias On Saturday 21 August 2004 19:27, Matthias Schuendehuette wrote: > Hi, > > there's still no change with 5.3-BETA1 :-( > > On Saturday 14 August 2004 18:54, Matthias Schuendehuette wrote: > > Hi all, > > > > I just rebooted into the new cuurent-kernel and found, that i4b > > isn't working any more. Last working kernel was of Aug 11, around > > 1800 UTC. > > > > Aug 14 18:19:46 current kernel: FreeBSD 5.2-CURRENT #0: \ > > Sat Aug 14 17:43:56 CEST 2004 > > [...] > > Aug 14 18:19:46 current kernel: ACPI link \_SB_.PCI0.LNKA \ > > has invalid initial irq 9, ignoring > > (this is a new message, which doesn't show up with my Aug 11 > > kernel) [...] > > Aug 14 18:19:46 current kernel: isic0: [GIANT-LOCKED] > > Aug 14 18:19:46 current kernel: isic0 at port \ > > 0x580-0x59f,0x180-0x19f,0x980-0x99f,0xd80-0xd9f \ > > irq 10 flags 0x3 on isa0 > > Aug 14 18:19:46 current kernel: isic0: passive stack unit 0 > > Aug 14 18:19:46 current kernel: isic0: Teles S0/16.3 > > [...] > > Aug 14 18:19:46 current kernel: i4bisppp: \ > > 2 ISDN SyncPPP device(s) attached > > Aug 14 18:19:46 current kernel: i4b: \ > > ISDN call control device attached > > Aug 14 18:19:46 current kernel: i4btrc: \ > > 1 ISDN trace device(s) attached > > Aug 14 18:19:46 current kernel: i4brbch: \ > > 2 raw B channel access device(s) attached > > Aug 14 18:19:46 current kernel: i4btel: \ > > 2 ISDN telephony interface device(s) attached > > Aug 14 18:19:46 current kernel: i4bipr: \ > > 2 IP over raw HDLC ISDN device(s) attached (VJ header compression) > > Aug 14 18:19:46 current kernel: i4bctl: \ > > ISDN system control port attached > > > > So far, the ISDN-Card is detected and attached as usual, but if I > > try to dial out, the following messages were recorded: > > > > Aug 14 18:22:25 current kernel: i4b-L1 timer3_expired: \ > > state = F4 Awaiting Signal > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > HSCX B: ISTA = 0x0 > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > ISAC: ISTA = 0x94 > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > ISAC: CISQ = 0x1e > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > HSCX B: IMASK = 0xff > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > HSCX A: IMASK = 0xf8 > > Aug 14 18:22:25 current kernel: i4b-L1 isic_recover: \ > > ISAC: IMASK = 0x2a > > Aug 14 18:22:25 current kernel: i4b-L2 i4b_T202_timeout: \ > > unit 0, N202 = 3 > > Aug 14 18:22:25 current kernel: i4b-L1 isic_ph_data_req: \ > > still in state F3! > > Aug 14 18:22:27 current kernel: i4b-L3 T303_timeout: \ > > SETUP not answered, cr = 15 > > Aug 14 18:22:27 current kernel: i4b-L3 next_l3state: \ > > FSM illegal state, state = ST_OW - Out Wait EST, \ > > event = EV_T303EXP - T303 timeout! > > Aug 14 18:22:27 current kernel: i4b-L1 timer3_expired: \ > > state = F4 Awaiting Signal > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > HSCX B: ISTA = 0x0 > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > ISAC: ISTA = 0x4 > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > ISAC: CISQ = 0x32 > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > HSCX B: IMASK = 0xff > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > HSCX A: IMASK = 0xf8 > > Aug 14 18:22:27 current kernel: i4b-L1 isic_recover: \ > > ISAC: IMASK = 0x2a > > > > Any ideas? ACPI or IRQ-Routing related? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F