From owner-freebsd-stable@FreeBSD.ORG Sat Jun 9 19:06:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9DD01065672 for ; Sat, 9 Jun 2012 19:06:23 +0000 (UTC) (envelope-from andrey@zonov.org) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3C2D38FC0A for ; Sat, 9 Jun 2012 19:06:23 +0000 (UTC) Received: by lbon10 with SMTP id n10so2504752lbo.13 for ; Sat, 09 Jun 2012 12:06:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=od/Qr+gIa6UfD6XL3PsKX6ysfij6Z/qZM53O7Zhvmt8=; b=aVp4c9H6V+VwtfkNsyU9tBduDgsHzCO3HONRgHjIiWa8RwFb6CXlEigRWtu4H561pH uOFZS/yCFcw9XgggFbN5WvvNgMha0YnFchL4roTL6TEXihRbpP/HkUDuz42r9sacjfUj zo9/IsPSSXoT8UH1mCj2nAvZT2S3Py0lpY33GiqgUagIzl/EvA0z7vv7DSQvsrXr/XZ1 dMGHrzQ1CQj4G2eYywUF2+TwS/gFy/PDVF4NQ27vLQXhHBS/LSdRVgDHyFzDM0udEvr8 btPWzbxFbkdWTr4HuvvHvSamT9+4bKoEeyff2sYDtw+FU82hMNRySvvi6vCtuKCmlfHM JquQ== Received: by 10.152.113.199 with SMTP id ja7mr12347405lab.10.1339268781122; Sat, 09 Jun 2012 12:06:21 -0700 (PDT) Received: from zont-osx.local (ppp95-165-147-222.pppoe.spdop.ru. [95.165.147.222]) by mx.google.com with ESMTPS id gd9sm5742997lbb.15.2012.06.09.12.06.19 (version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 12:06:20 -0700 (PDT) Message-ID: <4FD39EAB.3080805@zonov.org> Date: Sat, 09 Jun 2012 23:06:19 +0400 From: Andrey Zonov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Marius Strobl References: <4FD0ECB7.8040908@zonov.org> <201206081119.09164.jhb@freebsd.org> <201206081427.39718.jhb@freebsd.org> <4FD3101D.9010603@zonov.org> <20120609173523.GA41443@alchemy.franken.de> In-Reply-To: <20120609173523.GA41443@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnGJ/94HPEJQluST+dh7toTIUZArSj7pR739fyOnz1rqP8T38+x7cmA4TuUuP4PXCq8UuKf Cc: freebsd-stable , John Baldwin Subject: Re: mpt: Unable to memory map registers X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 19:06:24 -0000 On 6/9/12 9:35 PM, Marius Strobl wrote: > On Sat, Jun 09, 2012 at 12:58:05PM +0400, Andrey Zonov wrote: >> On 6/8/12 10:27 PM, John Baldwin wrote: >>> On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: >>>> On Fri, Jun 8, 2012 at 7:19 PM, John Baldwin wrote: >>>>> On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: >>>>>> On 6/7/12 10:02 PM, Andrey Zonov wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE >>>>>>> (r234600) and now they can't find any disk because SAS controller >>>>>>> cannot >>>>>>> initialize with the following diagnostic: >>>>>>> >>>>>>> mpt0: port 0xd000-0xd0ff irq 26 at device >>>>>>> 3.0 on pci6 >>>>>>> mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0xffffffffffffffff). >>>>>>> mpt0: Unable to memory map registers. >>>>>>> mpt0: Giving Up. >>>>>>> >>>>>>> pciconf -lv: >>>>>>> mpt0@pci0:6:3:0: class=0x010000 card=0x81dd1043 chip=0x00541000 >>>>>>> rev=0x02 >>>>>>> hdr=0x00 >>>>>>> vendor = 'LSI Logic / Symbios Logic' >>>>>>> device = 'SAS1068 PCI-X Fusion-MPT SAS' >>>>>>> class = mass storage >>>>>>> subclass = SCSI >>>>>>> >>>>>>> I tried to boot to latest HEAD and found the same problem. I also tried >>>>>>> to build kernel with mpt driver from my 8.2. Controller didn't >>>>>>> initialize with the same diagnostic. So it looks like the problem is >>>>>>> not >>>>>>> in mpt driver. >>>>>>> >>>>>>> Any help would be appreciated. >>>>>>> >>>>>> >>>>>> +jhb@ >>>>>> >>>>>> Hi John, >>>>>> >>>>>> Could you please help me with the problem above? It looks like the >>>>>> problem is in PCI code and you changed things there. >>>>> >>>>> Can you get a verbose dmesg? >>>>> >>>> >>>> Yes, it's in attach. >>> >>> Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken >>> kernel? >>> >> >> Attached. >> >>> Can you also try setting 'debug.acpi.disable=sysres' in the loader? >>> >> >> Didn't help. >> > > That's probably due to a typo, the corret loader tunable is > debug.acpi.disabled=sysres (note the 'd'). > This helps, thanks! Please explain what this means. -- Andrey Zonov