Date: Tue, 9 Jun 1998 09:04:12 +0100 From: Dimitris Krekoukias <Dimitris.Krekoukias@halliburton.com> To: "'Kevin G. Eliuk'" <kevin_eliuk@sunshine.net> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG> Subject: RE: weird kernel build problem Message-ID: <89EF1ED52E24D111804300805F19E92AA9EE6A@ABZEXCH001>
next in thread | raw e-mail | index | archive | help
I tried fsck'ing - even tried a clean re-install of everything. Yesterday it worked for some reason - I disabled the mouse daemon and XFree seems a bit more stable and the kernel compiled. I will try to recompile to see if that was the problem, but I don't think so, because XFree crashed again. FreeBSD is not at all stable for me (at least certain bits - the XFree server crashes all the time, without a pattern, even with different window managers running). Linux was far more stable in that machine (dual P133 - maybe better stick with Linux, since it supports MP). Thanks for your help, Dimitris PS. I'm including the kernel config file anyway: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # <URL:http://www.FreeBSD.ORG/>; # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: MYKERNEL,v 1.77.2.22 1998/03/24 01:20:14 jkh Exp $ machine "i386" cpu "I586_CPU" ident MYKERNEL maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device wfd0 #IDE floppy (LS-120) # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. # # Note: The dpt driver is present in this release but was left disabled # due to its relatively late entry (it's almost certainly benign to enable # it but we didn't want to risk any chance of destabilizing 2.2.6). To # enable DPT support, uncomment the dpt0 controller entry and the two # options DPTOPT and DPT_MEASURE_PERFORMANCE entries below. #options DPTOPT # will go away soon #options DPT_MEASURE_PERFORMANCE # just enable for now #options DPT_VERIFY_HINTR # Some hardware must have it! #options DPT_TRACK_CCB_STATES # Some hardware must have it! #options DPT_HANDLE_TIMEOUTS # Some hardware must have it! #options DPT_TIMEOUT_FACTOR=4 # Some hardware needs more # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. # This provides support for System V shared memory. # options SYSVSHM options SYSVMSG # SND card stuff controller snd0 device sb0 at isa? port 0x220 irq5 drq1 vector sbintr options "SBC_IRQ=5" device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 > -----Original Message----- > From: Kevin G. Eliuk [SMTP:kevin_eliuk@sunshine.net] > Sent: Monday, June 08, 1998 6:24 PM > To: Dimitris Krekoukias > Cc: 'freebsd-questions@freebsd.org' > Subject: Re: weird kernel build problem > > On Mon, 8 Jun 1998, Dimitris Krekoukias wrote: > > => Compiled it, installed it. > => > => Works fine. > > [ snip ] > > => So, I am > => > => a) Using the standard kernel to boot > => b) Trying to compile the same kernel and failing but what really > pisses > => me off is that > => c) It worked the first time I did it. > => > => I reinstalled FreeBSD just in case I'd screwed up something. > => > => The first time I build the kernel it works. > => > => It fails subsequently. > => > => Ideas? > > Only that I had a similar problem with a 386 and a 1Gb IDE drive. > I had some real problems with bad sectors, try `fsck'ing the slices > that > you have, from booting in single user mode. > > => Cheers, > => > => Dimitris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89EF1ED52E24D111804300805F19E92AA9EE6A>