From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 00:20:25 2004 Return-Path: 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 D18A816A4CE for ; Sun, 7 Mar 2004 00:20:25 -0800 (PST) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id D03B343D2D for ; Sun, 7 Mar 2004 00:20:24 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from localhost.invalid (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.10/8.12.10) with ESMTP id i278Cj0w009802; Sun, 7 Mar 2004 09:12:51 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Sun, 7 Mar 2004 09:20:16 +0100 User-Agent: KMail/1.6 References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> In-Reply-To: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200403070920.16107.thierry@herbelot.com> cc: Putinas Piliponis Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 08:20:25 -0000 Le Sunday 07 March 2004 08:10, Putinas Piliponis a écrit : > Hi all, > Is there any serial ata controller which works stable with 5.2.1 or Current > ? I had tried SiI3112A and Intel ICH5 both knocks system to panic or > lockup. ( ICH5 I tried only on 5.2.1-RELEASE , 3112 from yesterday current > and release as well ) Hello, I've got 4 machines at work, with ICH5 and SATA disk drives, running happily under 5.2.1-Rel (3 boxes) and various versions of -Current (last one). This is with a P4P800 motherboard. unfortunately, no dmesg here TfH PS : the -Current has been running a looped "make buildworld" for about a month From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 00:31:59 2004 Return-Path: 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 8456316A4CE for ; Sun, 7 Mar 2004 00:31:59 -0800 (PST) Received: from smtp-out-02.utu.fi (smtp-out-02.utu.fi [130.232.202.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBFF643D1D for ; Sun, 7 Mar 2004 00:31:58 -0800 (PST) (envelope-from yurtesen@ispro.net.tr) Received: from ispro.net.tr (perpetual.yok.utu.fi [130.232.138.155]) by smtp02.mess.utu.fi (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPS id <0HU7009YI6D8EY@smtp02.mess.utu.fi> for current@freebsd.org; Sun, 07 Mar 2004 10:31:56 +0200 (EET) Date: Sun, 07 Mar 2004 10:32:08 +0200 From: Evren Yurtesen In-reply-to: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> To: Putinas Piliponis Message-id: <404ADE08.5040500@ispro.net.tr> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808 References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> cc: current@freebsd.org Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 08:31:59 -0000 Putinas Piliponis wrote: > Hi all, > Is there any serial ata controller which works stable with 5.2.1 or Current ? > I had tried SiI3112A and Intel ICH5 both knocks system to panic or lockup. > ( ICH5 I tried only on 5.2.1-RELEASE , 3112 from yesterday current and release as well ) ICH5 works fine. I also used one integrated ViA. If ICH5 is crashing, you should maybe check from the bios SATA settings. I got it working by disabling the 'enchanced mode' off for ich5. Evren From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 01:19:54 2004 Return-Path: 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 F29E916A4CE for ; Sun, 7 Mar 2004 01:19:53 -0800 (PST) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2027043D39 for ; Sun, 7 Mar 2004 01:19:53 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from localhost.invalid (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.10/8.12.10) with ESMTP id i279CK0w027028; Sun, 7 Mar 2004 10:12:20 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Sun, 7 Mar 2004 10:19:51 +0100 User-Agent: KMail/1.6 References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> <404ADE08.5040500@ispro.net.tr> In-Reply-To: <404ADE08.5040500@ispro.net.tr> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200403071019.51285.thierry@herbelot.com> cc: Evren Yurtesen cc: Putinas Piliponis Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 09:19:54 -0000 Le Sunday 07 March 2004 09:32, Evren Yurtesen a écrit : > ICH5 works fine. I also used one integrated ViA. > > If ICH5 is crashing, you should maybe check from the bios SATA settings. > I got it working by disabling the 'enchanced mode' off for ich5. Hello, I have the ICH5 working with both compatibility mode or enjanced "native" mode, with good success (may be there's a problem with some disk brands) TfH From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 01:28:02 2004 Return-Path: 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 671D516A4CE for ; Sun, 7 Mar 2004 01:28:02 -0800 (PST) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99B2C43D2F for ; Sun, 7 Mar 2004 01:28:01 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from localhost.invalid (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.10/8.12.10) with ESMTP id i279KL0w004669; Sun, 7 Mar 2004 10:20:21 +0100 (CET) From: Thierry Herbelot To: Putinas Piliponis Date: Sun, 7 Mar 2004 10:27:52 +0100 User-Agent: KMail/1.6 References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> <200403070920.16107.thierry@herbelot.com> <20040307083034.GA99622@freebsd.icnspot.net> In-Reply-To: <20040307083034.GA99622@freebsd.icnspot.net> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200403071027.52044.thierry@herbelot.com> cc: current ML Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 09:28:02 -0000 Le Sunday 07 March 2004 09:30, vous avez écrit : > Intresting, I have same motherboard ( ok, +Deluxe ) > and I have tried all the possible settings, with HTT enabled/disabled, > with apic on/off .. > any special tricks you did ? > what bios revision you have ? I do not remember of any special trick : just the BIOS defaults (with compatibility mode or enhanced mode), and I kept IOAPIC and ACPI, in both the BIOS and FreeBSD. I have only disabled SMP on some machines, as the network stack is not yet SMP-aware, and there is a *huge* penalty when running network applications (I can get up to 75MByts/s FTP transfer rate when SMP is disabled, compared to around 6MByte/s with SMP enabled, all with nge-type NICs) TfH PS : please keep the -current address in the CC, or else I'll have to send you a bill for consulting charges ;-)) From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 02:02:51 2004 Return-Path: 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 4FC7616A4CE for ; Sun, 7 Mar 2004 02:02:51 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA79843D2D for ; Sun, 7 Mar 2004 02:02:50 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i27A2WQx034502; Sun, 7 Mar 2004 05:02:32 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i27A2Wfn034499; Sun, 7 Mar 2004 05:02:32 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 7 Mar 2004 05:02:32 -0500 (EST) From: Andre Guibert de Bruet To: Vincent Poy In-Reply-To: <20040306204553.H8264-100000@oahu.WURLDLINK.NET> Message-ID: <20040307044641.C21071@alpha.siliconlandmark.com> References: <20040306204553.H8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:02:51 -0000 On Sat, 6 Mar 2004, Vincent Poy wrote: > On Sat, 6 Mar 2004, Vincent Poy wrote: > > It seems to do it on the dump of /usr and restoring to /mnt/usr. > > I have tried the following but they panic the kernel as soon as the memory > > size is displayed. > > > > added to kernel config: > > options VM_KMEM_SIZE_MAX=(768*1048576) > > options VM_KMEM_SIZE_SCALE=2 > > > > Tried it on a kernel without the above but added in /boot/loader.conf > > > > vm.kmem_size=429391872 > > > > and they both crashed at the same spot as well... > > > > CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.60GHz (2592.36-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > > > Features=0xbfebf9ff > AT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > real memory = 2147360768 (2047 MB) > > avail memory = 2095669248 (1998 MB) > > > > Any ideas how to fix this? > > I managed to get the system not panicing on bootup if I set the > VM_KMEM_SIZE_MAX to 384MB. At 512MB and 768MB, it would panic but anyone > knows what the default VM_KMEM_SIZE_MAX size is? That's the maximum amount of KMEM that your system can have. Let's say for example that you have a system with 4GB of RAM. You set VM_KMEM_SIZE_MAX to 1GB but VM_KMEM_SIZE_SCALE to 8 you get: VM_KMEM_SIZE_MAX: 1024 MB of KMEM VM_KMEM_SIZE_SCALE: 512 MB of KMEM (4096/8) The algorithm uses the lesser of these two numbers. Remember that a whole lot of things use the allocated memory so don't skimp! If you don't want to use the memory in your system, take it out and set it on the desk. ;-) I've found through personal experience and endless hours of experimenting on fairly busy machines that the following values work for the various RAM configurations (Lower values may also work depending upon disk, net and load): RAM KMEM size 4.0GB 768MB 3.5GB 768MB 3.0GB 512MB 2.5GB 384MB 2.0GB 384MB 1.5GB and below 256MB As with everything, backup your data, put on your fire-retarding suit, and YMMV. :-) Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 02:18:35 2004 Return-Path: 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 CABBB16A4CE for ; Sun, 7 Mar 2004 02:18:35 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EB5543D1D for ; Sun, 7 Mar 2004 02:18:35 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i27AHjqQ080885; Sun, 7 Mar 2004 00:17:56 -1000 (HST) Received: from localhost (vince@localhost)i27AHjiO080882; Sun, 7 Mar 2004 00:17:45 -1000 (HST) Date: Sun, 7 Mar 2004 00:17:45 -1000 (HST) From: Vincent Poy To: Andre Guibert de Bruet In-Reply-To: <20040307044641.C21071@alpha.siliconlandmark.com> Message-ID: <20040307000926.F8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:18:36 -0000 On Sun, 7 Mar 2004, Andre Guibert de Bruet wrote: > On Sat, 6 Mar 2004, Vincent Poy wrote: > > On Sat, 6 Mar 2004, Vincent Poy wrote: > > > It seems to do it on the dump of /usr and restoring to /mnt/usr. > > > I have tried the following but they panic the kernel as soon as the memory > > > size is displayed. > > > > > > added to kernel config: > > > options VM_KMEM_SIZE_MAX=(768*1048576) > > > options VM_KMEM_SIZE_SCALE=2 > > > > > > Tried it on a kernel without the above but added in /boot/loader.conf > > > > > > vm.kmem_size=429391872 > > > > > > and they both crashed at the same spot as well... > > > > > > CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.60GHz (2592.36-MHz 686-class CPU) > > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > > > > > Features=0xbfebf9ff > > AT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > > real memory = 2147360768 (2047 MB) > > > avail memory = 2095669248 (1998 MB) > > > > > > Any ideas how to fix this? > > > > I managed to get the system not panicing on bootup if I set the > > VM_KMEM_SIZE_MAX to 384MB. At 512MB and 768MB, it would panic but anyone > > knows what the default VM_KMEM_SIZE_MAX size is? > > That's the maximum amount of KMEM that your system can have. Let's say for > example that you have a system with 4GB of RAM. You set VM_KMEM_SIZE_MAX > to 1GB but VM_KMEM_SIZE_SCALE to 8 you get: > > VM_KMEM_SIZE_MAX: 1024 MB of KMEM > VM_KMEM_SIZE_SCALE: 512 MB of KMEM (4096/8) > > The algorithm uses the lesser of these two numbers. Remember that a whole > lot of things use the allocated memory so don't skimp! If you don't want > to use the memory in your system, take it out and set it on the desk. ;-) Okay, here's a dumb question. If it uses the less of the two numbers, is there a reason to need to even define the VM_KMEM_SIZE_SCALE since wouldn't by default, it be 1/3rd of your RAM anyways? > I've found through personal experience and endless hours of experimenting > on fairly busy machines that the following values work for the various RAM > configurations (Lower values may also work depending upon disk, net and > load): > > RAM KMEM size > 4.0GB 768MB > 3.5GB 768MB > 3.0GB 512MB > 2.5GB 384MB > 2.0GB 384MB > 1.5GB and below 256MB You're right that anything above 384MB using a scale of 2, the kernel would panic as soon as the Real Memory is posted in the boot. Did this problem actually exist recently because prior to February 28, I was on a September 26, 2003 -CURRENT and it has not had the problem. I'm using maxusers=512 in the kernel as well as 65536 NMBCLUSTERS, it used to be 32768 but I thought that was what was causing the panic. > As with everything, backup your data, put on your fire-retarding suit, and > YMMV. :-) Nah, the kernel one doesn't require backing up the data since the only reason I get the panic is because I'm dumping both / and /usr to another identical drive. It's only doing the /boot/loader.conf variable for kmem that's scary. ;) Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:01:34 2004 Return-Path: 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 9271716A4CE for ; Sun, 7 Mar 2004 03:01:34 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F057143D2F for ; Sun, 7 Mar 2004 03:01:33 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i27B1Ir1034682; Sun, 7 Mar 2004 06:01:18 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i27B1Id1034679; Sun, 7 Mar 2004 06:01:18 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 7 Mar 2004 06:01:18 -0500 (EST) From: Andre Guibert de Bruet To: Vincent Poy In-Reply-To: <20040307000926.F8264-100000@oahu.WURLDLINK.NET> Message-ID: <20040307052158.D21071@alpha.siliconlandmark.com> References: <20040307000926.F8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:01:34 -0000 On Sun, 7 Mar 2004, Vincent Poy wrote: > On Sun, 7 Mar 2004, Andre Guibert de Bruet wrote: > > On Sat, 6 Mar 2004, Vincent Poy wrote: > > > > > > I managed to get the system not panicing on bootup if I set the > > > VM_KMEM_SIZE_MAX to 384MB. At 512MB and 768MB, it would panic but anyone > > > knows what the default VM_KMEM_SIZE_MAX size is? > > > > That's the maximum amount of KMEM that your system can have. Let's say for > > example that you have a system with 4GB of RAM. You set VM_KMEM_SIZE_MAX > > to 1GB but VM_KMEM_SIZE_SCALE to 8 you get: > > > > VM_KMEM_SIZE_MAX: 1024 MB of KMEM > > VM_KMEM_SIZE_SCALE: 512 MB of KMEM (4096/8) > > > > The algorithm uses the lesser of these two numbers. Remember that a whole > > lot of things use the allocated memory so don't skimp! If you don't want > > to use the memory in your system, take it out and set it on the desk. ;-) > > Okay, here's a dumb question. If it uses the less of the two > numbers, is there a reason to need to even define the VM_KMEM_SIZE_SCALE > since wouldn't by default, it be 1/3rd of your RAM anyways? The SCALE value is there to protect in the case of systems that might have memory amounts that change. If you had a set value for your KMEM which is larger than the amount of memory available when RAM is pulled out, your kernel would surely not boot. For short, the SCALE value lets you get creative with the size assigned to your KMEM. You might find the following mail interesting: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2003-06/1599.html > > I've found through personal experience and endless hours of experimenting > > on fairly busy machines that the following values work for the various RAM > > configurations (Lower values may also work depending upon disk, net and > > load): > > > > RAM KMEM size > > 4.0GB 768MB > > 3.5GB 768MB > > 3.0GB 512MB > > 2.5GB 384MB > > 2.0GB 384MB > > 1.5GB and below 256MB > > You're right that anything above 384MB using a scale of 2, the > kernel would panic as soon as the Real Memory is posted in the boot. Did > this problem actually exist recently because prior to February 28, I was > on a September 26, 2003 -CURRENT and it has not had the problem. I'm > using maxusers=512 in the kernel as well as 65536 NMBCLUSTERS, it used to > be 32768 but I thought that was what was causing the panic. This problem has been around since at least June of last year, which is the date that I first had a test system with more than 1GB running CURRENT (All my production systems still track STABLE). > > As with everything, backup your data, put on your fire-retarding suit, and > > YMMV. :-) > > Nah, the kernel one doesn't require backing up the data since the > only reason I get the panic is because I'm dumping both / and /usr to > another identical drive. It's only doing the /boot/loader.conf variable > for kmem that's scary. ;) Loader tunables for this type of thing scare me too. I guess we're just old school... Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:11:11 2004 Return-Path: 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 954A916A4CE for ; Sun, 7 Mar 2004 03:11:11 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E74143D1D for ; Sun, 7 Mar 2004 03:11:11 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i27BAug0034764; Sun, 7 Mar 2004 06:10:56 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i27BAuGv034761; Sun, 7 Mar 2004 06:10:56 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 7 Mar 2004 06:10:56 -0500 (EST) From: Andre Guibert de Bruet To: Doug White In-Reply-To: <20040305120154.L31036@carver.gumbysoft.com> Message-ID: <20040307060227.I21071@alpha.siliconlandmark.com> References: <4048AC8A.4060809@valdosta.edu> <20040305120154.L31036@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org cc: Nick Nelson Subject: Re: 5.2.1 Unbootable on my Hardware X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:11:11 -0000 On Fri, 5 Mar 2004, Doug White wrote: > On Fri, 5 Mar 2004, Nick Nelson wrote: > > > Hi folks, > > > > I've recently tried to install 5.2.1 on a new system of mine, basically > > it's an AMD 3000XP, Radeon9800 Pro, Corsair XMS RAM, Lanparty Ultra II > > (http://www.dfi.com.tw/Product/xx_product_spec_details_r_us.jsp?PRODUCT_ID=1524) > > with a SerialATA (Marvell 88i8030 chip), I have one SerialATA drive and > > one IDE drive. > > The Marvell chip is the SATA bridge, not the ATA controller. Its probably > the standard built-in nForce 2 ATA controller. > > > I've tried booting off both the SATA drive and the IDE drive, each time > > it gets to: > > > > --- > > > > Timecounters tick every 10.000 msec > > lo0: bpf attached > > > > --- > > > > and stops..I ran it with logging to get that much information. I've > > unplugged the SerialATA, which I thought would resolve it, but didn't. > > Any ideas? > > Hm ... try booting without ACPI, and if that doesn't work, try safe mode. > Looks like the controller is locking up or something... This hang could be ULE-related. I'm saying this because it's the exact same thing that I see when I try a ULE kernel on my Dual Athlon 2000+ MP running on a Asus A7M266-D using regular ATA133 disks. Luckily, it's been tracking current since before the switchover, so I run a custom generic with 4BSD in it and everything works fine. I wish I could offer more debugging information such a verbose boot or a ddb ps when it hangs but I'm swamped with work from my job and cannot seem to find the time to debug such problems. My suggestion to Nick: Try booting an older release (5.1, maybe?) and cvsup from there. Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:13:23 2004 Return-Path: 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 B0E1F16A4CE for ; Sun, 7 Mar 2004 03:13:23 -0800 (PST) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C2343D2F for ; Sun, 7 Mar 2004 03:13:23 -0800 (PST) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) i27BD7Ng1336034; Sun, 7 Mar 2004 12:13:15 +0100 Date: Sun, 7 Mar 2004 12:13:03 +0100 (CET) From: Lukas Ertl To: "Daniel O'Connor" In-Reply-To: <200403071526.46219.doconnor@gsoft.com.au> Message-ID: <20040307121054.T624@korben.in.tern> References: <200403071526.46219.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mailbox 4243; Body=0 Fuz1=0 Fuz2=0 cc: freebsd-current@FreeBSD.org Subject: Re: LCD Brightness control via sysctl.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:13:23 -0000 On Sun, 7 Mar 2004, Daniel O'Connor wrote: > I tried the acpi-vid patch earlier and have now updated my kernel to grab the > committed version, but I still don't see any brightness sysctls :( > > I don't understand how I can have a .active entry for a display but > no .brightness (after looking at the code). Your DSDT is missing the relevant methods, like _BCL and _BCM. It's the same here, I can see which display is active, but I can't control brightness. regards, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:26:12 2004 Return-Path: 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 1828C16A4CE for ; Sun, 7 Mar 2004 03:26:12 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 56F5343D31 for ; Sun, 7 Mar 2004 03:26:11 -0800 (PST) (envelope-from dhke@gmx.net) Received: (qmail 29976 invoked by uid 65534); 7 Mar 2004 11:26:09 -0000 Received: from p5091DF83.dip.t-dialin.net (EHLO peter.home.wul) (80.145.223.131) by mail.gmx.net (mp005) with SMTP; 07 Mar 2004 12:26:09 +0100 X-Authenticated: #14354366 Received: (qmail 7775 invoked by uid 1001); 7 Mar 2004 10:59:26 -0000 Date: Sun, 7 Mar 2004 11:59:26 +0100 From: Peter Wullinger To: freebsd-current@freebsd.org Message-ID: <20040307105926.GA755@peter.home.wul> Mail-Followup-To: freebsd-current@freebsd.org, Thomas Quinot References: <20040219204831.GA735@peter.home.wul> <20040226172036.GA88430@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040226172036.GA88430@melusine.cuivre.fr.eu.org> User-Agent: Mutt/1.4.1i cc: Thomas Quinot Subject: Re: timeouts on ATAPI cd-burner X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:26:12 -0000 On Thu, Feb 26, 2004 at 06:20:36PM +0100, Thomas Quinot wrote: > * Peter Wullinger, 2004-02-19 : > > > I have upgraded to 5.2-CURRENT #5 from yesterday, to > > test if the following commit fixes my problem, > > beeing to able to write to an PHILIPS CDRW48P P1.6 > > ATAPI burner using cdrecord: I've upgraded to a new -CURRENT in the meanwhile, but as far a I can tell, the behaviour has not changed. The output below is from a FreeBSD 5.2.1-RELEASE-p1 kernel, (cvs'd from yesterday): I you need more debugging output or other information, please contact me. > > Does burning CDs with burncd work on your setup? > % burncd -f /dev/acd1 -d -e -t -v data image.iso adding type 0x08 file image.iso size 659200 KB 329600 blocks next writeable LBA -150 CUE sheet: 41 00 00 14 00 00 00 00 41 01 01 10 00 00 02 00 41 aa 01 14 00 49 10 32 addr = 0 size = 675020800 blocks = 329600 writing from file image.iso size 659200 KB only wrote -1 of 32768 bytes: Input/output error Hangs for a while, but is interruptible by ^C. Trying it once again (after the camcontrol sequence you suggested below): % ps waxl | grep burncd 0 814 724 0 76 0 1324 556 ATA re D+ v1 0:00.00 burncd -f /dev/acd1 -d -e -t -v data image.iso > Also, when cdrecord hangs, you can try to at least unlock the drive with > the following commands: > > # FLUSH CACHE (abort CD write sequence) > camcontrol cmd 2:1:0 -c 0x35 -v && > # PREVENT/ALLOW MEDIUM REMOVAL > camcontrol cmd 2:1:0 -c 0x1e -v That one hangs, too: % cdrecord -v -dao -dummy image.iso [...] Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is OFF. Sending CUE sheet... Writing pregap for track 1 at -150 % ps waxl | grep camcontrol 0 755 749 0 -8 0 1364 752 cgticb D+ v2 0:00.00 camcontrol cmd 2:0:0 -c 0x35 -v Cheers, Peter From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:33:49 2004 Return-Path: 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 1499516A4CE for ; Sun, 7 Mar 2004 03:33:49 -0800 (PST) Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EF5343D41 for ; Sun, 7 Mar 2004 03:33:48 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.11.7/8.11.6) id i27BXkO18444; Sun, 7 Mar 2004 11:33:46 GMT (envelope-from rb) Message-Id: <6.0.3.0.2.20040307112816.036c9090@gid.co.uk> X-Sender: rbmail@gid.co.uk (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Sun, 07 Mar 2004 11:32:27 +0000 To: "Putinas Piliponis" , From: Bob Bishop In-Reply-To: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:33:49 -0000 Hi, At 07:10 07/03/2004, Putinas Piliponis wrote: >Hi all, >Is there any serial ata controller which works stable with 5.2.1 or Current ? FWIW I've had a Promise PDC20376 SATA150 running a RAID1 array under 5.1R for a guinea pig^W^Wcustomer for 6 months with no problems. -- Bob Bishop +44 (0)118 977 4017 rb@gid.co.uk fax +44 (0)118 989 4254 From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 04:07:36 2004 Return-Path: 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 328EF16A4D0 for ; Sun, 7 Mar 2004 04:07:36 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFA2943D2D for ; Sun, 7 Mar 2004 04:07:35 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i27C6qqQ082586; Sun, 7 Mar 2004 02:06:56 -1000 (HST) Received: from localhost (vince@localhost)i27C6pG6082583; Sun, 7 Mar 2004 02:06:51 -1000 (HST) Date: Sun, 7 Mar 2004 02:06:51 -1000 (HST) From: Vincent Poy To: Andre Guibert de Bruet In-Reply-To: <20040307052158.D21071@alpha.siliconlandmark.com> Message-ID: <20040307020010.N8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 12:07:36 -0000 On Sun, 7 Mar 2004, Andre Guibert de Bruet wrote: > On Sun, 7 Mar 2004, Vincent Poy wrote: > > On Sun, 7 Mar 2004, Andre Guibert de Bruet wrote: > > > On Sat, 6 Mar 2004, Vincent Poy wrote: > > > > > > > > I managed to get the system not panicing on bootup if I set the > > > > VM_KMEM_SIZE_MAX to 384MB. At 512MB and 768MB, it would panic but anyone > > > > knows what the default VM_KMEM_SIZE_MAX size is? > > > > > > That's the maximum amount of KMEM that your system can have. Let's say for > > > example that you have a system with 4GB of RAM. You set VM_KMEM_SIZE_MAX > > > to 1GB but VM_KMEM_SIZE_SCALE to 8 you get: > > > > > > VM_KMEM_SIZE_MAX: 1024 MB of KMEM > > > VM_KMEM_SIZE_SCALE: 512 MB of KMEM (4096/8) > > > > > > The algorithm uses the lesser of these two numbers. Remember that a whole > > > lot of things use the allocated memory so don't skimp! If you don't want > > > to use the memory in your system, take it out and set it on the desk. ;-) > > > > Okay, here's a dumb question. If it uses the less of the two > > numbers, is there a reason to need to even define the VM_KMEM_SIZE_SCALE > > since wouldn't by default, it be 1/3rd of your RAM anyways? > > The SCALE value is there to protect in the case of systems that might have > memory amounts that change. If you had a set value for your KMEM which is > larger than the amount of memory available when RAM is pulled out, your > kernel would surely not boot. For short, the SCALE value lets you get > creative with the size assigned to your KMEM. Yeah but assuming the SCALE value was the default of 3 and you had 768MB of RAM, your SCALE would still be higher than the KMEM undefined which is 200MB. > You might find the following mail interesting: > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2003-06/1599.html Actually, I read that portion already since I saw it in one of your posts in the archives. > > > I've found through personal experience and endless hours of experimenting > > > on fairly busy machines that the following values work for the various RAM > > > configurations (Lower values may also work depending upon disk, net and > > > load): > > > > > > RAM KMEM size > > > 4.0GB 768MB > > > 3.5GB 768MB > > > 3.0GB 512MB > > > 2.5GB 384MB > > > 2.0GB 384MB > > > 1.5GB and below 256MB > > > > You're right that anything above 384MB using a scale of 2, the > > kernel would panic as soon as the Real Memory is posted in the boot. Did > > this problem actually exist recently because prior to February 28, I was > > on a September 26, 2003 -CURRENT and it has not had the problem. I'm > > using maxusers=512 in the kernel as well as 65536 NMBCLUSTERS, it used to > > be 32768 but I thought that was what was causing the panic. > > This problem has been around since at least June of last year, which is > the date that I first had a test system with more than 1GB running CURRENT > (All my production systems still track STABLE). When I searched the lists, it seemed to happen for people in January 2004 and later though. Maybe the problem wasn't as big though. June 14, 2003 was when I first installed -CURRENT on the machine and it originally did have 128MB only but then I got 2 1GB SODIMM's sometime in early September and the last -current I did was September 26 and the system had stayed up for atleast a month until I actually rebooted it. It wasn't until I did a -CURRENT upgrade beginning with the February 28, 2004 -CURRENT that seemed to have this issue. Maybe the newer -CURRENT's are just more sensitive to this problem. Hopefully this problem eventually gets fixed though. > > > As with everything, backup your data, put on your fire-retarding suit, and > > > YMMV. :-) > > > > Nah, the kernel one doesn't require backing up the data since the > > only reason I get the panic is because I'm dumping both / and /usr to > > another identical drive. It's only doing the /boot/loader.conf variable > > for kmem that's scary. ;) > > Loader tunables for this type of thing scare me too. I guess we're just > old school... Yeah, since there is no such thing as loading a /boot/loader.conf.old ;) Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin From owner-freebsd-current@FreeBSD.ORG Sat Mar 6 13:05:44 2004 Return-Path: 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 5EAAE16A4CE; Sat, 6 Mar 2004 13:05:44 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFF843D2F; Sat, 6 Mar 2004 13:05:22 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 7A7752F8F9; Sat, 6 Mar 2004 16:05:23 -0500 (EST) Date: Sat, 6 Mar 2004 16:05:23 -0500 From: James To: Andre Oppermann Message-ID: <20040306210523.GA10214@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <404653DB.186DA0C2@freebsd.org> <4048F1B7.934AAC89@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4048F1B7.934AAC89@freebsd.org> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Sun, 07 Mar 2004 05:13:17 -0800 cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 21:05:44 -0000 thank you! :) i'll try this sometime next week and let you know of any feedbacks i have. -J > > Here you go: > > http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff > > This one implements the standard functionality, the definition of an > interface through which it has to be reachable is not (yet) supported. > > Using this option only makes sense when you don't have a default route > which naturally always matches. So this is useful for machines acting > as routers with a default-free view of the entire Internet as common > when running a BGP daemon (Zebra/Quagga or OpenBSD bgpd). > > One useful way of enabling it globally on a router looks like this: > > ipfw add xxxx deny ip from any to any not versrcreach > > or for an individual interface only: > > ipfw add xxxx deny ip from any to any not versrcreach recv fxp0 > > I'd like to get some feedback (and a man page draft) before I commit it > to -CURRENT. > > -- > Andre -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-current@FreeBSD.ORG Sat Mar 6 18:00:02 2004 Return-Path: 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 B85B016A4CE for ; Sat, 6 Mar 2004 18:00:02 -0800 (PST) Received: from gddsn.org.cn (mail.gddsn.org.cn [210.21.6.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50E2543D1F for ; Sat, 6 Mar 2004 18:00:02 -0800 (PST) (envelope-from wsk@gddsn.org.cn) Received: from gddsn.org.cn (unknown [192.168.168.17]) by gddsn.org.cn (Postfix) with ESMTP id DDDC338CB93 for ; Sun, 7 Mar 2004 09:59:57 +0800 (CST) Message-ID: <404A821D.7020506@gddsn.org.cn> Date: Sun, 07 Mar 2004 09:59:57 +0800 From: Suken User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; zh-CN; rv:1.3) Gecko/20030424 X-Accept-Language: zh-cn,zh MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 07 Mar 2004 05:13:17 -0800 Subject: 5.2-CURRENT buildworld failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 02:00:02 -0000 hi,list: cvsupd today and get the follow errors while buildworld: cc -O -pipe -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/gas -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/gas/config -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/.. -DVERSION=\""2.13.2 [FreeBSD] 2002-11-27"\" -DBFD_VERSION_STRING=\""2.13.2 [FreeBSD] 2002-11-27"\" -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/contrib/binutils/gas/config/tc-i386.c cc -O -pipe -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/gas -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils/gas/config -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/../../../../../contrib/binutils -I/usr/src/gnu/usr.bin/binutils/as/i386-freebsd/.. -DVERSION=\""2.13.2 [FreeBSD] 2002-11-27"\" -DBFD_VERSION_STRING=\""2.13.2 [FreeBSD] 2002-11-27"\" -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o as app.o as.o atof-generic.o atof-ieee.o bignum-copy.o cond.o dwarf2dbg.o ecoff.o expr.o flonum-copy.o flonum-konst.o flonum-mult.o frags.o hash.o input-file.o input-scrub.o listing.o literal.o macro.o messages.o output-file.o read.o sb.o stabs.o subsegs.o symbols.o write.o depend.o ehopt.o obj-elf.o tc-i386.o ../../libbfd/libbfd.a ../../libiberty/libiberty.a ../../libopcodes/libopcodes.a /usr/obj/usr/src/i386/legacy/usr/lib/libegacy.a -legacy as.o: In function `parse_args': as.o(.text+0x388): undefined reference to `getopt_long_only' *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/as/i386-freebsd. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/as. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-current@FreeBSD.ORG Sat Mar 6 21:46:03 2004 Return-Path: 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 60FCD16A4CE for ; Sat, 6 Mar 2004 21:46:03 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29C8043D2D for ; Sat, 6 Mar 2004 21:46:03 -0800 (PST) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.8) with ESMTP id i275k19Q058219; Sat, 6 Mar 2004 21:46:01 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i275k1PU058218; Sat, 6 Mar 2004 21:46:01 -0800 (PST) (envelope-from rizzo) Date: Sat, 6 Mar 2004 21:46:01 -0800 From: Luigi Rizzo To: kientzle@acm.org Message-ID: <20040306214601.B56351@xorpc.icir.org> References: <20040305134125.A37156@xorpc.icir.org> <404A6B59.5080006@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <404A6B59.5080006@kientzle.com>; from tim@kientzle.com on Sat, Mar 06, 2004 at 04:22:49PM -0800 X-Mailman-Approved-At: Sun, 07 Mar 2004 05:13:17 -0800 cc: current@freebsd.org Subject: Re: initdiskless/rc.diskless1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 05:46:03 -0000 On Sat, Mar 06, 2004 at 04:22:49PM -0800, Tim Kientzle wrote: > Luigi Rizzo wrote: > > > > ... extra paths in /conf/ to fetch the configuration > > using the T134 bootp tag (available as kern.bootp_cookie). > > How does this work with DHCP? same way. I think the syntax for dhcpd.conf is option unknown-134 "lab3 nvida foo bar"; or possibly option t134-cookie code 134 = text ; followed by option t134-cookie "lab3 nvida foo bar"; cheers luigi From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 03:53:14 2004 Return-Path: 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 D06FF16A4CF for ; Sun, 7 Mar 2004 03:53:14 -0800 (PST) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947E243D2D for ; Sun, 7 Mar 2004 03:53:11 -0800 (PST) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) i27BrAjV020122; Sun, 7 Mar 2004 11:53:10 GMT (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)i27Br9Js020121; Sun, 7 Mar 2004 11:53:10 GMT (envelope-from mark@grondar.org) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1])i27BqT0w046275; Sun, 7 Mar 2004 11:52:29 GMT (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200403071152.i27BqT0w046275@grimreaper.grondar.org> To: Marc Olzheim In-Reply-To: Your message of "Fri, 05 Mar 2004 10:44:00 +0100." <20040305094400.GA63352@stack.nl> Date: Sun, 07 Mar 2004 11:52:28 +0000 Sender: mark@grondar.org X-Spam-Score: 4 (****) FROM_NO_LOWER,MSGID_FROM_MTA_SHORT X-Scanned-By: MIMEDefang 2.39 X-Mailman-Approved-At: Sun, 07 Mar 2004 05:13:17 -0800 cc: current@FreeBSD.ORG Subject: Re: NULL vs 0 vs 0L bikeshed time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 11:53:15 -0000 Marc Olzheim writes: > On Wed, Mar 03, 2004 at 10:27:14PM +0100, Marc Olzheim wrote: > > Anyway, I'll run a portupgrade -af on my amd64 and see if anything > > breaks... > > After a complete rebuild on the amd64, everything still seems to work > out... No compile errors found. Likewise on i386 + X + KDE + arb.ports. M -- Mark Murray iumop ap!sdn w,I idlaH From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 02:44:35 2004 Return-Path: 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 90FB816A4CE; Sun, 7 Mar 2004 02:44:35 -0800 (PST) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 950AD43D31; Sun, 7 Mar 2004 02:44:34 -0800 (PST) (envelope-from mark.cullen@dsl.pipex.com) Received: from ape (81-178-207-121.dsl.pipex.com [81.178.207.121]) by pengo.systems.pipex.net (Postfix) with SMTP id 3D99E4C00063; Sun, 7 Mar 2004 10:44:32 +0000 (GMT) Message-ID: <000d01c40431$2d6b93b0$f700000a@ape> From: "Markie" To: , , , Date: Sun, 7 Mar 2004 10:44:32 -0000 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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailman-Approved-At: Sun, 07 Mar 2004 05:14:01 -0800 Subject: Yet another panic... using /dev/speaker this time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:44:35 -0000 Well I think I have worked around my other panic that I posted a few days ago by updating the modems firmware, atleast it doesn't panic under the situation it did last time. I still believe the bug exists somewhere though and i'm sure I could still reproduce it if anyone is interested. Just now I was playing about with /dev/speaker for a script I want to beep. I did an `echo a > /dev/speaker` and it worked, but I decided I wanted it longer or some kind of pattern. I followed this by an `echo aaa > /dev/speaker` and it worked :o) I then went on to read the man page and found out about raising and lowering octaves and pauses, so next I tried `echo aPa > /dev/speaker` and indeed there was a pause. However, when I tried `echo aP>a > /dev/speaker` (which I think is wrong anyhow but never mind) my SSH session froze and I knew something had gone wrong. Unfortuantly the monitor had become unplugged from when I was fiddling about so I didn't get to see anything on screen, but I did get a coredump for what it's worth. It isn't from a debugging kernel either, if need be I can load a debugging kernel and see if I can reproduce it. ( I am beginning to think I never should have upgraded :o) ) Anyway, here goes nothing: --- IdlePTD at phsyical address 0x00361000 initial pcb at physical address 0x002bb620 panicstr: getnewbuf: locked buf panic messages: --- panic: lockmgr: pid 8486, not exclusive lock holder 7018 unlocking syncing disks... panic: getnewbuf: locked buf Uptime: 3d13h40m34s dumping to dev #ad/0x20001, offset 65664 dump ata0: resetting devices .. done 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc015bea2 in dumpsys () (kgdb) bt #0 0xc015bea2 in dumpsys () #1 0xc015bc6c in boot () #2 0xc015c0a0 in poweroff_wait () #3 0xc0183d4f in getnewbuf () #4 0xc01849cf in geteblk () #5 0xc0182b8d in bwrite () #6 0xc018869f in vop_stdbwrite () #7 0xc01884b5 in vop_defaultop () #8 0xc0183006 in bawrite () #9 0xc01965b0 in spec_fsync () #10 0xc0214d48 in ffs_sync () #11 0xc018d74b in sync () #12 0xc015ba06 in boot () #13 0xc015c0a0 in poweroff_wait () #14 0xc0155e48 in lockmgr () #15 0xc0183698 in brelse () #16 0xc0260bea in spkrclose () #17 0xc019687f in spec_close () #18 0xc021cb06 in ufsspec_close () #19 0xc021d101 in ufs_vnoperatespec () #20 0xc01921a7 in vn_close () #21 0xc0192afe in vn_closefile () #22 0xc0150eb8 in fdrop () ---Type to continue, or q to quit--- #23 0xc0150dfc in closef () #24 0xc0150931 in fdfree () #25 0xc015381a in exit1 () #26 0xc015368d in sys_exit () #27 0xc0255361 in syscall2 () #28 0xc02466f5 in Xint0x80_syscall () #29 0x28084887 in ?? () #30 0x28082185 in ?? () #31 0x2808182f in ?? () #32 0x280812bf in ?? () #33 0x2808101a in ?? () #34 0x280940e3 in ?? () #35 0x28096958 in ?? () #36 0x8048502 in ?? () #37 0x8048442 in ?? () (kgdb) --- I'm not sure if this should goto hackers or current or bugs or... what, so i'll send it to all of them (although I am not subscribed to hackers and current or bugs anymore). It's a 4.9-R-p3 machine... sorry if I am annoying you all :o) From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 06:21:45 2004 Return-Path: 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 5DBBE16A4CE for ; Sun, 7 Mar 2004 06:21:45 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A38743D39 for ; Sun, 7 Mar 2004 06:21:45 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id E2FAF530E; Sun, 7 Mar 2004 15:21:43 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id CA781530A; Sun, 7 Mar 2004 15:21:38 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 5D9A133CA4; Sun, 7 Mar 2004 15:21:38 +0100 (CET) To: "Putinas Piliponis" References: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Sun, 07 Mar 2004 15:21:38 +0100 In-Reply-To: <00b501c40413$416d2c20$1e64a8c0@spotripoli.local> (Putinas Piliponis's message of "Sun, 7 Mar 2004 09:10:22 +0200") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: current@freebsd.org Subject: Re: serial ata on freebsd 5.2.1 or current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 14:21:45 -0000 "Putinas Piliponis" writes: > Is there any serial ata controller which works stable with 5.2.1 or > Current? The Promise ones work fine, as usual. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 06:35:06 2004 Return-Path: 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 9745D16A4CE for ; Sun, 7 Mar 2004 06:35:06 -0800 (PST) Received: from smtp040.tiscali.dk (smtp040.tiscali.dk [212.54.64.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4CDD43D49 for ; Sun, 7 Mar 2004 06:35:05 -0800 (PST) (envelope-from anh@tiscali.dk) Received: from gandalf (62.79.48.207.adsl.abc.tiscali.dk [62.79.48.207]) by smtp040.tiscali.dk (8.12.10/8.12.10) with SMTP id i27EZ1NW002709 for ; Sun, 7 Mar 2004 15:35:02 +0100 (MET) From: "Nikolaj Hansen" To: Date: Sun, 7 Mar 2004 15:36:07 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: 5.1-> 5.2.1 upgrade issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 14:35:06 -0000 Hi all, I have upgraded my 5.1 -> 5.2.1 with some problems. Here is the current kernel desc: FreeBSD sauron.progressit.dk 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Sat Mar 6 02:15:31 CET 2004 root@:/usr/obj/usr/src/sys/MYKERNEL i386 Problem #1: The buildworld, buildkernel and installkernel part executed without any errors at all, but the installworld did not however. So I am probably running a 5.1 / 5.2.1 hybrid at the moment. The major part of the OS is running ok. But as you can see from the below dmesg output, some system services do not find this fact at all amusing. The sendmail and netstat fails pretty hard.As far as I can tell the process is trying to move /usr/libexec/ld-elf.so.1 to /libexec/ld-elf.so.1. Since /libexec is a symbolic link to /usr/libexec this seems a bit strange to me. This is the installworld error: ... ... ===> libexec/ypxfr install -s -o root -g wheel -m 555 ypxfr /usr/libexec install -o root -g wheel -m 444 ypxfr.8.gz /usr/share/man/man8 ===> libexec/rtld-elf chflags noschg /usr/libexec/ld-elf.so.1 install -s -o root -g wheel -m 555 -fschg -C -b ld-elf.so.1 /libexec install -o root -g wheel -m 444 rtld.1.gz /usr/share/man/man1 /usr/share/man/man1/ld-elf.so.1.1.gz -> /usr/share/man/man1/rtld.1.gz /usr/share/man/man1/ld.so.1.gz -> /usr/share/man/man1/rtld.1.gz /usr/libexec/ld-elf.so.1 -> /libexec/ld-elf.so.1 *** Error code 1 Stop in /usr/src/libexec/rtld-elf. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Problem #2: For some reason the system refuses to find one of my disks. The disks are similar 114473MB disks. Ad6 is being found, but ad4 is not. They are on the same raid controller on seperate channels with seperate cables. The only difference is the cable where the ATA-133 is not being found, but the ATA-33 is? (Yes I know I should get around to buing a new cable). Has the ATA interface changed from 5.1 regarding this? The Vinum system disks seem to be working just fine. Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2.1-RELEASE #0: Sat Mar 6 02:15:31 CET 2004 root@:/usr/obj/usr/src/sys/MYKERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc09dc000. Preloaded elf module "/boot/kernel/vinum.ko" at 0xc09dc21c. MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (498.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 268419072 (255 MB) avail memory = 251092992 (239 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib0: slot 1 INTA routed to irq 11 pcib0: slot 6 INTA routed to irq 15 pcib0: slot 6 INTB routed to irq 10 pcib0: slot 9 INTA routed to irq 11 pcib0: slot 10 INTA routed to irq 9 pcib0: slot 15 INTA routed to irq 10 pcib0: slot 15 INTA routed to irq 10 atapci0: port 0x2020-0x202f,0x200c-0x200f,0x2010-0x2017,0x2008-0x200b,0x2000-0x2007 irq 11 at device 1.0 on pci0 atapci0: [MPSAFE] ata2: at 0x2000 on atapci0 ata2: [MPSAFE] ata3: at 0x2010 on atapci0 ata3: [MPSAFE] ahc0: port 0x2200-0x22ff mem 0xfebff000-0xfebfffff irq 15 at device 6.0 on pci0 aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x2300-0x23ff mem 0xfebfe000-0xfebfefff irq 10 at device 6.1 on pci0 aic7895C: Ultra Wide Channel B, SCSI Id=15, 32/253 SCBs lnc0: port 0x2040-0x205f mem 0xfebfdc00-0xfebfdc1f irq 11 at device 9.0 on pci0 lnc0: Attaching PCNet/PCI Ethernet adapter lnc0: PCnet-PCI address 00:06:29:39:61:39 pci0: at device 10.0 (no driver attached) isab0: port 0xfe00-0xfe0f at device 15.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0-0x3,0-0x7,0x3f4-0x3f7,0x1f0-0x1f7 irq 10 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata0: [MPSAFE] ata1: simplex device, DMA on primary only ata1: at 0x170 irq 15 on atapci1 ata1: [MPSAFE] ohci0: mem 0xff700000-0xff700fff irq 10 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: at pcibus 1 on motherboard pci1: on pcib1 pcib1: slot 4 INTA routed to irq 15 pci1: at device 4.0 (no driver attached) orm0: