From owner-freebsd-current Sun Sep 9 1: 1:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from hermes.dialup.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id DBF7637B407 for ; Sun, 9 Sep 2001 01:01:17 -0700 (PDT) Received: (from ache@localhost) by hermes.dialup.ru (8.11.5/8.11.5) id f8981Fa00488 for current@freebsd.org; Sun, 9 Sep 2001 12:01:15 +0400 (MSD) (envelope-from ache) Date: Sun, 9 Sep 2001 12:01:15 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: New ACPI dangerous false devices Message-ID: <20010909120115.A374@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 With new ACPI and my ASUS TUSL2-C I got following false devices configured: sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 port 0-0x7 irq 3 on acpi0 sio1: type 8250 (I disable sio1 in BIOS, it must not assign irq 3 here) sc1: on isa0 sc1: MDA <16 virtual consoles, flags=0x0> (I have no sc1 or MDA) sio1 maked by ACPI is dangerous ineed because when try to write something to /dev/cuaa1 I got system lockup. Please do something with it. Also I got lots of: fdc1: cannot reserve I/O port range (6 ports) ppc1: cannot reserve I/O port range I don't think they are dangerous because no devices created. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message