From owner-freebsd-current@FreeBSD.ORG Tue Aug 19 00:55:44 2003 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 8CADE16A4BF; Tue, 19 Aug 2003 00:55:44 -0700 (PDT) Received: from xyzzy.wireless.snsonline.net (dhcp.looksmart.com.au [210.9.52.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA3A43F3F; Tue, 19 Aug 2003 00:55:43 -0700 (PDT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) h7J7tm7x096584; Tue, 19 Aug 2003 17:55:48 +1000 (EST) (envelope-from msergeant@snsonline.net) Received: (from sarge@localhost)h7J7tmPn096583; Tue, 19 Aug 2003 17:55:48 +1000 (EST) X-Authentication-Warning: xyzzy.wireless.snsonline.net: sarge set sender to msergeant@snsonline.net using -f From: Mark Sergeant To: Scott Long In-Reply-To: <3F41D617.6000704@freebsd.org> References: <1061273955.58787.12.camel@xyzzy.wireless.snsonline.net> <3F41D617.6000704@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SNSOnline Technical Services Message-Id: <1061279747.58787.25.camel@xyzzy.wireless.snsonline.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 19 Aug 2003 17:55:48 +1000 cc: freebsd-current@freebsd.org Subject: Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE & scsi) 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: Tue, 19 Aug 2003 07:55:45 -0000 On Tue, 2003-08-19 at 17:47, Scott Long wrote: > Mark Sergeant wrote: > > Hi All, > > > > When trying to compile a kernel for my 8 cpu DELL 8450's I recieve an > > extremly puzzling error, I get a bunch of errors when compiling a kernel > > that has the following options in it... > > > > options WITNESS > > options NETSMB > > options NETSMBCRYPTO > > options LIBMCHAIN > > options LIBICONV > > options PAE > > options SMP > > options APIC_IO > > > > Without PAE SMP or APIC_IO the kernel will compile fine. With these > > options I get the following error when compiling the sym scsi driver. > > cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > > -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. > > -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter > > -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings > > -mpreferred-stack-boundary=2 -ffreestanding -Werror > > ../../../dev/sym/sym_hipd.c > > cc1: warnings being treated as errors > > ../../../dev/sym/sym_hipd.c: In function `sym_setup_data_and_start': > > ../../../dev/sym/sym_hipd.c:8146: warning: cast from pointer to integer > > of different size > > *** Error code 1 > > > > This is rather unfortunate as the only disks I have run off this > > controller. I've found that it does compile with the ahc driver but even > > then some usb stuff needs removing. > > > > Does anyone have any insight into this and what I can do to get it > > fixed. > > > > Cheers, > > The key kere is likely PAE, not APIC_IO, as PAE changes the size of > some data types. The USB problem is known. The sym problem looks to > be harmless assuming that the warning you got is the only one that > is emitted. However, it appears that it was never certified as being > ready for PAE. If you're adventurous, you can try compiling and > loading it as a module (warnings when compiling modules are not fatal > like they are in when compiling the kernel). > > If there are more errors/warning that what you list, I'd be interested > in seeing them. > > Scott There are no other errors apart from those listed so I may try compiling as a module that gets loaded on boot. Just one problem, I succesfully build an SMP kernel without PAE and then rebooted and the server is no longer responding, it seems it crashed just after coming up as I was able to ping it 5 or 6 times and then it went away again. If I've got a crash dump I'll post it. Cheers, -- Mark Sergeant SNSOnline Technical Services