From owner-freebsd-stable@FreeBSD.ORG Thu Sep 9 19:04:29 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0D8E10656E9; Thu, 9 Sep 2010 19:04:29 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id F0EA08FC1B; Thu, 9 Sep 2010 19:04:28 +0000 (UTC) Received: by eyx24 with SMTP id 24so1366161eyx.13 for ; Thu, 09 Sep 2010 12:04:27 -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=GEwtRxfGjQoeDdajr7HJLpemy4Bx7LmKeLGtJlzwREw=; b=vqwAtTv/326P9vqAZjSQpB5AJLn6WOz+AOew75gAU212JK7FEWO3otEQ3dxKIPRRHz ebFCPYjAyQlrEGBXit8nHJ+kRK0iyOX0g9nOuAlVlGcvwLMtKOVKtEZmiZwtvHqVdcVB 98h6v/auVIoLOSobOyab6kfphdSGtXVeatF6o= 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=YVq+Ueq+SClnIVlByZ51k6U51rWJf0TXqZCslJXKndveOShEqPIFIWwZ2mnBa59xPS 1lho534rwD140OrcLn5oZCwILpzoLKBoQY8eqsb9aRTBZfNC+CgtzEQjBFlrcYdiqCf1 +mHn/PnVIAXeQIBARmyc+CKBc7fp0YYpk/VbI= MIME-Version: 1.0 Received: by 10.216.11.129 with SMTP id 1mr684383wex.90.1284059067566; Thu, 09 Sep 2010 12:04:27 -0700 (PDT) Received: by 10.216.49.78 with HTTP; Thu, 9 Sep 2010 12:04:27 -0700 (PDT) In-Reply-To: <201009091437.21563.jhb@freebsd.org> References: <20100909143357.GG34314@home.opsec.eu> <201009091437.21563.jhb@freebsd.org> Date: Thu, 9 Sep 2010 12:04:27 -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 , Gareth de Vaux , freebsd-stable@freebsd.org, 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 19:04:29 -0000 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. Jack