From owner-svn-src-head@FreeBSD.ORG Mon Nov 15 00:28:06 2010 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21295106566B; Mon, 15 Nov 2010 00:28:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 34E528FC08; Mon, 15 Nov 2010 00:28:05 +0000 (UTC) Received: by gxk9 with SMTP id 9so2844846gxk.13 for ; Sun, 14 Nov 2010 16:28:04 -0800 (PST) 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=aWG0sf+fkxfhJAqhMtCZlBi/Q4PAioXnkCuIn5CkQkw=; b=f0iMTubu12fmCgZonaAwAH94KI7YsPNm/st2LcPbMUBoPFXIwrMdO2z7fwjP4NGJfT QuTZe+wW+AhXrSeW6ETylBs4olEQs54VCW//ku47Z7DlAcK52qTHaJNh6hvKIXEk8XSm Y1waOUS49KC+hD3IGB08sUqfLw0hMzVQJSjas= 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=OcACnu64sOfYRC1EgnBMPTz0zX1MIHTqmFiOuDrNdHZgyQpFNoed5FWOQ8JxPohohh xrvnJeey056s9HqkPcfvBJ4aVW6/XALbwKT8pydcsN293KUhDgx3ghrLdF/qe0cbH2Wv /UZ2avczTKvaXblh2PJa1BsQTfnGjYQ5Kqnaw= Received: by 10.150.190.3 with SMTP id n3mr8389258ybf.282.1289780884593; Sun, 14 Nov 2010 16:28:04 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 5sm4178402yhl.47.2010.11.14.16.28.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 14 Nov 2010 16:28:02 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 14 Nov 2010 16:27:59 -0800 From: Pyun YongHyeon Date: Sun, 14 Nov 2010 16:27:59 -0800 To: Alexander Motin Message-ID: <20101115002759.GA1351@michelle.cdnetworks.com> References: <201011142337.oAENbheD097425@svn.freebsd.org> <4CE07AA3.6040205@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CE07AA3.6040205@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Pyun YongHyeon Subject: Re: svn commit: r215327 - head/sys/dev/nfe X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 00:28:06 -0000 On Mon, Nov 15, 2010 at 02:11:15AM +0200, Alexander Motin wrote: > Pyun YongHyeon wrote: > > Author: yongari > > Date: Sun Nov 14 23:37:43 2010 > > New Revision: 215327 > > URL: http://svn.freebsd.org/changeset/base/215327 > > > > Log: > > P5N32-SLI PREMIUM from ASUSTeK is known to have MSI/MSI-X issue > > such that nfe(4) does not work with MSI-X. When MSI-X support was > > introduced, I remember MCP55 controller worked without problems so > > the issue could be either PCI bridge or BIOS issue. But I also > > noticed snd_hda(4) disabled MSI on all MCP55 chipset so I'm still > > not sure this is generic issue of MCP55 chipset. If this was PCI > > bridge issue we would have added it to a system wide black-list > > table but it's not clear to me at this moment whether it was caused > > by either broken BIOS or silicon bug of MCP55 chipset. > > MCP5x seem to be infinite source of surprises. Some reports I remember: Yeah, they even do not release any errata. > - snd_hda not working with MSI enabled - AFAIR not just loosing > interrupts but completely stops responding; > - using regular HPET interrupts breaks HDA sound after some time > (interrupts are not shared), while legacy_route mode operates properly; > - at least on one system I've seen non-functioning SATA interrupts. > It would be nice to find what's going on there. I've got tired to add > workarounds for it. :( > Yeah, I agree but I'm sure not all MCP55 was broken because one user who tested MCP55 with MSI-X reported success. This is reason why I didn't add it to system-wide blacklist table. If you remember exact PCI bridge chipset I think you can compare it with the pciconf output in PR/152150 and if it's the same we can move it to PCI quirk table.