From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 31 15:32:52 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C17B416A4DF; Mon, 31 Jul 2006 15:32:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97C6743D58; Mon, 31 Jul 2006 15:32:50 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6VFWibH064176; Mon, 31 Jul 2006 11:32:44 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 31 Jul 2006 11:20:55 -0400 User-Agent: KMail/1.9.1 References: <20060730223358.GN48334@hoeg.nl> In-Reply-To: <20060730223358.GN48334@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607311120.55563.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 31 Jul 2006 11:32:46 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1627/Sun Jul 30 19:34:54 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: FreeBSD Stable , Ed Schouten Subject: Re: Odd PCI and ACPI messages on 'INSYDE RSDT_000' laptop X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2006 15:32:52 -0000 On Sunday 30 July 2006 18:33, Ed Schouten wrote: > Hello, > > Last week I got a laptop from a few friends of mine with a broken > screen. I removed the screen from the device and connected a regular CRT > to it to install FreeBSD 6.1 on it for serving as a jukebox (silent, > doesn't consume too much power). > > I first tried FreeSBIE 1.1, which just deadlocked during the bootsplash. > After that I downloaded a FreeBSD 6.1 CD. When I boot FreeBSD 6.1 > without the ACPI kernel module, it panics (fatal trap 12) right after > probing uhci0. When I boot with ACPI, it boots like it should. Because > the laptop doesn't have a serial connector, I didn't copy the kernel > backtrace. If it is really needed, I'll boot the CD once again and type > over the screen contents. > > Anyway, I installed FreeBSD 6.1 on it, with the ACPI module loaded, but > I still get some really strange messages in my dmesg I thought would be > useful to mention: > > | ... > | cpu0: on acpi0 > | acpi_perf0: on cpu0 > | acpi_perf0: failed in PERF_STATUS attach > | device_attach: acpi_perf0 attach returned 6 > | ... > | acpi_perf0: on cpu0 > | acpi_perf0: failed in PERF_STATUS attach > | device_attach: acpi_perf0 attach returned 6 > | ... > > And these: > > | ... > | pci_link0: BIOS IRQ 11 for 0.2.INTA is invalid > | pci_link1: BIOS IRQ 5 for 0.31.INTB is invalid > | ... > | pci_link4: BIOS IRQ 11 for 1.0.INTA is invalid > | pci_link5: BIOS IRQ 11 for 1.1.INTA is invalid > | ... > > The device Just Works at the moment, so I can live with it, but I > was wondering if these messages do any harm. I've attached the entire > dmesg of the device for those who are interested. If your machine works, then don't worry about the pci_link messages. -- John Baldwin