From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 04:48:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6660116A4CE for ; Wed, 26 Jan 2005 04:48:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 007F543D2F for ; Wed, 26 Jan 2005 04:48:41 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so6835rne for ; Tue, 25 Jan 2005 20:48:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZyuJGZgQ8B7IWEyBsNXcI0BlvrCNtgnL/ovrkwIU3KK6DMUPkx7s0HZDtrV1kKwhDZ4jfusrOCNrbo6e6Z6HrLQr7tzISS2XhiwyuDf6zfUAuB+k/TBNN0JXMf1VXxHPCPbSoGOB+TEtV55ZSBOc8gukAy+7mSAfVDVxXIS5HwU= Received: by 10.38.71.4 with SMTP id t4mr21987rna; Tue, 25 Jan 2005 20:48:40 -0800 (PST) Received: by 10.39.1.45 with HTTP; Tue, 25 Jan 2005 20:48:40 -0800 (PST) Message-ID: <3aaaa3a05012520483adb5de6@mail.gmail.com> Date: Wed, 26 Jan 2005 04:48:40 +0000 From: Chris To: Artem Kuchin In-Reply-To: <00ba01c50211$23389ee0$0c00a8c0@artem> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <00ba01c50211$23389ee0$0c00a8c0@artem> cc: freebsd-stable@freebsd.org cc: Robert Watson Subject: Re: Lock up problems with 5.3-STABLE (was: Cannot build kernel with options WITNESS) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 04:48:44 -0000 I would suspect the jail code at this point here is my kernel config for my smp machine Dual Athlon-mp 40 gig ide hd 1024 Ram xl0 nic device 100mbit fdx machine i386 cpu I686_CPU ident WEB1 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. 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 directories options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT #options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] 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 extension s options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC options SMP # SMP # Bus support. Do not remove isa, even if you have no isa slots device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of ` ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals #device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers #device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD #device pass # Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem #device amr # AMI MegaRAID #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options #device hptmv # Highpoint RocketRAID 182x #device iir # Intel Integrated RAID #device ips # IBM (Adaptec) ServeRAID #device mly # Mylex AcceleRAID/eXtremeRAID #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers #device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver #device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device em # Intel PRO/1000 adapter Gigabit Ethernet Card #device ixgb # Intel PRO/10GbE Ethernet Card #device txp # 3Com 3cR990 (``Typhoon'') #device vx # 3Com 3c590, 3c595 (``Vortex'') # 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 bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device lge # Level 1 LXT1001 gigabit ethernet #device nge # NatSemi DP83820 gigabit ethernet #device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc' ) #device re # RealTek 8139C+/8169/8169S/8110S #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. #device lnc # NE2100, NE32-VL Lance Ethernet cards #device sn # SMC's 9000 series of Ethernet chips #device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device wlan # 802.11 support #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP 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) device snp # snoop device # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB Ethernet #device cue # CATC USB Ethernet #device kue # Kawasaki LSI USB Ethernet #device rue # RealTek RTL8150 USB Ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=50 options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPFIREWALL_FORWARD options IPDIVERT options IPSTEALTH #support for stealth forwarding options DUMMYNET options TCP_DROP_SYNFIN #options PREEMPTION options HZ=1000 options QUOTA options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP and dmesg.boot FreeBSD 5.3-RELEASE-p5 #1: Sat Jan 22 02:43:33 UTC 2005 root@web1.hostingfreak.net:/usr/obj/usr/src/sys/WEB1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) MP 2000+ (1666.73-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000 real memory = 1073741824 (1024 MB) avail memory = 1045397504 (996 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0xe800-0xe803 mem 0xfb800000-0xfb800fff, 0xfc000000-0xfdffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6 ,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xf8000000-0xf800 007f irq 16 at device 8.0 on pci0 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:e0:18:da:fa:c1 pcib2: at device 16.0 on pci0 pci2: on pcib2 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. 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: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to acc ept, logging limited to 50 packets/entry by default ad0: 39083MB [79408/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s1a Only thing that concerns me with my config is I see no "SMP: AP CPU #2 Launched!" is this normal for a 2 cpu machine? The box is stable. 4:48AM up 4 days, 26 mins, 2 users, load averages: 0.00, 0.01, 0.00 5.3-RELEASE-p5 Chris On Mon, 24 Jan 2005 15:26:42 +0300, Artem Kuchin wrote: > > > On Sun, 23 Jan 2005, Artem Kuchin wrote: > > > >> > On Sat, 22 Jan 2005, Artem Kuchin wrote: > >> > > >> >> I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with > >> >> WITNES. It complains: > >> > > >> > This occurs when building WITNESS without DDB in the kernel, which was not > >> > a tested build case when I added "show alllocks", and apparently is a > >> > relatively uncommon configuration as you're the first person to bump into > >> > it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and > >> > subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't > >> > fix the problem for you. > >> > >> It fixed the problem. I am actually stuggling with unpredictable weird > >> lock ups, when the host can be pinged but i cannot connect via > >> ssh/telnet or httpd or anything else. It happens w/o any visible reason. > >> I am running several jails with mysql and apache in each and canot make > >> the whole system stable yet. > > > > This is typically a sign of one of two problems: > > > > - The system is live locked due to very high load, so the ithread, > > netisrs, etc, in the kernel run fine, but user processes don't get a > > chance to run. > > > > - The system is dead locked due to user space processes getting wedged on > > common locks, but the kernel ithreads and netisrs can keep on > > responding. > > > > I generally assume that it's a deadlock as opposed to a live lock. I'd > > compile a kernel with DDB, KDB, WITNESS, and BREAK_TO_DEBUGGER. When the > > system appears to wedge, break into the debugger using a console or serial > > break (FYI: serial break is more reliable, and you get the benefit of > > being able to easily copy and paste debugging output using the serial > > console for DDB). Use "show alllocks" and "show lockedvnods" to examine > > most of the system's locking state. Changes are, either all the > > interesting processes are stacked up on VFS or VM locks, since those kinds > > of deadlocks produce the exact symptoms you describe: ping works fine > > because it only hits the netisr, but when you open TCP connections, the > > sshd (etc) block on VM or VFS locks attempting to fork new children or > > access a file in the file system name space. At first, the TCP > > connections will establish but there will be no application data; after a > > bit, they will not even return a SYN/ACK because the listen queue for the > > listen socket has filled. > > > > Well, i cvsed and reconpiled the kernel with WITNESS, INVARINATS, turned off > adaptive giant and got a lock today at 7 am. Since the server is remotely controlled > i took my digital camera because i cannot connect serial console to it and went to the server. > I expetced to see some special message about something going wrong, break > into debugger (CTRL+ALT+ESC) and to take some pictures of dumps of console. > But, i saw nothing. The lasrt message on th screen was about ssh loging last evening > and the last message in /var/log/all.log was about entropy save from cron. > I could not break into debugger usinmg CTRL-ALT+ESC. I did nothing. So, > it looked like a hard lock. > > At this point i would like to tell the whole story. > We bought this server in may 2004 and decided to extemsively test the hardware > while there were not 5.3. We actually expected it around august. SO, we installed > 5-CURRENT and ran high load tests (cpu, memory, disk storage, network) from > /usr/ports/benchmark at the same time and one-by-one several weeks. There were > not a glitch. After that we turned it off and waited for RELEASE. RELEASE has > come and we begun to setup the servre as it should work. As the server's > primary mission is to host a buch of site we decided to setup jails for each site, > So we did in december and put the server on prividers co-location severals > kilometer away from the office. Next day the server locked up. We were surprised > but just rebooted it, It locked up the next day gain. We cvsupped and rebuild the > system and the jails. The server locked up the next day. During the new year break > i have figureed that if there are more that one jail running the server locks withun > 24 hours with very hight probablity and within 48 hours with 100% probability. I > wrote into freebsd-stable about it. You have asked for debugger dump (pcpu, list of > lock, e.t.c). I could not do it at that time, so, i did not reply and just cvsupped in > the beginning of january and rebuilt the system and the jails again. Magically, after > that i could run 5 jails (did not tried more) for over a week and i already decided that > the bug was fixed and I could host the site. Alas, the next glitch did not wait to long. > After a few more days i saw a srange situatuon - i could not connect to server using > SSH. SSH replied about auth key or something like that. I rebootied the system and > ssh worked fine. Still have no idea what that was, but i setuo IPFIREWALL and a telnet > server for accept connection only from one ip address, so, if ssh fails I could use telnet. > After that i moved a real site with perl scripts, 1GB database, mail account (using qmail+vpopmail) > into one of the jails and the next day got the next problem: I could ping server, but could not > connect using ssh, www, telnet (110,25,23). I tried to recompile the kernel with INVARINATS, > WITNESS and disable the adaptive giant. I could not, so I wrote about it to you. You fixed > the source and now i recompliled the source again and today got a lock again with all those > options enabled and this time i could not ping the server. > I could thing that there is semething wrong with the hardware, but it passed > many days of testing. Anyway, my current idea are > > 1) Something wrong with jail code > 2) Something wrong with SMP code > 3) Something wrong with HYPERTHREADING code > 4) Something wrong with Memory disk code (md device, which i use) > 5) Something wrong with the hardware > > So, today, i opened bios, truned off hyperthreaading, fast strinmg operations and > all other 'more advanced' features in the bios. Turned off IDE controller the motherboard. > This rule out HYPERTHREADING code problem and somewaht hardware problem. > > I turned off MD usage (not more memory disk, but actually i need it very badly). > So i rule out the md code problem. > > Now, i will run some web access test (simulation of browsing for a week). It the > sever does not lock up, i will consider that i have found a workaround for some > hidden bug and the bug is somewere in md, ht code or hardware. > > If it locks up again the i will giveup jails and try for one more week. If it does not > lock up - jail code is the problem. > > If it locks up without jails, then i will turn off SMP and try again. > > If it locks up without nothing, then hardware if faulty and will have futher > choice of hanging myself or shooting in the head. > > I would like to see your and others' comments on the story and i have one > more question: what does options _KPOSIX_PRIORITY_SCHEDULING > do? May it be somehow related to the problem? > > The hardware is: > > MB dual xeon Supermicro X5DPE-G2 > CPU P4 XEON 2,667Ghz 512Kb cache 533mhz socket 604 > 2 Gb 266Mhz, DDR, ECC, Reg, 1GB dimm > 4 HDDs 120Gb (seagate baracuda 7200.7) > 3Ware Escalade 8506-4LP > Case Supermicro SC822T-550LP > Slim DVD/CD-RW Toshiba SD-R2412B IDE (OEM) > > The todays kernel CONFIG wich got locked: > > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident OMNI2 > > options SMP > > options QUOTA > > 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 directories > #options MD_ROOT # MD is a potential root device > #options NFSCLIENT # Network Filesystem Client > #options NFSSERVER # Network Filesystem Server > #options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > 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 extensions > #options KBD_INSTALL_CDEV # install a CDEV entry in /dev > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device da # Direct Access (disks) > device pass # Passthrough device (direct SCSI access) > device twe # 3ware ATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > #device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > device miibus # MII bus support > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > device em > > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp # Kernel PPP > 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) > > device bpf # Berkeley packet filter > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > > # FireWire support > device firewire # FireWire bus code > #device sbp # SCSI over FireWire (Requires scbus and da) > #device fwe # Ethernet over FireWire (non-standard!) > > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10000 > options IPFIREWALL_DEFAULT_TO_ACCEPT > > device snp > device speaker > > options DDB > options KDB > options BREAK_TO_DEBUGGER > options INVARIANT_SUPPORT > options INVARIANTS > options WITNESS > options WITNESS_KDB > options WITNESS_SKIPSPIN > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > DMESG (the config which got locked): > > Copyright (c) 1992-2005 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.3-STABLE #3: Sun Jan 23 01:04:00 MSK 2005 > matrix@omni2.itlegion.ru:/usr/obj/usr/src/sys/OMNI2 > WARNING: WITNESS option enabled, expect reduced performance. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.93-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 > Features=0xbfebfbff SE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 4160225280 (3967 MB) > avail memory = 4077486080 (3888 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > ioapic3 irqs 72-95 on motherboard > ioapic4 irqs 96-119 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: at device 0.1 (no driver attached) > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pci1: at device 28.0 (no driver attached) > pcib2: at device 29.0 on pci1 > pci2: on pcib2 > pci1: at device 30.0 (no driver attached) > pcib3: at device 31.0 on pci1 > pci3: on pcib3 > em0: port 0x3000-0x303f mem 0xfc200000-0xfc21ffff irq 28 at device 2 > .0 on pci3 > em0: Ethernet address: 00:30:48:2a:2d:bc > em0: Speed:N/A Duplex:N/A > em1: port 0x3040-0x307f mem 0xfc220000-0xfc23ffff irq 29 at device 2 > .1 on pci3 > em1: Ethernet address: 00:30:48:2a:2d:bd > em1: Speed:N/A Duplex:N/A > pcib4: at device 3.0 on pci0 > pci4: on pcib4 > pci4: at device 28.0 (no driver attached) > pcib5: at device 29.0 on pci4 > pci5: on pcib5 > pci4: at device 30.0 (no driver attached) > pcib6: at device 31.0 on pci4 > pci6: on pcib6 > twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x4000-0x400f mem 0xfc800000-0xfcffffff irq 72 at device 1. > 0 on pci6 > twe0: [GIANT-LOCKED] > twe0: 4 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > pcib7: at device 30.0 on pci0 > pci7: on pcib7 > pci7: at device 1.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x2060-0x206f,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 > ata0: channel #0 on atapci0 > ata2: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > speaker0: port 0x61 on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > atkbd0: [GIANT-LOCKED] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > orm0: at iomem 0xe0000-0xe3fff,0xc9000-0xc9fff,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 10.000 msec > ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 10000 packets/entry > by default > acd0: CDRW at ata0-slave UDMA33 > twed0: on twe0 > twed0: 343417MB (703318656 sectors) > SMP: AP CPU #2 Launched! > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > Mounting root from ufs:/dev/twed0s1a > em0: Link is up 100 Mbps Full Duplex > > _______________________________________________ > 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" >