From owner-freebsd-questions Thu Dec 27 14:30:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 5C8B737B416 for ; Thu, 27 Dec 2001 14:29:47 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA15117; Thu, 27 Dec 2001 17:29:45 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA16539; Thu, 27 Dec 2001 17:29:44 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA16535; Thu, 27 Dec 2001 17:29:44 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Thu, 27 Dec 2001 17:29:44 -0500 (EST) From: Kenneth Wayne Culver To: twig les Cc: freebsd-questions@FreeBSD.ORG Subject: Re: multiple panics in 4.4 stable In-Reply-To: <20011227190659.38389.qmail@web10104.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is probably bad memory. I've had similar problems and when I replaced the memory, the problems magically went away. Ken On Thu, 27 Dec 2001, twig les wrote: > Hey all, I'm having a devil of a time here with 4.4 > stable. I ssh into my box and sometimes get this > message: > > Segmentation fault - core dumped > > Then I can't su, instead I get a message saying the > > /kernel: pid 207(sh), uid 1001: exited on signal 11 > (core dumped) > > > > I've also gotten panics trying to rebuild the kernel; > after doing a config it gives me a panic message and > reboots. I will paste my dmesg at the end of this > mail-it has three panics in it. > > I'm no programmer but I think the version of Free4.4 > that comes with the new book "FreeBSD Unleashed" may > not be that stable. The machine is a development one > (to be a Snort box) and the hardware is a Supermicro > mobo, 1G RAM (I forget what kind but it's brand-name, > registed, ecc), 18gb Seagate scsi HD, dual p3 1ghz. > As I'm writing this the box panicked and rebooted > itself again. > > > > bash-2.05# dmesg > rq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on > isa0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE > mode > ppc0: FIFO with 16/16/8 bytes threshold > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > acd0: CDROM at ata0-master using > PIO4 > Mounting root from ufs:/dev/da0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access > SCSI-3 device > da0: 160.000MB/s transfers (80.000MHz, offset 63, > 16bit), Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T > 2231C) > panic: pmap_enter: pte vanished, va: 0x28053000 > > syncing disks... 20 20 2 2 > done > Uptime: 21s > Automatic reboot in 15 seconds - press a key on the > console to abort > Rebooting... > Copyright (c) 1992-2001 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, > 1991, 1992, 1993, 1994 > The Regents of the University of California. > All rights reserved. > FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001 > > murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (999.53-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x68a Stepping = 10 > > Features=0x383fbff > real memory = 536870912 (524288K bytes) > avail memory = 518168576 (506024K bytes) > Preloaded elf kernel "kernel" at 0xc0480000. > Pentium Pro MTRR support enabled > md0: Malloc disk > Using $PIR table, 10 entries at 0xc00f5340 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib4: > at device 0.1 on pci0 > pci1: on pcib4 > pci0: at 4.0 irq > 11 > ahc0: port > 0xde00-0xdeff mem 0xfeafb000-0xfeafbfff irq 5 at > device 5.0 on pci0 > aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 > SCBs > ahc1: port > 0xd400-0xd4ff mem 0xfeafe000-0xfeafefff irq 10 at > device 5.1 on pci0 > aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 > SCBs > fxp0: port > 0xd000-0xd03f mem > 0xfe900000-0xfe9fffff,0xfeafc000-0xfeafcfff irq 9 at > device 6.0 on pci0 > fxp0: Ethernet address 00:30:48:21:d8:44 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, > 100baseTX-FDX, auto > isab0: at > device 15.0 on pci0 > isa0: on isab0 > atapci0: port > 0xffa0-0xffaf at device 15.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ohci0: irq 0 at device > 15.2 on pci0 > ohci0: Could not map memory > device_probe_and_attach: ohci0 attach returned 6 > pcib1: > on motherboard > pci2: on pcib1 > pcib2: on motherboard > pci3: on pcib2 > pcib3: on motherboard > pci4: on pcib3 > orm0: