From owner-freebsd-stable Wed Oct 6 22:40:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta3.tm.net.my (mta3.tm.net.my [202.188.95.6]) by hub.freebsd.org (Postfix) with ESMTP id E967F14C33 for ; Wed, 6 Oct 1999 22:36:54 -0700 (PDT) (envelope-from penjejak@tm.net.my) Received: from opal ([203.106.62.10]) by mta3.tm.net.my (InterMail v03.02.05 118 121 101) with SMTP id <19991006124130.NHR10161@opal> for ; Wed, 6 Oct 1999 20:41:30 +0800 Message-ID: <000b01bf0ff9$9c9be900$db62640a@cyber.mmu.edu.my> From: "Nawfal M. Rouyan" To: "FreeBSD 3.2 STABLE" Subject: Help! FreeBSD can't boot into FreeBSD Date: Wed, 6 Oct 1999 20:51:55 +0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01BF103C.9FAF2100" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF103C.9FAF2100 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0006_01BF103C.9FAF2100" ------=_NextPart_001_0006_01BF103C.9FAF2100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi,=20 thanks to those who answered my questions before. I cvsuped today and = make world soon after I boot to single user. While making the world, I = noticed that there were signal 4 core dumps while building libraries=20 I think the statements are something like this...=20 Illegal instruction.... (nm) .... signal 4 core cumped)=20 Can't check the /var/tmp/mwout file since I can't boot into FreeBSD... = But the make world process managed to finish successfully. Then, I make a new sysinstall but the process stopped. Again signal 4 = core dumped but this time the statement is something like this... Illegal instruction ... cpp(1) ... signal 4 core dumped... After that I install a new kernel and reboot... Below is the message that I got Verifying DMI Pool Data _ BTX Loader 1.00 BTX version is 1.01 Console:internal video/keyboard panic:zfree(0x1cb04,4096):wild pointer I use osbs beta to boot between Win98 and FreeBSD. My computer is AMD K62 300MHz,=20 VA 503+ motherboard Maxtor hd (4G) -- for FreeBSD (secondary master) Quantum Fireball CR (4G) -- for Win98 The original FreeBSD is installed from ftp (FreeBSD-STABLE) from the = primary site. It is the second installation from ftp site since the first installation = also can't boot after I make a new kernel... (kernel trap after the npx = statement) The signal 4 core dumped happened frequently since I make world to = FreeBSD 3.3 Stable from FreeBSD 3.2 Stable. During 3.2 Stable, the = FreeBSD works great without any problems. I have already low level formated my hd before my second ftp = installation using maxtor's hd utility program to check whether I have a = faulty hd. The hd passed all tests. Attached is a copy of my kernel configuration file which I saved in my = Win98 partition. (I've edited it to make it smaller...;) Any hints on what I should do to boot into FreeBSD? (I don't use Win98, = my family use it...;) I do installed gcc 2.9.1, does this has anything to do with my problem?? thanks in advance... ------=_NextPart_001_0006_01BF103C.9FAF2100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

thanks to those = who answered my=20 questions before. I cvsuped today and make world soon after I boot to = single=20 user. While making the world, I noticed that there were signal 4 = core dumps=20 while building libraries

I think the statements are = something like=20 this...

Illegal instruction.... (nm) .... = signal 4 core=20 cumped)

Can't check the /var/tmp/mwout file = since I can't=20 boot into FreeBSD... But the make world process managed to finish=20 successfully.

Then, I make a new = sysinstall but the=20 process stopped. Again signal 4 core dumped but this time the statement = is=20 something like this...

Illegal instruction ... cpp(1) ... = signal 4=20 core dumped...

After that I install a new = kernel and=20 reboot...

Below is the message that I = got

Verifying DMI Pool Data

BTX Loader 1.00 BTX version is = 1.01

Console:internal = video/keyboard

panic:zfree(0x1cb04,4096):wild = pointer

I use osbs beta to boot between Win98 = and=20 FreeBSD.

My computer is

AMD K62 300MHz, =

VA 503+ = motherboard

Maxtor hd (4G) -- = for FreeBSD=20 (secondary master)

Quantum = Fireball CR (4G) --=20 for Win98

The original FreeBSD is installed = from ftp=20 (FreeBSD-STABLE) from the primary site.

It is the second installation from ftp = site since=20 the first installation also can't boot after I make a new kernel... = (kernel trap=20 after the npx statement)

The signal 4 core dumped happened = frequently since=20 I make world to FreeBSD 3.3 Stable from FreeBSD 3.2 Stable. During 3.2 = Stable,=20 the FreeBSD works great without any problems.

I have already low level formated my hd = before my=20 second ftp installation using maxtor's hd utility program to check = whether I=20 have a faulty hd. The hd passed all tests.

Attached is a copy of my kernel = configuration file=20 which I saved in my Win98 partition. (I've edited it to make it=20 smaller...;)

Any hints on what I should do to boot = into FreeBSD?=20 (I don't use Win98, my family use it...;)

I do installed gcc 2.9.1, does this has = anything to=20 do with my problem??

thanks in = advance...

------=_NextPart_001_0006_01BF103C.9FAF2100-- ------=_NextPart_000_0005_01BF103C.9FAF2100 Content-Type: application/octet-stream; name="Opal" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Opal" machine "i386" cpu "I586_CPU" ident OPAL maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" config kernel root on wd0 controller isa0 controller pnp0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller vpo0 at ppbus? device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 pseudo-device loop pseudo-device ether 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. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options USER_LDT options SYSVSHM options SYSVMSG options SYSVSEM #Stuff for my k6 CPU options "NO_F00F_HACK" options CPU_WT_ALLOC #some k6 optimization options NO_MEMORY_HOLE # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 1 #Berkeley packet filter device pcm0 ------=_NextPart_000_0005_01BF103C.9FAF2100-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message