From owner-freebsd-current@FreeBSD.ORG Wed Aug 27 10:35:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D34B716A4BF for ; Wed, 27 Aug 2003 10:35:08 -0700 (PDT) Received: from perrin.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54F2E43FF2 for ; Wed, 27 Aug 2003 10:35:06 -0700 (PDT) (envelope-from sean@nxad.com) Received: by perrin.nxad.com (Postfix, from userid 1001) id B569421058; Wed, 27 Aug 2003 10:35:05 -0700 (PDT) Date: Wed, 27 Aug 2003 10:35:05 -0700 From: Sean Chittenden To: freebsd-current@FreeBSD.ORG Message-ID: <20030827173505.GA72378@perrin.nxad.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ User-Agent: Mutt/1.5.4i cc: Soren Schmidt Subject: ata crash when disk io saturated on laptop... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 27 Aug 2003 17:35:08 -0000 I haven't been able to get any kind of a stack trace, but if I run two 'cvs up's at the same time on my laptop (one of /usr/src, the other of /usr/ports), my laptop eventually locks up in what looks like the disk thrashing continually. When I pull the plug and restart, I am only able to find this in the logs: Aug 27 10:05:44 localhost kernel: ad0: READ command timeout tag=0 serv=0 - resetting Aug 27 10:05:44 localhost kernel: ata0: resetting devices .. Aug 27 10:05:44 localhost kernel: done [boot msg follows] I can let my laptop sit for up to 5min grinding away, but caps lock doesn't work, acpi doesn't work, and my drive just cranks away resetting itself as fast as it can (resetting itself frequently given the sounds) in a nasty unbreakable loop. The HDD is a few months old and has been pretty battle proven to date, though I'd never done anything quite this disk intensive. It doesn't happen instantly either, it takes a good 5min or so before the drive begins to stumble. The relevant dmesg info: atapci0: port 0x860-0x86f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 38154MB [77520/16/63] at ata0-master UDMA33 hw.ata.ata_dma: 1 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 0 What's more odd, however, is that I can't reproduce this if I'm not listening to MP3s, it's like the extra interrupts from the snd card push it over the edge in terms of latency and the kernel improperly resets ad0 or resets it incorrectly. Soren, is this something that would be addressed in your recent ATAng commit? :-/ -sc -- Sean Chittenden