From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 4 18:53:25 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E14F16A41F for ; Tue, 4 Oct 2005 18:53:25 +0000 (GMT) (envelope-from malachid@gmail.com) Received: from qproxy.gmail.com (qproxy.gmail.com [72.14.204.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AD2643D45 for ; Tue, 4 Oct 2005 18:53:23 +0000 (GMT) (envelope-from malachid@gmail.com) Received: by qproxy.gmail.com with SMTP id p32so313385qba for ; Tue, 04 Oct 2005 11:53:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=PLKnEAlRaY0zQjM4T6bi9RVPIsk0Sg2hNZc36wzaQe+DiOhcRuD+8lm6joixqoKI2/1e/v2fbf2i096MDI6O88ZQOoTbImst7XCykkOR/tlNQ2YGr72gVz6yOxIEr6/Q4HJTB7XNiWeJsJWa8ZM/D0/FdADmnQfVwyDBCK+9gPs= Received: by 10.65.159.1 with SMTP id l1mr3261566qbo; Tue, 04 Oct 2005 11:27:24 -0700 (PDT) Received: by 10.65.84.18 with HTTP; Tue, 4 Oct 2005 11:27:23 -0700 (PDT) Message-ID: Date: Tue, 4 Oct 2005 11:27:23 -0700 From: =?ISO-8859-1?Q?Malachi_de_=C6lfweald?= To: =?ISO-8859-1?Q?Tulio_Guimar=E3es_da_Silva?= In-Reply-To: MIME-Version: 1.0 References: <013701c5c832$68480ec0$856f0b81@bmbpc733> <17217.28509.707672.467147@roam.psg.com> <43429707.5040902@pgt.mpt.gov.br> <4342B9F5.3010301@pgt.mpt.gov.br> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: panic: driver error: busdma dflt_lock called X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Malachi_de_=C6lfweald?= List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 18:53:25 -0000 hmmmm, I went back in and instead of starting over, just tried setting the mount points for the partitions... I notice the two that had a partition name 'X' (last two) are not listed.... maybe I am specificying too many labels? Malachi On 10/4/05, Malachi de =C6lfweald wrote: > > yep, happens exactly the same on disk1 as well > I notice it says that no dump device is defined -- any idea why that > would be? > Mal > > On 10/4/05, Malachi de =C6lfweald wrote: > > > > Hmmm, I did try using the fixit console, but nothing was available. > > Without a console with apps in it, I don't see how to configure the nic= , > > mount anything, dmesg, whatever. > > > > However, I had thought that I was supposed to use bootonly.iso to start > > the installation... Let me try with disc1 and get back to you. > > > > Thanks, > > Malachi > > > > On 10/4/05, Tulio Guimar=E3es da Silva < tuliogs@pgt.mpt.gov.br> wrote= : > > > > > Sorry, I didn=B4t reply to the list; "fixing" this now. :) > > > I don=B4t know if this changed in -6, but up to 5.4 you can take it f= rom > > > the install CD (disc1) itself: configure the NIC, open a "fixit" > > > terminal (for 5.3 and on it=B4s the install cd itself; prior to that, > > > it=B4s > > > the 2nd) and run "dmesg >dmesg.log" and ftp this dmesg.log to some > > > other > > > machine, so that you can attach it. ;) > > > I see you=B4re using bootonly.iso, but does this happen with the full > > > install (disc1) CD? > > > > > > Tulio G. Silva > > > > > > Malachi de =C6lfweald wrote: > > > > > > > how would I run dmesg? This is a fresh install. Even when I do it > > > with > > > > multi-terminal (from boot menu) dmesg isn't installed yet. > > > > > > > > 6.0-BETA5 bootonly.iso > > > > Asus A8N-SLI Premium > > > > nVidia raid controller doing RAID0+1 > > > > 4 hitachi deskstar 250GB SATAII > > > > > > > > Malachi > > > > > > > > On 10/4/05, *Tulio Guimar=E3es da Silva* < tuliogs@pgt.mpt.gov.br > > > > > wrote: > > > > > > > > Doesn=B4t dmesg show anything abnormal? You could try and see if > > > > there=B4s > > > > no error or warining messages, or else attach dmesg=B4s results, so= we > > > > > > > could have any clue. > > > > Or, at least, it would help A LOT to know which version you=B4re > > > > using. ;) > > > > > > > > Tulio G. Silva > > > > > > > > Malachi de =C6lfweald wrote: > > > > > > > > >yeah, it was too bad. say responses to my message and was hopefull= . > > > > > > > > > >oh well. > > > > > > > > > > > > > > >Malachi > > > > > > > > > >On 10/3/05, Randy Bush < randy@psg.com > > > > wrote: > > > > > > > > > > > > > > >>>I have 1/2 a rack spare in IFL1 (Manchester Computing centre in > > > the > > > > >>> > > > > >>> > > > > >>Kilburn > > > > >> > > > > >> > > > > >>>Building, Manchester). I'm slicing it up into 1 and 2U's for > > > > =A325 per > > > > >>> > > > > >>> > > > > >>month > > > > >> > > > > >> > > > > >>>per 1U or =A340 per month for a 2U. This includes 10GB data > > > > transfer per > > > > >>>month. Is anybody interested? Space is limited! > > > > >>> > > > > >>> > > > > >>anyone who would trust their equiment to a spammer is a fool > > > > >> > > > > >>randy > > > > >> > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > freebsd-hardware@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > > To unsubscribe, send any mail to " > > > freebsd-hardware-unsubscribe@freebsd.org" > > > > > > > > >