Date: Sat, 21 Aug 2004 19:27:36 +0200 From: Matthias Schuendehuette <msch@snafu.de> To: current@freebsd.org Subject: Re: ISDN4BSD broken... Message-ID: <200408211927.36948.msch@snafu.de> In-Reply-To: <200408141854.38477.msch@snafu.de> References: <200408141854.38477.msch@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <msch [at] snafu.de>, Berlin (Germany) PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408211927.36948.msch>