From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 9 08:15:47 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C0DA1065670; Tue, 9 Jun 2009 08:15:47 +0000 (UTC) (envelope-from josef.moellers@ts.fujitsu.com) Received: from dgate20.ts.fujitsu.com (dgate20.ts.fujitsu.com [80.70.172.51]) by mx1.freebsd.org (Postfix) with ESMTP id 7841F8FC17; Tue, 9 Jun 2009 08:15:46 +0000 (UTC) (envelope-from josef.moellers@ts.fujitsu.com) DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Message-ID:Date:From:Organization:User-Agent: MIME-Version:To:CC:Subject:References:In-Reply-To: Content-Type:Content-Transfer-Encoding; b=bmbtl3u86krSd91cZiFARCBFvbODVT30JdEAPfLBIuyfFlkpw3/7TOh6 OeuPud4eX/nCzNdMYPtrghMkb1vUG5kEtJc8Cv/P8TRgJJ4iJ6arCjxB4 5snO4V6jbgCAaDIZZpEYOaCdi1jgtw4ge1hLOJCL6kxn02hj8ahEW87o9 NaslWxGLghntyBSv2yLLqz11JXboir51ayTp0s7EtkJiyQHtuoJkZ3drZ SewGJ9/zPbJzTGXBI6a1Ortc8AW7y; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=josef.moellers@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1244535275; x=1276071275; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Josef=20Moellers=20|Subject:=20Re:=20Failure=20to=20get=20past=20a=20PCI =20bridge|Date:=20Tue,=2009=20Jun=202009=2010:15:48=20+02 00|Message-ID:=20<4A2E1A34.2010405@ts.fujitsu.com>|To:=20 John=20Baldwin=20|CC:=20"freebsd-acpi@fr eebsd.org"=20|MIME-Version:=201 .0|Content-Transfer-Encoding:=208bit|In-Reply-To:=20<2009 06081047.17487.jhb@freebsd.org>|References:=20<4A24D29A.5 030604@ts.fujitsu.com>=20<200906051152.24609.jhb@freebsd. org>=20<4A2CC727.50806@ts.fujitsu.com>=20<200906081047.17 487.jhb@freebsd.org>; bh=jfcn0Psd/IuqayEjR/E0l8Laig6jIlxbpTXsiO6G2Gc=; b=ROFNJCCbP1LTnCETiEZziVKNqpXgquDvUaGM86jQfxjsDjGv5KSJNF2k /eF6vQCCvpQQWyssMzdb4lzooOA0JkA0X9cPRxIyBNuQduClalbKBqdSP yEalTPT5oYS3yxSFuzNpKV/SVJHgq2rfbuB6hjIIpJ8oq8HwVRPzVZ4v5 p7p2ECY4nAqkB1qEVfYhjTGc8s5IaLZEqXTg3V0xBx1QJ7cep8vrt676Y ap2V8t7E3l5E5sBAs8v7VJoWnPes/; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.41,330,1241388000"; d="scan'208";a="71617926" Received: from abgdgate40u.abg.fsc.net ([172.25.138.90]) by dgate20u.abg.fsc.net with ESMTP; 09 Jun 2009 10:14:33 +0200 X-IronPort-AV: E=Sophos;i="4.41,329,1241388000"; d="scan'208";a="52195084" Received: from unknown (HELO [172.25.253.16]) ([172.25.253.16]) by abgdgate40u.abg.fsc.net with ESMTP; 09 Jun 2009 10:15:44 +0200 Message-ID: <4A2E1A34.2010405@ts.fujitsu.com> Date: Tue, 09 Jun 2009 10:15:48 +0200 From: Josef Moellers Organization: Fujitsu Technology Solutions User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: John Baldwin References: <4A24D29A.5030604@ts.fujitsu.com> <200906051152.24609.jhb@freebsd.org> <4A2CC727.50806@ts.fujitsu.com> <200906081047.17487.jhb@freebsd.org> In-Reply-To: <200906081047.17487.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-acpi@freebsd.org" Subject: Re: Failure to get past a PCI bridge 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: Tue, 09 Jun 2009 08:15:47 -0000 John Baldwin wrote: > On Monday 08 June 2009 4:09:11 am Josef Moellers wrote: > >> 'morning, >> >> John Baldwin wrote: >> >>> On Friday 05 June 2009 10:51:44 am Josef Moellers wrote: >>> >>> >>>> Hello, >>>> >>>> Thanks for the help! >>>> >>>> John Baldwin wrote: >>>> >>>> >>>>> On Friday 05 June 2009 5:17:25 am Josef Moellers wrote: >>>>> >>>>> >>>>> >>>>>> Difficult, since I can't boot properly. >>>>>> However, I have managed to get the dsdt using a SuSE Linux and have run >>>>>> that through acpidump -d on a 7.2 running on a XEN virtual machine. >>>>>> Here's the result. >>>>>> >>>>>> >>>>>> >>>>> Hmm, your BIOS is certainly hosed. First, it does have separate >>>>> > processor > >>>>> objects: >>>>> >>>>> >>>> [...] >>>> >>>> I'll show this to our BIOS people. When I talked to them before, they >>>> claimed that everything were OK, since the OSes we support do come up >>>> properly. >>>> >>>> >>> I think your BIOS is actually ok, sorry my e-mail was a bit of a stream of >>> conciousness. >>> >>> >> That's what my colleague confirmed ;-) >> However, being the nice guy that he is, he provided me with a >> preliminary extra special test version (he was on the brink of going on >> holiday!), which presents the bridges in their numerical order (0, 1, 2, >> 0xfe, 0xff). With that BIOS, I finally got access to the keyboard and >> RAID controller and all and I'm installing FBSD as I'm writing this. >> >> So, maybe the algorithm shouldn't be "if we find a bridge with number 0 >> which is not the first one, give it another number" shouldn't this be >> "if we find *a* *second* bridge with number 0, give it another number"? >> > > Yes, that's bascially what my patch does. > I promise to do my best to read mails in the future ;-) Yes, you're obviously right. Shame on me. > >>> Ah, if you have a working machine where you can build a kernel, you can >>> > build > >>> an new CD using an existing ISO as a template. Simply build a GENERIC >>> > kernel > >>> and install it into some DESTDIR=/foo and mount the ISO image using >>> > mdconfig > >>> to /dist. Then do something like 'mkisofs -o new.iso -r -J -b >>> boot/cdboot -no-emul-boot -x /dist/boot/kernel /dist /foo'. If that >>> complains about duplicate 'boot/kernel' then you may need to copy all >>> of /dist/boot to /foo/boot, install the new kernel into /foo, and >>> use '-x /dist/boot /dist /foo'. >>> >>> Also, if this machine supports PXE boot at all, that can be a way to boot >>> > a > >>> test kernel as well. >>> >> Maybe that's what we'll have to do after all. >> > > Ok, let me know if it works. Thanks. Yepp! Works like a charm. I had been able to boot the original kernel with the modified BIOS and apply your patch. Then I rebooted with that kernel (on the modified BIOS, i.e. the one with the 0 254 255 bus numbers) and it booted OK. Then I flashed the BIOS back to a release version (i.e. one with 255 254 0 bus numbers) and the patched kernel booted OK and the non-patched kernel (kernel.old) crashed because it did not find its root FS. BTW As I understand it, the 254 and 255 busses are on-chip Nehalem busses which provide access to certain chip registers. Will this make its way into a future release? 8.0? Josef -- These are my personal views and not those of Fujitsu Technology Solutions! Josef Möllers (Pinguinpfleger bei FTS) If failure had no penalty success would not be a prize (T. Pratchett) Company Details: http://de.ts.fujitsu.com/imprint.html