From owner-freebsd-questions Wed Oct 17 9:11:32 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail-relay1.mirrorimage.net (mail-relay1.mirrorimage.net [209.58.140.11]) by hub.freebsd.org (Postfix) with ESMTP id 6C85A37B408 for ; Wed, 17 Oct 2001 09:11:23 -0700 (PDT) Received: from leblanc.mirrorimage.net (leblanc.mirrorimage.net [209.192.210.146]) by mail-relay1.mirrorimage.net (8.9.3/8.9.3) with ESMTP id MAA21456 for ; Wed, 17 Oct 2001 12:11:22 -0400 Received: (from leblanc@localhost) by leblanc.mirrorimage.net (8.11.6/8.11.4) id f9HGBsu02251 for freebsd-questions@FreeBSD.org; Wed, 17 Oct 2001 12:11:54 -0400 (EDT) (envelope-from leblanc) Date: Wed, 17 Oct 2001 12:11:54 -0400 From: Louis LeBlanc To: freebsd-questions@FreeBSD.org Subject: Security check output questions Message-ID: <20011017121153.A2196@acadia.ne.mediaone.net> Reply-To: freebsd-questions@FreeBSD.org Mail-Followup-To: freebsd-questions@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.22.1i X-bright-idea: Lets abolish HTML mail! Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey folks. I know it's improper to ask multiple questions in a single message, especially unrelated, but please indulge me here. I found the following in my security check output mail message: > Oct 16 13:56:25 leblanc /kernel: pid 86613 (cheetah), uid 118: exited on signal 11 (core dumped) > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Now, the first is just one of many I get from the multitude of xscreensaver dumps. I am always having to clean up the *.core files from the various screensaver programs that just dump for whatever reason. Anyone know of a way to *prevent* these dumps? Other than the obvious "don't run xscreensaver" or "don't run the random screensavers". The random screensavers is my FAVORITE part of the xscreensaver. Failing any real solution, I'll probably just continue to clean out the cores. Maybe even search the ports archives for any references. The next two concern me a bit more than the screensaver cores. Quite a bit more. I haven't a clue what the problem here is, but ad0 is my only hard drive, so write failures are a bit concerning. And what does "non-ATA66 compliant cable" mean? The system is a Cyber Computer Technology system. Here are some dmesg entries that may be relevant: . . . atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 . . . ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 17206MB [34960/16/63] at ata0-master UDMA33 acd0: CDROM at ata0-slave using PIO4 afd0: 120MB [963/8/32] at ata1-master using PIO3 . . . ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable . . . Any ideas? TIA & HAND Lou -- Louis LeBlanc leblanc@acadia.ne.mediaone.net Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ The nation that controls magnetism controls the universe. -- Chester Gould/Dick Tracy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message