From owner-freebsd-current Fri Oct 15 14:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 1639615294 for ; Fri, 15 Oct 1999 14:59:15 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA80319 for ; Fri, 15 Oct 1999 16:59:15 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Fri, 15 Oct 1999 16:58:15 -0500 (CDT) From: David Scheidt To: Khetan Gajjar Subject: Re: Can't make crashdump after panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Oct 1999, Khetan Gajjar wrote: > > Looks like we have our problem; it's the ATA driver. I don't recall > seeing this error when using the wd driver. Yup. When I force a panic from DDB, I get panic: timeout table full and a message about "Dump already in progress, bailing". I haven't yet looked at them dump, to see whats in it. This doesn't happen with wd driver. Relevent bits of my dmesg: SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 DANGER wait_intr active=ATA_IGNORE_INTR ad1: ATA-? disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM unknown medium, unlocked Waiting 15 seconds for SCSI devices to settle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message