From owner-freebsd-current Tue Sep 11 18:48:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id C426637B40B for ; Tue, 11 Sep 2001 18:48:01 -0700 (PDT) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f8C1lk526869; Wed, 12 Sep 2001 10:47:46 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f8C1lju491807; Wed, 12 Sep 2001 10:47:45 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:wOdEkYojLs8cQ8TF5C8V0SLTGsNwMgl9@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id KAA18565; Wed, 12 Sep 2001 10:57:32 +0900 (JST) Message-Id: <200109120157.KAA18565@zodiac.mech.utsunomiya-u.ac.jp> To: "David W. Chapman Jr." Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: ps/2 mouse problems [boot -v messages] In-reply-to: Your message of "Tue, 11 Sep 2001 17:58:08 EST." <20010911175808.A27841@leviathan.inethouston.net> References: <20010911175808.A27841@leviathan.inethouston.net> Date: Wed, 12 Sep 2001 10:57:31 +0900 From: Kazutaka YOKOTA 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 Please send ENTIRE output, if possilbe, rather than partial exerpt. Also send "boot -v" output when the acpi module is not loaded. Please also tell which motherboard you have. It would be also useful to dump ACPI data blocks using acpidump(8). >Here's some more info on my ps/2 mouse problems I managed to dig up >from boot -v and some other errors I wanted ot know if I should worry >about. > > >atkbdc0: port 0x64,0x60 irq 1 on acpi0 >atkbd0: flags 0x1 irq 1 on atkbdc0 >atkbd: the current kbd controller command byte 0047 >atkbd: keyboard ID 0x41ab (2) >kbd0 at atkbd0 >kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 >atkbd1: unable to allocate IRQ >psm0: unable to allocate IRQ The above two lines are for debugging and benign. It's safe to ignore them. >ata-: ata0 already exists, using ata2 instead >ata-: ata1 already exists, using ata3 instead >atkbdc-: atkbdc0 already exists, using atkbdc1 instead >fdc-: fdc0 already exists, using fdc1 instead >ppc-: ppc0 already exists, using ppc1 instead >sc-: sc0 already exists, using sc1 instead >sio-: sio0 already exists, using sio2 instead >sio-: sio1 already exists, using sio3 instead >sio-: sio2 already exists, using sio4 instead >sio-: sio3 already exists, using sio5 instead >vga-: vga0 already exists, using vga1 instead > >ata2 failed to probe at port 0x1f0 irq 14 on isa0 >ata3 failed to probe at port 0x170 irq 15 on isa0 >atkbdc1: failed to probe at port 0x60 on isa0 >bt0 failed to probe on isa0 >cs0 failed to probe at port 0x300 on isa0 >ed0 failed to probe at port 0x280 iomem 0xd8000 irq 10 on isa0 >fdc1: cannot reserve I/O port range (6 ports) >fdc1 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > >ppc1: parallel port found at 0x378 >ppc1: cannot reserve I/O port range >ppc1: failed to probe at port 0x378-0x37f irq 7 on isa0 These are from "hinted" device instances created by /boot/device.hints. Something should be done for them. But no harm seems to be done in your case. >pid 271 (syslogd), uid 0: exited on signal 6 (core dumped) Hmm, Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message