Hi Chaps, I think something has changed with regards to loader in STABLE recently, it has prevented me from being able to boot my machine today. This ideally needs to get fixed so other people dont have the same problem. Previously I have been able to boot fine and the system has been solid as a rock, until... I did a make buildworld, buildkernel, installkernel, reboot, mergemaster -p, installworld, mergemaster and then reboot - since the second reboot (after mergemaster) my system wont boot up any more - I get to the FreeBSD boot options screen width the besatie logo "1. boot default - 6. escape to loader etc" and then I get this - FreeBSD/i386 bootstrap loader, Revision 1.1 (adam@funkalicious.home.dom, Thu Aug 31 12:53:11 BST 2006) Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: panic: free: guard1 fail @ 0x67184 from /usr/src/sys/boot/i386/loader/../../common/module.c:958 --> Press a key on the console to reboot <-- Now I solidly believe that it is the loader in STABLE that is the problem because, I can boot my system using a FreeBSD 6.1-BETA#1 Install CD and then escape to the loader on the cd and send it options so it boots my system from harddisk, the system then comes up no problem - in fact im writting this email on it. The process I use to boot my system via. the install cd is this - Boot from CD>From the boot options screen with the beastie logo, I press "6" toescape to the loader, I then use these commands - unload set rootdev=disk1s3a load disk1s3a:/boot/kernel/kernel load disk1s3a:/boot/kernel/linux.ko load disk1s3a:/boot/kernel/linprocfs.ko load disk1s3a:/boot/modules/nvidia.ko load disk1s3a:/boot/modules/hpt374.ko boot My System is - Intel Pentium 4 3.2GHz Processor 2 x 1GB Corsair DDR400 RAM MSI 848P Neo Motherboard Nvidia 6800LE DDR3 256MB 120GB Maxtor SATA Hard disk HPT 374 RAID 5 SATA Controller 3 x 250GB Maxtor SATA Hard disk (raid 5) DVD-ROM DDU1621/VER S3.5 DVDR DVD-RW IDE1004/VER 0251 Thanks Adam Retter
Yes, these are set in make.conf, but I have always had these set and there have been no problems in the past... # Compile for Pentium 4 CPU CPUTYPE=p4 # Compiler optimisation flags CFLAGS= -O2 -pipe -funroll-loops -ffast-math # Compiler optimisation flags for the Kernel COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math On Fri, 2006-09-08 at 08:48 +1000, Tony Maher wrote:> Adam Retter wrote: > > Hi Chaps, > > > > > > I think something has changed with regards to loader in STABLE recently, > > it has prevented me from being able to boot my machine today. This > > ideally needs to get fixed so other people dont have the same problem. > > > > Previously I have been able to boot fine and the system has been solid > > as a rock, until... > > > > I did a make buildworld, buildkernel, installkernel, reboot, mergemaster > > -p, installworld, mergemaster and then reboot - since the second reboot > > (after mergemaster) my system wont boot up any more - I get to the > > FreeBSD boot options screen width the besatie logo "1. boot default - 6. > > escape to loader etc" and then I get this - > > > > FreeBSD/i386 bootstrap loader, Revision 1.1 > > (adam@funkalicious.home.dom, Thu Aug 31 12:53:11 BST 2006) > > Can't work out which disk we are booting from. > > Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0: > > > > panic: free: guard1 fail @ 0x67184 > > from /usr/src/sys/boot/i386/loader/../../common/module.c:958 > > --> Press a key on the console to reboot <-- > > Do you have any compile options in /etc/make.conf? > These can affect loader. > > -- > tonym
Adam Retter wrote:> On Fri, 2006-09-08 at 08:48 +1000, Tony Maher wrote: >>Do you have any compile options in /etc/make.conf? >>These can affect loader. > > Yes, these are set in make.conf, but I have always had these set and > there have been no problems in the past... > > > # Compile for Pentium 4 CPU > CPUTYPE=p4 > > # Compiler optimisation flags > CFLAGS= -O2 -pipe -funroll-loops -ffast-math > > # Compiler optimisation flags for the Kernel > COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math>From private email from someone else with same problem (they had-funroll-loops in make.conf), "optimizations are bad for the loader"... but it still works fine for me using -O -pipe. -- tonym
> CFLAGS= -O2 -pipe -funroll-loops -ffast-mathI had used similar optimizations soon after going from 6.1-RELEASE to 6-STABLE and discovered it was a bad idea. Using -O -pipe has since stood me in good stead. The system is by no means sluggish, even on a cut-rate build-on-a-budget machine. I experienced that tuning for FS bottlenecks has a far greater performance impact. Splitting cache across different drives can have a positive effect similar to putting /usr/src and /usr/obj on different drives. After finding out where my needs were and partitioning appropriately, I have few complaints even with minimal optimization. That also holds for NetBSD on my dodgy old ACPI plus early AGP box that causes FreeBSD to panic unless I yank the s3 Trio for a couple of older cards and disable ACPI (1997 Microstar EISA/PCI/AGP K6 "transitional" hardware). Even when I just slap on an extra 2 gig drive for cache and /usr/obj, Net runs noticeably faster. Charles
Thanks very much Tony :-D I removed my CFLAGS and COPTFLAGS from make.conf and just left the CPUTYPE flag and rebuilt and installed kernel and world, all seems to work fine again now, if anything the system seems a bit faster :-D Thanks again. Adam. On Fri, 2006-09-08 at 10:16 +1000, Tony Maher wrote:> Adam Retter wrote: > > On Fri, 2006-09-08 at 08:48 +1000, Tony Maher wrote: > >>Do you have any compile options in /etc/make.conf? > >>These can affect loader. > > > > Yes, these are set in make.conf, but I have always had these set and > > there have been no problems in the past... > > > > > > # Compile for Pentium 4 CPU > > CPUTYPE=p4 > > > > # Compiler optimisation flags > > CFLAGS= -O2 -pipe -funroll-loops -ffast-math > > > > # Compiler optimisation flags for the Kernel > > COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math > > >From private email from someone else with same problem (they had > -funroll-loops in make.conf), > > "optimizations are bad for the loader"... but it still works fine for me > using -O -pipe. > > -- > tonym > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"