From owner-freebsd-current@FreeBSD.ORG Mon Jun 15 01:27:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D300106564A for ; Mon, 15 Jun 2009 01:27:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f192.google.com (mail-px0-f192.google.com [209.85.216.192]) by mx1.freebsd.org (Postfix) with ESMTP id CAF9A8FC1D for ; Mon, 15 Jun 2009 01:27:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by pxi30 with SMTP id 30so2530694pxi.3 for ; Sun, 14 Jun 2009 18:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=pVBz6UCf6NExh6U10n4/vcVUKajtuzQ8UiC/kTZGoHQ=; b=K/kcS6NM5lH8Um8EuN8sWhslxYqRylXL/jTuKCe5FNtVQJSPnKQB0r8e/tByVIOSzL j6skwR5OrcD5FEOMwBwlTx4a0onGFRmgi5qDLklI4LZWGQT1WYvpZVaiV3z9XEMYS3Z4 e2p1oDyN4RDYpMIm9f0YANlfCsPyka1Pz/+is= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=RC8o7tXQe2d0NUI8QV5JmJPi7/0XHvuxe56IPRauNs6CXc0YcMKW0T4v4rWqV+2UNd xR9eM4XwyJ8x2UyzikO8PkqxW7emcQ5yXs+BqUHq7xbGHpSZxM3zMvLUaEcxsn0MPrNl 15QdXYWeRBOPiJWgkRCrsRCYY8feJcDEnDjP4= Received: by 10.114.25.19 with SMTP id 19mr10780976way.89.1245029272323; Sun, 14 Jun 2009 18:27:52 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id j34sm5282952waf.64.2009.06.14.18.27.45 (version=SSLv3 cipher=RC4-MD5); Sun, 14 Jun 2009 18:27:46 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Mon, 15 Jun 2009 10:31:07 +0900 From: Pyun YongHyeon Date: Mon, 15 Jun 2009 10:31:06 +0900 To: Thomas Lotterer Message-ID: <20090615013106.GA78415@michelle.cdnetworks.co.kr> References: <4A2DA8D9.2030300@lotterer.net> <20090610024959.GD63941@michelle.cdnetworks.co.kr> <4A2FF8E3.4060501@lotterer.net> <20090611002923.GA68519@michelle.cdnetworks.co.kr> <4A30FD94.4030409@lotterer.net> <20090611130557.GB68519@michelle.cdnetworks.co.kr> <4A312517.9030206@lotterer.net> <20090612055032.GD72855@michelle.cdnetworks.co.kr> <4A32BAE7.40605@lotterer.net> <4A350565.3070504@lotterer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A350565.3070504@lotterer.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: suspect bug in vge(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 01:27:54 -0000 On Sun, Jun 14, 2009 at 04:12:53PM +0200, Thomas Lotterer wrote: > Thomas Lotterer wrote: > >Pyun YongHyeon wrote: > >>On Thu, Jun 11, 2009 at 05:39:03PM +0200, Thomas Lotterer wrote: > >>>Pyun YongHyeon wrote: > >>>>Could you show me dmesg output(only vge(4) related one)? > >>># dmesg | grep vge > >>>vge0: port 0xec00-0xecff mem > >>>0xdf7ff000-0xdf7ff0ff irq 28 at device 0.0 on pci2 > >>>vge0: MSIX count : 0 > >>>vge0: MSI count : 1 > >> > >>I wonder why "Using 1 MSI messages" message is missing. > > > I stud if_vge.c with device_printf() statements. > > Turns out pci_alloc_msi() returns 6 = ENXIO > > The pci_alloc_msi_method() in /usr/src/sys/dev/pci/pci.c > lists three cases returning ENXIO and all are located at the very top of > the function. > > - If rid 0 is allocated, then fail. > - Already have allocated messages? > - If MSI is blacklisted for this system, fail. > > The pci_msi_blacklisted() and pci_msi_device_blacklisted() in > /usr/src/sys/dev/pci/pci.c > seem to check chipsets, devices and tunables > Correct. FreeBSD maintains a quirk table of known devices that do not work with MSI. These buggy devices are black listed by default. Compare your device ids with the list. Use pciconf(8) to get PCI device ids. > Regarding the chipset > # dmesg | egrep ^acpi > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 7bde0000 (3) failed > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > > Regarding the tunables > # sysctl -a | fgrep hw.pci. > hw.pci.honor_msi_blacklist: 1 > hw.pci.enable_msix: 1 > hw.pci.enable_msi: 1 > hw.pci.do_power_resume: 1 > hw.pci.do_power_nodriver: 0 > hw.pci.enable_io_modes: 1 > hw.pci.host_mem_start: 2147483648 > hw.pci.mcfg: 1 > hw.pci.irq_override_mask: 57080 > > No cheating here > # sysctl hw.pci.honor_msi_blacklist=0 > sysctl: oid 'hw.pci.honor_msi_blacklist' is read only > That tunable is read only. You can set it in /boot/loader.conf. hw.pci.honor_msi_blacklist="0" > Ideas and suggestions welcome. > -- > http://thomas.lotterer.net