From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 17 13:20:01 2006 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD7E716A405 for ; Mon, 17 Apr 2006 13:20:01 +0000 (UTC) (envelope-from jparsons@sutv.com) Received: from mars.sutv.com (sutv.com [63.173.36.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8D0A43D48 for ; Mon, 17 Apr 2006 13:20:00 +0000 (GMT) (envelope-from jparsons@sutv.com) Received: from jparsons (sutvfirewall.sutv.com [63.173.36.6]) by mars.sutv.com (Postfix) with ESMTP id 7AAAD40269 for ; Mon, 17 Apr 2006 08:16:44 -0500 (CDT) From: "Jaron Parsons" To: Date: Mon, 17 Apr 2006 08:19:59 -0500 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Thread-Index: AcZiIaB82fBBA6gDQUq5k+1hItDV2Q== Message-Id: <20060417131644.7AAAD40269@mars.sutv.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ad4: req=0xc534b258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2006 13:20:02 -0000 Hello, I am currently running 6.1 PRERELEASE#1 however this problem has been haunting me since my initial install of 6.0Beta1 I was thinking of roling back to 5.4 (or 5.5) however in browsing through the posts it seems other have experienced the same on them as well. The problem occurs randomly it seems so far (I am sure there is some kind of trigger but not sure yet what) and happens at least once every week, if not every other day. It is getting annoying. the machine begin scrolling a message similar to the following: ad4: req=0xc534b258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! at which time and can get a login prompt, however after entering the username the machine seems to become unresponsive (at least I have not waited more than 15 minutes ofr it to allow a login) So a hard reset is the only way to recover. It is usually complaining about ad4, however it has complained about ad6 once or twice. I have not yet seen it complain about ad8 or ad10. There are several ACPI errors on boot up, so i have tried disabling ACPI, but it made no difference in this problem. Hardware info: acd0: DMA limited to UDMA33, controller found non-ATA66 cable acd0: DVDR at ata0-master UDMA33 ad4: 76319MB at ata2-master UDMA100 ad6: 76319MB at ata3-master UDMA100 ad8: 286168MB at ata4-master UDMA100 ad10: 286168MB at ata5-master UDMA100 sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) ar0: 76319MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master ar1: 286168MB status: READY ar1: disk0 READY (master) using ad8 at ata4-master ar1: disk1 READY (mirror) using ad10 at ata5-master the motherboard is a TYAN Thunder K7 dual AMD Athlon MP 1600+ 1 GB of DDR Ram I would be happy to supply anymore information needed. Does anyone have any ideas on things I could try to resolve this issue? I got daring and have always been comfortable with FreeBSD so I upgraded this machine to 6, and it is a production Web Hosting Server OOPS I would rather not reinstall it again, but will if rolling back is the only cure. Thank you, Jaron Parsons Network Administrator Sumner Communications