From owner-freebsd-questions@FreeBSD.ORG Mon Aug 28 17:08:52 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C99616A4E0 for ; Mon, 28 Aug 2006 17:08:52 +0000 (UTC) (envelope-from stanb@panix.com) Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2297343D80 for ; Mon, 28 Aug 2006 17:08:39 +0000 (GMT) (envelope-from stanb@panix.com) Received: from mailspool3.panix.com (mailspool3.panix.com [166.84.1.78]) by mail2.panix.com (Postfix) with ESMTP id 1337C9D9F2 for ; Mon, 28 Aug 2006 13:08:39 -0400 (EDT) Received: from teddy.fas.com (c-68-58-232-106.hsd1.sc.comcast.net [68.58.232.106]) by mailspool3.panix.com (Postfix) with ESMTP id EB370FB01A2 for ; Mon, 28 Aug 2006 13:08:38 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 1GHkbG-0006Rx-00 for ; Mon, 28 Aug 2006 13:08:38 -0400 Date: Mon, 28 Aug 2006 13:08:38 -0400 From: stan To: Free BSD Questions list Message-ID: <20060828170838.GA24408@teddy.fas.com> Mail-Followup-To: Free BSD Questions list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.23 X-Uptime: 12:57:57 up 133 days, 14:04, 1 user, load average: 0.05, 0.05, 0.01 User-Agent: Mutt/1.5.4i Sender: Stan Brown Subject: VTOBUS FAILED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 17:08:52 -0000 I'm trying to troubleshoot a problem on a Sun Ultra40 with 6.1 STABLE AMD64 on it, that looks like a hardware problem (Signal 10 aborts while compiling a kernel for instance). I have taken the root SATA disk out of this machine, and put it in another similar (but not identical U40). I thought that I would be able to confirm that it is a hardware problem on the first machine by booting off this disk, and repeating the things that failed on the suspect machine. However, with the disk in the 2nd machine, I get the boot menu, and during the kernel's hardware detection phase, it panics with a VTOBUS FAIL message. What's a VTOBUS, and why would this disk not be bootable in the 2nd machine? he 2nd machine has 2 dual core CPU's vs 2 single core in the problematic ones, and it also has a SCSI card in it. The kernel on the disk is most likely a custom one. Is thee a way to try booting from the GENERIC kernel on the disk? -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)