Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)
On 19 Aug, 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. Take a look at /usr/src/sys/i386/conf/PAE. It says: # What follows is a list of drivers that are normally in GENERIC, but either # don't work or are untested with PAE. Be very careful before enabling any # of these drivers. Drivers which use DMA and don't handle 64 bit physical # address properly may cause data corruption when used in a machine with more # than 4 gigabytes of memory. and under this comment it lists the sym and usb drivers. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)
Ohh bugger. I suppose I'll have to live without PAE then. Thanks anyway. Cheers, Mark On Tue, 2003-08-19 at 17:19, Don Lewis wrote: On 19 Aug, 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. Take a look at /usr/src/sys/i386/conf/PAE. It says: # What follows is a list of drivers that are normally in GENERIC, but either # don't work or are untested with PAE. Be very careful before enabling any # of these drivers. Drivers which use DMA and don't handle 64 bit physical # address properly may cause data corruption when used in a machine with more # than 4 gigabytes of memory. and under this comment it lists the sym and usb drivers. -- Mark Sergeant [EMAIL PROTECTED] SNSOnline Technical Services ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)
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 [EMAIL PROTECTED] SNSOnline Technical Services ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Broken kernel compile on 5.1-RELEASE / 5-CURRENT (SMP, PAE scsi)
On Tue, 19 Aug 2003, Mark Sergeant wrote: 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. Can't speak to the specifics of this, but you want to be very careful not to use kernel modules with PAE: modules are currently without the context of the kernel configuration file, and PAE introduces possible binary incompatibility with modules that dig into VM (which many drivers do). The only supported configuration is to not use modules, but link the driver directly into the kernel when running PAE. This is why the PAE kernel has no_modules defined in the sample PAE configuration file. Various conversations have happened regarding how to address this problem, and I'm not sure we've come up with the right answer yet. There seem to be two conflicting directions: build modules in the context of a kernel module (and get conditionally compiled type/structure/code/... pieces), and try to make the module build entirely independent of a kernel configuration. As someone who uses conditionally compiled components in modules, I tend to fall into the first camp, and no doubt we'll figure out the right answer in due course. The above crash sounds unfortunate too, but quite possibly a separate failure mode :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
