From owner-freebsd-multimedia Tue Oct 22 21:47:51 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05676 for multimedia-outgoing; Tue, 22 Oct 1996 21:47:51 -0700 (PDT) Received: from netrover.com (ottawa16.netrover.com [205.209.19.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA05641 for ; Tue, 22 Oct 1996 21:47:41 -0700 (PDT) Received: (from brianc@localhost) by netrover.com (8.7.6/8.7.3) id AAA00669; Wed, 23 Oct 1996 00:46:07 -0400 (EDT) Message-Id: <199610230446.AAA00669@netrover.com> Date: Wed, 23 Oct 1996 00:46:07 -0400 From: brianc@pobox.com (Brian Campbell) To: freebsd-multimedia@FreeBSD.org Subject: MPU-401: Interrupt #0? X-Mailer: Mutt 0.48.1 Mime-Version: 1.0 Reply-to: brianc@pobox.com Sender: owner-multimedia@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Since the 10/14 snap I get about three 'mpu-401: Interrupt #0?' messages everytime the mpu device is opened or reset. This didn't used to happen. Did some kernel change happen that affects the mpu401 driver that hasn't yet been accounted for?