Date: Wed, 28 Jul 1999 23:30:39 +0300 From: =?koi8-r?Q?=E1=CE=C4=D2=C5=CA=20=F7=2E=20=EF=CC=C5=CA=CE=C9=CB?= (Andy V. Oleynik) <andyo@prime.net.ua> To: freebsd-questions@FreeBSD.ORG Subject: Re: too many stray irq 7's; not logging any more. Solved Message-ID: <379F686D.BEA781F2@prime.net.ua> References: <379E080F.A79443A3@prime.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Yet another half of day and question is "yes, local port is dead as well as remote".But I'm still interesting about stray irq 7 and interrupt-level overflow. Though the latter is selfexplainig and one look in the source confirms guess, first is not obviouse. Anyway link is up now, errors in config file (0x0a01 flags to 0x0981) fixed. Thanks to all, war is finished, all can go back to home :) "Андрей В. Олейник (Andy V. Oleynik)" wrote: > Hi, guys, > yesterday I've got my multiport card down. > The msg was: > Jul 26 18:59:15 host1 /kernel: sio5: 944 more interrupt-level buffer > overflows (total 944) > Jul 26 18:59:15 host1 /kernel: sio6: 1 more silo overflow (total 30) > Jul 26 18:59:16 host1 /kernel: sio5: 1750 more silo overflows (total > 1799) > Jul 26 18:59:17 host1 /kernel: sio5: 242 more silo overflows (total > 2041) > Jul 26 18:59:17 host1 /kernel: sio9: 64 events for device with no tp > ------------------------------------------------------------------------- > > Jul 26 18:59:17 host1 /kernel: stray irq 7 > ----------------------------------------------- > Jul 26 18:59:17 host1 last message repeated 4 times > Jul 26 18:59:17 host1 /kernel: too many stray irq 7's; not logging any > more > -------------------------------------------------------------------------------- > > Jul 26 18:59:18 host1 /kernel: sio9: 64 events for device with no tp > Jul 26 18:59:18 host1 /kernel: sio9: 64 events for device with no tp > Jul 26 18:59:18 host1 /kernel: sio5: 307 more silo overflows (total > 2348) > Jul 26 18:59:18 host1 /kernel: sio5: 8 more interrupt-level buffer > overflows (total 952) > --------------------------------------------------------------------------------------------- > > Jul 26 18:59:18 host1 /kernel: sio6: 1 more silo overflow (total 31) > Jul 26 18:59:19 host1 /kernel: sio5: 587 more silo overflows (total > 2935) > Jul 26 18:59:19 host1 /kernel: sio5: 2286 more interrupt-level buffer > overflows (total 3238) > ------------------------------------------------------------------------------------------------- > > Jul 26 18:59:20 host1 /kernel: sio5: 79 more silo overflows (total 3014) > > Jul 26 18:59:20 host1 /kernel: sio5: 7438 more interrupt-level buffer > overflows (total 10676) > What do the understiked lines mean? It seems to be the problems with > interrupts controller? > sio9 is master port for 8ports card. > restarting services didnt help. > rebooted. > Jul 27 12:12:58 host1 /kernel: FreeBSD 2.2.5-RELEASE #0: Thu Jan 21 > 18:11:04 GMT 1999 > Jul 27 12:12:58 host1 /kernel: > root@mogos-link.prime.net.ua:/usr/src/sys/compile/FIREWALL > Jul 27 12:12:58 host1 /kernel: CPU: i486DX (486-class CPU) > Jul 27 12:12:59 host1 /kernel: real memory = 33554432 (32768K bytes) > Jul 27 12:12:59 host1 /kernel: avail memory = 30801920 (30080K bytes) > Jul 27 12:12:59 host1 /kernel: Probing for devices on PCI bus 0: > Jul 27 12:12:59 host1 /kernel: chip0 <SiS 85c496> rev 49 on pci0:5 > Jul 27 12:12:59 host1 /kernel: Probing for devices on the ISA bus: > Jul 27 12:12:59 host1 /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Jul 27 12:12:59 host1 /kernel: sc0: VGA color <16 virtual consoles, > flags=0x0> > Jul 27 12:12:59 host1 /kernel: ed0 at 0x220-0x23f irq 5 on isa > Jul 27 12:12:59 host1 /kernel: ed0: address 00:80:48:e5:4b:61, type > NE2000 (16 bit) > Jul 27 12:12:59 host1 /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > Jul 27 12:12:59 host1 /kernel: sio0: type 16550A > Jul 27 12:12:59 host1 /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Jul 27 12:12:59 host1 /kernel: sio1: type 16550A > Jul 27 12:12:59 host1 /kernel: sio2 at 0x300-0x307 flags 0xa01 on isa > Jul 27 12:12:59 host1 /kernel: sio2: type 16550A > Jul 27 12:12:59 host1 /kernel: sio3 at 0x308-0x30f flags 0xa01 on isa > Jul 27 12:12:59 host1 /kernel: sio3: type 16550A > Jul 27 12:12:59 host1 /kernel: sio4 at 0x310-0x317 flags 0xa01 on isa > Jul 27 12:12:59 host1 /kernel: sio4: type 16550A > Jul 27 12:13:00 host1 /kernel: sio5 at 0x318-0x31f flags 0xa01 on isa > Jul 27 12:13:00 host1 /kernel: sio5: type 16550A > Jul 27 12:13:00 host1 /kernel: sio6 at 0x320-0x327 flags 0xa01 on isa > Jul 27 12:13:00 host1 /kernel: sio6: type 16550A > Jul 27 12:13:00 host1 /kernel: sio7 at 0x328-0x32f flags 0xa01 on isa > Jul 27 12:13:00 host1 /kernel: sio7: type 16550A > Jul 27 12:13:00 host1 /kernel: sio8 at 0x330-0x337 flags 0xa01 on isa > Jul 27 12:13:00 host1 /kernel: sio8: type 16550A > Jul 27 12:13:00 host1 /kernel: sio9 at 0x338-0x33f irq 10 flags 0xa01 on > isa > Jul 27 12:13:00 host1 /kernel: sio9: type 16550A > Jul 27 12:13:00 host1 /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > Jul 27 12:13:00 host1 /kernel: fd0: 1.44MB 3.5in > Jul 27 12:13:00 host1 /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa > Jul 27 12:13:00 host1 /kernel: wdc0: unit 0 (wd0): <QUANTUM > FIREBALL_TM1080A> > Jul 27 12:13:00 host1 /kernel: wd0: 1039MB (2128896 sectors), 2112 cyls, > 16 heads, 63 S/T, 512 B/S > Jul 27 12:13:00 host1 /kernel: npx0 flags 0x1 on motherboard > Jul 27 12:13:00 host1 /kernel: npx0: INT 16 interface > > As U can see kernel has got all the ports up. > Thought cu can connect to sio5 latter doesnt accept neither input nor > does output. > This line provides leased port2port connection to another host. And it > worked fine before > the trouble with card. Now it doesnt. > The log is filled with msgs: > > Jul 27 18:31:04 host1 getty[1740]: modem answer problem on /dev/ttyd7 > Jul 27 18:31:17 host1 getty[1772]: modem answer problem on /dev/ttyd7 > Jul 27 18:58:25 host1 getty[1773]: modem answer problem on /dev/ttyd7 > Jul 27 20:08:40 host1 getty[1790]: modem answer problem on /dev/ttyd7 > Jul 27 20:09:06 host1 getty[1874]: modem answer problem on /dev/ttyd7 > > pppd that should be started from script bound to pp field in gettytab > doesnt start too. /etc/ttys and /etc/gettytab looks fine. Futhermore > on the same card on the another ports the same service perfectly starts > to another host2 (with another IP of course). My question is should be > the > ports on the both ends of link considered as dead? Unfortunatly the > other > end of link is not under my control. But I've connected the wire to > any of functional ports (having /etc/ttys and script changed accordingly > > of course). Without any success to start ppp. Wire is functional (I > spent > half of the day to be sure of it). Any ideas? > > -- > Andy V. Oleynik > (When U aim for perfection, > U discover it's a moving target Ж80) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Andy V. Oleynik (When U aim for perfection, U discover it's a moving target Ж80) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?379F686D.BEA781F2>