From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 10:08:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EF0C16A4D6 for ; Tue, 28 Oct 2003 10:08:52 -0800 (PST) Received: from cardinal.mail.pas.earthlink.net (cardinal.mail.pas.earthlink.net [207.217.121.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39FF443FF2 for ; Tue, 28 Oct 2003 10:08:49 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from lsanca1-ar6-4-62-200-124.lsanca1.elnk.dsl.genuity.net ([4.62.200.124] helo=netcom1.netcom.com) by cardinal.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1AEYGn-0001x1-00; Tue, 28 Oct 2003 10:08:42 -0800 Received: from localhost (localhost [127.0.0.1]) by netcom1.netcom.com (Postfix) with ESMTP id 14A2F53C8; Tue, 28 Oct 2003 10:08:43 -0800 (PST) Received: from netcom1.netcom.com ([127.0.0.1]) by localhost (netcom1.netcom.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00290-03; Tue, 28 Oct 2003 10:08:38 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by netcom1.netcom.com (Postfix) with ESMTP id 14FFA539E; Tue, 28 Oct 2003 10:08:38 -0800 (PST) From: Mike Harding To: Luoqi Chen In-Reply-To: References: Content-Type: text/plain Message-Id: <1067364517.1457.1.camel@netcom1.netcom.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 28 Oct 2003 10:08:38 -0800 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at ix.netcom.com cc: stable@freebsd.org Subject: RE: Possible mouse/ATA problems in -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 28 Oct 2003 18:08:52 -0000 I rebuilt the world without CPUTYPE=686 and tried again... The CPUTYPE flag doesn't appear to make any difference - a large recursive copy still causes the mouse to lose sync. KB/t is still > 64.00. - Mike H. On Tue, 2003-10-28 at 00:03, Luoqi Chen wrote: > > Sorry if this is confusing - the history, from my end at least, goes > > like this: > > > > - my mouse started getting 'flaky' around Sept. 1. I was get 'psmintr' > > sync errors, and sometimes the mouse would get disabled, necessitating a > > reboot. I have seen the psmintr errors occasionally before, but never > > had the mouse disappear. This started happening right after I saw some > > ATA changes in my cvsup, so I suspect ATA changes, committed (by luoqi) > > on Sept. 5 and after. The mouse had been rock solid for at least a year > > before this. > > - The were some 'mfc' comments in the ATA code specifically in the DMA > > code, sorry to rope Soren into this... the changes don't necessarily > > have anything to do with -current, but the comments on ata-dma.c, rev > > 1.35.2.33 did say MFC. > > - I was suprised to see -any- ATA changes during code slush... > > - The mouse seems to fail during heaving IDE activity, such as when I do > > a release build and the /usr/ports/distfiles gets copied. This is a > > high throughput situation, it's possible that the IDE code is now > > hogging the interrupt. When the mouse gets confused 'systat -vmstat' > > shows a sustained rate of about 100KB/transfer. > > - I do have a 'cursed' VIA 686b motherboard, which has caused mucho > > problems (like silent disk corruption) in the past until I found a bios > > (from Brazil!) that fixed it. This problem may only occur on machines > > like mine, but I did not have a problem until recently. > > > > Sorry to make so much noise right now, I just know that things like this > > tend to get fixed -right after- the release when a bigger population > > actually uses the system. > > > > - Mike H. > > > Mike, I'm looking into this problem now. I'd like to get more info on the > system with the reported problem, /var/run/dmesg.boot and a copy of your > kernel config would be very helpful. I've also have a couple of questions, > 1. You mentioned transfer rate of 100KB/t, this is certainly not archievable > by a single disk, our physical i/o size is limited to 64KB/t. Is this > the sum of more than one disk? Are you using an IDE raid? > 2. At the time you're having mouse trouble, what's the % of cpu time spent > in interrupt as shown in the `systat -vm' window? > 3. Are you using tagged queue? > 4. Is there any chance that your disk(s) were running in PIO mode instead > (maybe as a result of DMA transfer failure)? > 5. I searched the @stable list and saw your postings about jumpy mouse > a month earlier. Is the problem getting worse now? > > Thanks > -lq