From owner-freebsd-hackers  Fri Oct 25 18:08:02 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA11236
          for hackers-outgoing; Fri, 25 Oct 1996 18:08:02 -0700 (PDT)
Received: from netrover.com (ottawa12.netrover.com [205.209.19.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA11206
          for <hackers@freebsd.org>; Fri, 25 Oct 1996 18:07:51 -0700 (PDT)
Resent-From: brianc@netrover.com
Received: (from brianc@localhost) by netrover.com (8.7.6/8.7.3) id VAA00798 for hackers@freebsd.org; Fri, 25 Oct 1996 21:06:07 -0400 (EDT)
Resent-Message-Id: <199610260106.VAA00798@netrover.com>
Message-Id: <199610260106.VAA00798@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
Resent-Date: Date: Fri, 25 Oct 1996 21:06:07 -0400
Resent-To: hackers@freebsd.org
Sender: owner-hackers@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?