ISDN-Problem beim Neustart

From: Christian Lackas <lackas(at)sun52a.desy.de>
Date: Fri, 12 Oct 2001 13:26:14 +0200

Hallo zusammen,

ich habe ein Problem mit meiner ISDN-Anbindung. Wenn der Rechner aus ist
und ich ihn einschalte, dann bootet das System normal hoch, aber ich
kann keine ISDN-Verbindung herstellen. Es hilft auch nicht den isdnd neu
zu starten, isp0, ispppcontrol, etc. zu konfigurieren. Es klappt nicht.

Wenn ich dann aber mit "reboot" neu starte (ohne den Rechner
auszuschalten), dann klappt das ganze ohne Problem.

Hier die Logmeldungen des ersten Starts:
Oct 12 11:12:14 antares /kernel: i4btrc: 4 ISDN trace device(s) attached
Oct 12 11:12:14 antares /kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached (VJ header compression)
Oct 12 11:12:14 antares /kernel: i4b: ISDN call control device attached
Oct 12 11:12:14 antares /kernel: i4btel: 4 ISDN telephony interface device(s) attached
Oct 12 11:12:14 antares /kernel: i4brbch: 4 raw B channel access device(s) attached
Oct 12 11:12:14 antares /kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression)
Oct 12 11:12:17 antares /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_recover: HSCX B: ISTA = 0x0
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_recover: ISAC: ISTA = 0x0
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_recover: HSCX B: IMASK = 0xff
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_recover: HSCX A: IMASK = 0xf8
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_recover: ISAC: IMASK = 0x2a
Oct 12 11:12:17 antares /kernel: i4b-L2 i4b_T202_timeout: unit 0, N202 = 3
Oct 12 11:12:17 antares /kernel: i4b-L1 isic_ph_data_req: still in state F3!
Oct 12 11:12:19 antares /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 21
Oct 12 11:12:19 antares /kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout!
Oct 12 11:12:19 antares /kernel: i4b-L1 timer3_expired: state = F4 Awaiting Signal
Oct 12 11:12:19 antares /kernel: i4b-L1 isic_recover: HSCX B: ISTA = 0x0
Oct 12 11:12:19 antares /kernel: i4b-L1 isic_recover: ISAC: ISTA = 0x0
Oct 12 11:12:19 antares /kernel: i4b-L1 isic_recover: HSCX B: IMASK = 0xff
Oct 12 11:12:19 antares /kernel: i4b-L1 isic_recover: HSCX A: IMASK = 0xf8
Oct 12 11:12:19 antares /kernel: i4b-L1 isic_recover: ISAC: IMASK = 0x2a
Oct 12 11:17:08 antares reboot: rebooted by lackas
Oct 12 11:17:08 antares syslogd: exiting on signal 15

Nach dem Neustart geht es dann:
Oct 12 11:18:44 antares /kernel: isic0: <ELSA MicroLink ISDN/PCI> port 0xe000-0xe003,0xdc00-0xdc7f mem 0xea000000-0xea00007f irq 9 at device 11.0 on pci0
Oct 12 11:18:44 antares /kernel: isic0: passive stack unit 0
Oct 12 11:18:44 antares /kernel: i4bctl: ISDN system control port attached
Oct 12 11:18:44 antares /kernel: i4btrc: 4 ISDN trace device(s) attached
Oct 12 11:18:44 antares /kernel: i4bisppp: 4 ISDN SyncPPP device(s) attached (VJ header compression)
Oct 12 11:18:44 antares /kernel: i4b: ISDN call control device attached
Oct 12 11:18:44 antares /kernel: i4btel: 4 ISDN telephony interface device(s) attached
Oct 12 11:18:45 antares /kernel: i4brbch: 4 raw B channel access device(s) attached
Oct 12 11:18:45 antares /kernel: i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression)
Oct 12 11:18:45 antares /kernel: i4b: unit 0, assigned TEI = 80 = 0x50
Oct 12 11:18:46 antares /kernel: i4b-L4 i4b_l4_setup_timeout_fix_unit: 1002878326: ERROR: idletime[300]+earlyhup[5] > unitlength[60]!
Oct 12 11:18:46 antares isdnd[150]: DMN date/time from exchange = 0110121118

Hat jemand eine Idee woran das liegen koennte? Die Konfiguration scheint
ja zu stimmen, weil es beim zweiten Mal geht.

Gruss
 Christian Lackas

-- 
Heute kommt kein Spruch.
http://www.lackas.net/ Perl Delphi Linux MP3 Searchengines Domainchecker
To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Fri 12 Oct 2001 - 13:26:46 CEST

search this site