From owner-freebsd-hardware@FreeBSD.ORG Sun Jan 16 04:14:00 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB5B4106566C for ; Sun, 16 Jan 2011 04:14:00 +0000 (UTC) (envelope-from jctune@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id BD3CD8FC0C for ; Sun, 16 Jan 2011 04:14:00 +0000 (UTC) Received: by pzk32 with SMTP id 32so666620pzk.13 for ; Sat, 15 Jan 2011 20:14:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=9Eki7O4yxSpiEA8SHM35MT5OcN2I4Vu4vyhh1mFEPgA=; b=imAWOyuQLWOLDtEMYTnw47v6AHtCDuCJhRlcK6NXhfV6J38e+bRtWNaJsWI6V+tsQm cu3DyIwvNVKQaKPbjf+mNouTYzOQta17GBtXHSR+l2y2a5tQzO2NeumMoKpvzZhGIe9d 5vO1EtlCYNf1bTbAvXOpWGwpCwJsNl/8dzZIA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; b=H/pRunFgiisIw3L/tI3TyUbiTq358NvHM/V89Oz2VWo0kzWIvjsAr3NEyUPyBoGNSf oSxi6jeXSenb7xxSMwUqIGv9TPC2vDn60isAiZIwcWnMUhMBGJITcURuv9gTs1pRVeV4 h60iBp0RPVU+s7N90NJvlSVAQRW+y3empJ1gw= Received: by 10.142.239.11 with SMTP id m11mr2194778wfh.120.1295149601159; Sat, 15 Jan 2011 19:46:41 -0800 (PST) Received: from [10.222.111.121] (c-174-51-181-166.hsd1.co.comcast.net [174.51.181.166]) by mx.google.com with ESMTPS id w22sm4259065wfd.7.2011.01.15.19.46.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 15 Jan 2011 19:46:40 -0800 (PST) Sender: Cameron Tune From: Cameron Tune Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 15 Jan 2011 20:46:35 -0700 Message-Id: <48E61CAB-27B8-4EED-9D9B-A0CF35FE14CD@yahoo.com> To: freebsd-hardware@freebsd.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Mailman-Approved-At: Sun, 16 Jan 2011 04:24:04 +0000 Subject: Problem with Highpoint 2320 Raid card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2011 04:14:01 -0000 Last month I purchased a Highpoint 2320 raid card, = http://www.newegg.com/Product/Product.aspx?Item=3DN82E16816115026 , for = my FreeBSD server. I'm new to the FreeBSD world - so please bear with = me as I try to solve the following issue. With the card installed - the server hangs during the boot process. I = don't even get to the standard FreeBSD boot menus (loader prompt, = single-user mode, etc.), rather the freeze occurs after a "console" = message and then a listing of physical disks. A picture of where the = hang occurs is at http://www.camerontune.com/images/photo.jpg .=20 As far as I can tell this card is supported on FreeBSD (running 8.1 = STABLE i386). I've updated the motherboard bios, and have also monkeyed = around with just about every possible setting in the card's bios. = Motherboard is a Gigabyte GA-EP45-UD3P. I've combed through every possible log I can find in /var/logs - but I'm = not finding anything that starts this early in the boot process. I've = also ensured that all drivers are present and loaded in loader.conf - = however I don't think I'm even getting to the point of drivers being = loaded. Any thoughts are appreciated - and please let me know if there's any = additional information I can provide that may help diagnose the problem.= From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 18:45:13 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1D06106564A for ; Tue, 18 Jan 2011 18:45:13 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6E7388FC1C for ; Tue, 18 Jan 2011 18:45:13 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PfGJj-0005n5-59 for freebsd-hardware@freebsd.org; Tue, 18 Jan 2011 19:30:07 +0100 Received: from 213.202.123.54 ([213.202.123.54]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Jan 2011 19:30:07 +0100 Received: from ivoras by 213.202.123.54 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Jan 2011 19:30:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Tue, 18 Jan 2011 19:29:54 +0100 Lines: 41 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 213.202.123.54 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 Subject: IBM / LSI disk card & 10 Gbit broadcom NIC not detected X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2011 18:45:13 -0000 Hi, I have a bleeding edge machine here with new hardware, unrecognized by FreeBSD (stable and current). The RAID controller is a LSI/IBM-rebranded product and the 10 gbit NICs are Broadcom's. I'd be interested in a (very) quick solution, especially for the disk driver, otherwise I'll have to (quickly) install something else on the server. none2@pci0:3:0:0: class=0x010400 card=0x03b11014 chip=0x00731000 rev=0x03 hdr=0x00 class = mass storage subclass = RAID cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 10[68] = PCI-Express 2 endpoint max data 128(4096) link x8(x8) cap 03[d0] = VPD cap 05[a8] = MSI supports 1 message, 64 bit cap 11[c0] = MSI-X supports 15 messages in map 0x14 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0004[138] = unknown 1 none3@pci0:4:0:0: class=0x020000 card=0xe62910df chip=0x070019a2 rev=0x02 hdr=0x00 class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 11[48] = MSI-X supports 32 messages in map 0x14 cap 10[c0] = PCI-Express 2 endpoint max data 128(512) link x8(x8) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[194] = Serial 1 0000c9fffea9585c none4@pci0:4:0:1: class=0x020000 card=0xe62910df chip=0x070019a2 rev=0x02 hdr=0x00 class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 11[48] = MSI-X supports 32 messages in map 0x14 cap 10[c0] = PCI-Express 2 endpoint max data 128(512) link x8(x8) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[194] = Serial 1 0000c9fffea9585c From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 22:06:57 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C968106566C for ; Tue, 18 Jan 2011 22:06:57 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx03.pub.collaborativefusion.com (mx03.pub.collaborativefusion.com [206.83.220.142]) by mx1.freebsd.org (Postfix) with ESMTP id 040D58FC16 for ; Tue, 18 Jan 2011 22:06:56 +0000 (UTC) Received: from Internal Mail-Server by mx03 (envelope-from korvus@comcast.net) with SMTP; 18 Jan 2011 16:34:33 -0500 Message-ID: <4D3608BD.7010604@comcast.net> Date: Tue, 18 Jan 2011 16:40:13 -0500 From: Steve Polyack User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101109 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, User Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2011 22:06:57 -0000 We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, "enter") for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers? Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Thanks, Steve Polyack From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 22:57:12 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D11F61065698; Tue, 18 Jan 2011 22:57:12 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6AF8FC0C; Tue, 18 Jan 2011 22:57:12 +0000 (UTC) Received: by qwj9 with SMTP id 9so164807qwj.13 for ; Tue, 18 Jan 2011 14:57:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4tF8tuiuhA/p4JppNlNLYm6owl/w6r51cgWWBqXeEvM=; b=oSdJQf0VRFSdCIMpkBBDgIVuz+oOr540HivprvPjhWkJRPpTDA28w19EdBskvxt1lm wgIBihShg4d/Ou971SWamSusAG5zH5lOjl1hQHw5dFk3fNxJ8M+8q7BxzkBJhmoPm++7 mEkoWgNf0IuQBGKCxF2ZLPGScdFU0tLEtE1TQ= 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:content-transfer-encoding; b=EqSQhHeISzn+n6Nm+3uBIw9WUIDeVFGA3FevTcMBoyoMRuv+j1FG3SJigcGVvZQxyM NPme6bjOrJ/y3LERppqU5q1GU2yiLQ+9cskBWophm3Qxw9trldmWKR3l/atTNAdyZyzo +LyXhvQhUdAbod27eG4et/1ID55bFZwRH73RY= MIME-Version: 1.0 Received: by 10.229.185.1 with SMTP id cm1mr5263190qcb.81.1295389738683; Tue, 18 Jan 2011 14:28:58 -0800 (PST) Received: by 10.229.102.87 with HTTP; Tue, 18 Jan 2011 14:28:58 -0800 (PST) In-Reply-To: References: Date: Wed, 19 Jan 2011 01:28:58 +0300 Message-ID: From: Sergey Kandaurov To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hardware@freebsd.org Subject: Re: IBM / LSI disk card & 10 Gbit broadcom NIC not detected X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2011 22:57:12 -0000 On 18 January 2011 21:29, Ivan Voras wrote: > Hi, > > I have a bleeding edge machine here with new hardware, unrecognized by > FreeBSD (stable and current). The RAID controller is a LSI/IBM-rebranded > product and the 10 gbit NICs are Broadcom's. > > I'd be interested in a (very) quick solution, especially for the disk > driver, otherwise I'll have to (quickly) install something else on the > server. > > > none2@pci0:3:0:0: =A0 =A0 =A0 class=3D0x010400 card=3D0x03b11014 chip=3D0= x00731000 Hi. LSI itself identifies that h/w with chip=3D0x00731000 as "Drake Skinny". As per my conversation with Scott Long some time ago, "the current driver i= n FreeBSD will work adequately for every MegaRAID SAS card except the "Skinny= " and "Drake" models. There are some serious bugs in the code provided by LSI= . First, they assume that only one adapter will be present in the system, and store per-instance data in a set of global variables." I don't know personally if something has changes since then. --=20 wbr, pluknet From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 23:09:29 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF7411065675 for ; Tue, 18 Jan 2011 23:09:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 52BD88FC0A for ; Tue, 18 Jan 2011 23:09:29 +0000 (UTC) Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by qmta03.emeryville.ca.mail.comcast.net with comcast id x1Jk1f0040FhH24A3AwJN4; Tue, 18 Jan 2011 22:56:18 +0000 Received: from koitsu.dyndns.org ([98.248.34.134]) by omta08.emeryville.ca.mail.comcast.net with comcast id xAwH1f00a2tehsa8UAwJde; Tue, 18 Jan 2011 22:56:18 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C3F979B422; Tue, 18 Jan 2011 14:56:17 -0800 (PST) Date: Tue, 18 Jan 2011 14:56:17 -0800 From: Jeremy Chadwick To: Steve Polyack Message-ID: <20110118225617.GA16727@icarus.home.lan> References: <4D3608BD.7010604@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D3608BD.7010604@comcast.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable , User Questions , freebsd-hardware@freebsd.org Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2011 23:09:29 -0000 On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: > > We've recently upgraded a few desktop workstations from Dell > Optiplex 960s to Optiplex 980s. We were running FreeBSD > 8.1-RELEASE. The migration was performed by simply swapping the > drives into the new systems. Immediately after switching people > over, they all began to report bizarre keyboard issues - things like > infinite key repeats (letters, numbers, "enter") for keys they did > not hold down. The key repeats continue indefinitely until another > key is pressed. Occasionally, even mouse input will trigger similar > infinite keyboard input repetition. In addition to the repeat > issue, sometimes physical key-presses are not registered by FreeBSD, > leading to typos and angry developers. > > We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these > systems, and the issue persists. Because of the observed behavior, > I'm thinking that this is due to new hardware in the 980s which > isn't timing or handling interrupts correctly under the FreeBSD > kernel. > > Looking at a 'pciconf -lvb' from each system, I noticed that the 980 > has two USB controllers which probe under ehci(4), while the 960 > (which does not exhibit this problem), enumerates six uhci(4) > controllers and two ehci(4) controllers. To cut to the chase here, > the 960 users' keyboards probe under a USB1.0 uhci(4), while the > 980s only have ehci(4) devices to attach to. > > So, I guess what I'm asking is - has anyone else seen any keyboard > repeat or other USB craziness with ehci(4) ports or otherwise Intel > PCH controllers? Any fellow Optiplex 980 users? I'd be more than > happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the "excessive repeat" behaviour changes: hint.kbdmux.0.disabled="1" It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 08:27:31 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC0CC106566C for ; Wed, 19 Jan 2011 08:27:31 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 93FF48FC0A for ; Wed, 19 Jan 2011 08:27:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PfTO6-0004Rm-9n for freebsd-hardware@freebsd.org; Wed, 19 Jan 2011 09:27:30 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Jan 2011 09:27:30 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Jan 2011 09:27:30 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Wed, 19 Jan 2011 09:27:16 +0100 Lines: 26 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: X-Enigmail-Version: 1.1.2 Subject: Re: IBM / LSI disk card & 10 Gbit broadcom NIC not detected X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 08:27:31 -0000 On 18/01/2011 23:28, Sergey Kandaurov wrote: > On 18 January 2011 21:29, Ivan Voras wrote: >> Hi, >> >> I have a bleeding edge machine here with new hardware, unrecognized by >> FreeBSD (stable and current). The RAID controller is a LSI/IBM-rebranded >> product and the 10 gbit NICs are Broadcom's. >> >> I'd be interested in a (very) quick solution, especially for the disk >> driver, otherwise I'll have to (quickly) install something else on the >> server. >> >> >> none2@pci0:3:0:0: class=0x010400 card=0x03b11014 chip=0x00731000 > > Hi. > > LSI itself identifies that h/w with chip=0x00731000 as "Drake Skinny". > As per my conversation with Scott Long some time ago, "the current driver in > FreeBSD will work adequately for every MegaRAID SAS card except the "Skinny" > and "Drake" models. There are some serious bugs in the code provided by LSI. > First, they assume that only one adapter will be present in the system, and > store per-instance data in a set of global variables." Wait, LSI provides FreeBSD reference code? :)) From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 13:52:38 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16BAB106564A for ; Wed, 19 Jan 2011 13:52:38 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx03.pub.collaborativefusion.com (mx03.pub.collaborativefusion.com [206.83.220.142]) by mx1.freebsd.org (Postfix) with ESMTP id E502F8FC0A for ; Wed, 19 Jan 2011 13:52:37 +0000 (UTC) Received: from Internal Mail-Server by mx03 (envelope-from korvus@comcast.net) with SMTP; 19 Jan 2011 08:46:54 -0500 Message-ID: <4D36ECA2.5080204@comcast.net> Date: Wed, 19 Jan 2011 08:52:34 -0500 From: Steve Polyack User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101109 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Jeremy Chadwick References: <4D3608BD.7010604@comcast.net> <20110118225617.GA16727@icarus.home.lan> <4D36EB91.1050406@comcast.net> In-Reply-To: <4D36EB91.1050406@comcast.net> Content-Type: multipart/mixed; boundary="------------060306010205010009040206" Cc: freebsd-stable , User Questions , freebsd-hardware@freebsd.org Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 13:52:38 -0000 This is a multi-part message in MIME format. --------------060306010205010009040206 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/19/11 08:48, Steve Polyack wrote: > On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: >> On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: >>> We've recently upgraded a few desktop workstations from Dell >>> Optiplex 960s to Optiplex 980s. We were running FreeBSD >>> 8.1-RELEASE. The migration was performed by simply swapping the >>> drives into the new systems. Immediately after switching people >>> over, they all began to report bizarre keyboard issues - things like >>> infinite key repeats (letters, numbers, "enter") for keys they did >>> not hold down. The key repeats continue indefinitely until another >>> key is pressed. Occasionally, even mouse input will trigger similar >>> infinite keyboard input repetition. In addition to the repeat >>> issue, sometimes physical key-presses are not registered by FreeBSD, >>> leading to typos and angry developers. >>> >>> We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these >>> systems, and the issue persists. Because of the observed behavior, >>> I'm thinking that this is due to new hardware in the 980s which >>> isn't timing or handling interrupts correctly under the FreeBSD >>> kernel. >>> >>> Looking at a 'pciconf -lvb' from each system, I noticed that the 980 >>> has two USB controllers which probe under ehci(4), while the 960 >>> (which does not exhibit this problem), enumerates six uhci(4) >>> controllers and two ehci(4) controllers. To cut to the chase here, >>> the 960 users' keyboards probe under a USB1.0 uhci(4), while the >>> 980s only have ehci(4) devices to attach to. >>> >>> So, I guess what I'm asking is - has anyone else seen any keyboard >>> repeat or other USB craziness with ehci(4) ports or otherwise Intel >>> PCH controllers? Any fellow Optiplex 980 users? I'd be more than >>> happy to provide pciconf or other output if requested. >> Try adding the following to /boot/loader.conf then reboot and see if >> the "excessive repeat" behaviour changes: >> >> hint.kbdmux.0.disabled="1" >> >> It would also help if you would state exactly what brand/model of >> keyboard is used. Yes, believe it or not, it matters. dmesg output >> would be helpful in this case. >> > The keyboard is also a Dell model - model KB1421, or listed as "Dell > QuiteKey Keyboard" under dmesg. The same keyboard does not exhibit > the strange behavior when used with the older model of tower (Optiplex > 960). > > I'll reboot today with the loader.conf hint you provided. I'll let > you guys know if it helps. Thanks! > I forgot to attach my dmesg - here it is! --------------060306010205010009040206 Content-Type: text/plain; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RC2 #1: Mon Jan 17 12:10:53 EST 2011 root@galvatron:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2660.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106e5 Family = 6 Model = 1e Stepping = 5 Features=0xbfebfbff Features2=0x98e3fd AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4082315264 (3893 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 3.0 on pci0 pci1: on pcib1 vgapci0: port 0xdc80-0xdcff mem 0xf6000000-0xf6ffffff,0xe0000000-0xefffffff,0xf0000000-0xf1ffffff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io nvidia0: [ITHREAD] hdac0: mem 0xf7dfc000-0xf7dfffff irq 17 at device 0.1 on pci1 hdac0: HDA Driver Revision: 20100226_0142 hdac0: [ITHREAD] pci0: at device 8.0 (no driver attached) pci0: at device 8.1 (no driver attached) pci0: at device 8.2 (no driver attached) pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) em0: port 0xecc0-0xecdf mem 0xf7fe0000-0xf7ffffff,0xf7fdc000-0xf7fdcfff irq 21 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 84:2b:2b:a5:d0:45 ehci0: mem 0xf7fdd000-0xf7fdd3ff irq 16 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 hdac1: mem 0xff87c000-0xff87ffff irq 16 at device 27.0 on pci0 hdac1: HDA Driver Revision: 20100226_0142 hdac1: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 ehci1: mem 0xf7fde000-0xf7fde3ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus1: EHCI version 1.0 usbus1: on ehci1 pcib4: at device 30.0 on pci0 pci4: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem 0xff870000-0xff8707ff irq 18 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier supported with FBS ahcich0: at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: at channel 4 on ahci0 ahcich4: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 atrtc0: port 0x70-0x7f irq 8 on acpi0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 plip0: on ppbus0 plip0: [ITHREAD] lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 uart0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] orm0: at iomem 0xc0000-0xcdfff,0xce000-0xcffff,0xd0000-0xd27ff,0xd2800-0xd3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 est2: on cpu2 p4tcc2: on cpu2 est3: on cpu3 p4tcc3: on cpu3 ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version 4 ZFS storage pool version 15 RTC BIOS diagnostic error 11 Timecounters tick every 1.000 msec vboxdrv: fAsync=0 offMin=0x120 offMax=0x3c0 hdac0: HDA Codec #0: NVidia (Unknown) hdac0: HDA Codec #1: NVidia (Unknown) hdac0: HDA Codec #2: NVidia (Unknown) hdac0: HDA Codec #3: NVidia (Unknown) usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 1 nid 1 on hdac0 pcm2: at cad 2 nid 1 on hdac0 pcm3: at cad 3 nid 1 on hdac0 hdac1: HDA Codec #0: Realtek ALC269 pcm4: at cad 0 nid 1 on hdac1 pcm5: at cad 0 nid 1 on hdac1 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C) ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: ATA-7 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 152587MB (312500000 512 byte sectors: 16H 63S/T 16383C) cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closedlapic6: Forcing LINT1 to edge trigger SMP: AP CPU #3 Launched! lapic4: Forcing LINT1 to edge trigger SMP: AP CPU #2 Launched! lapic2: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! Root mount waiting for: usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 uhub2: on usbus0 ugen1.2: at usbus1 uhub3: on usbus1 Root mount waiting for: usbus1 usbus0 uhub2: 6 ports with 6 removable, self powered uhub3: 8 ports with 8 removable, self powered ugen0.3: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x4001 Root mount waiting for: usbus1 usbus0 ugen1.3: at usbus1 uhub4: on usbus1 uhub4: 4 ports with 4 removable, self powered umass0:5:0:-1: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus5 target 0 lun 1 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 scbus5 target 0 lun 2 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 scbus5 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present ugen1.4: at usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 Root mount waiting for: usbus1 ugen1.5: at usbus1 ums0: on usbus1 ums0: 5 buttons and [XYZ] coordinates ID=0 ugen1.6: at usbus1 ukbd0: on usbus1 kbd2 at ukbd0 Trying to mount root from ufs:/dev/ada0s1a --------------060306010205010009040206-- From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 14:00:56 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BD7B10656B1 for ; Wed, 19 Jan 2011 14:00:56 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id 5CFBD8FC26 for ; Wed, 19 Jan 2011 14:00:56 +0000 (UTC) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta01.westchester.pa.mail.comcast.net with comcast id xRF51f00227AodY51Rnhbr; Wed, 19 Jan 2011 13:47:41 +0000 Received: from [10.0.0.79] ([71.199.122.142]) by omta19.westchester.pa.mail.comcast.net with comcast id xRnh1f01Y34Sj4f3fRnhmC; Wed, 19 Jan 2011 13:47:41 +0000 Message-ID: <4D36EB91.1050406@comcast.net> Date: Wed, 19 Jan 2011 08:48:01 -0500 From: Steve Polyack User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jeremy Chadwick References: <4D3608BD.7010604@comcast.net> <20110118225617.GA16727@icarus.home.lan> In-Reply-To: <20110118225617.GA16727@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable , User Questions , freebsd-hardware@freebsd.org Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 14:00:56 -0000 On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: > On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: >> We've recently upgraded a few desktop workstations from Dell >> Optiplex 960s to Optiplex 980s. We were running FreeBSD >> 8.1-RELEASE. The migration was performed by simply swapping the >> drives into the new systems. Immediately after switching people >> over, they all began to report bizarre keyboard issues - things like >> infinite key repeats (letters, numbers, "enter") for keys they did >> not hold down. The key repeats continue indefinitely until another >> key is pressed. Occasionally, even mouse input will trigger similar >> infinite keyboard input repetition. In addition to the repeat >> issue, sometimes physical key-presses are not registered by FreeBSD, >> leading to typos and angry developers. >> >> We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these >> systems, and the issue persists. Because of the observed behavior, >> I'm thinking that this is due to new hardware in the 980s which >> isn't timing or handling interrupts correctly under the FreeBSD >> kernel. >> >> Looking at a 'pciconf -lvb' from each system, I noticed that the 980 >> has two USB controllers which probe under ehci(4), while the 960 >> (which does not exhibit this problem), enumerates six uhci(4) >> controllers and two ehci(4) controllers. To cut to the chase here, >> the 960 users' keyboards probe under a USB1.0 uhci(4), while the >> 980s only have ehci(4) devices to attach to. >> >> So, I guess what I'm asking is - has anyone else seen any keyboard >> repeat or other USB craziness with ehci(4) ports or otherwise Intel >> PCH controllers? Any fellow Optiplex 980 users? I'd be more than >> happy to provide pciconf or other output if requested. > Try adding the following to /boot/loader.conf then reboot and see if > the "excessive repeat" behaviour changes: > > hint.kbdmux.0.disabled="1" > > It would also help if you would state exactly what brand/model of > keyboard is used. Yes, believe it or not, it matters. dmesg output > would be helpful in this case. > The keyboard is also a Dell model - model KB1421, or listed as "Dell QuiteKey Keyboard" under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 14:51:43 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C612A106566C for ; Wed, 19 Jan 2011 14:51:43 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx03.pub.collaborativefusion.com (mx03.pub.collaborativefusion.com [206.83.220.142]) by mx1.freebsd.org (Postfix) with ESMTP id A49838FC31 for ; Wed, 19 Jan 2011 14:51:43 +0000 (UTC) Received: from Internal Mail-Server by mx03 (envelope-from korvus@comcast.net) with SMTP; 19 Jan 2011 09:46:00 -0500 Message-ID: <4D36FA7D.1030503@comcast.net> Date: Wed, 19 Jan 2011 09:51:41 -0500 From: Steve Polyack User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101109 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: Jeremy Chadwick References: <4D3608BD.7010604@comcast.net> <20110118225617.GA16727@icarus.home.lan> <4D36EB91.1050406@comcast.net> In-Reply-To: <4D36EB91.1050406@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable , User Questions , freebsd-hardware@freebsd.org Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 14:51:44 -0000 On 01/19/11 08:48, Steve Polyack wrote: > On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: >> On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: >>> We've recently upgraded a few desktop workstations from Dell >>> Optiplex 960s to Optiplex 980s. We were running FreeBSD >>> 8.1-RELEASE. The migration was performed by simply swapping the >>> drives into the new systems. Immediately after switching people >>> over, they all began to report bizarre keyboard issues - things like >>> infinite key repeats (letters, numbers, "enter") for keys they did >>> not hold down. The key repeats continue indefinitely until another >>> key is pressed. Occasionally, even mouse input will trigger similar >>> infinite keyboard input repetition. In addition to the repeat >>> issue, sometimes physical key-presses are not registered by FreeBSD, >>> leading to typos and angry developers. >>> >>> We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these >>> systems, and the issue persists. Because of the observed behavior, >>> I'm thinking that this is due to new hardware in the 980s which >>> isn't timing or handling interrupts correctly under the FreeBSD >>> kernel. >>> >>> Looking at a 'pciconf -lvb' from each system, I noticed that the 980 >>> has two USB controllers which probe under ehci(4), while the 960 >>> (which does not exhibit this problem), enumerates six uhci(4) >>> controllers and two ehci(4) controllers. To cut to the chase here, >>> the 960 users' keyboards probe under a USB1.0 uhci(4), while the >>> 980s only have ehci(4) devices to attach to. >>> >>> So, I guess what I'm asking is - has anyone else seen any keyboard >>> repeat or other USB craziness with ehci(4) ports or otherwise Intel >>> PCH controllers? Any fellow Optiplex 980 users? I'd be more than >>> happy to provide pciconf or other output if requested. >> Try adding the following to /boot/loader.conf then reboot and see if >> the "excessive repeat" behaviour changes: >> >> hint.kbdmux.0.disabled="1" >> >> It would also help if you would state exactly what brand/model of >> keyboard is used. Yes, believe it or not, it matters. dmesg output >> would be helpful in this case. >> > The keyboard is also a Dell model - model KB1421, or listed as "Dell > QuiteKey Keyboard" under dmesg. The same keyboard does not exhibit > the strange behavior when used with the older model of tower (Optiplex > 960). > > I'll reboot today with the loader.conf hint you provided. I'll let > you guys know if it helps. Thanks! > The problem still exists with the kbdmux.0.disabled hint. It definitely took effect, as there is no longer a /dev/kbdmux0, and dmesg lists the refusal to register the kbdmux module. Any other ideas? We've tried playing with the hw.usb.ehci.lostinrbug and hw.usb.ehci.no_hs sysctls, but they don't make a difference either. Looking at the ehci(4) man page, this sticks out at me: BUGS The driver is not finished and is quite buggy. There is currently no support for isochronous transfers. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 15:04:38 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59B2A106566C; Wed, 19 Jan 2011 15:04:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.c2i.net [212.247.154.2]) by mx1.freebsd.org (Postfix) with ESMTP id 787808FC19; Wed, 19 Jan 2011 15:04:37 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=A4HDTGXxjEDC1UuJ6rl8GMp0zaXu4XgXPL1dbujgs48= c=1 sm=1 a=XTUqBGVsqOAA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=l_Y0fWRYadet1y9gK_0A:9 a=RwtVsJ-TxpBShPIPgmwA:7 a=RmbvT1dXn1wWusJJl8Vx2HMxa8oA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 76974602; Wed, 19 Jan 2011 16:04:33 +0100 From: Hans Petter Selasky To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2011 16:04:35 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <4D3608BD.7010604@comcast.net> <4D36EB91.1050406@comcast.net> <4D36FA7D.1030503@comcast.net> In-Reply-To: <4D36FA7D.1030503@comcast.net> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201101191604.35867.hselasky@c2i.net> Cc: freebsd-stable , Steve Polyack , Jeremy Chadwick , User Questions Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 15:04:38 -0000 On Wednesday 19 January 2011 15:51:41 Steve Polyack wrote: > On 01/19/11 08:48, Steve Polyack wrote: > > On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: > >> On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: > >>> We've recently upgraded a few desktop workstations from Dell > >>> Optiplex 960s to Optiplex 980s. We were running FreeBSD > >>> 8.1-RELEASE. The migration was performed by simply swapping the > >>> drives into the new systems. Immediately after switching people > >>> over, they all began to report bizarre keyboard issues - things like > >>> infinite key repeats (letters, numbers, "enter") for keys they did > >>> not hold down. The key repeats continue indefinitely until another > >>> key is pressed. Occasionally, even mouse input will trigger similar > >>> infinite keyboard input repetition. In addition to the repeat > >>> issue, sometimes physical key-presses are not registered by FreeBSD, > >>> leading to typos and angry developers. > >>> > >>> We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these > >>> systems, and the issue persists. Because of the observed behavior, > >>> I'm thinking that this is due to new hardware in the 980s which > >>> isn't timing or handling interrupts correctly under the FreeBSD > >>> kernel. > >>> > >>> Looking at a 'pciconf -lvb' from each system, I noticed that the 980 > >>> has two USB controllers which probe under ehci(4), while the 960 > >>> (which does not exhibit this problem), enumerates six uhci(4) > >>> controllers and two ehci(4) controllers. To cut to the chase here, > >>> the 960 users' keyboards probe under a USB1.0 uhci(4), while the > >>> 980s only have ehci(4) devices to attach to. > >>> > >>> So, I guess what I'm asking is - has anyone else seen any keyboard > >>> repeat or other USB craziness with ehci(4) ports or otherwise Intel > >>> PCH controllers? Any fellow Optiplex 980 users? I'd be more than > >>> happy to provide pciconf or other output if requested. > >> > >> Try adding the following to /boot/loader.conf then reboot and see if > >> the "excessive repeat" behaviour changes: > >> > >> hint.kbdmux.0.disabled="1" > >> > >> It would also help if you would state exactly what brand/model of > >> keyboard is used. Yes, believe it or not, it matters. dmesg output > >> would be helpful in this case. > > > > The keyboard is also a Dell model - model KB1421, or listed as "Dell > > QuiteKey Keyboard" under dmesg. The same keyboard does not exhibit > > the strange behavior when used with the older model of tower (Optiplex > > 960). > > > > I'll reboot today with the loader.conf hint you provided. I'll let > > > > you guys know if it helps. Thanks! > > The problem still exists with the kbdmux.0.disabled hint. It definitely > took effect, as there is no longer a /dev/kbdmux0, and dmesg lists the > refusal to register the kbdmux module. Any other ideas? We've tried > playing with the hw.usb.ehci.lostinrbug and hw.usb.ehci.no_hs sysctls, > but they don't make a difference either. > > Looking at the ehci(4) man page, this sticks out at me: > BUGS > The driver is not finished and is quite buggy. > > There is currently no support for isochronous transfers. For FreeBSD 8+ this is not true. Probably the manpage has not been updated. Hence you are seeing a different number of UHCI controllers, this looks like an ACPI problem. USB keyboards usually require a UHCI to enumerate. The EHCI can only enumerate High Speed devices. --HPS From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 00:43:45 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF7FF1065695 for ; Fri, 21 Jan 2011 00:43:45 +0000 (UTC) (envelope-from Rick.van.Hattem@fawo.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.freebsd.org (Postfix) with ESMTP id F15378FC1B for ; Fri, 21 Jan 2011 00:43:44 +0000 (UTC) Received: from lappie.localnet (g27041.upc-g.chello.nl [80.57.27.41]) (authenticated bits=0) by smtp-vbr4.xs4all.nl (8.13.8/8.13.8) with ESMTP id p0L0O47Q023869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Jan 2011 01:24:09 +0100 (CET) (envelope-from Rick.van.Hattem@fawo.nl) From: Rick van Hattem To: freebsd-hardware@freebsd.org Date: Fri, 21 Jan 2011 01:23:57 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.35-24-generic-pae; KDE/4.5.1; i686; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1624433.Keim91nXfQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101210124.02738.Rick.van.Hattem@fawo.nl> X-Virus-Scanned: by XS4ALL Virus Scanner X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Regular garbled data on console and failing igb0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 00:43:46 -0000 --nextPart1624433.Keim91nXfQ Content-Type: multipart/mixed; boundary="Boundary-01=_eINON4LFaYyUEWI" Content-Transfer-Encoding: 7bit --Boundary-01=_eINON4LFaYyUEWI Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, A couple of weeks ago I installed FreeBSD 8.2RC1 on a new machine (8.1 was= =20 having issues with the raid card, since 8.2 is nearly final I figured... wh= y=20 not). The machine has been running smoothly for a while, even while load- testing the harddrives and network for more than 24 hours. Since everything was running smoothly I decided to move one of the producti= on=20 PostgreSQL databases to this machine. However... after a couple of hours I = got=20 the following error from the iDRAC: PCIE Fatal Err: Critical Event sensor, bus fatal error (Slot 3) was asserted =46ollowed by a lot of garbled text in the console (see the full log in the= =20 attachment) and immediately this message: Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA N2M0I, I ESIASNA Mff2 =46ollowed by this: Jan 20 21:09:38 sh4 kernel: igb0: Watchdog timeout -- resetting Jan 20 21:09:38 sh4 kernel: igb0: Queue(0) tdh =3D 944, hw tdt =3D 945 Jan 20 21:09:38 sh4 kernel: igb0: TX(0) desc avail =3D 1023,Next TX to Clea= n =3D=20 944 Jan 20 21:09:38 sh4 kernel: igb0: link state changed to DOWN Jan 20 21:09:41 sh4 kernel: igb0: link state changed to UP After which the lagg0 interface (which is using igb0 and igb1 as an lacp=20 trunk) marks the igb0 interface as down. After a while the second interface= =20 got the same issue which caused the lagg0 interface to become non-functiona= l=20 and the server unreachable. This error looks quite a bit like the one talked about in this thread:=20 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D81462+0+/usr/local/www/db/te= xt/2010/freebsd- net/20100801.freebsd-net But the given solution there (disabling polling) won't help because I don't= =20 even have device polling enabled in the kernel. =46or the record, the machine regularly shows small amounts of garbled text= even=20 outside of these network interface crashes as can be seen in the "garbled.l= og"=20 file. The real crash starts at 21:09:24 according to the iDRAC log. My kernel config is mainly stock, some modules disabled. DEVICE_POLLING is not enabled. The garbled text should be caused by the print buffer since I do have=20 PRINTF_BUFR_SIZE=3D128 in the config. Thanks in advance for any help. ~rick --Boundary-01=_eINON4LFaYyUEWI-- --nextPart1624433.Keim91nXfQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk040h4ACgkQ25UAkonD6zxvxgCgz324PHg5lkIeNpqq/sbOzQ/A 9jYAoM4uTeb3uCkHO4u8jfR8IDbQZUCH =Z0Sa -----END PGP SIGNATURE----- --nextPart1624433.Keim91nXfQ-- From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 00:55:20 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62F0F106564A for ; Fri, 21 Jan 2011 00:55:20 +0000 (UTC) (envelope-from Rick.van.Hattem@fawo.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.freebsd.org (Postfix) with ESMTP id DEFEC8FC0C for ; Fri, 21 Jan 2011 00:55:19 +0000 (UTC) Received: from lappie.localnet (g27041.upc-g.chello.nl [80.57.27.41]) (authenticated bits=0) by smtp-vbr14.xs4all.nl (8.13.8/8.13.8) with ESMTP id p0L0tDNa080972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Jan 2011 01:55:18 +0100 (CET) (envelope-from Rick.van.Hattem@fawo.nl) From: Rick van Hattem To: freebsd-hardware@freebsd.org Date: Fri, 21 Jan 2011 01:55:07 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.35-24-generic-pae; KDE/4.5.1; i686; ; ) References: <201101210124.02738.Rick.van.Hattem@fawo.nl> In-Reply-To: <201101210124.02738.Rick.van.Hattem@fawo.nl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart16005729.mEXxVpXs2B"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101210155.11270.Rick.van.Hattem@fawo.nl> X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Regular garbled data on console and failing igb0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 00:55:20 -0000 --nextPart16005729.mEXxVpXs2B Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Friday 21 January 2011 01:23:57 Rick van Hattem wrote: > Hi, >=20 > A couple of weeks ago I installed FreeBSD 8.2RC1 on a new machine (8.1 was > having issues with the raid card, since 8.2 is nearly final I figured... > why not). The machine has been running smoothly for a while, even while > load- testing the harddrives and network for more than 24 hours. I forgot that attachments and mailing lists don't work together ;) The specs: Type: Dell R815 CPU: 4x Opteron 6134 Ram: 16x 8GB DDR3 1333 Raid card: Perc H700 Network cards: Broadcom NetXtreme II BCM5709 1000Base-T (4 port, currently unused) Intel(R) PRO/1000 Network Connection version - 2.0.7 (dual port) Some of the garbled logs: Jan 20 19:18:03 sh4 kernel: 74 Jan 20 19:30:03 sh4 kernel: 71 Jan 20 19:30:03 sh4 kernel:=20 Jan 20 19:30:03 sh4 kernel: <1<10>1.110:05292>4 09:55.21709.28 894.513.91:7= 406.854.1 3i9n: v9i95 ai nv lvaina3 0v Jan 20 19:30:03 sh4 kernel: l Jan 20 19:39:03 sh4 kernel: 0 Jan 20 19:42:03 sh4 kernel: 9 Jan 20 19:44:36 sh4 kernel: mfi0: 1999 (348864277s/0x0008/info) - Battery c= harge complete Jan 20 19:45:03 sh4 kernel: v Jan 20 19:48:03 sh4 kernel: 8. Jan 20 19:48:03 sh4 kernel:=20 Jan 20 19:48:03 sh4 kernel: <1<11100>4>.117309.:844.6153 9i:n vi9a93 ivnl = an3v0ia=20 Jan 20 19:48:03 sh4 kernel: v Jan 20 19:51:03 sh4 kernel: 9: Jan 20 20:09:27 sh4 kernel: ichwd module loaded Jan 20 20:09:27 sh4 kernel: ipmi1: on isa0 Jan 20 20:09:27 sh4 kernel: device_attach: ipmi1 attach returned 16 Jan 20 20:10:48 sh4 kernel: ichwd module unloaded Jan 20 20:33:03 sh4 kernel: 3 Jan 20 21:07:04 sh4 kernel: <11<0>i110p>fiwpf:w :6 500605 D0e0n0y DTeCnPy = 8T0C.P6 98.06.7.169.06:76.1000:9630 09955. 19750..1708.48.41.31399::49695 = 3i ni nv=20 ivaia vvllaann330 Jan 20 21:07:04 sh4 kernel: 0 Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA N2M0I, I ESIASNA Mff2 Jan 20 21:09:25 sh4 kernel: 0 Jan 20 21:09:25 sh4 kernel: <2 Jan 20 21:09:25 sh4 kernel: N<<>M,22N>I> NMI EMNI. IIN MN.NIM SINNINMM.SNII= AMSNNM NMII ANM S NINIAMMNMININ gNM N MIIIAfM NSIMMINI MIIoIMM I2SI2 IN = fIIAM MS IIISSiSI=20 ISI 0AI 0 I Jan 20 21:09:25 sh4 kernel: I2IIAS AIAA n AS, S2,IIIS Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: N Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 last message repeated 10 times Jan 20 21:09:25 sh4 kernel: g Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: << Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 last message repeated 2 times Jan 20 21:09:25 sh4 kernel: <<2>2>22>= >22>t222>>>>>>>>>>A0>>S> > >> >I So > A I2IA ,SAIISA.ES2AS 2=20 S0023S3 E2 A. NSAS IA=20 Jan 20 21:09:25 sh4 kernel: A0A0dAE3,,000I 03N . A3AS3, 3 ,e, I0 ,,, S033= 02 A0 0 b2 2SE,gE2 A Jan 20 21:09:25 sh4 kernel: ,200,0 E,3E,EEu00 AI oI0EE 0,, ,fI 0IS ISIg,,E = Ei ,II f, EfS2222I22222>22>>22>>>= 2>2o>><>> Jan 20 21:09:25 sh4 kernel: >>E> > >SS>>>E>IS >> f SIfS.SIAA=20 Jan 20 21:09:25 sh4 kernel: IAISfNAIfAfdfffSA.AS =20 Jan 20 21:09:25 sh4 kernel: ffS Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: N Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: M Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 last message repeated 3 times Jan 20 21:09:25 sh4 kernel: 22e Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: . Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: << Jan 20 21:09:25 sh4 kernel: << Jan 20 21:09:25 sh4 kernel: <<< Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel: < 222 Jan 20 21:09:25 sh4 kernel: >>2>>>>>22u>2>> g>>>ff>> >.A S>fS>> Jan 20 21:09:25 sh4 kernel: gf> =20 Jan 20 21:09:25 sh4 kernel: Af Affof Jan 20 21:09:25 sh4 kernel: .f. fAf Jan 20 21:09:25 sh4 kernel: I222M>Ig2>>>gI>2>2= 2>2> Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: I>>>> g of> Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: I> Jan 20 21:09:25 sh4 kernel: >f f > f N ffo.iffff=20 Jan 20 21:09:25 sh4 kernel: .. Jan 20 21:09:25 sh4 kernel: t Jan 20 21:09:25 sh4 kernel: ffNfMN.Nf Jan 20 21:09:25 sh4 kernel: i Jan 20 21:09:25 sh4 kernel: <.n Jan 20 21:09:25 sh4 kernel: .< Jan 20 21:09:25 sh4 kernel: f<..ofn Jan 20 21:09:25 sh4 kernel: 2MfI2M.2M Jan 20 21:09:25 sh4 kernel: N.g.N Jan 20 21:09:25 sh4 kernel: .N>N. > Jan 20 21:09:25 sh4 kernel: >gI Jan 20 21:09:25 sh4 kernel: N I..I.g.> oooo<>IM>=20 Jan 20 21:09:25 sh4 kernel: Mgo. b. Jan 20 21:09:25 sh4 kernel: .o2 Jan 20 21:09:25 sh4 kernel: ..i ii I.Io ...>u N.N.i.>..Nndnn f. id ..ggM.M = n. ..Mgegg. Jan 20 21:09:25 sh4 kernel: ..neg.goI .Igg.g.I b eN .gboo ig o. tutti= ggrMn..I uiIgog.tgi .ogoonooIg. tgnoio.o onig. gg ogi .ggini. di gnno..deo= d t e Jan 20 21:09:25 sh4 kernel: ngn dent ggi.g erriedotg ggbgeot ong.bnb Jan 20 21:09:25 sh4 kernel: e Mo< t ou b ottigo ugubd totigtud oeon igg gud= o ongooged b egtngtgdg< ge igbedudb ogedoeegd rdneubegeut ree=20 rbetegrgubgbgodtbbdour bgguueug eougue gteggrgedb gggbdgo Jan 20 21:09:25 sh4 kernel: regegr udgeguee2rebedgeeregbr>rgurebrrgu2>IA>I IIS SAI2A S0A , EI22S300A0 ,,, f EEIfEI Jan 20 21:09:25 sh4 kernel: ISS Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 kernel: < Jan 20 21:09:25 sh4 kernel: <M>AS2IA > Af.f .fff Jan 20 21:09:25 sh4 kernel: . Jan 20 21:09:25 sh4 kernel: f=20 Jan 20 21:09:25 sh4 kernel: g<2oN>Ni Jan 20 21:09:25 sh4 kernel: MnIgMN IM. t.I.o.. ..d .e .gbgou oiginggnoegi= r ngtg o tt ood eddbeeubgbugugeggregrer Jan 20 21:09:25 sh4 kernel:=20 Jan 20 21:09:25 sh4 last message repeated 30 times Jan 20 21:09:38 sh4 kernel: igb0: Watchdog timeout -- resetting Jan 20 21:09:38 sh4 kernel: igb0: Queue(0) tdh =3D 944, hw tdt =3D 945 Jan 20 21:09:38 sh4 kernel: igb0: TX(0) desc avail =3D 1023,Next TX to Clea= n =3D 944 Jan 20 21:09:38 sh4 kernel: igb0: link state changed to DOWN Jan 20 21:09:41 sh4 kernel: igb0: link state changed to UP ~rick --nextPart16005729.mEXxVpXs2B Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk042WsACgkQ25UAkonD6zxnHwCfX1I3TVv8F5jtUWbvuJp64eBX NU8An2PEXAGCafyRBllfdDWIs1kYaaZe =frkD -----END PGP SIGNATURE----- --nextPart16005729.mEXxVpXs2B-- From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 09:21:43 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9382C1065670; Fri, 21 Jan 2011 09:21:43 +0000 (UTC) (envelope-from jan.koum@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0D41F8FC0A; Fri, 21 Jan 2011 09:21:42 +0000 (UTC) Received: by qyk36 with SMTP id 36so1504999qyk.13 for ; Fri, 21 Jan 2011 01:21:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ltGeUY4YQGVssVWWTNGNKhFLyvYA0g+PaaNj40t0GpM=; b=wwBmQMGX/RdGxtigd4h6c/abjdpSLAzbqFHPJ1wtsAXT/5MAfJpRGyQRxRCC2yPMMx wX1IwPvjq87u2Y6f1HD/AHBKbx12b2ZDSFozKlaZLNmI7o9CFB4M3Q03bV3N40IVfOY2 Io0Mld/l+bksGYMHv/izOXasnAa6iuUzGBBA0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=oZJHpFPXTqbqGhWdvwg8IFzrP+F/i6z594pcBgugEPpJhiUEVPf63T2cB/rbOVA0HK tXbjO8HGVkY2mG0YcjyrBRvWulxh6djLO1a3TTv2nH4IYHmQsB4EKwEHMVELCGZpR4pl ErKYSHd6aP+DzWMYoU0x5u+aonsgjM+ixPZ2s= MIME-Version: 1.0 Received: by 10.229.81.12 with SMTP id v12mr389841qck.132.1295601702129; Fri, 21 Jan 2011 01:21:42 -0800 (PST) Sender: jan.koum@gmail.com Received: by 10.229.241.211 with HTTP; Fri, 21 Jan 2011 01:21:42 -0800 (PST) In-Reply-To: <4D2C636B.5040003@sentex.net> References: <1290533941.3173.50.camel@home-yahoo> <4CEC0548.1080801@sentex.net> <4D2C636B.5040003@sentex.net> Date: Fri, 21 Jan 2011 01:21:42 -0800 X-Google-Sender-Auth: I7GFIa1SqtQFCkpYjIN6devPe0A Message-ID: From: Jan Koum To: Mike Tancsa , Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-net@freebsd.org" , Sean Bruno , Ivan Voras , "freebsd-hardware@freebsd.org" Subject: Re: em driver, 82574L chip, and possibly ASPM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 09:21:43 -0000 On Tue, Jan 11, 2011 at 6:04 AM, Mike Tancsa wrote: > On 12/24/2010 5:44 PM, Jan Koum wrote: > > hi Ivan and Mike, > > > > wanted to follow up and see if you found a solid long-term solution to > this > > bug. we are still seeing this problem in our 8.2 environment with ASPM > > already disabled. here is what we have: > > > > 1. motherboard is SuperMicro X8SIE-LN4F Intel Xeon: > > > > Hi Jack, > Looks like this problem is not completely gone :( Dear Mike and Jack, sadly the problem is not gone for us either. here is what we know so far: - we are running latest e1000 drivers from 8.2 - we have ASPM disabled and we have the following bios settings: http://camel.ethereal.net/~jkb/bios/ - we have updated our BIOS and IPMI to the latest firmware available from our ISP - we added hw.em.rxd=4096 and hw.em.txd=4096 to loader.conf (thanks Sean for this tip -- these settings made problem happen much less frequently but didn't go away completely) the ONLY thing sort of saving our butts right now is this cron job that runs every minute: if /sbin/ping -q -c 10 www.google.com> /dev/null; then echo "OK" >> /tmp/em1.out else date >> /tmp/em1.out echo "broken" >> /tmp/em1.out /sbin/ifconfig em1 down sleep 3 /sbin/ifconfig em1 up fi this is obviously no way to run a high performance web servers in a long term. as mentioned in my previous emails, let us know if you need any further information or if you have any debug code you want us to run in production. we are willing to do pretty much anything to get this issue fixed thanks From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 11:16:41 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E3041065672 for ; Fri, 21 Jan 2011 11:16:41 +0000 (UTC) (envelope-from Rick.van.Hattem@fawo.nl) Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by mx1.freebsd.org (Postfix) with ESMTP id B66408FC1A for ; Fri, 21 Jan 2011 11:16:40 +0000 (UTC) Received: from lappie.localnet (a83-163-234-86.adsl.xs4all.nl [83.163.234.86]) (authenticated bits=0) by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id p0LBGYGM069805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Jan 2011 12:16:39 +0100 (CET) (envelope-from Rick.van.Hattem@fawo.nl) From: Rick van Hattem To: freebsd-hardware@freebsd.org Date: Fri, 21 Jan 2011 12:16:29 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.35-24-generic-pae; KDE/4.5.1; i686; ; ) References: <201101210124.02738.Rick.van.Hattem@fawo.nl> In-Reply-To: <201101210124.02738.Rick.van.Hattem@fawo.nl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1405649.ig1KPUUhXq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101211216.31970.Rick.van.Hattem@fawo.nl> X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Regular garbled data on console and failing igb0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 11:16:41 -0000 --nextPart1405649.ig1KPUUhXq Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable The original message without the attachments: A couple of weeks ago I installed FreeBSD 8.2RC1 on a new machine (8.1 was= =20 having issues with the raid card, since 8.2 is nearly final I figured... wh= y=20 not). The machine has been running smoothly for a while, even while load- testing the harddrives and network for more than 24 hours. Since everything was running smoothly I decided to move one of the producti= on=20 PostgreSQL databases to this machine. However... after a couple of hours I = got=20 the following error from the iDRAC: PCIE Fatal Err: Critical Event sensor, bus fatal error (Slot 3) was asserted =46ollowed by a lot of garbled text in the console (see the full log in the= =20 attachment) and immediately this message: Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA 30, EISA ff Jan 20 21:09:25 sh4 kernel: NMI ... going to debugger Jan 20 21:09:25 sh4 kernel: NMI ISA N2M0I, I ESIASNA Mff2 =46ollowed by this: Jan 20 21:09:38 sh4 kernel: igb0: Watchdog timeout -- resetting Jan 20 21:09:38 sh4 kernel: igb0: Queue(0) tdh =3D 944, hw tdt =3D 945 Jan 20 21:09:38 sh4 kernel: igb0: TX(0) desc avail =3D 1023,Next TX to Clea= n =3D=20 944 Jan 20 21:09:38 sh4 kernel: igb0: link state changed to DOWN Jan 20 21:09:41 sh4 kernel: igb0: link state changed to UP After which the lagg0 interface (which is using igb0 and igb1 as an lacp=20 trunk) marks the igb0 interface as down. After a while the second interface= =20 got the same issue which caused the lagg0 interface to become non-functiona= l=20 and the server unreachable. This error looks quite a bit like the one talked about in this thread:=20 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D81462+0+/usr/local/www/db/te= xt/2010/freebsd- net/20100801.freebsd-net But the given solution there (disabling polling) won't help because I don't= =20 even have device polling enabled in the kernel. =46or the record, the machine regularly shows small amounts of garbled text= even=20 outside of these network interface crashes as can be seen in the "garbled.l= og"=20 file. The real crash starts at 21:09:24 according to the iDRAC log. My kernel config is mainly stock, some modules disabled. DEVICE_POLLING is not enabled. The garbled text should be caused by the print buffer since I do have=20 PRINTF_BUFR_SIZE=3D128 in the config. Thanks in advance for any help. ~rick --nextPart1405649.ig1KPUUhXq Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk05aw0ACgkQ25UAkonD6zxjlgCgms+1osjwIcA2cjTRCuvB8W0d EHIAoIg1D/dQxhTgG5d4xYZq5a58o05w =DviF -----END PGP SIGNATURE----- --nextPart1405649.ig1KPUUhXq-- From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 19:38:09 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05E94106564A for ; Sat, 22 Jan 2011 19:38:09 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 811968FC08 for ; Sat, 22 Jan 2011 19:38:08 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PgjHj-0003cw-4Q for freebsd-hardware@freebsd.org; Sat, 22 Jan 2011 20:38:07 +0100 Received: from 89-164-107-17.dsl.iskon.hr ([89.164.107.17]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Jan 2011 20:38:07 +0100 Received: from ivoras by 89-164-107-17.dsl.iskon.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Jan 2011 20:38:07 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Sat, 22 Jan 2011 20:37:55 +0100 Lines: 44 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 89-164-107-17.dsl.iskon.hr User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 In-Reply-To: Subject: Re: IBM / LSI disk card & 10 Gbit broadcom NIC not detected X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2011 19:38:09 -0000 On 18.1.2011 19:29, Ivan Voras wrote: > Hi, > > I have a bleeding edge machine here with new hardware, unrecognized by > FreeBSD (stable and current). The RAID controller is a LSI/IBM-rebranded > product and the 10 gbit NICs are Broadcom's. > > I'd be interested in a (very) quick solution, especially for the disk > driver, otherwise I'll have to (quickly) install something else on the > server. FWIW, Ubuntu 10.04 and CentOS 5.5 support both controllers. > none2@pci0:3:0:0: class=0x010400 card=0x03b11014 chip=0x00731000 > rev=0x03 hdr=0x00 > class = mass storage > subclass = RAID > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 10[68] = PCI-Express 2 endpoint max data 128(4096) link x8(x8) > cap 03[d0] = VPD > cap 05[a8] = MSI supports 1 message, 64 bit > cap 11[c0] = MSI-X supports 15 messages in map 0x14 > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0004[138] = unknown 1 > none3@pci0:4:0:0: class=0x020000 card=0xe62910df chip=0x070019a2 > rev=0x02 hdr=0x00 > class = network > subclass = ethernet > cap 01[40] = powerspec 3 supports D0 D3 current D0 > cap 11[48] = MSI-X supports 32 messages in map 0x14 > cap 10[c0] = PCI-Express 2 endpoint max data 128(512) link x8(x8) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0003[194] = Serial 1 0000c9fffea9585c > none4@pci0:4:0:1: class=0x020000 card=0xe62910df chip=0x070019a2 > rev=0x02 hdr=0x00 > class = network > subclass = ethernet > cap 01[40] = powerspec 3 supports D0 D3 current D0 > cap 11[48] = MSI-X supports 32 messages in map 0x14 > cap 10[c0] = PCI-Express 2 endpoint max data 128(512) link x8(x8) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0003[194] = Serial 1 0000c9fffea9585c