From owner-freebsd-current Thu Apr 4 21:02:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA15686 for current-outgoing; Thu, 4 Apr 1996 21:02:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA15677 for ; Thu, 4 Apr 1996 21:02:12 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA18213; Fri, 5 Apr 1996 14:59:10 +1000 Date: Fri, 5 Apr 1996 14:59:10 +1000 From: Bruce Evans Message-Id: <199604050459.OAA18213@godzilla.zeta.org.au> To: bde@zeta.org.au, root@deadline.snafu.de Subject: Re: tty-level buffer overflows - what to do? Cc: current@FreeBSD.org, jgreco@brasil.moneng.mei.com, nate@sri.MT.net, rgrimes@GndRsh.aac.dev.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >] The cause has to be a signal on one of the IRQ lines enabled by FreeBSD >] (because masked lines are completely ignored). The signal can then interfere >] with the signal from the enabled board. >But what card could generate such IRQ? The problem seems to occur _only_ >during boot at about the time when fsck gets run and a second time a bit >later when some of the daemons get started. Any misdesigned, misconfigured or misprogrammed card might do it, so it's hard to say. >A vmstat -i says: >interrupt total rate >clk0 irq0 2039463 100 >rtc0 irq8 2610423 127 >wdc0 irq14 17877 0 >fdc0 irq6 1 0 >sc0 irq1 1 0 >sio0 irq4 1657 0 >sio1 irq3 283893 13 >sio2 irq9 1539814 75 >sio3 irq5 25268 1 >ed0 irq12 171733 8 >stray irq7 5032 0 >Total 6695162 328 >The rate for irq7 is 0, so I think it hasn't recently occured anymore since >bootup. I think you had 5032 irq7's :-). That's a lot for an unused device. I have 6 after running for about twice as long. Bruce