From owner-freebsd-current Thu Sep 6 9: 2:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 8BF7C37B401 for ; Thu, 6 Sep 2001 09:02:27 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id f86G1um88789; Fri, 7 Sep 2001 01:01:58 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Fri, 07 Sep 2001 01:01:47 +0900 (JST) Message-Id: <20010907.010147.104026307.iwasaki@jp.FreeBSD.org> To: acpi-jp@jp.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: current@freebsd.org Subject: Re: [acpi-jp 1246] ACPI and PS/2 mouse problem From: Mitsuru IWASAKI In-Reply-To: <200109061151.UAA20428@zodiac.mech.utsunomiya-u.ac.jp> References: <200109061151.UAA20428@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks Yokota-san for tracking down the problem. > As reported in this list by several people, you may be seeing that > your PS/2 mouse is not detected after the recent ACPI update. > > This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse > interrupt) to both the PS/2 mouse device node and the system reserved > resource node. And if such a problem was found, please send ACPI data with the report. This is very useful info. for our debugging. To get ACPI data, # acpidump -o foo.dsdt > foo.asl and send both files to acpi-jp@. See also acpidump(8). > To see if this is to be your case, put the following line in > /boot/device.hints and reboot. > > debug.acpi.disable="sysresource" I personally, don't have enough time to hack the code for now (sorry), but I think that newly added `placeholders' code causes the problem for my first impression. for (i = 0; i < 100; i++) { rid = i; res = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0, ~0, 1, 0); rid = i; res = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0, ~0, 1, 0); rid = i; res = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0, 1, 0); } Mike, do you have any idea on this? Anyway, Yokota-san thank you very much for finding a workaround. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message