From owner-freebsd-stable@FreeBSD.ORG Tue Jun 9 02:16:04 2009 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 A1BDC106566C for ; Tue, 9 Jun 2009 02:16:04 +0000 (UTC) (envelope-from pete@altadena.net) Received: from puffin.altadena.net (puffin.altadena.net [173.10.157.234]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6938FC1F for ; Tue, 9 Jun 2009 02:16:04 +0000 (UTC) (envelope-from pete@altadena.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=2.puffin; d=altadena.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=qX6Kkz4Ws71Wiedk4CIz/wH27AcX2DluGrib3riv8M9mj0ouu1xxYlKM4dCzfVYoMUALxcLCGwrI9yGQ44D5Nr7H3/xS6yejvdSNdUE+Fp0ZsTGOGKRBdn/zcYxgENQh8WHS9PujHccWDVxFx03HcZ0f+7pKU7tz+QJRLcbGjr8=; Received: from gate.east.altadena.net ([173.10.157.233] helo=port4l.altadena.net) by puffin.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1MDqVj-000K8t-LG for stable@freebsd.org; Mon, 08 Jun 2009 21:52:23 -0400 Message-ID: <4A2DC056.8090500@altadena.net> Date: Mon, 08 Jun 2009 21:52:22 -0400 From: Pete Carah User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Bug between DRM, MSI, or somewhere, re7-stable amd64 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: Tue, 09 Jun 2009 02:16:04 -0000 I updated my recently acquired core-2 duo laptop to 7-stable amd64 (I had been running 7-stable i386 with few problems) and have acquired an apparent irq problem. Fortunately in debugging a linux shared-interrupt problem about a month ago I learned that the X server will happily accept mouse motion as if it was a display interrupt, so at least with some inconvenience I can read the screen... (the keyboard isn't so obliging) Ours does this too... /usr/src was picked up via svn on last Saturday morning EDT, ports via csup about the same time. I have no idea if this bug is in the intel driver, drm, or the core msi code... There are 2 peripherals that dmesg says uses msi - re0 (which doesn't get a kernel thread indicated in ps for either the stated irq (257) or re0) and drm0/vgapci0 (which indicates irq256 in systat and ps). As I said, this worked properly with earlier source (about a week) in i386 mode. I've used both G45 and re controllers in (f10) linux msi mode with no problems in both 32 and 64-bit. Fortunately this laptop now has enough disk to triple-boot so at least something works... I am using svn instead of csup because I am trying (haven't gotten time yet either :-) to port Sam's ath 92xx code to -stable and handling code porting is much easier that way. -- Pete