From owner-freebsd-stable Wed Jan 6 00:31:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06663 for freebsd-stable-outgoing; Wed, 6 Jan 1999 00:31:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from wattres.Watt.COM (wattres.Watt.COM [207.33.154.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06657 for ; Wed, 6 Jan 1999 00:31:57 -0800 (PST) (envelope-from steve@Watt.COM) Received: (from steve@localhost) by wattres.Watt.COM (8.8.8/8.8.8) id AAA02383 for freebsd-stable@freebsd.org; Wed, 6 Jan 1999 00:31:22 -0800 (PST) (envelope-from steve) Date: Wed, 6 Jan 1999 00:31:22 -0800 From: Steve Watt To: freebsd-stable@FreeBSD.ORG Subject: IRQ entropy causes panics? Message-ID: <19990106003122.A1906@wattres.Watt.COM> Reply-To: Steve Watt Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i X-Callsign: KD6GGD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just finished setting up my 2.2.8-STABLE box, and I just noticed an "interesting" bug. If one configures the rand_irq in rc.conf to be a reasonable-seeming set (the PCI bus 0 irq and some serial ports that only get used for UUCP), the system seems to become quite unstable, and panics fairly regularly (every few hours, but quite variable) with a stack trace very similar to: _generic_bcopy + 0x1a _comstart + 0xa6 _ttstart + 0x18 _siopoll + 0x175 splz_swi + 0x14 _add_timer_randomness + 0x1c2 _add_interrupt_randomness + 0x2d _Xfastintr3 + 0x17 I've returned the rand_irq setting to NO, and the problem seems to have gone away. Is this known, or should I do a little more characterization? It feels like a race between the timer update and another (say, serial) update of the pool doesn't play right, but I haven't even looked at the code yet. Please Cc: me directly on replies - I can barely keep up. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message