From owner-freebsd-stable@FreeBSD.ORG Thu Sep 9 20:48:15 2010 Return-Path: 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 E5CD110656C0; Thu, 9 Sep 2010 20:48:15 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 42A3C8FC19; Thu, 9 Sep 2010 20:48:14 +0000 (UTC) Received: by ewy4 with SMTP id 4so1477287ewy.13 for ; Thu, 09 Sep 2010 13:48:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=tj1eKYqnSsWEabaWx21PRXRNyjiKIZGNqAwXv58JgAw=; b=Dlvj38LqAsRbCbx53CtHUIEyQijrOQ97wGQbXt9sSTYQJPVd3mTdzlQ1WKIrHL+WiO 6sXbIVLPVIMzZe9PDX3otXtxyfUz/iGGeoBXPBUJrKiNtZyCr7366sPg4U/UQgsz+DtD 7GiUK89LPLoZaPDQMWjVmDU/1wA5Fk/pahaj0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qP35VOX4Kfshk+hhpeOs/yBYjErxaiLsnBRuZ60+rvysku2CoHP/AvdaFKfxvSpCfs dwvka+iW8UkJlpS4x4QmnBT9Mjkoep8AzZfKa6F9mOWC2gQa6LBVD+dQS2ar0nkUVNlO 6qq59mjnoB2BCSxt0u4f2SAcomqWo+vmQcUGo= MIME-Version: 1.0 Received: by 10.216.13.17 with SMTP id a17mr75635wea.46.1284065293787; Thu, 09 Sep 2010 13:48:13 -0700 (PDT) Received: by 10.216.49.78 with HTTP; Thu, 9 Sep 2010 13:48:13 -0700 (PDT) In-Reply-To: <201009091620.25299.jhb@freebsd.org> References: <201009091437.21563.jhb@freebsd.org> <201009091620.25299.jhb@freebsd.org> Date: Thu, 9 Sep 2010 13:48:13 -0700 Message-ID: From: Jack Vogel To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Kurt Jaeger , freebsd-stable@freebsd.org Subject: Re: MSIX failure 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: Thu, 09 Sep 2010 20:48:16 -0000 Gareth's email bouncing for anybody else or is it just me? Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot btw. Tell me more exactly the make/model of the hardware so I might try to get my hands on one? Jack On Thu, Sep 9, 2010 at 1:20 PM, John Baldwin wrote: > On Thursday, September 09, 2010 3:04:27 pm Jack Vogel wrote: > > On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin wrote: > > > > > On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote: > > > > On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger wrote: > > > > > > > > > Hi! > > > > > > > > > > > > Is this within a jail or something else along those lines? I > can't > > > > > > > reproduce the problem otherwise. Frustrating! Someone else on > the > > > > > list > > > > > > > might have ideas as to what could cause this. > > > > > > > > > > > > Nope, this's a normal host. I've got securelevel on 1, but doubt > that > > > > > > would affect this? > > > > > > > > > > I assume it affects it. > > > > > > > > > > http://www.freebsd.org/doc/en/books/faq/security.html#SECURELEVEL > > > > > > > > > > Basically, when the securelevel is positive, the kernel restricts > > > > > certain tasks; not even the superuser (i.e., root) is allowed to > > > > > do them. > > > > > > > > > > There: > > > > > > > > > > # Write to kernel memory via /dev/mem and /dev/kmem. > > > > > > > > > > So I assume it also restricts reading /dev/kmem ? > > > > > > > > > > > > > > OH YUCK, another root isn't really root, so is it also possibly > > > > the reason for the MSIX failure?? Is this pile, er feature, on by > > > default? > > > > > > securelevel does not affect any of the MSI/MSI-X bits. > > > > > > > Well then there's something else funny going on with that hardware, as at > > least MSI should work with the chipset, I am not able to get that exact > > skew from what I am told. > > I think the first would be to disable the MSI blacklists via a tunable to > see > if that enables MSI. > > -- > John Baldwin >