From owner-freebsd-current Tue Jan 14 13:42:36 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A29F37B401 for ; Tue, 14 Jan 2003 13:42:34 -0800 (PST) Received: from hotmail.com (oe55.law10.hotmail.com [64.4.14.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id B82F143ED8 for ; Tue, 14 Jan 2003 13:42:33 -0800 (PST) (envelope-from coercitas@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 14 Jan 2003 13:42:33 -0800 X-Originating-IP: [212.198.0.93] From: "Coercitas Temet'Nosce" To: "Steve Kargl" Cc: "Francis Barnhart" , "Kevin Oberman" , "Nate Lawson" , "FreeBSD current users" References: <20030114181040.2BFBF5D04@ptavv.es.net> <20030114205556.GB5746@troutmask.apl.washington.edu> Subject: Re: Problem with RC3 Date: Tue, 14 Jan 2003 22:42:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 14 Jan 2003 21:42:33.0640 (UTC) FILETIME=[D8BD1280:01C2BC15] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, problem solved... Thanx for your notes, it helped a lot. For thse who may wonder, I simply changed 2 parameters : hw.pci.enable_io_modes Enable PCI resources which are left off by some BIOSes or are not enabled correctly by the device driver. Tunable value set to ON (1) by default, but this may cause problems with some peripherals. hw.pci_allow_unsupported_io_range Allow the PCI bridge to pass through an unsupported memory range assigned by the BIOS. Tunable value set to OFF (0) by default. can't say exactly which one prevented me from crash (surely 1st one but didn't tried any further). Dunno if it would be possible to prevent such things to happen by simply test it, I guess testing it will crash the whole system too. Thanx all btw, I learn, I learn :o) ----- Original Message ----- From: "Steve Kargl" To: "Coercitas Temet'Nosce" Cc: "Francis Barnhart" ; "Kevin Oberman" ; "Nate Lawson" ; "FreeBSD current users" Sent: Tuesday, January 14, 2003 9:55 PM Subject: Re: Problem with RC3 > On Tue, Jan 14, 2003 at 09:52:10PM +0100, Coercitas Temet'Nosce wrote: > > > > Thanx all for your messages, I think I start to figure how it is handled. > > Problem still exists, system still hangs at "agp0: > bridge> mem 0xf0000000-0xf3ffffff at device 0.0 on pci0" but I think it is > > in this way I may find a solution. Is there by chance anyway to see what > > will be load or not simply hitting SPACEBAR at prompt ? I didn't find any > > place where it is discussed nor a way to see the "set" variables that will > > be used to boot. > > > > lsdev and lsmod show the devices that can be loaded and > the deviced currently loaded, respectively. > > -- > Steve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message