Date: Tue, 15 Jul 2003 23:03:01 -0700 (PDT) From: Josh Brooks <user@mail.econolodgetulsa.com> To: Bruce M Simpson <bms@spc.org> Cc: freebsd-hackers@freebsd.org Subject: Re: running 5.1-RELEASE with no procfs mounted (lockups?) Message-ID: <20030715225109.T36933-100000@mail.econolodgetulsa.com> In-Reply-To: <20030716054419.GE22295@spc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jul 2003, Bruce M Simpson wrote: > On Tue, Jul 15, 2003 at 10:43:19PM -0700, Josh Brooks wrote: > > I have loaded two 5.1-RELEASE systems, both of them have PROCFS and > > PSEUDOFS in the kernel, and yet neither of them have a procfs mounted. > > I think one of the first things people are going to ask is: > which scheduler are you using, SCHED_BSD or SCHED_ULE ? > > Also, if you could attach a dmesg and kernel configuration file, that > may be most helpful. I am running the SCHED_BSD scheduler. Below you will find the kernel config, the dmesg, and a further crash description. Here is the kernel config: # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.384.2.2 2003/05/31 15:18:41 scottl Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident GENERIC maxusers 512 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device vga # VGA video card driver # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. device npx # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter options SHMMAXPGS=12288 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMSEG=256 options SEMMNI=384 options SEMMNS=512 options SEMMNU=256 options SEMMAP=256 options IPSEC options IPSEC_ESP options QUOTA options RANDOM_IP_ID options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_DEFAULT_TO_ACCEPT options TCP_DROP_SYNFIN And here is the dmesg: Copyright (c) 1992-2003 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 5.1-RELEASE #0: Mon Jul 14 16:49:15 PDT 2003 someuser@www.example.com:/usr/src/sys/i386/compile/example Preloaded elf kernel "/boot/kernel/kernel" at 0xc04f2000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04f21f4. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1390660796 Hz CPU: Intel(R) Pentium(R) III CPU family 1400MHz (1390.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> real memory = 4026466304 (3839 MB) avail memory = 3917295616 (3735 MB) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Changing APIC ID for IO APIC #1 from 0 to 3 on chip Programming 16 pins in IOAPIC #0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled npx0: <math processor> on motherboard npx0: INT 16 interface acpi0: <DELL PE2550 > on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fc270 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: <CPU> on acpi0 acpi_cpu1: <CPU> on acpi0 pcib0: <ACPI Host-PCI bridge> on acpi0 pci0: <ACPI PCI bus> on pcib0 pci0: <display, VGA> at device 14.0 (no driver attached) isab0: <PCI-ISA bridge> port 0x8a0-0x8af at device 15.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <ServerWorks ROSB4 UDMA33 controller> port 0x8b0-0x8bf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: <serial bus, USB> at device 15.2 (no driver attached) pcib1: <ACPI Host-PCI bridge> on acpi0 pci1: <ACPI PCI bus> on pcib1 IOAPIC #1 intpin 1 -> irq 2 pci1: <network, ethernet> at device 8.0 (no driver attached) pcib2: <ACPI Host-PCI bridge> on acpi0 pci2: <ACPI PCI bus> on pcib2 IOAPIC #1 intpin 15 -> irq 5 IOAPIC #1 intpin 0 -> irq 10 pcib3: <ACPI PCI-PCI bridge> at device 2.0 on pci2 pci3: <ACPI PCI bus> on pcib3 IOAPIC #1 intpin 14 -> irq 13 pci3: <mass storage, SCSI> at device 4.0 (no driver attached) ahc0: <Adaptec aic7899 Ultra160 SCSI adapter> port 0xc800-0xc8ff mem 0xfe7fe000-0xfe7fefff irq 13 at device 4.1 on pci3 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 5 at device 2.1 on pci2 aac0: i960RX 100MHz, 118MB cache memory, optional battery present aac0: Kernel 2.7-1, Build 3571, S/N 2c21d2 aac0: Supported Options=0 fxp0: <Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet> port 0xbcc0-0xbcff mem 0xfe500000-0xfe5fffff,0xfe900000-0xfe900fff irq 10 at device 4.0 on pci2 fxp0: Ethernet address 00:00:00:00:00:00:00 miibus0: <MII bus> on fxp0 inphy0: <i82555 10/100 media interface> on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: <Parallel port bus> on ppc0 ppi0: <Parallel I/O> on ppbus0 orm0: <Option ROMs> at iomem 0xec000-0xeffff,0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. acd0: CDROM <SAMSUNG CD-ROM SN-124> at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle aacd0: <RAID 1 (Mirror)> on aac0 aacd0: 69998MB (143357184 sectors) aacd1: <RAID 1 (Mirror)> on aac0 aacd1: 69998MB (143357184 sectors) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/aacd0s1a In addition to my earlier crash description, I have also noticed that if I restore a dump-file into a mdconfig file-backed filesystem, it will lock up in the same manner. The more mdconfig file-backed filesystems mounted, the worse it is. For example, if I have 1-3 file-backed filesystems mounted, I can restore _into_ a file-backed FS from diskA to diskB, but not from diskA to diskA ... but once I get to 4-5 file-backed filesystems mounted, I cannot even restore from diskA to diskB anymore - it won't work period. It will just freeze (the restore operation) and the PID will be unkillable, and eventually other processes in other login sessions (especially df, pwd, ls) will freeze (unkillable) also. At some point the entire system freezes up, although you can still ping it. thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715225109.T36933-100000>