From owner-freebsd-stable@FreeBSD.ORG  Fri Jun 22 19:40:16 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E2E58106564A;
	Fri, 22 Jun 2012 19:40:16 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net
	[IPv6:2001:470:1f10:75::2])
	by mx1.freebsd.org (Postfix) with ESMTP id B7C088FC08;
	Fri, 22 Jun 2012 19:40:16 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
	by bigwig.baldwin.cx (Postfix) with ESMTPSA id D4B21B95D;
	Fri, 22 Jun 2012 15:40:15 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: Mike Tancsa <mike@sentex.net>
Date: Fri, 22 Jun 2012 15:06:35 -0400
User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; )
References: <201206201439.q5KEdaF9048424@svn.freebsd.org>
	<4FE4BC5F.30002@sentex.net>
In-Reply-To: <4FE4BC5F.30002@sentex.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201206221506.35489.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
	(bigwig.baldwin.cx); Fri, 22 Jun 2012 15:40:16 -0400 (EDT)
Cc: Alexander Motin <mav@freebsd.org>,
	FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam
	sys/cam/scsi sys/conf
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 19:40:17 -0000

On Friday, June 22, 2012 2:41:35 pm Mike Tancsa wrote:
> Using jhb's handy pciconf from HEAD, I see (pciconf -lvcbe)
> 
> twa0@pci0:2:0:0:        class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00
>     vendor     = '3ware Inc'
>     device     = '9650SE SATA-II RAID PCIe'
>     class      = mass storage
>     subclass   = RAID
>     bar   [10] = type Prefetchable Memory, range 64, base 0x81c000000, size 33554432, enabled
>     bar   [18] = type Memory, range 64, base 0xe2420000, size 4096, enabled
>     bar   [20] = type I/O Port, range 32, base 0x4000, size 256, enabled
>     cap 01[40] = powerspec 2  supports D0 D1 D2 D3  current D0
>     cap 05[50] = MSI supports 32 messages, 64 bit 
>     cap 10[70] = PCI-Express 1 legacy endpoint max data 128(512) link x1(x8)
> ecap 0001[100] = AER 1 1 fatal 0 non-fatal 0 corrected
>   PCI-e errors = Fatal Error Detected
>                  Unsupported Request Detected
>          Fatal = Unsupported Request
> 
> 
> Looking at the pciconf output from the older kernel, the unsupported request is there too
> 
> twa0@pci0:2:0:0:        class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00
>     vendor     = '3ware Inc'
>     device     = '9650SE SATA-II RAID PCIe'
>     class      = mass storage
>     subclass   = RAID
>     bar   [10] = type Prefetchable Memory, range 64, base 0x81c000000, size 33554432, enabled
>     bar   [18] = type Memory, range 64, base 0xe2420000, size 4096, enabled
>     bar   [20] = type I/O Port, range 32, base 0x4000, size 256, enabled
>     cap 01[40] = powerspec 2  supports D0 D1 D2 D3  current D0
>     cap 05[50] = MSI supports 32 messages, 64 bit 
>     cap 10[70] = PCI-Express 1 legacy endpoint max data 128(512) link x1(x8)
> ecap 0001[100] = AER 1 1 fatal 0 non-fatal 0 corrected
>   PCI-e errors = Fatal Error Detected
>                  Unsupported Request Detected
>          Fatal = Unsupported Request

I think you can ignore these.  I think they happen during POST.

-- 
John Baldwin