From owner-freebsd-current@FreeBSD.ORG Fri Jan 19 18:55:52 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BCDB16A400 for ; Fri, 19 Jan 2007 18:55:52 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.freebsd.org (Postfix) with ESMTP id 92A0413C44B for ; Fri, 19 Jan 2007 18:55:51 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id 71so520014wri for ; Fri, 19 Jan 2007 10:55:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tLpYsfwtBYgSvWRxvK6XxqS4qCR0ZZgfkmXrcvz+rAhySfAZ7MAmXn3XbwAs3HXQXj7taftrAlZICapeiIan+AnG7F+8UQ/VOg1b/eReAVcBevVgjs4szLcLTbDMX0C12f/CYXDYddERV14ktdtjNmV97KWLMNFiyCbQYpRZCEU= Received: by 10.90.51.17 with SMTP id y17mr3215264agy.1169232950891; Fri, 19 Jan 2007 10:55:50 -0800 (PST) Received: by 10.90.74.7 with HTTP; Fri, 19 Jan 2007 10:55:50 -0800 (PST) Message-ID: <2a41acea0701191055u20b91c84tfabb242c9b6815fd@mail.gmail.com> Date: Fri, 19 Jan 2007 10:55:50 -0800 From: "Jack Vogel" To: "Mark Atkinson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-current@freebsd.org Subject: Re: another msi blacklist candidate? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2007 18:55:52 -0000 On 1/19/07, Mark Atkinson wrote: > I upgraded a box to -current yesterday with the following pci card in it, > (this is the msi disabled verbose boot below) but upon bootup, any heavy > network activity caused watchdog timeouts and resets. Disabling msi via > the two tunables fixed the problem. > > What info do you need on this problem? > > found-> vendor=0x8086, dev=0x1076, revid=0x00 > bus=4, slot=2, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) > lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D3 current D0 > MSI supports 1 message, 64 bit > map[10]: type 1, range 32, base 0xdf9c0000, size 17, enabled > pcib4: requested memory range 0xdf9c0000-0xdf9dffff: good > map[14]: type 1, range 32, base 0xdf9e0000, size 17, enabled > pcib4: requested memory range 0xdf9e0000-0xdf9fffff: good > map[18]: type 4, range 32, base 0xdcc0, size 6, enabled > pcib4: requested I/O range 0xdcc0-0xdcff: in range > pcib4: matched entry for 4.2.INTA > pcib4: slot 2 INTA hardwired to IRQ 18 > em0: port > 0xdcc0-0xdcff m > em 0xdf9c0000-0xdf9dffff,0xdf9e0000-0xdf9fffff irq 18 at device 2.0 on pci4 > em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xdf9c0000 > em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xdcc0 > em0: bpf attached > em0: Ethernet address: 00:0e:0c:6e:a1:39 > em0: [FAST] Talked about this internally, and the advise here is that the em driver change so that only PCI-E adapters can use MSI, this would eliminate the need to blacklist in the kernel PCI code. Jack