From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 01:38:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 A254316A4DA for ; Sun, 27 Aug 2006 01:38:16 +0000 (UTC) (envelope-from j.porter.clark@nasa.gov) Received: from x500msfc.msfc.nasa.gov (x500msfc.msfc.nasa.gov [198.116.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22E7243D49 for ; Sun, 27 Aug 2006 01:38:16 +0000 (GMT) (envelope-from j.porter.clark@nasa.gov) Received: from drum.msfc.nasa.gov by x500msfc.msfc.nasa.gov with ESMTP for freebsd-stable@freebsd.org; Sat, 26 Aug 2006 20:38:15 -0500 Received: by drum.msfc.nasa.gov (Postfix, from userid 134) id D71DE6144; Sat, 26 Aug 2006 20:38:14 -0500 (CDT) Date: Sat, 26 Aug 2006 20:38:14 -0500 From: "J. Porter Clark" To: freebsd-stable@freebsd.org Message-Id: <20060827013814.GA1441@drum.msfc.nasa.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: http://www.msfc.nasa.gov/ X-PGP-Key-ID: 0x677B780D User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: 6.1-STABLE panic using revoked pty X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 01:38:16 -0000 I'm having a problem with a surprisingly easily provoked panic on an SMP machine. (If I try it with a non-SMP machine, I can get it to hang but not panic.) The easiest way I've found to do it is to login to target SMP machine "drum" from two different windows on some other machine "remote" using ssh. In the first window: remote % ssh drum Password: Last login: Sat Aug 26 12:02:07 2006 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE (DRUM6) #0: Fri Aug 25 10:07:09 CDT 2006 $ In the second window, log in: remote % ssh drum Password: Last login: Sat Aug 26 12:02:07 2006 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE (DRUM6) #0: Fri Aug 25 10:07:09 CDT 2006 $ ls -l `tty` crw------- 1 jpc tty 0, 142 Aug 26 18:58 /dev/ttyp1 $ exit Now go back to the first window and write to the other terminal's revoked tty: $ echo hello > /dev/ttyp1 Go to the second window and log in again, or try to: remote % ssh drum Password: ...and that's as far as I get. drum has panicked. drum# kgdb kernel.debug /usr/crash/vmcore.13 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xe921f974 frame pointer = 0x28:0xe921f988 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1287 (sshd) trap number = 12 panic: page fault cpuid = 0 Uptime: 8m57s Dumping 2047 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 2047MB (524032 pages) #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) x/80xw 0xe921f974 0xe921f974: 0xc0571543 0x00000000 0xc6b74800 0xc6b74800 0xe921f984: 0xc6bb6c00 0xe921f9a4 0xc05c01a9 0xc6b74888 0xe921f994: 0x00000000 0x00000000 0xc6b74810 0xc6b74800 0xe921f9a4: 0xe921f9bc 0xc05beda0 0xc6b74800 0xc6b74800 0xe921f9b4: 0xc73b0e80 0xc6b74800 0xe921f9d8 0xc05c32ad 0xe921f9c4: 0xc6b74800 0x00000001 0xc6ebc400 0xe921fbcc 0xe921f9d4: 0xc07c0520 0xe921f9f4 0xc056315b 0xc6ebc400 0xe921f9e4: 0x00000003 0x00002000 0xc6bb6c00 0x00000000 0xe921f9f4: 0xe921fa34 0xc0533c6b 0xc6ebc400 0x00000003 0xe921fa04: 0x00002000 0xc6bb6c00 0xc6ebc400 0xc71ff440 0xe921fa14: 0xc6bb6c00 0xc07de2c0 0xc71ff440 0x00000000 0xe921fa24: 0xc6bb6c00 0x00000000 0xe921fbcc 0x00000003 0xe921fa34: 0xe921fa40 0xc073e0b8 0xe921fa64 0xe921fb20 0xe921fa44: 0xc05f33a8 0xc07b2a60 0xe921fa64 0x00000000 0xe921fa54: 0x00000180 0xc6bb6c00 0xc71ff440 0xe921fa78 0xe921fa64: 0xc07ddcc0 0xc71ff440 0x00000003 0xc6f71680 0xe921fa74: 0xc6bb6c00 0x00000006 0xe921fa84 0xc146cd20 0xe921fa84: 0x00000400 0xc6b74800 0xe921fa94 0xc0582668 0xe921fa94: 0xe921faac 0xc05827ed 0xc07bfe80 0x00000400 0xe921faa4: 0xc6b74800 0x00000000 0xe921fad0 0xc05c0c73 (kgdb) quit drum# addr2line -e kernel.debug 0xc0571543 ../../../kern/kern_event.c:1534 drum# addr2line -e kernel.debug 0xc05c01a9 ../../../kern/tty.c:2427 drum# addr2line -e kernel.debug 0xc05beda0 ../../../kern/tty.c:1681 drum# addr2line -e kernel.debug 0xc05c32ad ../../../sys/linedisc.h:136 drum# addr2line -e kernel.debug 0xc056315b ../../../kern/kern_conf.c:242 drum# addr2line -e kernel.debug 0xc0533c6b ../../../fs/devfs/devfs_vnops.c:680 drum# addr2line -e kernel.debug 0xc05f33a8 ./vnode_if.h:198 drum# addr2line -e kernel.debug 0xc0582668 ../../../kern/kern_malloc.c:251 drum# addr2line -e kernel.debug 0xc05827ed ../../../kern/kern_malloc.c:404 drum# addr2line -e kernel.debug 0xc05c0c73 ../../../kern/tty.c:2829 Copyright (c) 1992-2006 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 6.1-STABLE #0: Fri Aug 25 10:07:09 CDT 2006 jpc@drum.msfc.nasa.gov:/usr/src/sys/i386/compile/DRUM6 MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Features2=0x4400> Logical CPUs per core: 2 real memory = 2147483648 (2048 MB) avail memory = 2091847680 (1994 MB) 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: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic2: Assuming intbase of 32 ioapic3: Assuming intbase of 48 ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard ioapic2 irqs 32-47 on motherboard ioapic3 irqs 48-63 on motherboard netsmb_dev: loaded cpu0 on motherboard cpu1 on motherboard cpu2 on motherboard cpu3 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 7.0 on pci0 pci1: on pcib1 fwohci0: port 0xa800-0xa87f mem 0xfc8ff000-0xfc8ff7ff irq 24 at device 8.0 on pci1 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:11:06:00:00:00:50:66 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:06:00:50:66 fwe0: Ethernet address: 02:11:06:00:50:66 fwe0: if_start running deferred for Giant fwip0: on firewire0 fwip0: Firewire address: 00:11:06:00:00:00:50:66 @ 0xfffe00000000, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) ohci0: mem 0xfc8fd000-0xfc8fdfff irq 25 at device 9.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfc8fe000-0xfc8fefff irq 20 at device 9.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xfc8ffc00-0xfc8ffcff irq 21 at device 9.2 on pci1 ehci0: [GIANT-LOCKED] usb2: EHCI version 0.95 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 5 ports with 5 removable, self powered em0: port 0xc800-0xc83f mem 0xfea60000-0xfea7ffff irq 28 at device 8.0 on pci0 em0: Ethernet address: 00:30:48:53:37:e4 em0: [FAST] em1: port 0xd000-0xd03f mem 0xfeba0000-0xfebbffff irq 26 at device 9.0 on pci0 em1: Ethernet address: 00:30:48:53:37:e5 em1: [FAST] ahd0: port 0xd800-0xd8ff,0xd400-0xd4ff mem 0xfebfa000-0xfebfbfff irq 30 at device 10.0 on pci0 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs ahd1: port 0xe400-0xe4ff,0xe000-0xe0ff mem 0xfebfc000-0xfebfdfff irq 31 at device 10.1 on pci0 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs drm0: port 0xe800-0xe8ff mem 0xfd000000-0xfdffffff,0xfebff000-0xfebfffff irq 29 at device 11.0 on pci0 info: [drm] Initialized mach64 1.0.0 20020904 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 15.1 on pci0 ata0: on atapci0 ata1: on atapci0 ohci2: mem 0xfebfe000-0xfebfefff irq 17 at device 15.2 on pci0 ohci2: [GIANT-LOCKED] usb3: OHCI version 1.0, legacy support usb3: on ohci2 usb3: USB revision 1.0 uhub3: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 4 ports with 4 removable, self powered isab0: at device 15.3 on pci0 isa0: on isab0 pcib255: pcibus 255 on motherboard pci255: on pcib255 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 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 ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) speaker0: at port 0x61 on isa0 unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA66 Waiting 5 seconds for SCSI devices to settle firewire0: New S400 device ID:0010b920007ad726 sa0 at ahd1 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0 at ahd0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) da1 at ahd0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da1: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) da2 at sbp0 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-4 device da2: 50.000MB/s transfers da2: 286103MB (585938944 512 byte sectors: 255H 63S/T 36473C) cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted -- J. Porter Clark j.porter.clark@nasa.gov NASA/MSFC Flight & Ground Computers Branch (EI31) Phone (256)544-3661 Fax (256)544-6193 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 01:46:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 4FED016A4DD for ; Sun, 27 Aug 2006 01:46:55 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id A18DD43D45 for ; Sun, 27 Aug 2006 01:46:54 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J4M00J0ZVM5U350@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 03:46:53 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J4M009V5VM5NOE0@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 03:46:53 +0200 (CEST) Date: Sun, 27 Aug 2006 03:46:52 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH To: freebsd-stable@freebsd.org Message-id: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 01:46:55 -0000 Hello, I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, floppy and CD-rom. It doesn't have built in networking, neither wired nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release installed a long time, and was recently upgraded to 4.11-release from CD, sucessfully. However, I would like better pccard support, ie. 32 bit cardbus and wireless network cards, so I would like to install 6.1-release (or -stable) on it. However, when I try the 6.1-release CD (CD1), it boots as far as loading the kernel, botting the kernel, and then reboots again?? I have also tried 6.0-release, and 7.0-current (both July 06 and Aug 06 snapshots) with the same results. Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 03:44:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7C14616A4E1 for ; Sun, 27 Aug 2006 03:44:26 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C21143D45 for ; Sun, 27 Aug 2006 03:44:25 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1292623wxd for ; Sat, 26 Aug 2006 20:44:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lFk+HRTWydGMlEriQNv2kQbV5TK2vogTqN0bwRcm31LioepQ8zy7/a/QEGfyqwMnFGlBz3Kw5SztOq5risdbSgg6z906JpKaZkeMfwxVgvHje9QYEiB+O0v5gJc867T4huQNUrWGfjCcPM3U8gE7Z9hhX/ZXuKgBeb3oHj8tuKQ= Received: by 10.70.32.6 with SMTP id f6mr7045985wxf; Sat, 26 Aug 2006 20:44:24 -0700 (PDT) Received: by 10.70.49.3 with HTTP; Sat, 26 Aug 2006 20:44:24 -0700 (PDT) Message-ID: Date: Sat, 26 Aug 2006 22:44:24 -0500 From: "Nikolas Britton" To: "Torfinn Ingolfsen" In-Reply-To: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 03:44:26 -0000 On 8/26/06, Torfinn Ingolfsen wrote: > Hello, > > I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, > floppy and CD-rom. It doesn't have built in networking, neither wired > nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release > installed a long time, and was recently upgraded to 4.11-release from > CD, sucessfully. > > However, I would like better pccard support, ie. 32 bit cardbus and > wireless network cards, so I would like to install 6.1-release (or > -stable) on it. How do you know it has CardBus / PCMCIA 2.1 / JEIDA 4.2? have you checked? This standard was introduced in 1995. > However, when I try the 6.1-release CD (CD1), it boots as far as > loading the kernel, botting the kernel, and then reboots again?? > > I have also tried 6.0-release, and 7.0-current (both July 06 and Aug 06 > snapshots) with the same results. > > Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? Yep. Try DragonFly BSD, it's based on FreeBSD 4.x code so it should be able to cope with an antique such as this. NetBSD would also be a good choice. I would say at least 32MB for FreeBSD 6.x... my FreeBSD 6.1-STABLE kernel is using 52MB (I think I have debugging enabled though). -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 03:47:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 E4B4616A4DE for ; Sun, 27 Aug 2006 03:47:44 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E7F343D4C for ; Sun, 27 Aug 2006 03:47:44 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [10.242.169.24] (c-67-171-135-169.hsd1.or.comcast.net [67.171.135.169]) by mail.twinthornes.com (Postfix) with ESMTP id E051A21; Sat, 26 Aug 2006 20:47:42 -0700 (PDT) Received: from 127.0.0.1 (AVG SMTP 7.1.405 [268.11.6/428]); Sat, 26 Aug 2006 20:48:37 -0700 Message-ID: <44F11615.1050902@bitfreak.org> Date: Sat, 26 Aug 2006 20:48:37 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Torfinn Ingolfsen References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 03:47:45 -0000 Torfinn Ingolfsen wrote: > Hello, > > I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, > floppy and CD-rom. It doesn't have built in networking, neither wired > nor wireless. It does have PC card slots. It has had FreeBSD > 4.9-release installed a long time, and was recently upgraded to > 4.11-release from CD, sucessfully. > > However, I would like better pccard support, ie. 32 bit cardbus and > wireless network cards, so I would like to install 6.1-release (or > -stable) on it. However, when I try the 6.1-release CD (CD1), it > boots as far as loading the kernel, botting the kernel, and then > reboots again?? Try turning off all power management and plug-and-play support in the BIOS and booting FreeBSD without ACPI. Try combinations of these three things. Often older hardware has really broken APM/ACPI support that makes FreeBSD do odd things. Failing that, you may need to build a custom kernel with just the minimum required to get yourself to a shell prompt. You can build a new kernel with cardbus, usb and other extras after you get FreeBSD installed. -- Darren Pilgrim From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 04:12:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7C2B216A4DD for ; Sun, 27 Aug 2006 04:12:28 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 076A643D49 for ; Sun, 27 Aug 2006 04:12:27 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1296728wxd for ; Sat, 26 Aug 2006 21:12:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=f8cr/EgDIkiHP0PG9xsxqCPKcfLAs2APf1y3BO/KzZLeog0UFaTcD9of7DfGnJ0DDt0cpBfWNMDguaXxidBtEyyx+frezZEY2vJjAZ3oWIKT+kaC2Gee54JSznKS0jplCai4TvjQQ0Q/zwiOf0/m0PgWAvufIrg7fTYpoH2VUQo= Received: by 10.70.52.5 with SMTP id z5mr7162982wxz; Sat, 26 Aug 2006 21:12:27 -0700 (PDT) Received: by 10.70.49.3 with HTTP; Sat, 26 Aug 2006 21:12:27 -0700 (PDT) Message-ID: Date: Sat, 26 Aug 2006 23:12:27 -0500 From: "Nikolas Britton" To: "Torfinn Ingolfsen" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 04:12:28 -0000 On 8/26/06, Nikolas Britton wrote: > On 8/26/06, Torfinn Ingolfsen wrote: > > Hello, > > > > I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, > > floppy and CD-rom. It doesn't have built in networking, neither wired > > nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release > > installed a long time, and was recently upgraded to 4.11-release from > > CD, sucessfully. > > > > However, I would like better pccard support, ie. 32 bit cardbus and > > wireless network cards, so I would like to install 6.1-release (or > > -stable) on it. > > How do you know it has CardBus / PCMCIA 2.1 / JEIDA 4.2? have you > checked? This standard was introduced in 1995. > > > However, when I try the 6.1-release CD (CD1), it boots as far as > > loading the kernel, botting the kernel, and then reboots again?? > > > > I have also tried 6.0-release, and 7.0-current (both July 06 and Aug 06 > > snapshots) with the same results. > > > > Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? > > Yep. Try DragonFly BSD, it's based on FreeBSD 4.x code so it should be > able to cope with an antique such as this. NetBSD would also be a good > choice. I would say at least 32MB for FreeBSD 6.x... my FreeBSD > 6.1-STABLE kernel is using 52MB (I think I have debugging enabled > though). > Ok I checked three other 6.x boxes. Dmesg reports the kernel using 35MB, 34MB, and 19MB of RAM at system startup. Top reports 297MB, 38MB, 167MB, and 621MB active... The two largest numbers are running X11/KDE and the two smallest numbers are servers. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 05:42:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0587D16A4DF for ; Sun, 27 Aug 2006 05:42:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 200B843D46 for ; Sun, 27 Aug 2006 05:42:14 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 15960 invoked by uid 399); 27 Aug 2006 05:42:12 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 27 Aug 2006 05:42:12 -0000 Message-ID: <44F130B2.8010702@FreeBSD.org> Date: Sat, 26 Aug 2006 22:42:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Dmitry Pryanishnikov References: <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> <44EB6411.4040406@paladin.bulgarpress.com> <20060823193309.GA77890@rambler-co.ru> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru> <20060827002203.A39026@atlantis.atlantis.dp.ua> In-Reply-To: <20060827002203.A39026@atlantis.atlantis.dp.ua> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 05:42:16 -0000 Dmitry Pryanishnikov wrote: > I've tried to use sysutils/portconf, but found that it still doesn't > give an universal solution: I think we need to be careful what our expectations of "universal" are with a ports tree as large, and a userbase as diverse, as what we have. However ... > 1) it doesn't work if /usr/ports is a link to another location. Sure it does. You just have to be smarter about how you specify the triggers in make.conf. :) I have the following: .if !empty(.CURDIR:M/mnt/slave/space/ports*) # Begin portconf settings ... Works like a charm. > 2) it still doesn't affect OPTIONS (in the ports sense); try e.g. the > following: If it's not working at all to start with (as you specified above), then this additional example of brokenness is meaningless. Additionally, OPTIONS ignores settings in the environment at all times to start with. It's easy enough to test this for yourself by placing something in make.conf. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 07:13:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 8A5AF16A4DD for ; Sun, 27 Aug 2006 07:13:35 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F7A43D45 for ; Sun, 27 Aug 2006 07:13:33 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k7R7DTZU027112 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 27 Aug 2006 17:13:29 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k7R7DT5w023557; Sun, 27 Aug 2006 17:13:29 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k7R7DTYq023556; Sun, 27 Aug 2006 17:13:29 +1000 (EST) (envelope-from peter) Date: Sun, 27 Aug 2006 17:13:29 +1000 From: Peter Jeremy To: Torfinn Ingolfsen Message-ID: <20060827071329.GK16768@turion.vk2pj.dyndns.org> References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1y1tiN5hVw5cPBDe" Content-Disposition: inline In-Reply-To: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 07:13:35 -0000 --1y1tiN5hVw5cPBDe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2006-Aug-27 03:46:52 +0200, Torfinn Ingolfsen wrote: >I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, =2E.. >However, when I try the 6.1-release CD (CD1), it boots as far as >loading the kernel, botting the kernel, and then reboots again?? The CD-ROMs create a RAMdisk and need a minimum of 24MB last I checked. Once you have FreeBSD installed, it will limp along in 16MB (though not very happily). I strongly suggest you find a SODIMM to expand it. --=20 Peter Jeremy --1y1tiN5hVw5cPBDe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8UYZ/opHv/APuIcRAlCFAJ9Nw/0ekm2dx059EOmVW3kBhE/thgCgiaFb IqMlz/FPWHyQq0ptcUEM4d0= =FQlt -----END PGP SIGNATURE----- --1y1tiN5hVw5cPBDe-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 08:06:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5F90E16A5DC for ; Sun, 27 Aug 2006 08:06:14 +0000 (UTC) (envelope-from orlic@big12.ru) Received: from mail.uzel9.ru (brown.ud9.ru [83.143.48.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C76243D45 for ; Sun, 27 Aug 2006 08:06:13 +0000 (GMT) (envelope-from orlic@big12.ru) Received: from www.big12.ru ([83.143.49.30] helo=big12.ru) by mail.uzel9.ru with esmtp id 1GHFek-0000zW-Nb for ; Sun, 27 Aug 2006 13:06:10 +0500 Received: from NOTEBOOK ([192.168.0.2]) by big12.ru ([192.168.0.206]) with SMTP (MDaemon.PRO.v6.7.9.R) for ; Sun, 27 Aug 2006 13:04:41 +0500 Date: Sun, 27 Aug 2006 13:04:54 +0500 From: =?utf-8?B?0J7RgNC70L7QsiDQldCy0LPQtdC90LjQuQ==?= X-Mailer: The Bat! (v3.80.06) Professional Organization: =?utf-8?B?0J7QntCeICLQmtCw0YDQsNGCIg==?= X-Priority: 3 (Normal) Message-ID: <116211880.20060827130454@big12.ru> To: freebsd-stable@freebsd.org In-Reply-To: <200608241719.10921.jhb@freebsd.org> References: <200608232337.k7NNbJT8032059@repoman.freebsd.org> <200608241520.47903.jhb@freebsd.org> <20060824194220.GA59229@submonkey.net> <200608241719.10921.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Authenticated-Sender: orlic@big12.ru X-MDRemoteIP: 192.168.0.2 X-Return-Path: orlic@big12.ru X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-Spam-Score: 0.1 X-Spam-Report: Spam detection software, running on the system "mail.uzel9.ru", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi! I'm a junior in FreeBSD, and I faced with problem. I've a FreeBSD 6.1-stable box as a gate+firewall, and I want to divert incoming requests to my web-server, placed in DeMilitarized Zone (DMZ). To do this I wrote down settings in /etc/rc.conf as shown above: [...] Content analysis details: (0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 FORGED_RCVD_HELO Received: contains a forged HELO Subject: IPFW + NATD rules X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?utf-8?B?0J7RgNC70L7QsiDQldCy0LPQtdC90LjQuQ==?= List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 08:06:14 -0000 Hi! I'm a junior in FreeBSD, and I faced with problem. I've a FreeBSD 6.1-stable box as a gate+firewall, and I want to divert incoming requests to my web-server, placed in DeMilitarized Zone (DMZ). To do this I wrote down settings in /etc/rc.conf as shown above: natd_flags="-redirect_port tcp 80 192.168.1.234 80" natd_flags="-redirect_port tcp 443 192.168.1.234 443" I think, that all packets incoming from Internet will be diverted from the External interface via DMZ interface to my We-server. Is it right? If not, why not, and what the way to make it working? Thanks a lot, yours sincerely Eugene Orlov, Russia, Izhevsk orlic@big12.ru +7 3412 43-12-12 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 08:42:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 A19A316A4E2 for ; Sun, 27 Aug 2006 08:42:36 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 219F843D46 for ; Sun, 27 Aug 2006 08:42:36 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J4N00JOEEUZU5D0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 10:42:35 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J4N00288EUYUZ00@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 10:42:35 +0200 (CEST) Date: Sun, 27 Aug 2006 10:42:34 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: To: freebsd-stable@freebsd.org Message-id: <20060827104234.97acfc35.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 08:42:36 -0000 On Sat, 26 Aug 2006 22:44:24 -0500 Nikolas Britton wrote: > How do you know it has CardBus / PCMCIA 2.1 / JEIDA 4.2? have you > checked? This standard was introduced in 1995. I don't *know* it, but all evidence seems to point in that direction. :-) Quote from chapter 7 of the user guide: "Important: the PC Card slots on the computer are CardBus slots that support 16- and 32-bit PC Cards. They support the newer generation of 32-bit (CardBus) designed to take advantage of audio, video, multifunction and high-speed LAN capabilities". BTW, first edition of the User Guide is from March 1997, I also tested with a CardBus card, and it fits into the slot. > Yep. Try DragonFly BSD, it's based on FreeBSD 4.x code so it should be Ok, So DragonFlyBSD supports CardBus cards? I'll try it. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 09:00:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9A6A616A4DD for ; Sun, 27 Aug 2006 09:00:32 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D44043D4C for ; Sun, 27 Aug 2006 09:00:32 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J4N00JX7FOVTWD0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 11:00:31 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J4N002GKFOUUQ10@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 11:00:31 +0200 (CEST) Date: Sun, 27 Aug 2006 11:00:30 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20060827071329.GK16768@turion.vk2pj.dyndns.org> To: freebsd-stable@freebsd.org Message-id: <20060827110030.cebfbbf0.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827071329.GK16768@turion.vk2pj.dyndns.org> Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 09:00:32 -0000 On Sun, 27 Aug 2006 17:13:29 +1000 Peter Jeremy wrote: > The CD-ROMs create a RAMdisk and need a minimum of 24MB last I > checked. And I guess that the floppies work in the same way? > Once you have FreeBSD installed, it will limp along in 16MB > (though not very happily). Hmm, I see. I'm planning to run X on this old box (it's going to be a PictureFrame project), perhaps that will not work. > I strongly suggest you find a SODIMM to > expand it. Ok. Are all SODIMMs equal (ie. a real standard), or do I hvae to look specifically for memory upgrades for the Armada 1580 (or 1500 series)? -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 10:09:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 6952E16A4DF for ; Sun, 27 Aug 2006 10:09:21 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 773FC43D70 for ; Sun, 27 Aug 2006 10:09:16 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail09.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k7RA9BjD018497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 27 Aug 2006 20:09:11 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k7RA9BHn032914; Sun, 27 Aug 2006 20:09:11 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k7RA9B2t032913; Sun, 27 Aug 2006 20:09:11 +1000 (EST) (envelope-from peter) Date: Sun, 27 Aug 2006 20:09:11 +1000 From: Peter Jeremy To: Torfinn Ingolfsen Message-ID: <20060827100911.GM16768@turion.vk2pj.dyndns.org> References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827071329.GK16768@turion.vk2pj.dyndns.org> <20060827110030.cebfbbf0.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qgof7w7UksPF5inF" Content-Disposition: inline In-Reply-To: <20060827110030.cebfbbf0.torfinn.ingolfsen@broadpark.no> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 10:09:21 -0000 --Qgof7w7UksPF5inF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2006-Aug-27 11:00:30 +0200, Torfinn Ingolfsen wrote: >On Sun, 27 Aug 2006 17:13:29 +1000 >Peter Jeremy wrote: > >> The CD-ROMs create a RAMdisk and need a minimum of 24MB last I >> checked. > >And I guess that the floppies work in the same way? Yes. >> Once you have FreeBSD installed, it will limp along in 16MB >> (though not very happily).=20 > >Hmm, I see. I'm planning to run X on this old box (it's going to be a >PictureFrame project), perhaps that will not work. I think you would be thrashing if there was any actual activity. I'll prod a friend with the same setup to comment tomorrow. >> I strongly suggest you find a SODIMM to >> expand it. > >Ok. Are all SODIMMs equal (ie. a real standard), or do I hvae to look >specifically for memory upgrades for the Armada 1580 (or 1500 series)? I'm 99% certain that you can't use anything bigger than 64MB (at least a 128MB Cpq Armada SODIMM that I had wouldn't work in any of the 15xx machines I tried it in - that included a 1580). I'm not sure how interchangeable they are. --=20 Peter Jeremy --Qgof7w7UksPF5inF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8W9H/opHv/APuIcRAtYOAJ4k+WOeJQt76xRkrEX4XWB3na1iJwCgsADP +0yviBwanTFM3TI3YSY/Z0w= =9fvn -----END PGP SIGNATURE----- --Qgof7w7UksPF5inF-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 11:24:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 CBF0516A4DE for ; Sun, 27 Aug 2006 11:24:19 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0615543D45 for ; Sun, 27 Aug 2006 11:24:18 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7RBOH3E049290 for ; Sun, 27 Aug 2006 11:24:17 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7RBODgO049287 for ; Sun, 27 Aug 2006 11:24:17 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Sun, 27 Aug 2006 11:24:13 +0000 (GMT) From: Michael Abbott To: freebsd-stable@freebsd.org Message-ID: <20060827102135.B49194@saturn.araneidae.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 11:24:19 -0000 I've been trying to make some sense of the "NFS locking" issue. I am trying to run # make installworld DESTDIR=/mnt where /mnt is an NFS mount on a FreeBSD 4.11 server, but I am unable to get past a call to `lockf`. On this mailing list I've seen a thread starting with this message: http://lists.freebsd.org/pipermail/freebsd-stable/2006-August/027561.html and elsewhere I've seen this thread: http://www.gatago.com/mpc/lists/freebsd/stable/21851805.html The gist seems to be that rpc.lockd is badly behaved and broken and nobody knows how to fix it. So, in case my experience is any help, here is what I can report. 1. I have installed a fresh installation of FreeBSD 6.1 from the CD, 6.1-RELEASE-i386-disc1.iso, and have run `cd /usr/src; make buildworld; make buildkernel` successfully (takes nearly 8 hours, but then it is a fanless machine). The full distribution (as installed by sysinstall) is present, but nothing else. 2. Intending to experiment with network booting, I've attempted `make installworld DESTDIR=/mnt`, where /mnt is an NFS mount point on my master server, running FreeBSD 4.11-RELEASE-p11. 3. This fails when invoking lockf. To work around this, I have started rpc.lockd on the 4.11 server and configured all of the following lines in rc.conf: rpcbind_enable="YES" nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" 4. Now here is the behaviour: # mount $MY_SERVER:$MY_PATH /mnt # lockf /mnt/test ls This works just fine # cd /usr/src; make installworld DESTDIR=/mnt This hangs in lockf, and is unkillable (even `kill -9` is no good, and ps shows state = D+). So let's start another shell (Alt-F2): # lockf /mnt/test ls Also hangs. Rebooting the test machine clears the problem, returning to the state at the start of point (4), and the problem is completely repeatable in my configuration. Some observations: - Hanging in "uninterruptible sleep" is not good. No doubt it's quite possible that my 4.11 server has a broken rpc.lockd (or maybe I've not configured it right: I just started rpc.lockd, rather than restarting the server), but the behaviour of 6.1 is exceptionally unfriendly. In particular, unkillable processes look like outright bugs to me. - The conversation on mpc.lists.freebsd.stable (and elsewhere) looks alarming. I get the impression that this part of FreeBSD 6.1 is really rather broken and that there's no real sense of what to do about it. I hope I've sent this mail to the right place and that it's of some help. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 13:08:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0A2CB16A4E1 for ; Sun, 27 Aug 2006 13:08:13 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E97144B27 for ; Sun, 27 Aug 2006 13:08:11 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.6/8.13.6) with ESMTP id k7RD7wY4071502; Sun, 27 Aug 2006 15:07:58 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.6/8.13.6/Submit) id k7RD7wsC071501; Sun, 27 Aug 2006 15:07:58 +0200 (CEST) (envelope-from byshenknet) Date: Sun, 27 Aug 2006 15:07:58 +0200 From: Greg Byshenk To: Michael Abbott Message-ID: <20060827130758.GO633@core.byshenk.net> References: <20060827102135.B49194@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060827102135.B49194@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on core.byshenk.net Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 13:08:13 -0000 On Sun, Aug 27, 2006 at 11:24:13AM +0000, Michael Abbott wrote: > I've been trying to make some sense of the "NFS locking" issue. I am > trying to run > # make installworld DESTDIR=/mnt > where /mnt is an NFS mount on a FreeBSD 4.11 server, but I am unable to > get past a call to `lockf`. I have not closely followed the discussion, as I have not experienced the problem. I am currently running FreeBSD6 based fileservers in an environment that includes FreeBSD, Linux (multiple flavors), Solaris, and Irix clients, and have experienced no nfs locking issues (I have one occasional problem with 64-bit Linux clients, but it is not locking related and appears to be due to a 64-bit Linux problem). Further, (though there may well be problems with nfs locking) I cannot recreate the problem you described -- at least in a FreeBSD6 environment. I have just performed a test of what you describe, using 'smbtest' (6.1-STABLE #17: Fri Aug 25 12:25:19 CEST 2006) as the client and 'data-2' (FreeBSD 6.1-STABLE #16: Wed Aug 9 15:38:12 CEST 2006) as the server. data-2 # mkdir /export/rw/bsd6root/ ## /export/rw is already exported via NFS smbtest # mount data-2:/export/rw/bsd6root /mnt smbtest # cd /usr/src smbtest # make installworld DESTDIR=/mnt [...] makewhatis /mnt/usr/share/man makewhatis /mnt/usr/share/openssl/man rm -rf /tmp/install.2INObZ3j smbtest # Which is to say that it completed successfully. Which suggests that there is not a serious and ongoing problem. There may well be a problem with FreeBSD4, but I no longer have any NFS servers running FreeBSD4.x, so I cannot confirm. Alternatively, there may have been a problem in 6.1-RELEASE that has since been solved in 6.1-STABLE that I am using. Or there could be a problem with the configuration of your server. Or there could be something else going on (in the network...?). But to see what exactly is happening in your case, you would probably want to look at what exactly is happening on the client, the server, and the network between them. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 14:18:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7355E16A559 for ; Sun, 27 Aug 2006 14:18:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52E3A4450A for ; Sun, 27 Aug 2006 13:54:47 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k7RDsWSN081833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Aug 2006 16:54:32 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8) with ESMTP id k7RDsYRL010656; Sun, 27 Aug 2006 16:54:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8/Submit) id k7RDsYj8010655; Sun, 27 Aug 2006 16:54:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 27 Aug 2006 16:54:34 +0300 From: Kostik Belousov To: Michael Abbott Message-ID: <20060827135434.GH79046@deviant.kiev.zoral.com.ua> References: <20060827102135.B49194@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uJrvpPjGB3z5kYrA" Content-Disposition: inline In-Reply-To: <20060827102135.B49194@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=1.9 required=5.0 tests=DNS_FROM_RFC_ABUSE, SPF_NEUTRAL,UNPARSEABLE_RELAY autolearn=no version=3.1.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 14:18:59 -0000 --uJrvpPjGB3z5kYrA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 27, 2006 at 11:24:13AM +0000, Michael Abbott wrote: > I've been trying to make some sense of the "NFS locking" issue. I am=20 > trying to run > # make installworld DESTDIR=3D/mnt > where /mnt is an NFS mount on a FreeBSD 4.11 server, but I am unable to= =20 > get past a call to `lockf`. >=20 > On this mailing list I've seen a thread starting with this message: > http://lists.freebsd.org/pipermail/freebsd-stable/2006-August/027561.html > and elsewhere I've seen this thread: > http://www.gatago.com/mpc/lists/freebsd/stable/21851805.html >=20 > The gist seems to be that rpc.lockd is badly behaved and broken and nobod= y=20 > knows how to fix it. So, in case my experience is any help, here is what= =20 > I can report. >=20 > 1. I have installed a fresh installation of FreeBSD 6.1 from the CD,=20 > 6.1-RELEASE-i386-disc1.iso, and have run `cd /usr/src; make buildworld;= =20 > make buildkernel` successfully (takes nearly 8 hours, but then it is a=20 > fanless machine). The full distribution (as installed by sysinstall) is= =20 > present, but nothing else. >=20 > 2. Intending to experiment with network booting, I've attempted > `make installworld DESTDIR=3D/mnt`, where /mnt is an NFS mount point on m= y=20 > master server, running FreeBSD 4.11-RELEASE-p11. >=20 > 3. This fails when invoking lockf. To work around this, I have started= =20 > rpc.lockd on the 4.11 server and configured all of the following lines in= =20 > rc.conf: > rpcbind_enable=3D"YES" > nfs_client_enable=3D"YES" > rpc_lockd_enable=3D"YES" > rpc_statd_enable=3D"YES" >=20 > 4. Now here is the behaviour: >=20 > # mount $MY_SERVER:$MY_PATH /mnt > # lockf /mnt/test ls > This works just fine > # cd /usr/src; make installworld DESTDIR=3D/mnt > This hangs in lockf, and is unkillable (even `kill -9` is no good, and ps= =20 > shows state =3D D+). So let's start another shell (Alt-F2): > # lockf /mnt/test ls > Also hangs. >=20 > Rebooting the test machine clears the problem, returning to the state at= =20 > the start of point (4), and the problem is completely repeatable in my=20 > configuration. >=20 >=20 > Some observations: >=20 > - Hanging in "uninterruptible sleep" is not good. No doubt it's quite= =20 > possible that my 4.11 server has a broken rpc.lockd (or maybe I've not=20 > configured it right: I just started rpc.lockd, rather than restarting the= =20 > server), but the behaviour of 6.1 is exceptionally unfriendly. In=20 > particular, unkillable processes look like outright bugs to me. >=20 > - The conversation on mpc.lists.freebsd.stable (and elsewhere) looks=20 > alarming. I get the impression that this part of FreeBSD 6.1 is really= =20 > rather broken and that there's no real sense of what to do about it. Make sure that rpc.statd is running. For debugging purposes, tcpdump of the corresponding communications would be quite useful. Besides this, output of ps auxww | grep 'rpc\.' may be interesting. --uJrvpPjGB3z5kYrA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8aQZC3+MBN1Mb4gRAuyrAJ9Ai8k0z360StJsvDDzP8+JRnt3vACeKEvZ fRiLTmiJ05l7ykyRG0fl1ss= =wS7e -----END PGP SIGNATURE----- --uJrvpPjGB3z5kYrA-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 14:35:28 2006 Return-Path: X-Original-To: stable@FreeBSD.org 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 4A61716A4EF; Sun, 27 Aug 2006 14:35:28 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EAC344770; Sun, 27 Aug 2006 14:02:38 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id D171917047; Sun, 27 Aug 2006 16:03:50 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx0.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjxX8ZEQtEb9; Sun, 27 Aug 2006 16:03:47 +0200 (CEST) Received: by mx0.rink.nu (Postfix, from userid 1000) id 837CC1703B; Sun, 27 Aug 2006 16:03:47 +0200 (CEST) Date: Sun, 27 Aug 2006 16:03:47 +0200 From: Rink Springer To: current@FreeBSD.org, stable@FreeBSD.org Message-ID: <20060827140347.GD95784@rink.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3siQDZowHQqNOShm" Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: FreeBSD/xbox live/installcd's available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 14:35:28 -0000 --3siQDZowHQqNOShm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, In order to aid people installing FreeBSD on their xbox, I have created combined install/livecds to aid those willing to give FreeBSD/xbox a try. The images can be used to boot a full multi-user FreeBSD environment, but you can also boot directly into sysinstall to install FreeBSD on your Xbox. As I've recently merged Xbox support back to -STABLE, an ISO for 6-STABLE is also provided. The images are hosted by MCGV Stack (http://www.stack.nl), and can be retrieved from ftp://ftp.stack.nl/pub/freebsd-xbox/. A list of the files and checksums is: xbox-6stable-20060821.iso.bz2 - install/livecd for FreeBSD 6-STABLE MD5 =3D 9afbab92bbb43a797753a941737ef0bb SHA1 =3D 26908c6301484c133f23875a8136c2dbeb336e88 SHA256 =3D d67e51c2a37e14193a5cbfb49903899f60784e39f91888f8e0a48c85ee3eee46 xbox-7current-20060517.iso.bz2 - install/livecd for FreeBSD 7-CURRENT MD5 =3D 82108c6112f8b39fb82e71fdc727704a SHA1 =3D 83e40e292ac8ace395fcf199f1bb16b0a34531c5 SHA256 =3D 2176904283707273e7d62e31c516bc81c9a2021556bb84adbe23071ba9b8dd83 Some important points of attention: (1) The loader used is Cromwell; the Cromwell version on the images has spe= cial patches which do not appear in any official releases build [1]. Therefo= re, if you already use Cromwell on your Xbox, please chain-load the Cromwel= l on the images beforing attempting to boot FreeBSD. (2) 'patched' dashboard (the Xbox 'operating system') versions can directly boot the /DEFAULT.XBE file on the CDROM. The official Dashboard will fail to boot this, however, as the DEFAULT.XBE file is not signed with any Microsoft-approved key. Booting this file will directly start the FreeBSD-enabled Cromwell. (3) There is no loader support. Any tunables must be set using kernel options (such as the root device to use) (4) The xbox is very picky on the media used. If you get random panics or hangs during installation, try another brand of media. (5) If you keep experiencing DMA errors or timeouts, please use a 80 pin UDMA IDE cable. As there is no loader support, there is no way to force ata(4) to use only UDMA2 modes. (6) You currently need an USB keyboard; I'm planning to add dhclient(8) and sshd(8) automatic startup to the liveCD later. Anyway, feel free to give this a try and report any problems back to me. I intend to clean up the script used to build the ISO images in a short while. [1] Cromwell from xbox-linux.org CVS contains all patches required to be able to boot the recent FreeBSD kernels. However, it does not support direct booting from UFS partitions. Regards, --=20 Rink P.W. Springer - http://rink.nu "When will the internet move from 64Kb max .com domains to .exe domains which can use much more memory?" - Edwin Groothuis --3siQDZowHQqNOShm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE8aZDb3O60uztv/8RAoVDAKCTqfISyh44iuyt8lsL1AsOE/x6QQCeIwT8 vNCD6olv3cncei5eZgc+AHU= =kkpc -----END PGP SIGNATURE----- --3siQDZowHQqNOShm-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 15:42:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0E7F316A5FB for ; Sun, 27 Aug 2006 15:42:21 +0000 (UTC) (envelope-from nikolas.britton@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9E47445FD for ; Sun, 27 Aug 2006 15:18:50 +0000 (GMT) (envelope-from nikolas.britton@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1399496wxd for ; Sun, 27 Aug 2006 08:18:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Opu0vDHKlaKL82JYpnAgI84/00VXxmbXUuydmpfrk0fSw4QrBHUAie1fEUivb35Sm+l+pxI2L1iJx6wtIonDIb4hgkEFc4vEzkG5Sw2XZwafz4Is0mJZOspkQWNR25hElmbQrAcNcXCojJvuS01kFYKubtE2riAR5TwKD9trVwQ= Received: by 10.70.116.1 with SMTP id o1mr7745493wxc; Sun, 27 Aug 2006 08:18:50 -0700 (PDT) Received: by 10.70.49.3 with HTTP; Sun, 27 Aug 2006 08:18:50 -0700 (PDT) Message-ID: Date: Sun, 27 Aug 2006 10:18:50 -0500 From: "Nikolas Britton" To: "Peter Jeremy" In-Reply-To: <20060827100911.GM16768@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827071329.GK16768@turion.vk2pj.dyndns.org> <20060827110030.cebfbbf0.torfinn.ingolfsen@broadpark.no> <20060827100911.GM16768@turion.vk2pj.dyndns.org> Cc: Torfinn Ingolfsen , freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 15:42:21 -0000 On 8/27/06, Peter Jeremy wrote: > On Sun, 2006-Aug-27 11:00:30 +0200, Torfinn Ingolfsen wrote: > >On Sun, 27 Aug 2006 17:13:29 +1000 > >Peter Jeremy wrote: > > > >> The CD-ROMs create a RAMdisk and need a minimum of 24MB last I > >> checked. > > > >And I guess that the floppies work in the same way? > > Yes. > > >> Once you have FreeBSD installed, it will limp along in 16MB > >> (though not very happily). > > > >Hmm, I see. I'm planning to run X on this old box (it's going to be a > >PictureFrame project), perhaps that will not work. > > I think you would be thrashing if there was any actual activity. I'll > prod a friend with the same setup to comment tomorrow. > > >> I strongly suggest you find a SODIMM to > >> expand it. > > > >Ok. Are all SODIMMs equal (ie. a real standard), or do I hvae to look > >specifically for memory upgrades for the Armada 1580 (or 1500 series)? > > I'm 99% certain that you can't use anything bigger than 64MB (at least > a 128MB Cpq Armada SODIMM that I had wouldn't work in any of the 15xx > machines I tried it in - that included a 1580). I'm not sure how > interchangeable they are. > Max mem size and chip density is a function of the MCH, If you post a copy of dmesg here I can look it up for you. >From the service manual: "The computer supports optional 8-, 16-, 32-, and 64-MB memory boards. The memory boards are 60 ns EDO RAM without parity. System memory can be expanded to 80-MB of DRAM depending on the model." The Service Manual is here: http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=96219&targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00139858%2Fc00139858.pdf And Addendum to the service manual is here: http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=96219&targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00139129%2Fc00139129.pdf -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 16:13:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3AF9D16A4DA for ; Sun, 27 Aug 2006 16:13:23 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF6B44849 for ; Sun, 27 Aug 2006 16:13:22 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 24621 invoked from network); 27 Aug 2006 16:13:19 -0000 Received: from unknown (HELO localhost) (775067@[217.50.131.231]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 27 Aug 2006 16:13:19 -0000 Date: Sun, 27 Aug 2006 18:13:12 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20060827181312.38bd2ab6@localhost> In-Reply-To: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_PJ=_ip0z1a02ZNnaxJuvEIW"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 16:13:23 -0000 --Sig_PJ=_ip0z1a02ZNnaxJuvEIW Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Torfinn Ingolfsen wrote: > I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, > floppy and CD-rom. It doesn't have built in networking, neither wired > nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release > installed a long time, and was recently upgraded to 4.11-release from > CD, sucessfully. > However, when I try the 6.1-release CD (CD1), it boots as far as > loading the kernel, botting the kernel, and then reboots again?? > Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? With the default configuration yes. I recently tried to install FreeBSD 6.1-PRERELEASE on a Pentium 90 with 16 MB RAM, and hit the rebooting problem as well. I moved the harddisk into a more powerful machine, installed FreeBSD there, build a lighter kernel and put the disk back. NFS mounting needed a work around: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/94830 but the rest worked out of the box. In your case it's probably easier to create a disk image in Qemu, copy it to a CD and then use something that boots from a floppy, supports the CD-Rom drive and brings dd with it, to "install" the image.=20 Depending on your partition layout you may even be able to use your old FreeBSD installation to do that. (I'm not sure if it's possible to use FreeBSD to overwrite the partition it's running from). Fabian --=20 http://www.fabiankeil.de/ --Sig_PJ=_ip0z1a02ZNnaxJuvEIW Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8cSdBYqIVf93VJ0RAtyRAKCYIL7Z9ldbKHJWfSfvjI3s8VIYsQCeJpx6 CPAQqU+j/1fOrr4XS2sgCqg= =tcBo -----END PGP SIGNATURE----- --Sig_PJ=_ip0z1a02ZNnaxJuvEIW-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 17:29:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 14FCF16A4E1 for ; Sun, 27 Aug 2006 17:29:06 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8BD943DBA for ; Sun, 27 Aug 2006 17:28:21 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J4O00AKC3666A90@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 19:27:42 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J4O0087E366T470@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 27 Aug 2006 19:27:42 +0200 (CEST) Date: Sun, 27 Aug 2006 19:27:41 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20060827181312.38bd2ab6@localhost> To: freebsd-stable@freebsd.org Message-id: <20060827192741.fd7c86a4.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827181312.38bd2ab6@localhost> Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 17:29:06 -0000 On Sun, 27 Aug 2006 18:13:12 +0200 Fabian Keil wrote: For information: I'm still trying to find a sodimm card for this machine, as everything would be easier if it had more memory. We'll see how I manage that; here in Norway it is not so easy to find things like that, and transport costs from the US are prohibitive for a hobby budget. > I moved the harddisk into a more powerful machine, > installed FreeBSD there, build a lighter kernel and > put the disk back. Are there any FAQ's arounf for things I can safely remove from a 6.1 kernel? > NFS mounting needed a work around: I won't need NFS, so that's not a problem. > In your case it's probably easier to create a disk image > in Qemu, copy it to a CD and then use something that Hmm, I'm not very familiar with Qemu. A quick web search didn't turn up any obvious pointers on how to create a ISO image from a qemu image, or how to make an ISO image from the (currently running) Qemu image. Do you have any pointers to a HowTo for this? > boots from a floppy, supports the CD-Rom drive and brings > dd with it, to "install" the image. Yes, this sounds like a good plan. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 17:34:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 1904416A4DE; Sun, 27 Aug 2006 17:34:07 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F0B543D78; Sun, 27 Aug 2006 17:33:39 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k7RHH4et040129; Sun, 27 Aug 2006 20:17:12 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k7RHH4ps040126; Sun, 27 Aug 2006 20:17:04 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Sun, 27 Aug 2006 20:17:04 +0300 (EEST) From: Dmitry Pryanishnikov To: Doug Barton In-Reply-To: <44F130B2.8010702@FreeBSD.org> Message-ID: <20060827193347.J1751@atlantis.atlantis.dp.ua> References: <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> <44EB6411.4040406@paladin.bulgarpress.com> <20060823193309.GA77890@rambler-co.ru> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru> <20060827002203.A39026@atlantis.atlantis.dp.ua> <44F130B2.8010702@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 17:34:07 -0000 Hello! On Sat, 26 Aug 2006, Doug Barton wrote: >> I've tried to use sysutils/portconf, but found that it still doesn't >> give an universal solution: > > I think we need to be careful what our expectations of "universal" are with > a ports tree as large, and a userbase as diverse, as what we have. However ... Hmm, let me cite your letter in this thread: ========================================================================= >From dougb@freebsd.org Wed Aug 23 23:56:09 2006 Date: Wed, 23 Aug 2006 13:51:52 -0700 From: Doug Barton To: Ruslan Ermilov Cc: Vivek Khera , "Todorov @ Paladin" , freebsd-stable Subject: Re: 5.5 to 6.1 upgrade Ruslan Ermilov wrote: > On Tue, Aug 22, 2006 at 11:07:45PM +0300, Todorov @ Paladin wrote: >> Also - why portupgrade is not always aware of >> previously chosen options for a port build? >> > It depends. If options are OPTIONS (in the ports sense), they > are saved and independent of portupgrade. If options are > makefile options specified in pkgtools.conf, they are only > taken into accont if the port is (re)build explicitly; they > are not taken into account if a port is (re)built as a > dependency of another port. In plain text: if port B has > options in pkgtools.conf, and port A has B as its dependency, > and you portinstall/portupgrade A, B will be built (if needs > be) without pkgtools.conf options. Be careful. sysutils/portconf does not have that limitation. If you specify flags using that method, they will always be used. FYI, Doug ========================================================================= So, one can mistakenly think that "always" here really means ALWAYS (i.e., for every port). However many ports use that funny OPTIONS (in the ports sense) which completely ignore make's WITH_xxx / WITHOUT_xxx environment variables, so "always" isn't correct word here I suppose. >> 1) it doesn't work if /usr/ports is a link to another location. > > Sure it does. You just have to be smarter about how you specify the triggers > in make.conf. :) I have the following: > > .if !empty(.CURDIR:M/mnt/slave/space/ports*) > # Begin portconf settings > ... > > Works like a charm. Sure this (changing the body of the "Do not touch these lines" block ;) works! However portconf's +DISPLAY message doesn't even suggest that trigger in /etc/make.conf should be changed according to the `realpath /usr/ports/`. BTW, can this trigger line be changed in order to work in both standard case (/usr/ports is a port directory itself) and case when /usr/ports is a symlink to the actual port tree? I don't know make's language enough to embed `realpath /usr/ports/` to the trigger, sorry. >> 2) it still doesn't affect OPTIONS (in the ports sense); try e.g. the >> following: > > If it's not working at all to start with (as you specified above), then this > additional example of brokenness is meaningless. Additionally, OPTIONS > ignores settings in the environment at all times to start with. It's easy > enough to test this for yourself by placing something in make.conf. Yes, OPTIONS ignore settings in the make's environment, and it's confusing. At least option's default could follow WITH_xxx / WITHOUT_xxx, so I'd expect e.g. "SNMP support" to be checked when /etc/make.conf contains WITH_SNMP=yes To add even more confusion, OPTIONS _do_ obey shell's (not make's) environment variables: cd /usr/ports/net/quagga && WITH_SNMP=yes make rmconfig config correctly checks "SNMP support"! So (at least, from consistency POV) I think that OPTIONS should obey make's WITH_xxx / WITHOUT_xxx environment variables in the same way as they obey shell's variables. The more "perfect" solution, I think, would be to make those options (set via both make's and shell's WITH_xxx / WITHOUT_xxx variables) unchangeable in OPTIONS dialog (paint them grey as Windows does? Not so unreasonable I think). So in the case when _all_ menu items have appropriate WITH_xxx / WITHOUT_xxx settings, the entire menu dialog could be skipped and port installation could be made unattended. Wouldn't that be nice? > hth, > > Doug Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 18:19:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 822C516A4E5 for ; Sun, 27 Aug 2006 18:19:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 723AB43D4C for ; Sun, 27 Aug 2006 18:19:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k7RIHcNr057211; Sun, 27 Aug 2006 12:17:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 27 Aug 2006 12:17:38 -0600 (MDT) Message-Id: <20060827.121738.74693185.imp@bsdimp.com> To: torfinn.ingolfsen@broadpark.no From: Warner Losh In-Reply-To: <20060827192741.fd7c86a4.torfinn.ingolfsen@broadpark.no> References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827181312.38bd2ab6@localhost> <20060827192741.fd7c86a4.torfinn.ingolfsen@broadpark.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 27 Aug 2006 12:17:38 -0600 (MDT) Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 18:19:15 -0000 16MB is enough to run FreeBSD for limited applications, with carefully crafted kernel. It is not enough to run sysinstall. Last I checked, sysinstall was pushing 24MB in size, with 32MB being really better. Warner From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 18:38:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3FEAE16A4DA for ; Sun, 27 Aug 2006 18:38:58 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9034043D4C for ; Sun, 27 Aug 2006 18:38:57 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7RIct7P052390; Sun, 27 Aug 2006 18:38:55 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7RIcsRr052387; Sun, 27 Aug 2006 18:38:54 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Sun, 27 Aug 2006 18:38:54 +0000 (GMT) From: Michael Abbott To: Greg Byshenk In-Reply-To: <20060827130758.GO633@core.byshenk.net> Message-ID: <20060827131143.A49701@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827130758.GO633@core.byshenk.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 18:38:58 -0000 On Sun, 27 Aug 2006, Greg Byshenk wrote: > On Sun, Aug 27, 2006 at 11:24:13AM +0000, Michael Abbott wrote: >> I've been trying to make some sense of the "NFS locking" issue. I am >> trying to run >> # make installworld DESTDIR=/mnt >> where /mnt is an NFS mount on a FreeBSD 4.11 server, but I am unable to >> get past a call to `lockf`. > I have just performed a test of what you describe, using 'smbtest' > (6.1-STABLE #17: Fri Aug 25 12:25:19 CEST 2006) as the client and > 'data-2' (FreeBSD 6.1-STABLE #16: Wed Aug 9 15:38:12 CEST 2006) as the > server. ... > Which is to say that it completed successfully. Which suggests that there > is not a serious and ongoing problem. Hm. That's a useful data point: thanks for making the test! What about the non-interruptible sleep? Is this regarded as par for the course with NFS, or as a problem? I know that "hard" NFS mounts are treated as completely unkillable, though why `kill -9` isn't made to work escapes me, but a locking operation which (presumably) suffers a protocol error? Or is rpc.lockd simply waiting to hear back from the (presumably broken) NFS server? Even so: `kill -9` ought to work! From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 19:06:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 4673316A4DD for ; Sun, 27 Aug 2006 19:06:28 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (smtp2.utsp.utwente.nl [130.89.2.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AC8843D46 for ; Sun, 27 Aug 2006 19:06:27 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id k7RJ6ONc004739; Sun, 27 Aug 2006 21:06:24 +0200 From: Pieter de Goeje To: Torfinn Ingolfsen Date: Sun, 27 Aug 2006 21:06:24 +0200 User-Agent: KMail/1.9.3 References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827071329.GK16768@turion.vk2pj.dyndns.org> In-Reply-To: <20060827071329.GK16768@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608272106.24334.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: freebsd-stable@freebsd.org Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 19:06:28 -0000 On Sunday 27 August 2006 09:13, Peter Jeremy wrote: > On Sun, 2006-Aug-27 03:46:52 +0200, Torfinn Ingolfsen wrote: > >I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, > > ... > > >However, when I try the 6.1-release CD (CD1), it boots as far as > >loading the kernel, botting the kernel, and then reboots again?? > > The CD-ROMs create a RAMdisk and need a minimum of 24MB last I checked. > Once you have FreeBSD installed, it will limp along in 16MB (though > not very happily). I strongly suggest you find a SODIMM to expand it. A friend of mine installed 6.1 successfully on a pentium with 48MB ram. It runs quite well actually :) He didn't try to to install X however. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 19:17:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 2CF1416A4E0 for ; Sun, 27 Aug 2006 19:17:40 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20C5B43D55 for ; Sun, 27 Aug 2006 19:17:35 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7RJHYpf052524; Sun, 27 Aug 2006 19:17:34 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7RJHYs0052521; Sun, 27 Aug 2006 19:17:34 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Sun, 27 Aug 2006 19:17:34 +0000 (GMT) From: Michael Abbott To: Kostik Belousov In-Reply-To: <20060827135434.GH79046@deviant.kiev.zoral.com.ua> Message-ID: <20060827183903.G52383@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 19:17:40 -0000 On Sun, 27 Aug 2006, Kostik Belousov wrote: > Make sure that rpc.statd is running. Yep. Took me some while to figure that one out, but the first lockf test failed without that. > For debugging purposes, tcpdump of the corresponding communications > would be quite useful. Besides this, output of ps auxww | grep 'rpc\.' > may be interesting. Um. How interesting would tcpdump be? I'm prepared to do the work, but as I've never used the tool, it may take me some effort and time to figure out the right commands. Yes: `man tcpdump | wc -l` == 1543. Fancy giving me a sample command to try? As for the other test, let's have a look. Here we are before the test (NFS server, 4.11, is saturn, test machine, 6.1, is venus): saturn$ ps auxww | grep rpc\\. root 48917 0.0 0.1 980 640 ?? Is 7:56am 0:00.01 rpc.lockd root 115 0.0 0.1 263096 536 ?? Is 18Aug06 0:00.00 rpc.statd venus# ps auxww | grep rpc\\. root 510 0.0 0.9 263460 1008 ?? Ss 6:05PM 0:00.01 /usr/sbin/rpc.statd root 515 0.0 1.0 1416 1120 ?? Is 6:05PM 0:00.02 /usr/sbin/rpc.lockd daemon 520 0.0 1.0 1420 1124 ?? I 6:05PM 0:00.00 /usr/sbin/rpc.lockd That's interesting. Don't know how significant the differences are... Ok, let's run the test: venus# cd /usr/src; make installworld DESTDIR=/mnt Well, how odd: as soon as I start the test process 515 on venus goes away. Now to wait for it to fail... (doesn't take too long): saturn$ ps auxww | grep rpc\\. root 48917 0.0 0.1 980 640 ?? Is 7:56am 0:00.01 rpc.lockd root 115 0.0 0.1 263096 536 ?? Is 18Aug06 0:00.00 rpc.statd venus# ps auxww | grep rpc\\. root 510 0.0 0.9 263460 992 ?? Ss 6:05PM 0:00.01 /usr/sbin/rpc.statd daemon 520 0.0 1.0 1440 1152 ?? S 6:05PM 0:00.01 /usr/sbin/rpc.lockd venus# ps auxww | grep lockf ... root 7034 0.0 0.5 1172 528 v0 D+ 6:51PM 0:00.01 lockf -k /mnt/usr/... (I've truncated the lockf call: the detail of the install call it's making is hardly relevant!) Note that now any call to lockf on this server will fail... Hmm. What about a different mount point? Bet I can't unmount ... venus# umount /mnt umount: unmount of /mnt failed: Device busy venus# umount -f /mnt venus# mount saturn:/tmp /mnt venus# lockf /mnt/test ls (Hangs) Now this is interesting: the file saturn:/tmp/test exists! And it appears to be owned by uid=4294967294 (-2?)! How very odd. If I reboot venus and try just a single lockf: venus# lockf /mnt/test stat -f%u /mnt/test 0 As one might expect, indeed. A hint as to who's got stuck (saturn, I'm sure), but beside the point, I guess. Note also that the `umount -f /mnt` *didn't* release the lockf, and also note that /tmp/test is still there (on saturn) after a reboot of venus. In conclusion: I agree with Greg Byshenk that the NFS server is bound to be the one at fault, BUT, is this "freeze until reboot" behaviour really what we want? I remain astonished (and irritated) that `kill -9` doesn't work! From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 19:56:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 4A08816A4DA for ; Sun, 27 Aug 2006 19:56:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7BEF43D6E for ; Sun, 27 Aug 2006 19:56:02 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k7RJtsMf090530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Aug 2006 22:55:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8) with ESMTP id k7RJtuXL020197; Sun, 27 Aug 2006 22:55:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8/Submit) id k7RJttWj020196; Sun, 27 Aug 2006 22:55:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 27 Aug 2006 22:55:55 +0300 From: Kostik Belousov To: Michael Abbott Message-ID: <20060827195555.GI79046@deviant.kiev.zoral.com.ua> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4BlIp4fARb6QCoOq" Content-Disposition: inline In-Reply-To: <20060827183903.G52383@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=1.9 required=5.0 tests=DNS_FROM_RFC_ABUSE, SPF_NEUTRAL,UNPARSEABLE_RELAY autolearn=no version=3.1.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 19:56:17 -0000 --4BlIp4fARb6QCoOq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 27, 2006 at 07:17:34PM +0000, Michael Abbott wrote: > On Sun, 27 Aug 2006, Kostik Belousov wrote: > >For debugging purposes, tcpdump of the corresponding communications=20 > >would be quite useful. Besides this, output of ps auxww | grep 'rpc\.'= =20 > >may be interesting. >=20 > Um. How interesting would tcpdump be? I'm prepared to do the work, but= =20 > as I've never used the tool, it may take me some effort and time to figur= e=20 > out the right commands. Yes: `man tcpdump | wc -l` =3D=3D 1543. Fancy= =20 > giving me a sample command to try? On server, tcpdump -p -s 1500 -w file -i host This is assuming you use ethernet with usual MTU, iface is interface where communication with client comes from. > > As for the other test, let's have a look. Here we are before the test > (NFS server, 4.11, is saturn, test machine, 6.1, is venus): > > saturn$ ps auxww | grep rpc\\. My fault, better use ps axlww. =2E.... > Well, how odd: as soon as I start the test process 515 on venus goes away= .=20 > Now to wait for it to fail... (doesn't take too long): Yes, this is very interesting. Does something appears in the logs ? Also, you shall use -d option of rpc.lockd (and show the output together with tcpdump output). --4BlIp4fARb6QCoOq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8fjKC3+MBN1Mb4gRArnOAKCJZFYRt97Kx3zctxJawi+ZjuGI9ACgo6gq 1psT+mbzoLzRvZLeaI/MKfs= =NDR0 -----END PGP SIGNATURE----- --4BlIp4fARb6QCoOq-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 27 20:28:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7C4A016A4DA for ; Sun, 27 Aug 2006 20:28:12 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id B34C643D4C for ; Sun, 27 Aug 2006 20:28:11 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.6/8.13.6) with ESMTP id k7RKS4aR075768; Sun, 27 Aug 2006 22:28:04 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.6/8.13.6/Submit) id k7RKS40F075767; Sun, 27 Aug 2006 22:28:04 +0200 (CEST) (envelope-from byshenknet) Date: Sun, 27 Aug 2006 22:28:04 +0200 From: Greg Byshenk To: Michael Abbott Message-ID: <20060827202803.GP633@core.byshenk.net> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060827183903.G52383@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on core.byshenk.net Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2006 20:28:12 -0000 On Sun, Aug 27, 2006 at 07:17:34PM +0000, Michael Abbott wrote: > On Sun, 27 Aug 2006, Kostik Belousov wrote: > >Make sure that rpc.statd is running. > Yep. Took me some while to figure that one out, but the first lockf test > failed without that. [...] > As for the other test, let's have a look. Here we are before the test > (NFS server, 4.11, is saturn, test machine, 6.1, is venus): > saturn$ ps auxww | grep rpc\\. > root 48917 0.0 0.1 980 640 ?? Is 7:56am 0:00.01 rpc.lockd > root 115 0.0 0.1 263096 536 ?? Is 18Aug06 0:00.00 rpc.statd [...] > Well, how odd: as soon as I start the test process 515 on venus goes away. > Now to wait for it to fail... (doesn't take too long): [...] > In conclusion: I agree with Greg Byshenk that the NFS server is bound to > be the one at fault, BUT, is this "freeze until reboot" behaviour really > what we want? I remain astonished (and irritated) that `kill -9` doesn't > work! The problem here is that the process is waiting for somthing, and thus not listening to signals (including your 'kill'). I'm not an expert on this, but my first guess would be that saturn (your server) is offering something that it can't deliver. That is, the client asks the server "can you do X?", and the server says "yes I can", so the client says "do X" and waits -- and the server never does it. Or alternatively (based on your rpc.statd dying), rpc.lockd on your client is trying to use rpc.statd to communicate with your server. And it starts successfully, but then rpc.statd dies (for some reason) and your lock ends up waiting forever for it to answer. I would recommend starting both rpc.lockd and rpc.statd with the '-d' flag, to see if this provides any information as to what is going on. There may well be a bug somewhere, but you need to find where it is. I suspect that it is not actually in rpc.statd, as nothing in the source has changed since January 2005. An alternative would be to update to RELENG_6 (or at least RELENG_6_1) and then try again. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 07:17:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 D51D416A4DF for ; Mon, 28 Aug 2006 07:17:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 3CD6B43D46 for ; Mon, 28 Aug 2006 07:17:44 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 16065 invoked by uid 399); 28 Aug 2006 07:17:43 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 28 Aug 2006 07:17:43 -0000 Message-ID: <44F29894.9040700@FreeBSD.org> Date: Mon, 28 Aug 2006 00:17:40 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Dmitry Pryanishnikov References: <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> <44EB6411.4040406@paladin.bulgarpress.com> <20060823193309.GA77890@rambler-co.ru> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru> <20060827002203.A39026@atlantis.atlantis.dp.ua> <44F130B2.8010702@FreeBSD.org> <20060827193347.J1751@atlantis.atlantis.dp.ua> In-Reply-To: <20060827193347.J1751@atlantis.atlantis.dp.ua> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 07:17:44 -0000 Dmitry Pryanishnikov wrote: > Hmm, let me cite your letter in this thread: This isn't a court of law. :) > sysutils/portconf does not have that limitation. If you specify flags using > that method, they will always be used. > > FYI, > > Doug > ========================================================================= > > So, one can mistakenly think that "always" here really means ALWAYS > (i.e., for every port). However many ports use that funny OPTIONS (in > the ports sense) which completely ignore make's WITH_xxx / WITHOUT_xxx > environment variables, so "always" isn't correct word here I suppose. I probably should have said, "will always work like a a variable in make.conf would." If I caused confusion, I apologize. As for the other things you mentioned, I'm sure that the respective authors would welcome patches to correct the shortcomings you perceive. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 08:46:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 C38FB16A531 for ; Mon, 28 Aug 2006 08:46:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08C2043FD5 for ; Mon, 28 Aug 2006 08:43:48 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k7S8hgK5006751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Aug 2006 18:43:42 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k7S8hg3t000876; Mon, 28 Aug 2006 18:43:42 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k7S8hguR000875; Mon, 28 Aug 2006 18:43:42 +1000 (EST) (envelope-from peter) Date: Mon, 28 Aug 2006 18:43:42 +1000 From: Peter Jeremy To: Kostik Belousov Message-ID: <20060828084342.GA747@turion.vk2pj.dyndns.org> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827195555.GI79046@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20060827195555.GI79046@deviant.kiev.zoral.com.ua> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 08:46:55 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2006-Aug-27 22:55:55 +0300, Kostik Belousov wrote: >On server, >tcpdump -p -s 1500 -w file -i host Recent tcpdumps appear to want the ethernet frame size rather than the MTU: Specifying 1500 appears to truncate full-size frames. Try '-s 1516' instead. --=20 Peter Jeremy --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8qy9/opHv/APuIcRAkMNAKC8ZnmdVvYphjmpWABUlFjdfVkeKQCglllZ OgEzK+M06Fny3ch1X7CpBjM= =OlO8 -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 09:01:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 17E2A16A4E0 for ; Mon, 28 Aug 2006 09:01:09 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9849043D53 for ; Mon, 28 Aug 2006 09:01:07 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k7S8xwfb070346; Mon, 28 Aug 2006 12:00:36 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k7S8xwBI070337; Mon, 28 Aug 2006 11:59:58 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Mon, 28 Aug 2006 11:59:58 +0300 (EEST) From: Dmitry Pryanishnikov To: Peter Jeremy In-Reply-To: <20060828084342.GA747@turion.vk2pj.dyndns.org> Message-ID: <20060828115701.S67072@atlantis.atlantis.dp.ua> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827195555.GI79046@deviant.kiev.zoral.com.ua> <20060828084342.GA747@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 09:01:09 -0000 Hello! On Mon, 28 Aug 2006, Peter Jeremy wrote: > On Sun, 2006-Aug-27 22:55:55 +0300, Kostik Belousov wrote: >> On server, >> tcpdump -p -s 1500 -w file -i host > > Recent tcpdumps appear to want the ethernet frame size rather than > the MTU: Specifying 1500 appears to truncate full-size frames. > Try '-s 1516' instead. 'tcpdump -s 0' always works OK for me. > Peter Jeremy > Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 09:48:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9DEAC16A4DA for ; Mon, 28 Aug 2006 09:48:54 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9A1043D4C for ; Mon, 28 Aug 2006 09:48:53 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7S9mm7O062031; Mon, 28 Aug 2006 09:48:48 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7S9mmft062028; Mon, 28 Aug 2006 09:48:48 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Mon, 28 Aug 2006 09:48:48 +0000 (GMT) From: Michael Abbott To: Greg Byshenk In-Reply-To: <20060827202803.GP633@core.byshenk.net> Message-ID: <20060828082047.J61842@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827202803.GP633@core.byshenk.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 09:48:54 -0000 Well, the result I have to report is so interesting, I'll give the executive summary right away: If rpc.lockd is run with -d255 it works perfectly If rpc.lockd is run with -d1 (or no -d option) it locks up Sweet. Does anyone out there who understands rpc.lockd fancy a deeper look? On Sun, 27 Aug 2006, Greg Byshenk wrote: > The problem here is that the process is waiting for somthing, and > thus not listening to signals (including your 'kill'). > > I'm not an expert on this, but my first guess would be that saturn (your > server) is offering something that it can't deliver. That is, the client > asks the server "can you do X?", and the server says "yes I can", so the > client says "do X" and waits -- and the server never does it. I buy that analysis. However, I think that the client's (venus) behaviour is unreasonable, and there must be some problem at the driver level: unkillable processes? (Tries to bang drum about this!) Interesting: it looks like `nfslocking stop` releases the processes. > Or alternatively (based on your rpc.statd dying), rpc.lockd on your > client is trying to use rpc.statd to communicate with your server. And > it starts successfully, but then rpc.statd dies (for some reason) and > your lock ends up waiting forever for it to answer. Not quite: it was the first instantiation of rpc.lockd that went away, almost as if it was just waiting for something to happen! However, it doesn't do this on the simple one-line test, so yes, I think there's something here to investigate. Definitely: after running the test with no failures (see below), both lockd instances are still up and about. > I would recommend starting both rpc.lockd and rpc.statd with the '-d' > flag, to see if this provides any information as to what is going on. > There may well be a bug somewhere, but you need to find where it is. > I suspect that it is not actually in rpc.statd, as nothing in the > source has changed since January 2005. Ok, I'll try that. I'll try -d1, see what I get. venus# /etc/rc.d/nfslocking stop venus# /etc/rc.d/nfslocking start Oddly, running restart only restarts statd, not lockd. Strange naming convention for the commands, too -- have to put the following in rc.conf: rpc_lockd_enable=YES lockd_flags=-d1 rpc_statd_enable=YES statd_flags=-d Hmm. Not terribly consistent. Ok, let's see what a single lockf exchange looks like: venus# mount saturn:$EXPORT /mnt venus# lockf /mnt/test ls /mnt test venus# tail -n3 /var/log/debug.log Aug 28 08:52:44 venus rpc.statd: unmon_all for host: NFS NLM prog: 0 ver: 0 proc: 0 Aug 28 08:54:19 venus rpc.lockd: nlm_lock_res from saturn.araneidae.co.uk Aug 28 08:54:19 venus rpc.lockd: nlm_unlock_res from saturn.araneidae.co.uk Good. Now let's run the test: venus# cd /usr/src; make installworld DESTDIR=/mnt and, at the same time, in another shell: venus# tail -f /var/log/debug.log Well, that's odd. I get five nlm_lock_res/nlm_unlock_res pairs, with the last three in less than a second... and then nothing: the last, blocking, lockf doesn't generate any messages at all! Interesting: stopping the lock daemon, by running `/etc/rc.d/nfslocking stop`, releases the lock! Good. Now I can run the test again with more logging (I'll set lockd_flags=-d255, though a quick grep of the source suggests that 6 would suffice). Hmmm. It's working perfectly now! Well well well. What are the differences? 1. I'm rerunning the test after restarting the lock and stat daemons without an intervening reboot. 2. I'm running lockd with maximum debugging. 3. I'm running the test in a different virtual console (I think we can ignore that difference!) Fantastic: it ran to completion without a fault! Wow. I'll reboot (keep the same debug level) and try again... Astounding! Watch carefully: 1. Reboot 2. Login on virtual consoles 1 & 2 3. On console 2 run venus# tail -f /var/log/debug.log 4. On console 1 run venus# mount saturn:$EXPORT /mnt venus# rm -rf /mnt/* venus# cd /usr/src; make installworld DESTDIR=/mnt 5. Switch to console 2 and watch the console and the PC's activity lights. Lots and lots of network activity (well, there's a surprise), and the occasional flurry of rcp.lockd messages. 6. When the lights stop flashing (five minutes or so) switch back to console 1 and see that everything ran perfectly. Runs ok. Well. I can think of two possiblities: 1. High levels of logging do more than just logging: there's an inadvertent side effect. 2. There's a tight timing issue that is changed by the extra delays introduced by logging. On the whole I buy 2, and it's not altogether clear whether the issue is on the client or the server. Hmm. Maybe I need to try Kostik Belousov's suggestion of running tcpdump. Another message for that... > An alternative would be to update to RELENG_6 (or at least RELENG_6_1) > and then try again. This machine is so painfully slow that I'll probably have to do that overnight, and then I'm out of time until next weekend. Just installed cvsup (from ports; oops, my mistake, forgot about having to build ezm3!) From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 10:10:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 36D8316A4E1 for ; Mon, 28 Aug 2006 10:10:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E5DE43D46 for ; Mon, 28 Aug 2006 10:09:59 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k7SA9eDK013000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Aug 2006 13:09:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8) with ESMTP id k7SA9h6N076460; Mon, 28 Aug 2006 13:09:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8/Submit) id k7SA9gOK076455; Mon, 28 Aug 2006 13:09:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 28 Aug 2006 13:09:42 +0300 From: Kostik Belousov To: Michael Abbott Message-ID: <20060828100942.GF20390@deviant.kiev.zoral.com.ua> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827202803.GP633@core.byshenk.net> <20060828082047.J61842@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DEueqSqTbz/jWVG1" Content-Disposition: inline In-Reply-To: <20060828082047.J61842@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=1.9 required=5.0 tests=DNS_FROM_RFC_ABUSE, SPF_NEUTRAL,UNPARSEABLE_RELAY autolearn=no version=3.1.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on fw.zoral.com.ua Cc: Greg Byshenk , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 10:10:01 -0000 --DEueqSqTbz/jWVG1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 28, 2006 at 09:48:48AM +0000, Michael Abbott wrote: > >An alternative would be to update to RELENG_6 (or at least RELENG_6_1) > >and then try again. >=20 > This machine is so painfully slow that I'll probably have to do that=20 > overnight, and then I'm out of time until next weekend. Just installed= =20 > cvsup (from ports; oops, my mistake, forgot about having to build ezm3!) BTW, at least one fix after 6.1 could fix exactly issue with client rpc.loc= kd disappearing, that was mentioned before. Anyway, I think that tcpdump output would be crucial in debugging the issue. --DEueqSqTbz/jWVG1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8sDlC3+MBN1Mb4gRAikmAJ4tyxMjheER4YYSkCGNqssbZXCNygCfUQ1F Fd0+EamZByVxAqX18OCdTLU= =vm1m -----END PGP SIGNATURE----- --DEueqSqTbz/jWVG1-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 10:11:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9F0E616A4DE for ; Mon, 28 Aug 2006 10:11:19 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id A34FD43D64 for ; Mon, 28 Aug 2006 10:11:15 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7SABE6f062126; Mon, 28 Aug 2006 10:11:14 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7SABEjx062123; Mon, 28 Aug 2006 10:11:14 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Mon, 28 Aug 2006 10:11:14 +0000 (GMT) From: Michael Abbott To: Kostik Belousov In-Reply-To: <20060827195555.GI79046@deviant.kiev.zoral.com.ua> Message-ID: <20060828095941.J62085@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827195555.GI79046@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 10:11:19 -0000 On Sun, 27 Aug 2006, Kostik Belousov wrote: > On server, > tcpdump -p -s 1500 -w file -i host Ok. I've run saturn# tcpdump -p -s 1500 -w tcpdump.out -i xl0 host 10.0.0.105 and run the failing test on venus (with `rpc.lockd -d1`). The failing lockf has moved -- it took longer to fail this time -- but it does fail. As before, one of the lockd processes has vanished. venus# ps axlww | grep rpc\\. 0 18303 1 0 96 0 263460 916 select Ss ?? 0:00.00 /usr/sbin/rpc.statd -d 0 18308 1 0 96 0 1416 1024 select Is ?? 0:00.01 /usr/sbin/rpc.lockd -d1 1 18309 18308 0 4 0 1420 1036 nfsloc I ?? 0:00.00 /usr/sbin/rpc.lockd -d1 venus# ps axlww | grep rpc\\. 0 18303 1 0 96 0 263460 884 select Ss ?? 0:00.00 /usr/sbin/rpc.statd -d 1 18309 1 0 4 0 1440 1008 nfsloc S ?? 0:00.00 /usr/sbin/rpc.lockd -d1 > Yes, this is very interesting. Does something appears in the logs ? > Also, you shall use -d option of rpc.lockd (and show the output together > with tcpdump output). Well. See my previous message this smorning for -d output. As for tcpdump, I have an interesting (and rather obvious) problem: saturn# stat -f%z /tmp/tcpdump.out 161794058 Hmm. Perhaps you don't want that. I'll hang onto it for a bit: let me know what you want to do with it! From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 11:36:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 38B7016A4DD for ; Mon, 28 Aug 2006 11:36:12 +0000 (UTC) (envelope-from rabe@p-i-n.com) Received: from dns.p-i-n.com (dns.p-i-n.com [145.253.185.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C757B43D67 for ; Mon, 28 Aug 2006 11:36:10 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from p-i-n.com (inside.p-i-n.com [129.10.9.21]) by dns.p-i-n.com (8.12.9p2/8.12.9) with ESMTP id k7SBa70x092279 for ; Mon, 28 Aug 2006 13:36:07 +0200 (CEST) (envelope-from rabe@p-i-n.com) Received: (from rabe@localhost) by p-i-n.com (8.11.6/8.11.6) id k7SBa7I79413 for freebsd-stable@freebsd.org; Mon, 28 Aug 2006 13:36:07 +0200 (CEST) (envelope-from rabe) Date: Mon, 28 Aug 2006 13:36:07 +0200 From: "Raphael H. Becker" To: freebsd-stable@freebsd.org Message-ID: <20060828133607.A65093@p-i-n.com> References: <20060622121421.X1114@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20060622121421.X1114@ganymede.hub.org>; from scrappy@hub.org on Thu, Jun 22, 2006 at 12:17:12PM -0300 Organization: PHOENIX Pharmahandel AG & Co KG, Mannheim, Deutschland Subject: RAID Controller problems (was: Re: kern.ipc.maxpipekva ...) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 11:36:12 -0000 Hi, I've also seen this "kernel: kern.maxpipekva exceeded, please see tuning(7)" on the console of our Dell PE6650, which (again) had lost its amr (LSI RAID/Perc). This machine isn't under load but runs rsync every 5 minutes. amr0@pci3:1:0: class=0x010400 card=0x05181028 chip=0x19601000 rev=0x01 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'MegaRAID' class = mass storage subclass = RAID # uname -srm FreeBSD 6.1-RELEASE-p3 i386 ... with just this KERNCONF: include GENERIC ident PE6650 options SMP options COMPAT_FREEBSD4 options COMPAT_FREEBSD5 The amr seems more stable since "Scott's Mega Update" (see: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/amr/amr_cam.c?rev=1.15.2.1&content-type=text/x-cvsweb-markup&only_with_tag=RELENG_6_1_BP ) but probably under high load or after a while it still fails (no disk access possible, no messages). Has anyone else running a Dell PE6650 with this LSI RAID? Anyone else got this errors? Regards Raphael Becker On Thu, Jun 22, 2006 at 12:17:12PM -0300, Marc G. Fournier wrote: > > I've read the comments in /usr/src/sys/kern/sys_pipe.c, but couldn't see > anything in there ... I'm up to 32M (as set through /boot/loader.conf) and > am still hitting the max after a period of time (latest was 7 hours) ... > > Figuring that the last time I checked, I was using something like 7000 > pipes, @ 16k each, I should be setting it closer to 128M, and that is > assuming no 64k pipes ... > > So, is there an 'upper max' that it won't allow me to set it past? > > Thanks ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email . scrappy@hub.org MSN . scrappy@hub.org > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 12:21:13 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 062DA16A4DE for ; Mon, 28 Aug 2006 12:21:13 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6ADB43D80 for ; Mon, 28 Aug 2006 12:21:04 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (gripyj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k7SCKocP054183; Mon, 28 Aug 2006 14:20:55 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k7SCKoJW054182; Mon, 28 Aug 2006 14:20:50 +0200 (CEST) (envelope-from olli) Date: Mon, 28 Aug 2006 14:20:50 +0200 (CEST) Message-Id: <200608281220.k7SCKoJW054182@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, michael@araneidae.co.uk In-Reply-To: <20060827131143.A49701@saturn.araneidae.co.uk> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 28 Aug 2006 14:20:56 +0200 (CEST) Cc: Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, michael@araneidae.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 12:21:13 -0000 Michael Abbott wrote: > What about the non-interruptible sleep? Is this regarded as par for the > course with NFS, or as a problem? > > I know that "hard" NFS mounts are treated as completely unkillable, though > why `kill -9` isn't made to work escapes me, but a locking operation which > (presumably) suffers a protocol error? Or is rpc.lockd simply waiting to > hear back from the (presumably broken) NFS server? Even so: `kill -9` > ought to work! SIGKILL _does_ always work. However, signal processing can be delayed for various reasons. For example, if a process is stopped (SIGSTOP), further signals will only take effect when it continues (SIGCONT). Signal processing does not occur if a process is currently not scheduled, which is the case if the process is blocked on I/O (indicated by "D" in the STAT column of ps(1), also called the "disk-wait" state). That can happen if the hardware is broken (disk, controller, cable), so an I/O request doesn't return. It can also happen if there are NFS hiccups, as seems to be the case here. As soon as the "D" state ends, the process becomes runnable again (i.e. it's put on the schedulers "run queue"), which means that it'll get a CPU share, and the SIGKILL signal that you sent it before will be processed, finally. Some background information: Each process has a bit mask which stores the set of received signals. kill(2) (and therefore also kill(1)) only sets a bit in that bit mask. The next time the process is scheduled onto a CPU, the mask of received signals is processed and acted upon. That's not FreeBSD-specific; it works like that on almost all UNIX systems. Why does it work that way? Well, if signals were processed for processes not on the CPU, then there would be a "hole": A process would be able to circumvent the scheduler, because signal processing happens on behalf of the process, which means that it runs with the credentials, resource limits, nice value etc. of that process. Well, in theory, a special case could be made for SIGKILL, but it's quite difficult if you don't want break existing semantics (or creating holes). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 12:50:05 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 E8B0D16A4E0 for ; Mon, 28 Aug 2006 12:50:05 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D06E043D45 for ; Mon, 28 Aug 2006 12:50:04 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (rahsrq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k7SCnvnS055816; Mon, 28 Aug 2006 14:50:02 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k7SCnuP1055815; Mon, 28 Aug 2006 14:49:57 +0200 (CEST) (envelope-from olli) Date: Mon, 28 Aug 2006 14:49:57 +0200 (CEST) Message-Id: <200608281249.k7SCnuP1055815@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, torfinn.ingolfsen@broadpark.no In-Reply-To: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 28 Aug 2006 14:50:02 +0200 (CEST) Cc: Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, torfinn.ingolfsen@broadpark.no List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 12:50:06 -0000 Torfinn Ingolfsen wrote: > Are 16 Megs of RAM to little to install FreeBSD 6.0 or newer? As others have pointed out, installation via sysinstall requires at least 24 MB of RAM. So you either have to prepare your own installation media, or put the harddisk in a different PC, install FreeBSD there, and move the disk back. In any case you should carefully tune your kernel confi- guration to only include those things that you really need. There are also options to exclude certain parts, e.g. the syscons driver has seveal options to exclude copy&paste, font loading and other things, which can save some space. Don't forget to configure plenty of swap space; you'll probably need it. And have a look at the tuning(7) man page which has several hints that may help for low-memory situations. If you want to run X11 (a current version of Xorg), you absolutely must upgrade the RAM. You won't be happy with 16 MB only. But even with more RAM, running X11 won't be much fun, because the CPU isn't very fast, I guess. If you want to run a light-weight graphical web browser, I recommend links (in X11 graphics mode, option "-g") or dillo. Both are available from the ports collection. They support only limited JavaScript, though, and no Flash, Java or anything more advanced. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "IRIX is about as stable as a one-legged drunk with hypothermia in a four-hundred mile per hour wind, balancing on a banana peel on a greased cookie sheet -- when someone throws him an elephant with bad breath and a worse temper." -- Ralf Hildebrandt From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 13:23:33 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 22D7916A4DD for ; Mon, 28 Aug 2006 13:23:33 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A2843D4C for ; Mon, 28 Aug 2006 13:23:32 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7SDNVhO062804; Mon, 28 Aug 2006 13:23:31 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7SDNUL2062801; Mon, 28 Aug 2006 13:23:30 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Mon, 28 Aug 2006 13:23:30 +0000 (GMT) From: Michael Abbott To: Oliver Fromme In-Reply-To: <200608281220.k7SCKoJW054182@lurza.secnetix.de> Message-ID: <20060828124935.G62656@saturn.araneidae.co.uk> References: <200608281220.k7SCKoJW054182@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 13:23:33 -0000 On Mon, 28 Aug 2006, Oliver Fromme wrote: > SIGKILL _does_ always work. However, signal processing can be delayed > for various reasons. [...] > Well, in theory, a special case could be made for SIGKILL, but it's > quite difficult if you don't want break existing semantics (or creating > holes). Thank you, that was both instructive and interesting. > if a process is stopped (SIGSTOP), further signals will only take effect > when it continues (SIGCONT). Um. Doesn't this mean that SIGCONT is already a special case? I think there is a case to be made for special casing SIGKILL, but in a sense it's not so much the fate of the process receiving the SIGKILL that counts: after all, having sent -9 I know that it will never process again. More to the point, all processes which are waiting for the killed process should be released. I think maybe I'd like to change the process into Z ('zombie') state while it's still blocked in IO! Sounds like a new state to me, actually: K, "killed in disk wait". Of course, ideally, all other resources held by the new zombie should also be released ... including the return context for the blocked IO call! Tricky, but the process is never going to use its resources again. Of course, any resources held in the blocked IO call itself are another matter... Ah well. I guess it's a bit of an academic point. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 13:25:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 435CD16A4DE for ; Mon, 28 Aug 2006 13:25:37 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D47F43D70 for ; Mon, 28 Aug 2006 13:25:30 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 13659 invoked from network); 28 Aug 2006 13:25:28 -0000 Received: from unknown (HELO localhost) (775067@[217.50.145.224]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 28 Aug 2006 13:25:28 -0000 Date: Mon, 28 Aug 2006 15:25:21 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20060828152521.2973b8e4@localhost> In-Reply-To: <20060827192741.fd7c86a4.torfinn.ingolfsen@broadpark.no> References: <20060827034652.ad43299b.torfinn.ingolfsen@broadpark.no> <20060827181312.38bd2ab6@localhost> <20060827192741.fd7c86a4.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2008-08-18.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_QMha4GaUNNa0N5NR.J.XZPf; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: 16M RAM enough for FreeBSD 6.1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 13:25:37 -0000 --Sig_QMha4GaUNNa0N5NR.J.XZPf Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Torfinn Ingolfsen wrote: > On Sun, 27 Aug 2006 18:13:12 +0200 > Fabian Keil wrote: >=20 > For information: I'm still trying to find a sodimm card for this > machine, as everything would be easier if it had more memory. > We'll see how I manage that; here in Norway it is not so easy to find > things like that, and transport costs from the US are prohibitive for > a hobby budget. >=20 > > I moved the harddisk into a more powerful machine, > > installed FreeBSD there, build a lighter kernel and > > put the disk back. >=20 > Are there any FAQ's arounf for things I can safely remove from a 6.1 > kernel? I don't think so, but usually the comments are enough to decide if you need something or not. The man pages help with the rest. > > In your case it's probably easier to create a disk image > > in Qemu, copy it to a CD and then use something that >=20 > Hmm, I'm not very familiar with Qemu. A quick web search didn't turn up > any obvious pointers on how to create a ISO image from a qemu image, or > how to make an ISO image from the (currently running) Qemu image. You can burn the Qemu image like every other file, you can even burn it directly without putting it into an ISO file first. You should stop Qemu first though, otherwise you might end up with an inconsistent image. If you only want to replace a partition, you can load the image with mdconfig to extract the partition you need. Fabian --=20 http://www.fabiankeil.de/ --Sig_QMha4GaUNNa0N5NR.J.XZPf Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8u7GBYqIVf93VJ0RAuHRAKC77fHMJ87YpZVU4MOvMKXFh8i29QCfdgyQ y6u68+1sEsopMPTXOrtkrYM= =H1v+ -----END PGP SIGNATURE----- --Sig_QMha4GaUNNa0N5NR.J.XZPf-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 22:50:26 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 8433B16A501 for ; Mon, 28 Aug 2006 22:50:26 +0000 (UTC) (envelope-from kuriyama@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2180843D49 for ; Mon, 28 Aug 2006 22:50:25 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id E4C0650E54 for ; Tue, 29 Aug 2006 07:50:24 +0900 (JST) Received: from pink.imgsrc.co.jp (pink.imgsrc.co.jp [210.226.20.36]) by black.imgsrc.co.jp (Postfix) with ESMTP id 56DC450DFA for ; Tue, 29 Aug 2006 07:50:22 +0900 (JST) Date: Tue, 29 Aug 2006 07:50:22 +0900 Message-ID: <7m1wr0xyoh.wl%kuriyama@imgsrc.co.jp> From: Jun Kuriyama To: Stable User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 Cc: Subject: panic: lockmgr: thread 0x..., not exclusive lock holder 0x... unlocking X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 22:50:26 -0000 I got a panic on my workstation (6.1-RELEASE-p2 amd64). ----- panic: lockmgr: thread 0xffffff007b910be0, not exclusive lock holder 0xffffff001c114720 unlocking cpuid = 1 KDB: enter: panic [thread pid 43 tid 100037 ] Stopped at kdb_enter+0x2f: nop db> bt Tracing pid 43 tid 100037 td 0xffffff007b910be0 kdb_enter() at kdb_enter+0x2f panic() at panic+0x291 lockmgr() at lockmgr+0x7a7 VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x49 vput() at vput+0x81 handle_workitem_remove() at handle_workitem_remove+0x215 process_worklist_item() at process_worklist_item+0x1d9 softdep_process_worklist() at softdep_process_worklist+0x7f softdep_flush() at softdep_flush+0x15d fork_exit() at fork_exit+0x86 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb1b8ad00, rbp = 0 --- ----- -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 22:53:11 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 0C09E16A4DF for ; Mon, 28 Aug 2006 22:53:11 +0000 (UTC) (envelope-from kuriyama@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2503443D46 for ; Mon, 28 Aug 2006 22:53:04 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id 814CF50EA4 for ; Tue, 29 Aug 2006 07:53:03 +0900 (JST) Received: from pink.imgsrc.co.jp (pink.imgsrc.co.jp [210.226.20.36]) by black.imgsrc.co.jp (Postfix) with ESMTP id EFB9250E66 for ; Tue, 29 Aug 2006 07:52:58 +0900 (JST) Date: Tue, 29 Aug 2006 07:52:58 +0900 Message-ID: <7mzmdowjzp.wl%kuriyama@imgsrc.co.jp> From: Jun Kuriyama To: Stable User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 Cc: Subject: panic: snapblkfree: inconsistent block type X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 22:53:11 -0000 After previous panic, I got another panic... (6.1-REL-p2 amd64) ----- panic: snapblkfree: inconsistent block type cpuid = 1 KDB: enter: panic [thread pid 844 tid 100110 ] Stopped at kdb_enter+0x2f: nop db> bt Tracing pid 844 tid 100110 td 0xffffff0055e07260 kdb_enter() at kdb_enter+0x2f panic() at panic+0x291 ffs_snapblkfree() at ffs_snapblkfree+0x611 ffs_blkfree() at ffs_blkfree+0x1b1 handle_workitem_freeblocks() at handle_workitem_freeblocks+0x142 softdep_setup_freeblocks() at softdep_setup_freeblocks+0x8cf ffs_truncate() at ffs_truncate+0x1c1 ufs_inactive() at ufs_inactive+0x28c VOP_INACTIVE_APV() at VOP_INACTIVE_APV+0x3d vinactive() at vinactive+0x6e vput() at vput+0x1f2 kern_unlink() at kern_unlink+0x17a syscall() at syscall+0x642 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (10, FreeBSD ELF64, unlink), rip = 0x800afc75c, rsp = 0x7fffffffead8, rbp = 0x507710 --- ----- -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 07:50:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 6EB5816A4DF for ; Tue, 29 Aug 2006 07:50:43 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail29.syd.optusnet.com.au (mail29.syd.optusnet.com.au [211.29.132.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id B262043D46 for ; Tue, 29 Aug 2006 07:50:42 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail29.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k7T7oZ6S004545 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 29 Aug 2006 17:50:36 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k7T7oZfM000983; Tue, 29 Aug 2006 17:50:35 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k7T7oYfX000982; Tue, 29 Aug 2006 17:50:34 +1000 (EST) (envelope-from peter) Date: Tue, 29 Aug 2006 17:50:34 +1000 From: Peter Jeremy To: Michael Abbott Message-ID: <20060829075034.GA727@turion.vk2pj.dyndns.org> References: <200608281220.k7SCKoJW054182@lurza.secnetix.de> <20060828124935.G62656@saturn.araneidae.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20060828124935.G62656@saturn.araneidae.co.uk> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 07:50:43 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Aug-28 13:23:30 +0000, Michael Abbott wrote: >I think there is a case to be made for special casing SIGKILL, but in a=20 >sense it's not so much the fate of the process receiving the SIGKILL that= =20 >counts: after all, having sent -9 I know that it will never process again. Currently, if you send SIGKILL, the process will never enter userland again. Going further, so that if you send a process SIGKILL, it will always terminate immediately is significantly more difficult. In the normal case, a process is sleeping on some condition with PCATCH specified. If the process receives a signal, sleep(9) will return ERESTART or EINTR and the code has to then arrange to return back to userland (which will cause the signal to be handled as per sigaction(2) and the processes signal handlers). In some cases, it may be inconvenient to unwind back to userland from a particular point so PCATCH isn't specified on the sleep. --=20 Peter Jeremy --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8/HK/opHv/APuIcRAhQEAKCWv2sentHLbSPJ9oW8AJ8Y6Y+HdACeIaAD /NHhnK8Bh+2/Jj1tfk5AJbw= =8D3p -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 07:56:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 AFD6316A4DD for ; Tue, 29 Aug 2006 07:56:29 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4474143D58 for ; Tue, 29 Aug 2006 07:56:28 +0000 (GMT) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (localhost.cmotd.com [127.0.0.1]) by sun-fish.com (Postfix) with ESMTP id DCC3838425 for ; Tue, 29 Aug 2006 09:56:26 +0200 (CEST) Received: from [192.168.3.112] (boar.cmotd.com [192.168.3.112]) by sun-fish.com (Postfix) with ESMTP id A985238420 for ; Tue, 29 Aug 2006 09:56:26 +0200 (CEST) Message-ID: <44F3F2FE.8000407@sun-fish.com> Date: Tue, 29 Aug 2006 10:55:42 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV Subject: linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 07:56:29 -0000 Hi all, First sorry if this is not the right place to post my questions :) I'm trying to run linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 (ports/databases/linux-oracle-instantclient-sqlplus) on FreeBSD 6.1-STABLE (i386 or/and amd64), but with no success for now. After installation I run: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib /compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/bin/sqlplus /nolog but it just freezes. Friend of mine told me that he have no problems with FreeBSD 5.4(i386) My goal is to run oracle-instant client (i386) on FreeBSD-6.x amd64. So is there some big change in linux module in FreeBSD 6.1 compared to 5.4 ? Did somebody manage to run successfully linux-instant-oracle-client under FreeBSD 6.1 (i386/amd64)? Please help :)) P.S. oracle instant client does not depend on any linux_base, which was little strange for me, but just for info I have installed latest linux_base_fc4. Thanks in advance. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 08:04:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 50EF816A4DA for ; Tue, 29 Aug 2006 08:04:26 +0000 (UTC) (envelope-from leafy7382@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id C892A43D4C for ; Tue, 29 Aug 2006 08:04:25 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so1134757nzn for ; Tue, 29 Aug 2006 01:04:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=isRUbT63uS2bBxdGArL0zS+jBT1L0IbOwd9CA00Ixr0aUhvDc0ioRECc92547zhCgkO/P+inG0Ro7sMSsXII9D3zxo4aGIksd8LGvPfppFTnsmauarmHCrwBkPeoiYr7G6usr/sw1Xm4hA0L92c7zjS5SeCQzGQjoA9UC+mMTk8= Received: by 10.35.49.4 with SMTP id b4mr14371108pyk; Tue, 29 Aug 2006 01:04:25 -0700 (PDT) Received: by 10.35.124.18 with HTTP; Tue, 29 Aug 2006 01:04:25 -0700 (PDT) Message-ID: Date: Tue, 29 Aug 2006 16:04:25 +0800 From: "Jiawei Ye" To: "Stefan Lambrev" In-Reply-To: <44F3F2FE.8000407@sun-fish.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44F3F2FE.8000407@sun-fish.com> Cc: freebsd-stable@freebsd.org Subject: Re: linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 08:04:26 -0000 On 8/29/06, Stefan Lambrev wrote: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib > /compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/bin/sqlplus /nolog I am running it off a -current system with the following command: LD_LIBRARY_PATH=/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib /compat/linux/usr/bin/sqlplus > > but it just freezes. Friend of mine told me that he have no problems > with FreeBSD 5.4(i386) > > P.S. oracle instant client does not depend on any linux_base, which was > little strange for me, but just for info > I have installed latest linux_base_fc4. > > Thanks in advance. > > -- > Best Wishes, > Stefan Lambrev -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 08:27:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 018CF16A4DD for ; Tue, 29 Aug 2006 08:27:59 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E65A43D5D for ; Tue, 29 Aug 2006 08:27:58 +0000 (GMT) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (localhost.cmotd.com [127.0.0.1]) by sun-fish.com (Postfix) with ESMTP id B350438512; Tue, 29 Aug 2006 10:27:56 +0200 (CEST) Received: from [192.168.3.112] (boar.cmotd.com [192.168.3.112]) by sun-fish.com (Postfix) with ESMTP id 7EA8838501; Tue, 29 Aug 2006 10:27:56 +0200 (CEST) Message-ID: <44F3FA60.7030401@sun-fish.com> Date: Tue, 29 Aug 2006 11:27:12 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <44F3F2FE.8000407@sun-fish.com> In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV Cc: Jiawei Ye Subject: Re: linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 08:27:59 -0000 Hi, Jiawei Ye wrote: > On 8/29/06, Stefan Lambrev wrote: > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib > >> /compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/bin/sqlplus /nolog > I am running it off a -current system with the following command: > LD_LIBRARY_PATH=/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib > /compat/linux/usr/bin/sqlplus using the link doesn't help here :( >> >> but it just freezes. Friend of mine told me that he have no problems >> with FreeBSD 5.4(i386) >> >> P.S. oracle instant client does not depend on any linux_base, which was >> little strange for me, but just for info >> I have installed latest linux_base_fc4. >> >> Thanks in advance. >> >> -- >> Best Wishes, >> Stefan Lambrev -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 09:28:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0214F16A4DA for ; Tue, 29 Aug 2006 09:28:10 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1C3C43D5F for ; Tue, 29 Aug 2006 09:28:06 +0000 (GMT) (envelope-from karagodov@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so2625324pye for ; Tue, 29 Aug 2006 02:28:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=DNdwpquPpGIF7cqOLSXNSiRW6UxgBY9pA+CzCdqm6jJrihCVcCjYuEfDjDuCjL6JCjy4dR63NqD2YT7K2WbpEiy0KyHP9mv1u1CkcvhfzzTl55h4BqGP76euA1Ws06brEI82eJFKZaDftSW94VO+DiRwegBo141FhSiaSmvyzbE= Received: by 10.35.49.4 with SMTP id b4mr14509673pyk; Tue, 29 Aug 2006 02:28:06 -0700 (PDT) Received: by 10.35.66.6 with HTTP; Tue, 29 Aug 2006 02:28:00 -0700 (PDT) Message-ID: Date: Tue, 29 Aug 2006 13:28:00 +0400 From: "Alexey Karagodov" To: "Peter Jeremy" In-Reply-To: <20060829075034.GA727@turion.vk2pj.dyndns.org> MIME-Version: 1.0 References: <200608281220.k7SCKoJW054182@lurza.secnetix.de> <20060828124935.G62656@saturn.araneidae.co.uk> <20060829075034.GA727@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Michael Abbott , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 09:28:10 -0000 it's all is very good, but what can you say about to fix problem with rpc.lockd ??? 2006/8/29, Peter Jeremy : > > On Mon, 2006-Aug-28 13:23:30 +0000, Michael Abbott wrote: > >I think there is a case to be made for special casing SIGKILL, but in a > >sense it's not so much the fate of the process receiving the SIGKILL that > >counts: after all, having sent -9 I know that it will never process > again. > > Currently, if you send SIGKILL, the process will never enter userland > again. > > Going further, so that if you send a process SIGKILL, it will always > terminate immediately is significantly more difficult. In the normal > case, a process is sleeping on some condition with PCATCH specified. > If the process receives a signal, sleep(9) will return ERESTART or > EINTR and the code has to then arrange to return back to userland > (which will cause the signal to be handled as per sigaction(2) and > the processes signal handlers). In some cases, it may be inconvenient > to unwind back to userland from a particular point so PCATCH isn't > specified on the sleep. > > -- > Peter Jeremy > > > From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 10:06:42 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 6E31416A4DD for ; Tue, 29 Aug 2006 10:06:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B792143D49 for ; Tue, 29 Aug 2006 10:06:41 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (klyvwf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k7TA6YZE007779; Tue, 29 Aug 2006 12:06:40 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k7TA6YBN007778; Tue, 29 Aug 2006 12:06:34 +0200 (CEST) (envelope-from olli) Date: Tue, 29 Aug 2006 12:06:34 +0200 (CEST) Message-Id: <200608291006.k7TA6YBN007778@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, karagodov@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 29 Aug 2006 12:06:40 +0200 (CEST) Cc: Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, karagodov@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 10:06:42 -0000 Alexey Karagodov wrote: > it's all is very good, but what can you say about to fix problem with > rpc.lockd ??? It has been mentioned several times in this mailing list: rpc.lockd is in need of a complete rewrite. Someone will have to write a new rpc.lockd implementation. As far as I know, there is currently nobody working on it. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "And believe me, as a C++ programmer, I don't hesitate to question the decisions of language designers. After a decent amount of C++ exposure, Python's flaws seem ridiculously small." -- Ville Vainio From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 10:53:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 2060E16A4DE for ; Tue, 29 Aug 2006 10:53:12 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49EB943D60 for ; Tue, 29 Aug 2006 10:53:02 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7TAr0ta082861; Tue, 29 Aug 2006 10:53:00 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7TAqxxY082858; Tue, 29 Aug 2006 10:52:59 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Tue, 29 Aug 2006 10:52:59 +0000 (GMT) From: Michael Abbott To: Alexey Karagodov In-Reply-To: Message-ID: <20060829105114.O82850@saturn.araneidae.co.uk> References: <200608281220.k7SCKoJW054182@lurza.secnetix.de> <20060828124935.G62656@saturn.araneidae.co.uk> <20060829075034.GA727@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Jeremy , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 10:53:12 -0000 On Tue, 29 Aug 2006, Alexey Karagodov wrote: > it's all is very good, but what can you say about to fix problem with > rpc.lockd ??? Well, I will repeat the test with RELENG_6 (as of yesterday lunchtime), probably tonight, and report back. Unfortunately building takes around 8 hours on my test machine! From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 13:26:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3B51F16A4DA for ; Tue, 29 Aug 2006 13:26:42 +0000 (UTC) (envelope-from joji@eskimo.com) Received: from ultra5.eskimo.com (ultra5.eskimo.com [204.122.16.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B393F43D4C for ; Tue, 29 Aug 2006 13:26:41 +0000 (GMT) (envelope-from joji@eskimo.com) Received: from eskimo.com (eskimo.com [204.122.16.13]) by ultra5.eskimo.com (8.13.6/8.13.4) with ESMTP id k7TDQdai023531; Tue, 29 Aug 2006 06:26:39 -0700 Received: (from joji@localhost) by eskimo.com (8.9.1a/8.9.1) id GAA12325; Tue, 29 Aug 2006 06:26:40 -0700 (PDT) Date: Tue, 29 Aug 2006 06:26:40 -0700 From: Joseph Olatt To: Stefan Lambrev Message-ID: <20060829062640.A11793@eskimo.com> References: <44F3F2FE.8000407@sun-fish.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <44F3F2FE.8000407@sun-fish.com>; from stefan.lambrev@sun-fish.com on Tue, Aug 29, 2006 at 10:55:42AM +0300 Cc: freebsd-stable@freebsd.org Subject: Re: linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 13:26:42 -0000 On Tue, Aug 29, 2006 at 10:55:42AM +0300, Stefan Lambrev wrote: > Hi all, > > First sorry if this is not the right place to post my questions :) > > I'm trying to run linux-oracle-instantclient-sqlplus-10.2.0.2.20060331 > (ports/databases/linux-oracle-instantclient-sqlplus) > on FreeBSD 6.1-STABLE (i386 or/and amd64), but with no success for now. > > After installation I run: > > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/lib > /compat/linux/usr/lib/oracle/10.2.0.2.20060331/client/bin/sqlplus /nolog > > but it just freezes. Friend of mine told me that he have no problems > with FreeBSD 5.4(i386) > > My goal is to run oracle-instant client (i386) on FreeBSD-6.x amd64. > > So is there some big change in linux module in FreeBSD 6.1 compared to 5.4 ? > Did somebody manage to run successfully linux-instant-oracle-client > under FreeBSD 6.1 (i386/amd64)? > Please help :)) > > P.S. oracle instant client does not depend on any linux_base, which was > little strange for me, but just for info > I have installed latest linux_base_fc4. > > Thanks in advance. > > -- > Best Wishes, > Stefan Lambrev > ICQ# 24134177 FWIW, I have oracle8-client-0.1.1_1 package running in FreeBSD 6-STABLE. This package does not have sqlplus but allows me to connect to Oracle using p5-DBD-Oracle-1.16_3 & p5-DBI-1.50 and perl. $ pkg_info | egrep "Oracle|DBI" oracle8-client-0.1.1_1 Oracle 8 client p5-DBD-Oracle-1.16_3 DBI driver for Oracle RDBMS server p5-DBI-1.50 The perl5 Database Interface. Required for DBD::* modules $ uname -sr FreeBSD 6.1-STABLE regards, joseph From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 16:52:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 62C8C16A4DD for ; Tue, 29 Aug 2006 16:52:38 +0000 (UTC) (envelope-from sam@fqdn.net) Received: from host.fqdn.net (host.fqdn.net [194.242.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121C943D4C for ; Tue, 29 Aug 2006 16:52:37 +0000 (GMT) (envelope-from sam@fqdn.net) Received: by host.fqdn.net (Postfix, from userid 1003) id 5E2F520C; Tue, 29 Aug 2006 17:52:34 +0100 (BST) Date: Tue, 29 Aug 2006 17:52:34 +0100 From: Sam Eaton To: freebsd-stable@freebsd.org Message-ID: <20060829165234.GA15988@host.fqdn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: bce0 watchdog timeout errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 16:52:38 -0000 I'm still seeing an ongoing problem with the bce device on my Dell 1950. I'm running AMD64 6-STABLE, with the stock SMP kernel, and I'm running the most recent version of the bce driver, which did cure the other errors we were seeing (the mbuf related ones). The card is currently connected at an auto-negotiated 100BaseTX full duplex (rather than gigabit) as we don't currently have a gigabit switch to test on (the machine is under test rather than deployed). I can consistently cause the system to go into a 'Watchdog timeout occurred, resetting!' loop, by trying to do any reasonable amount of work over an nfs mounted filesystem. An easy way to reproduce this for me is to try and build some reasonably large port on our nfs mounted copy of the ports tree. I can also cause this by running bonnie++ against an nfs mounted filesystem. I've so far failed to find some simpler network only test to trigger the problem (I've tried sshing large amounts of data back and forth, iperf, ping floods, etc). NFS seems to do the trick every time though. Once it's reported the watchdog timeout, the networking on the box never recovers. Is anyone else seeing anything similar? And does anyone have any suggestions as to what I can do to try and diagnose this further so we can get to the bottom of it? Thanks, Sam. -- "Fortified with Essential Bitterness and Sarcasm" Matt Groening, "Binky's Guide to Love". From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 17:08:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 A366516A518 for ; Tue, 29 Aug 2006 17:08:43 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CFC843E5D for ; Tue, 29 Aug 2006 17:05:33 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7TH5RLK084045; Tue, 29 Aug 2006 17:05:27 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7TH5QLA084042; Tue, 29 Aug 2006 17:05:27 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Tue, 29 Aug 2006 17:05:26 +0000 (GMT) From: Michael Abbott To: Kostik Belousov In-Reply-To: <20060828100942.GF20390@deviant.kiev.zoral.com.ua> Message-ID: <20060829165820.F83998@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827202803.GP633@core.byshenk.net> <20060828082047.J61842@saturn.araneidae.co.uk> <20060828100942.GF20390@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Greg Byshenk , freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 17:08:43 -0000 >>> An alternative would be to update to RELENG_6 (or at least RELENG_6_1) >>> and then try again. So. I have done this. And I can't reproduce the problem. # uname -a FreeBSD venus.araneidae.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon Aug 28 18:32:17 UTC 2006 root@venus.araneidae.co.uk:/usr/obj/usr/src/sys/GENERIC i386 Hmm. Hopefully this is a *good* thing, ie, the problem really has been fixed, rather than just going into hiding. So, as far as I can tell, lockf works properly in this release. Sorry to have generated so much traffic on this! From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 01:49:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 BC56D16A4F4 for ; Wed, 30 Aug 2006 01:49:35 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9412243D45 for ; Wed, 30 Aug 2006 01:49:34 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GIFCl-000JZt-R7 for freebsd-stable@freebsd.org; Wed, 30 Aug 2006 10:49:28 +0900 Message-ID: <44F4EEA3.6000008@micom.mng.net> Date: Wed, 30 Aug 2006 10:49:23 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 01:49:35 -0000 Hi, I've got panic on FreeBSD 6.1-STABLE when I enabled following kernel options: options WITNESS options WITNESS_KDB options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT options DEBUG_LOCKS options DEBUG_VFS_LOCKS FreeBSD devil.micom.mng.net 6.1-STABLE FreeBSD 6.1-STABLE #10: Mon Aug 28 12:32:10 ULAST 2006 tsgan@devil.micom.mng.net:/usr/obj/usr/src/sys/DEVIL i386 bge0: mem 0xdfcf0000-0xdfcfffff irq 18 at device 0.0 on pci9 bge0: firmware handshake timed out miibus0: on bge0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:14:22:fb:32:a6 bge0@pci9:0:0: class=0x020000 card=0x01c21028 chip=0x160014e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme Gigabit Ethernet' class = network subclass = ethernet panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia cpuid = 1 KDB: enter: panic [thread pid 251 tid 100062 ] Stopped at kdb_enter+0x2b: nop db> bt Tracing pid 249 tid 100054 td 0xc4c50000 kdb_enter(c07a8a15) at kdb_enter+0x2b panic(c0796b5a,a,c086a7e0,2,c07aa244,...) at panic+0x127 mii_phy_setmedia(c4be6600) at mii_phy_setmedia+0x7f ukphy_service(c4be6600,c4bde880,2) at ukphy_service+0xfd mii_mediachg(c4bde880,8803,c4bde880,c4be7400,c4be9000,...) at mii_mediachg+0x27 bge_stop(c4be9000,80206910,c4db26c0,c4be9000,e5036c0c,...) at bge_stop+0x5b8 bge_init_locked(c4be9000) at bge_init_locked+0x36 bge_ioctl(c4be7400,80206910,c4db26c0) at bge_ioctl+0x1ef ifhwioctl(80206910,c4be7400,c4db26c0,c4c50000) at ifhwioctl+0x303 ifioctl(c4eca164,80206910,c4db26c0,c4c50000,0,...) at ifioctl+0xbd soo_ioctl(c4e00240,80206910,c4db26c0,c4ac2780,c4c50000) at soo_ioctl+0x2db ioctl(c4c50000,e5036d04) at ioctl+0x370 syscall(3b,3b,3b,3,1,...) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281472ff, esp = 0xbfbfe5dc, ebp = 0xbfbfe628 --- db> c Uptime: 11s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort KDB: stack backtrace: kdb_backtrace(e4fd1c2c,c05fb7ba,c07b2a73,c07b2b98,c4e962b8,...) at kdb_backtrace+0x29 vfs_badlock(c07b2a73,c07b2b98,c4e962b8) at vfs_badlock+0x11 assert_vop_locked(c4e962b8,c07b2b98) at assert_vop_locked+0x4a vop_lock_post(e4fd1c78,0,1002,c4e962b8,e4fd1c94,...) at vop_lock_post+0x2a VOP_LOCK_APV(c081c280,e4fd1c78) at VOP_LOCK_APV+0xa0 vn_lock(c4e962b8,1002,c4c06480) at vn_lock+0xac sync_vnode(c4e963c4,c4c06480) at sync_vnode+0xe3 sched_sync(0,e4fd1d38,0,c05f9150,0,...) at sched_sync+0x1ed fork_exit(c05f9150,0,e4fd1d38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd1d6c, ebp = 0 --- VOP_LOCK: 0xc4e962b8 is not locked but should be KDB: enter: lock violation [thread pid 46 tid 100042 ] Stopped at kdb_enter+0x2b: nop db> c KDB: stack backtrace: kdb_backtrace(e4fd1c78,c05fb86d,c07b2ab5,c07ceb78,c4e962b8,...) at kdb_backtrace+0x29 vfs_badlock(c07b2ab5,c07ceb78,c4e962b8) at vfs_badlock+0x11 assert_vop_elocked(c4e962b8,c07ceb78,c4e962b8,c07ceb78) at assert_vop_elocked+0x4d VOP_FSYNC_APV(c081c280,e4fd1cbc) at VOP_FSYNC_APV+0x8e sync_vnode(c4e963c4,c4c06480) at sync_vnode+0x106 sched_sync(0,e4fd1d38,0,c05f9150,0,...) at sched_sync+0x1ed fork_exit(c05f9150,0,e4fd1d38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd1d6c, ebp = 0 --- VOP_FSYNC: 0xc4e962b8 is not exclusive locked but should be KDB: enter: lock violation [thread pid 46 tid 100042 ] Stopped at kdb_enter+0x2b: nop db> c KDB: stack backtrace: kdb_backtrace(e4fd1c78,c05fb86d,c07b2ab5,c07ceb78,c4e962b8,...) at kdb_backtrace+0x29 vfs_badlock(c07b2ab5,c07ceb78,c4e962b8) at vfs_badlock+0x11 assert_vop_elocked(c4e962b8,c07ceb78,c4e962b8,c07ceb78) at assert_vop_eloc ked+0x4d VOP_FSYNC_APV(c081c280,e4fd1cbc) at VOP_FSYNC_APV+0xcb sync_vnode(c4e963c4,c4c06480) at sync_vnode+0x106 sched_sync(0,e4fd1d38,0,c05f9150,0,...) at sched_sync+0x1ed fork_exit(c05f9150,0,e4fd1d38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd1d6c, ebp = 0 --- VOP_FSYNC: 0xc4e962b8 is not exclusive locked but should be KDB: enter: lock violation [thread pid 46 tid 100042 ] Stopped at kdb_enter+0x2b: nop db> c KDB: tack backtrace: kdb_backtrace(e4fd1c70,c05fb7ba,c07b2a73,c07b2ba1,c4e962b8,...) at kdb_backtrace+0x29 vfs_badlock(c07b2a73,c07b2ba1,c4e962b8) at vfs_badlock+0x11 assert_vop_locked(c4e962b8,c07b2ba1,c081c280,e4fd1c98,c0762f26,...) at assert_vop_locked+0x4a vop_unlock_pre(e4fd1cac) at vop_unlock_pre+0x2d VOP_UNLOCK_APV(c081c280,e4fd1cac) at VOP_UNLOCK_APV+0x82 sync_vnode(c4e963c4,c4c06480) at sync_vnode+0x129 sched_sync(0,e4fd1d38,0,c05f9150,0,...) at sched_sync+0x1ed fork_exit(c05f9150,0,e4fd1d38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd1d6c, ebp = 0 --- VOP_UNLOCK: 0xc4e962b8 is not locked but should be KDB: enter: lock violation [thread pid 46 tid 100042 ] Stopped at kdb_enter+0x2b: nop db> c Rebooting... cpu_reset: Stopping other CPUs Where should I get patches for bge driver? Is there any fix for it? thanks, Ganbold From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 03:23:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 6632416A4DA; Wed, 30 Aug 2006 03:23:31 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50F5A43D49; Wed, 30 Aug 2006 03:23:30 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GIGfg-000KLJ-9m; Wed, 30 Aug 2006 12:23:20 +0900 Message-ID: <44F504A8.8070503@micom.mng.net> Date: Wed, 30 Aug 2006 12:23:20 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: pyunyh@gmail.com References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> In-Reply-To: <20060830023537.GA47208@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, glebius@freebsd.org, oleg@freebsd.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 03:23:31 -0000 Hi, Thanks a lot for your patch. Your patch fixes panic, however I still see bge0: firmware handshake timed out bge0: link state changed to DOWN messages. When I tried to use Oleg's if_bge.c, rev. 1.140 in STABLE buildkernel stops: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/usr/include -I/usr/obj/usr/src/sys/DEVIL /usr/src/sys/modules/bge/../../dev/bge/if_bge.c /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2570:35: macro "VLAN_INPUT_TAG" requires 4 arguments, but only 3 given mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 mkdep: compile failed *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error I see VLAN_INPUT_TAG is defined as VLAN_INPUT_TAG(_ifp, _m, _t, _errcase) in if_vlan_var.h, rev v 1.21.2.2 with 4 arguments, however new if_bge.c, rev. 1.140 uses 3 arguments. Is it safe to use if_vlan_var.h, rev 1.24 and if_vlan.c, rev 1.114 only? What other patches should I use? When all these changes MFC to STABLE? thanks, Ganbold Pyun YongHyeon wrote: > I think your PHY was not recognized by brgphy(4). But I don't know it > fixes "firmware handshake timed out" issue you've seen. > Recently oleg fixed a long standing bug in bge(4). So you may also want > to merge the change.(See if_bge.c, rev. 1.140) > Patch generated against RELENG_6(compile tested only). > > > ------------------------------------------------------------------------ > > Index: miidevs > =================================================================== > RCS file: /home/ncvs/src/sys/dev/mii/miidevs,v > retrieving revision 1.30.2.3 > diff -u -r1.30.2.3 miidevs > --- miidevs 8 Aug 2006 07:51:21 -0000 1.30.2.3 > +++ miidevs 30 Aug 2006 02:28:07 -0000 > @@ -118,6 +118,7 @@ > model xxBROADCOM BCM5400 0x0004 Broadcom 1000baseTX PHY > model xxBROADCOM BCM5401 0x0005 BCM5401 10/100/1000baseTX PHY > model xxBROADCOM BCM5411 0x0007 BCM5411 10/100/1000baseTX PHY > +model xxBROADCOM BCM5752 0x0010 BCM5752 10/100/1000baseTX PHY > model xxBROADCOM BCM5701 0x0011 BCM5701 10/100/1000baseTX PHY > model xxBROADCOM BCM5703 0x0016 BCM5703 10/100/1000baseTX PHY > model xxBROADCOM BCM5704 0x0019 BCM5704 10/100/1000baseTX PHY > Index: brgphy.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/mii/brgphy.c,v > retrieving revision 1.34.2.6 > diff -u -r1.34.2.6 brgphy.c > --- brgphy.c 8 Aug 2006 04:37:18 -0000 1.34.2.6 > +++ brgphy.c 30 Aug 2006 02:28:07 -0000 > @@ -126,6 +126,12 @@ > } > > if (MII_OUI(ma->mii_id1, ma->mii_id2) == MII_OUI_xxBROADCOM && > + MII_MODEL(ma->mii_id2) == MII_MODEL_xxBROADCOM_BCM5752) { > + device_set_desc(dev, MII_STR_xxBROADCOM_BCM5752); > + return(BUS_PROBE_DEFAULT); > + } > + > + if (MII_OUI(ma->mii_id1, ma->mii_id2) == MII_OUI_xxBROADCOM && > MII_MODEL(ma->mii_id2) == MII_MODEL_xxBROADCOM_BCM5701) { > device_set_desc(dev, MII_STR_xxBROADCOM_BCM5701); > return(BUS_PROBE_DEFAULT); > @@ -665,6 +671,7 @@ > bcm5704_load_dspcode(sc); > break; > case MII_MODEL_xxBROADCOM_BCM5750: > + case MII_MODEL_xxBROADCOM_BCM5752: > case MII_MODEL_xxBROADCOM_BCM5714: > case MII_MODEL_xxBROADCOM_BCM5780: > case MII_MODEL_xxBROADCOM_BCM5706C: > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 07:29:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3586816A4E2 for ; Wed, 30 Aug 2006 07:29:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49DEB43D5A for ; Wed, 30 Aug 2006 07:29:00 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so154773pye for ; Wed, 30 Aug 2006 00:28:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=jrTk7g9Td9MRZF+Jy3GzpYuHVjoeOcRbpSJ5+eFMOuFtuwb/bawIuz9o5Tu3a38p/fMcBLamKemUbjDyIsG9cey5/W8GnY8SRxT90279QJRy2aUJA6zB+VUKTgneKqCVFZW7pkqAyPOIk9tFQw8Kahnhkf3LnDRExGskVwbG1vc= Received: by 10.35.39.13 with SMTP id r13mr395530pyj; Wed, 30 Aug 2006 00:28:59 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 15sm1008088nzp.2006.08.30.00.28.57; Wed, 30 Aug 2006 00:28:59 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k7U7URl6049338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 16:30:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k7U7UPqU049337; Wed, 30 Aug 2006 16:30:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 30 Aug 2006 16:30:25 +0900 From: Pyun YongHyeon To: Ganbold Message-ID: <20060830073025.GB47208@cdnetworks.co.kr> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <44F504A8.8070503@micom.mng.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, glebius@freebsd.org, oleg@freebsd.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 07:29:02 -0000 --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: > Hi, > > Thanks a lot for your patch. Your patch fixes panic, however I still see > bge0: firmware handshake timed out > bge0: link state changed to DOWN > messages. > > When I tried to use Oleg's if_bge.c, rev. 1.140 in STABLE buildkernel stops: > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- > -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include > -I/usr/include -I/usr/obj/usr/src/sys/DEVIL > /usr/src/sys/modules/bge/../../dev/bge/if_bge.c > /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2570:35: macro > "VLAN_INPUT_TAG" requires 4 arguments, but only 3 given > mkdep: compile failed > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > mkdep: compile failed > *** Error code 1 > 2 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > I see VLAN_INPUT_TAG is defined as VLAN_INPUT_TAG(_ifp, _m, _t, > _errcase) in if_vlan_var.h, rev v 1.21.2.2 with 4 arguments, however > new if_bge.c, rev. 1.140 uses 3 arguments. > Is it safe to use if_vlan_var.h, rev 1.24 and if_vlan.c, rev 1.114 only? > What other patches should I use? > When all these changes MFC to STABLE? > You should use VLAN_INPUT_TAG_NEW macro in RELENG_6. Anyway, here is guess work for BCM5752(obtained from OpenBSD). Because I don't have 5752 hardware I don't know whether it works or not. The patch is for RELENG_6(You need brgphy(4) patch too). > thanks, > > Ganbold > > Pyun YongHyeon wrote: > >I think your PHY was not recognized by brgphy(4). But I don't know it > >fixes "firmware handshake timed out" issue you've seen. > >Recently oleg fixed a long standing bug in bge(4). So you may also want > >to merge the change.(See if_bge.c, rev. 1.140) > >Patch generated against RELENG_6(compile tested only). > > -- Regards, Pyun YongHyeon --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="bge.5752.diff" Index: if_bge.c =================================================================== RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v retrieving revision 1.91.2.16 diff -u -r1.91.2.16 if_bge.c --- if_bge.c 10 Aug 2006 11:02:14 -0000 1.91.2.16 +++ if_bge.c 30 Aug 2006 07:20:43 -0000 @@ -1007,9 +1007,26 @@ /* Set up the PCI DMA control register. */ if (sc->bge_pcie) { /* PCI Express bus */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + uint32_t device_ctl; + + /* alternative from Linux driver */ +#define DMA_CTRL_WRITE_PCIE_H20MARK_128 0x00180000 +#define DMA_CTRL_WRITE_PCIE_H20MARK_256 0x00380000 + + dma_rw_ctl = 0x76000000; /* XXX XXX XXX */; + device_ctl = pci_read_config(sc->bge_dev, + BGE_PCI_CONF_DEV_CTRL, 4); + if ((device_ctl & 0x00e0) && 0) { + /* + * This clause is exactly what the Broadcom-supplied + * Linux does; but given overall register programming + * by bge(4), this larger DMA-write watermark + * value causes BCM5721 chips to totally wedge. + */ + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256; + } else { + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128; + } } else if (sc->bge_pcix) { /* PCI-X bus */ if (BGE_IS_5714_FAMILY(sc)) { @@ -1148,22 +1165,20 @@ CSR_WRITE_4(sc, BGE_BMAN_DMA_DESCPOOL_HIWAT, 10); /* Enable buffer manager */ - if (!(BGE_IS_5705_OR_BEYOND(sc))) { - CSR_WRITE_4(sc, BGE_BMAN_MODE, - BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); + CSR_WRITE_4(sc, BGE_BMAN_MODE, + BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); - /* Poll for buffer manager start indication */ - for (i = 0; i < BGE_TIMEOUT; i++) { - if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) - break; - DELAY(10); - } + /* Poll for buffer manager start indication */ + for (i = 0; i < BGE_TIMEOUT; i++) { + if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) + break; + DELAY(10); + } - if (i == BGE_TIMEOUT) { - device_printf(sc->bge_dev, - "buffer manager failed to start\n"); - return (ENXIO); - } + if (i == BGE_TIMEOUT) { + device_printf(sc->bge_dev, + "buffer manager failed to start\n"); + return (ENXIO); } /* Enable flow-through queues */ Index: if_bgereg.h =================================================================== RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v retrieving revision 1.36.2.7 diff -u -r1.36.2.7 if_bgereg.h --- if_bgereg.h 10 Aug 2006 11:02:14 -0000 1.36.2.7 +++ if_bgereg.h 30 Aug 2006 07:20:43 -0000 @@ -196,6 +196,15 @@ #define BGE_PCI_ISR_MBX_HI 0xB0 #define BGE_PCI_ISR_MBX_LO 0xB4 +/* XXX: + * Used in PCI-Express code for 575x chips. + * Should be replaced with checking for a PCI config-space + * capability for PCI-Express, and PCI-Express standard + * offsets into that capability block. + */ +#define BGE_PCI_CONF_DEV_CTRL 0xD8 +#define BGE_PCI_CONF_DEV_STUS 0xDA + /* PCI Misc. Host control register */ #define BGE_PCIMISCCTL_CLEAR_INTA 0x00000001 #define BGE_PCIMISCCTL_MASK_PCI_INTR 0x00000002 @@ -305,6 +314,10 @@ #define BGE_PCIDMARWCTL_DFLT_PCI_WR_CMD 0xF0000000 # define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 +/* PCI DMA Read/Write Control register, alternate usage for PCI-Express */ +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128 0x00180000 +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256 0x00380000 + #define BGE_PCI_READ_BNDRY_DISABLE 0x00000000 #define BGE_PCI_READ_BNDRY_16BYTES 0x00000100 #define BGE_PCI_READ_BNDRY_32BYTES 0x00000200 --4SFOXa2GPu3tIq4H-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 07:37:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0FB8C16A4DE; Wed, 30 Aug 2006 07:37:38 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D755F43D45; Wed, 30 Aug 2006 07:37:36 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GIKdc-000MHK-CR; Wed, 30 Aug 2006 16:37:28 +0900 Message-ID: <44F54038.3020404@micom.mng.net> Date: Wed, 30 Aug 2006 16:37:28 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: pyunyh@gmail.com References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> In-Reply-To: <20060830073025.GB47208@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: oleg@freebsd.org, glebius@freebsd.org, freebsd-stable@freebsd.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 07:37:38 -0000 Pyun YongHyeon wrote: > On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: > > Hi, > > > > Thanks a lot for your patch. Your patch fixes panic, however I still see > > bge0: firmware handshake timed out > > bge0: link state changed to DOWN > > messages. > > > > When I tried to use Oleg's if_bge.c, rev. 1.140 in STABLE buildkernel stops: > > > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- > > -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include > > -I/usr/include -I/usr/obj/usr/src/sys/DEVIL > > /usr/src/sys/modules/bge/../../dev/bge/if_bge.c > > /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2570:35: macro > > "VLAN_INPUT_TAG" requires 4 arguments, but only 3 given > > mkdep: compile failed > > *** Error code 1 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > mkdep: compile failed > > *** Error code 1 > > 2 errors > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > > > I see VLAN_INPUT_TAG is defined as VLAN_INPUT_TAG(_ifp, _m, _t, > > _errcase) in if_vlan_var.h, rev v 1.21.2.2 with 4 arguments, however > > new if_bge.c, rev. 1.140 uses 3 arguments. > > Is it safe to use if_vlan_var.h, rev 1.24 and if_vlan.c, rev 1.114 only? > > What other patches should I use? > > When all these changes MFC to STABLE? > > > > You should use VLAN_INPUT_TAG_NEW macro in RELENG_6. > Anyway, here is guess work for BCM5752(obtained from OpenBSD). > Because I don't have 5752 hardware I don't know whether it works or > not. The patch is for RELENG_6(You need brgphy(4) patch too). > Where can I get brgphy(4) patch for RELENG_6? thanks, Ganbold > > thanks, > > > > Ganbold > > > > Pyun YongHyeon wrote: > > >I think your PHY was not recognized by brgphy(4). But I don't know it > > >fixes "firmware handshake timed out" issue you've seen. > > >Recently oleg fixed a long standing bug in bge(4). So you may also want > > >to merge the change.(See if_bge.c, rev. 1.140) > > >Patch generated against RELENG_6(compile tested only). > > > > > > ------------------------------------------------------------------------ > > Index: if_bge.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v > retrieving revision 1.91.2.16 > diff -u -r1.91.2.16 if_bge.c > --- if_bge.c 10 Aug 2006 11:02:14 -0000 1.91.2.16 > +++ if_bge.c 30 Aug 2006 07:20:43 -0000 > @@ -1007,9 +1007,26 @@ > /* Set up the PCI DMA control register. */ > if (sc->bge_pcie) { > /* PCI Express bus */ > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > + uint32_t device_ctl; > + > + /* alternative from Linux driver */ > +#define DMA_CTRL_WRITE_PCIE_H20MARK_128 0x00180000 > +#define DMA_CTRL_WRITE_PCIE_H20MARK_256 0x00380000 > + > + dma_rw_ctl = 0x76000000; /* XXX XXX XXX */; > + device_ctl = pci_read_config(sc->bge_dev, > + BGE_PCI_CONF_DEV_CTRL, 4); > + if ((device_ctl & 0x00e0) && 0) { > + /* > + * This clause is exactly what the Broadcom-supplied > + * Linux does; but given overall register programming > + * by bge(4), this larger DMA-write watermark > + * value causes BCM5721 chips to totally wedge. > + */ > + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256; > + } else { > + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128; > + } > } else if (sc->bge_pcix) { > /* PCI-X bus */ > if (BGE_IS_5714_FAMILY(sc)) { > @@ -1148,22 +1165,20 @@ > CSR_WRITE_4(sc, BGE_BMAN_DMA_DESCPOOL_HIWAT, 10); > > /* Enable buffer manager */ > - if (!(BGE_IS_5705_OR_BEYOND(sc))) { > - CSR_WRITE_4(sc, BGE_BMAN_MODE, > - BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); > + CSR_WRITE_4(sc, BGE_BMAN_MODE, > + BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); > > - /* Poll for buffer manager start indication */ > - for (i = 0; i < BGE_TIMEOUT; i++) { > - if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) > - break; > - DELAY(10); > - } > + /* Poll for buffer manager start indication */ > + for (i = 0; i < BGE_TIMEOUT; i++) { > + if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) > + break; > + DELAY(10); > + } > > - if (i == BGE_TIMEOUT) { > - device_printf(sc->bge_dev, > - "buffer manager failed to start\n"); > - return (ENXIO); > - } > + if (i == BGE_TIMEOUT) { > + device_printf(sc->bge_dev, > + "buffer manager failed to start\n"); > + return (ENXIO); > } > > /* Enable flow-through queues */ > Index: if_bgereg.h > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v > retrieving revision 1.36.2.7 > diff -u -r1.36.2.7 if_bgereg.h > --- if_bgereg.h 10 Aug 2006 11:02:14 -0000 1.36.2.7 > +++ if_bgereg.h 30 Aug 2006 07:20:43 -0000 > @@ -196,6 +196,15 @@ > #define BGE_PCI_ISR_MBX_HI 0xB0 > #define BGE_PCI_ISR_MBX_LO 0xB4 > > +/* XXX: > + * Used in PCI-Express code for 575x chips. > + * Should be replaced with checking for a PCI config-space > + * capability for PCI-Express, and PCI-Express standard > + * offsets into that capability block. > + */ > +#define BGE_PCI_CONF_DEV_CTRL 0xD8 > +#define BGE_PCI_CONF_DEV_STUS 0xDA > + > /* PCI Misc. Host control register */ > #define BGE_PCIMISCCTL_CLEAR_INTA 0x00000001 > #define BGE_PCIMISCCTL_MASK_PCI_INTR 0x00000002 > @@ -305,6 +314,10 @@ > #define BGE_PCIDMARWCTL_DFLT_PCI_WR_CMD 0xF0000000 > # define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 > > +/* PCI DMA Read/Write Control register, alternate usage for PCI-Express */ > +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128 0x00180000 > +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256 0x00380000 > + > #define BGE_PCI_READ_BNDRY_DISABLE 0x00000000 > #define BGE_PCI_READ_BNDRY_16BYTES 0x00000100 > #define BGE_PCI_READ_BNDRY_32BYTES 0x00000200 > > ------------------------------------------------------------------------ > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 07:50:24 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 4A9EE16A4E7; Wed, 30 Aug 2006 07:50:24 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C621D43D49; Wed, 30 Aug 2006 07:50:16 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7U7oDHH024121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 11:50:14 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7U7oDC8024120; Wed, 30 Aug 2006 11:50:13 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 30 Aug 2006 11:50:12 +0400 From: Gleb Smirnoff To: Pyun YongHyeon Message-ID: <20060830075012.GP76666@cell.sick.ru> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="XIiC+We3v3zHqZ6Z" Content-Disposition: inline In-Reply-To: <20060830073025.GB47208@cdnetworks.co.kr> User-Agent: Mutt/1.5.6i Cc: freebsd-stable@FreeBSD.org, Ganbold , oleg@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 07:50:24 -0000 --XIiC+We3v3zHqZ6Z Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Pyun, On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote: P> =================================================================== P> RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v P> retrieving revision 1.91.2.16 P> diff -u -r1.91.2.16 if_bge.c P> --- if_bge.c 10 Aug 2006 11:02:14 -0000 1.91.2.16 P> +++ if_bge.c 30 Aug 2006 07:20:43 -0000 P> @@ -1007,9 +1007,26 @@ P> /* Set up the PCI DMA control register. */ P> if (sc->bge_pcie) { P> /* PCI Express bus */ P> - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | P> - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | P> - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); P> + uint32_t device_ctl; P> + P> + /* alternative from Linux driver */ P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_128 0x00180000 P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_256 0x00380000 P> + P> + dma_rw_ctl = 0x76000000; /* XXX XXX XXX */; P> + device_ctl = pci_read_config(sc->bge_dev, P> + BGE_PCI_CONF_DEV_CTRL, 4); P> + if ((device_ctl & 0x00e0) && 0) { P> + /* P> + * This clause is exactly what the Broadcom-supplied P> + * Linux does; but given overall register programming P> + * by bge(4), this larger DMA-write watermark P> + * value causes BCM5721 chips to totally wedge. P> + */ P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256; P> + } else { P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128; P> + } P> } else if (sc->bge_pcix) { My small penny into the discussion. I was working on reviewing the difference in initializing the PCI DMA control register in Linux tg3.c and in bge(4). I was quite lost in this stuff, and so I asked for help from David Christensen (davidch@). He has explained me all the differencies in this register between chips and I have prepared the attached patch. Since I have very small collection of bge(4) cards, I avoid to commit it. May be I will commit it after 6.2-RELEASE if several people test it on their cards and all is OK. And it will live unmerged in HEAD until 6.3-RELEASE. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --XIiC+We3v3zHqZ6Z Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="bge.dmarwctl" Index: if_bge.c =================================================================== RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v retrieving revision 1.139 diff -u -p -r1.139 if_bge.c --- if_bge.c 23 Aug 2006 11:32:54 -0000 1.139 +++ if_bge.c 23 Aug 2006 15:18:22 -0000 @@ -1005,36 +1005,48 @@ bge_chipinit(struct bge_softc *sc) BGE_MEMWIN_WRITE(sc, i, 0); /* Set up the PCI DMA control register. */ + dma_rw_ctl = BGE_PCIDMARWCTL_READ_CMD | BGE_PCIDMARWCTL_WRITE_CMD; + + /* Bits 23, 22. */ + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || + sc->bge_asicrev == BGE_ASICREV_BCM5701 || + sc->bge_asicrev == BGE_ASICREV_BCM5714) + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE | + BGE_PCIDMARWCTL_USE_MRM; + + /* DMA watermarks: bits 21 - 19, 18 - 16. */ if (sc->bge_flags & BGE_FLAG_PCIE) { - /* PCI Express bus */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + /* + * DMA read watermark not used on PCI-E. + * DMA write watermark set to 128 bytes. + */ + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); } else if (sc->bge_flags & BGE_FLAG_PCIX) { - /* PCI-X bus */ - if (BGE_IS_5714_FAMILY(sc)) { - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD; - dma_rw_ctl &= ~BGE_PCIDMARWCTL_ONEDMA_ATONCE; /* XXX */ - /* XXX magic values, Broadcom-supplied Linux driver */ - if (sc->bge_asicrev == BGE_ASICREV_BCM5780) - dma_rw_ctl |= (1 << 20) | (1 << 18) | - BGE_PCIDMARWCTL_ONEDMA_ATONCE; - else - dma_rw_ctl |= (1 << 20) | (1 << 18) | (1 << 15); - - } else if (sc->bge_asicrev == BGE_ASICREV_BCM5704) + switch (sc->bge_asicrev) { + case BGE_ASICREV_BCM5780: + /* XXX: Linux driver magic values. */ + dma_rw_ctl |= (1 << 20) | (1 << 18) | + BGE_PCIDMARWCTL_ONEDMA_ATONCE; + break; + case BGE_ASICREV_BCM5714: + case BGE_ASICREV_BCM5714_A0: + /* XXX: Linux driver magic values. */ + dma_rw_ctl |= (1 << 20) | (1 << 18) | + BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL; + break; + case BGE_ASICREV_BCM5704: /* * The 5704 uses a different encoding of read/write - * watermarks. + * watermarks: 384 bytes for write and 1536 for read. */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); - else - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | - (0x0F); + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + break; + default: + /* All other chips: 384 for write and read. */ + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + } /* * 5703 and 5704 need ONEDMA_AT_ONCE as a workaround @@ -1047,18 +1059,20 @@ bge_chipinit(struct bge_softc *sc) tmp = CSR_READ_4(sc, BGE_PCI_CLKCTL) & 0x1f; if (tmp == 0x6 || tmp == 0x7) dma_rw_ctl |= BGE_PCIDMARWCTL_ONEDMA_ATONCE; + + /* Set bit 23 to enable PCIX hw bug fix. */ + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE; } } else - /* Conventional PCI bus */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | - (0x0F); - - if (sc->bge_asicrev == BGE_ASICREV_BCM5703 || - sc->bge_asicrev == BGE_ASICREV_BCM5704 || - sc->bge_asicrev == BGE_ASICREV_BCM5705) - dma_rw_ctl &= ~BGE_PCIDMARWCTL_MINDMA; + /* Conventional PCI bus: 1024 bytes for read and write. */ + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + + /* Set minimum DMA only for 5700 and 5701. */ + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || + sc->bge_asicrev == BGE_ASICREV_BCM5701) + dma_rw_ctl |= 0xf; + pci_write_config(sc->bge_dev, BGE_PCI_DMA_RW_CTL, dma_rw_ctl, 4); /* Index: if_bgereg.h =================================================================== RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v retrieving revision 1.52 diff -u -p -r1.52 if_bgereg.h --- if_bgereg.h 23 Aug 2006 11:32:54 -0000 1.52 +++ if_bgereg.h 23 Aug 2006 15:16:12 -0000 @@ -290,20 +290,25 @@ #define BGE_CHIPREV_5701_AX 0x00 /* PCI DMA Read/Write Control register */ +#define BGE_PCIDMARWCTL_WRITE_CMD 0x70000000 +#define BGE_PCIDMARWCTL_READ_CMD 0x06000000 + #define BGE_PCIDMARWCTL_MINDMA 0x000000FF #define BGE_PCIDMARWCTL_RDADRR_BNDRY 0x00000700 #define BGE_PCIDMARWCTL_WRADDR_BNDRY 0x00003800 #define BGE_PCIDMARWCTL_ONEDMA_ATONCE 0x00004000 +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_GLOBAL 0x00004000 +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL 0x00008000 #define BGE_PCIDMARWCTL_RD_WAT 0x00070000 -# define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 +#define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 #define BGE_PCIDMARWCTL_WR_WAT 0x00380000 -# define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 +#define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 #define BGE_PCIDMARWCTL_USE_MRM 0x00400000 #define BGE_PCIDMARWCTL_ASRT_ALL_BE 0x00800000 #define BGE_PCIDMARWCTL_DFLT_PCI_RD_CMD 0x0F000000 -# define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 +#define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 #define BGE_PCIDMARWCTL_DFLT_PCI_WR_CMD 0xF0000000 -# define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 +#define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 #define BGE_PCI_READ_BNDRY_DISABLE 0x00000000 #define BGE_PCI_READ_BNDRY_16BYTES 0x00000100 @@ -2075,9 +2080,6 @@ struct bge_status_block { #define BGE_MEDIA_COPPER 0x00000010 #define BGE_MEDIA_FIBER 0x00000020 -#define BGE_PCI_READ_CMD 0x06000000 -#define BGE_PCI_WRITE_CMD 0x70000000 - #define BGE_TICKS_PER_SEC 1000000 /* --XIiC+We3v3zHqZ6Z-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 07:53:37 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 6622C16A4DA; Wed, 30 Aug 2006 07:53:37 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B504943D46; Wed, 30 Aug 2006 07:53:35 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7U7rYKC024166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 11:53:34 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7U7rXqE024165; Wed, 30 Aug 2006 11:53:34 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 30 Aug 2006 11:53:33 +0400 From: Gleb Smirnoff To: Ganbold Message-ID: <20060830075333.GQ76666@cell.sick.ru> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="XRI2XbIfl/05pQwm" Content-Disposition: inline In-Reply-To: <44F504A8.8070503@micom.mng.net> User-Agent: Mutt/1.5.6i Cc: pyunyh@gmail.com, freebsd-stable@FreeBSD.org, oleg@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 07:53:37 -0000 --XRI2XbIfl/05pQwm Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Ganbold, On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: G> Thanks a lot for your patch. Your patch fixes panic, however I still see G> bge0: firmware handshake timed out G> bge0: link state changed to DOWN G> messages. And yesterday delphij@ have sent me patch against "firmware handshake timed out". It is attached. Can you please test it? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --XRI2XbIfl/05pQwm Content-Type: message/rfc822 Content-Disposition: inline Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7T6e7Xv016363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 29 Aug 2006 10:40:09 +0400 (MSD) (envelope-from delphij@delphij.net) Received: from relay2.bestcom.ru (relay2.bestcom.ru [217.72.144.6]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id k7T6e7wc085014 for ; Tue, 29 Aug 2006 10:40:07 +0400 (MSD) (envelope-from delphij@delphij.net) Received: from localhost (localhost [127.0.0.1]) by relay2.bestcom.ru (Postfix) with ESMTP id 54C2C4ACFF for ; Tue, 29 Aug 2006 10:41:17 +0400 (MSD) X-Virus-Scanned: by amavisd-new using ClamAV at bestcom.ru Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by relay2.bestcom.ru (Postfix) with ESMTP id 363944ACE5 for ; Tue, 29 Aug 2006 10:41:02 +0400 (MSD) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 89D8655D1E for ; Tue, 29 Aug 2006 06:39:51 +0000 (GMT) (envelope-from delphij@delphij.net) Received: by hub.freebsd.org (Postfix) id 8757216A4DD; Tue, 29 Aug 2006 06:39:51 +0000 (UTC) Delivered-To: glebius@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D5CE16A4DA; Tue, 29 Aug 2006 06:39:51 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA6943D46; Tue, 29 Aug 2006 06:39:47 +0000 (GMT) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 6D313EB36ED; Tue, 29 Aug 2006 14:39:44 +0800 (CST) Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id QogYaXnZOkbA; Tue, 29 Aug 2006 14:39:41 +0800 (CST) Received: from [10.217.12.84] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 28AABEB24F9; Tue, 29 Aug 2006 14:39:40 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:x-enigmail-version:content-type; b=OhhR7GxJD73QxLVSnBlkBP7VFzdJuFRkqw0Otm+xWE8WJMu9E3lvxZFN/3V8Hurg6 HlUR3J6L7G8zSx1zuK3ZQ== Message-ID: <44F3E123.7000100@delphij.net> Date: Tue, 29 Aug 2006 14:39:31 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: oleg@FreeBSD.org, glebius@FreeBSD.org Subject: [PATCH FOR REVIEW] Broadcom BCM 5752 A02 "firmware handshake timeout" X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig080E669DC7176E89A24520D7" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig080E669DC7176E89A24520D7 Content-Type: multipart/mixed; boundary="------------070402090405020206020700" This is a multi-part message in MIME format. --------------070402090405020206020700 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, A colleague of mine has found that BCM 5752 A02 would get "firmware handshake timeout" problem during the ifconfig stage. After some investigation and comparing to the Linux driver I have the attached patch make the problem disappear. Unfortunately I do not have specification documentation from Broadcom so I can not say if that is a "real fix" :-( The patch was tested on Dell Latitude D820. The only problem remains is that the -CURRENT kernel crashes if I did not explicitly set the media and do a "ifconfig bge0 up", with "panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia". Backtrace is available upon request. Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------070402090405020206020700 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="patch-bge-firmware-handshake-timeout" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="patch-bge-firmware-handshake-timeout" Index: if_bge.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v retrieving revision 1.140 diff -u -r1.140 if_bge.c --- if_bge.c 24 Aug 2006 14:41:16 -0000 1.140 +++ if_bge.c 29 Aug 2006 06:20:44 -0000 @@ -2313,6 +2313,13 @@ BGE_PCIMISCCTL_INDIRECT_ACCESS|BGE_PCIMISCCTL_MASK_PCI_INTR| BGE_HIF_SWAP_OPTIONS|BGE_PCIMISCCTL_PCISTATE_RW, 4); =20 + /* XXX: Broadcom Linux driver. */ + if (sc->bge_asicrev =3D=3D BGE_ASICREV_BCM5752 || + sc->bge_asicrev =3D=3D BGE_ASICREV_BCM5755 || + sc->bge_asicrev =3D=3D BGE_ASICREV_BCM5787) { + CSR_WRITE_4(sc, BGE_FASTBOOT_PC, 0x0); + } + reset =3D BGE_MISCCFG_RESET_CORE_CLOCKS|(65<<1); =20 /* XXX: Broadcom Linux driver. */ Index: if_bgereg.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v retrieving revision 1.52 diff -u -r1.52 if_bgereg.h --- if_bgereg.h 23 Aug 2006 11:32:54 -0000 1.52 +++ if_bgereg.h 29 Aug 2006 06:32:31 -0000 @@ -1656,6 +1656,7 @@ #define BGE_EE_CTL 0x6840 #define BGE_MDI_CTL 0x6844 #define BGE_EE_DELAY 0x6848 +#define BGE_FASTBOOT_PC 0x6894 =20 /* Mode control register */ #define BGE_MODECTL_INT_SNDCOAL_ONLY 0x00000001 --------------070402090405020206020700-- --------------enig080E669DC7176E89A24520D7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE8+EjOfuToMruuMARAxxmAKCK7Qy6CCGCW1uq1NTuAlnNWGqjzwCghN39 dmZJszLIGj5poU7Jet4jg/Q= =vPM8 -----END PGP SIGNATURE----- --------------enig080E669DC7176E89A24520D7-- --XRI2XbIfl/05pQwm-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 08:22:49 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 94A5616A4DD; Wed, 30 Aug 2006 08:22:49 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A68C43D68; Wed, 30 Aug 2006 08:22:40 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GILL5-000McH-Sd; Wed, 30 Aug 2006 17:22:24 +0900 Message-ID: <44F54ABF.30109@micom.mng.net> Date: Wed, 30 Aug 2006 17:22:23 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Gleb Smirnoff References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830075333.GQ76666@cell.sick.ru> In-Reply-To: <20060830075333.GQ76666@cell.sick.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pyunyh@gmail.com, oleg@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 08:22:49 -0000 Gleb, Pyun, Gleb Smirnoff wrote: > Ganbold, > > On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: > G> Thanks a lot for your patch. Your patch fixes panic, however I still see > G> bge0: firmware handshake timed out > G> bge0: link state changed to DOWN > G> messages. > > And yesterday delphij@ have sent me patch against "firmware handshake timed out". > It is attached. Can you please test it? > Applied delphij@'s patch and now "bge0: firmware handshake timed out" message is gone. Previously there was applied Pyun's brgphy(4) patch. Ganbold > > > ------------------------------------------------------------------------ > > Subject: > [PATCH FOR REVIEW] Broadcom BCM 5752 A02 "firmware handshake timeout" > From: > LI Xin > Date: > Tue, 29 Aug 2006 14:39:31 +0800 > To: > oleg@FreeBSD.org, glebius@FreeBSD.org > > To: > oleg@FreeBSD.org, glebius@FreeBSD.org > > > Hi, > > A colleague of mine has found that BCM 5752 A02 would get "firmware > handshake timeout" problem during the ifconfig stage. After some > investigation and comparing to the Linux driver I have the attached > patch make the problem disappear. Unfortunately I do not have > specification documentation from Broadcom so I can not say if that is a > "real fix" :-( > > The patch was tested on Dell Latitude D820. The only problem remains is > that the -CURRENT kernel crashes if I did not explicitly set the media > and do a "ifconfig bge0 up", with "panic: invalid ife->ifm_data (0xa) in > mii_phy_setmedia". Backtrace is available upon request. > > Cheers, > > ------------------------------------------------------------------------ > > Index: if_bge.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v > retrieving revision 1.140 > diff -u -r1.140 if_bge.c > --- if_bge.c 24 Aug 2006 14:41:16 -0000 1.140 > +++ if_bge.c 29 Aug 2006 06:20:44 -0000 > @@ -2313,6 +2313,13 @@ > BGE_PCIMISCCTL_INDIRECT_ACCESS|BGE_PCIMISCCTL_MASK_PCI_INTR| > BGE_HIF_SWAP_OPTIONS|BGE_PCIMISCCTL_PCISTATE_RW, 4); > > + /* XXX: Broadcom Linux driver. */ > + if (sc->bge_asicrev == BGE_ASICREV_BCM5752 || > + sc->bge_asicrev == BGE_ASICREV_BCM5755 || > + sc->bge_asicrev == BGE_ASICREV_BCM5787) { > + CSR_WRITE_4(sc, BGE_FASTBOOT_PC, 0x0); > + } > + > reset = BGE_MISCCFG_RESET_CORE_CLOCKS|(65<<1); > > /* XXX: Broadcom Linux driver. */ > Index: if_bgereg.h > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v > retrieving revision 1.52 > diff -u -r1.52 if_bgereg.h > --- if_bgereg.h 23 Aug 2006 11:32:54 -0000 1.52 > +++ if_bgereg.h 29 Aug 2006 06:32:31 -0000 > @@ -1656,6 +1656,7 @@ > #define BGE_EE_CTL 0x6840 > #define BGE_MDI_CTL 0x6844 > #define BGE_EE_DELAY 0x6848 > +#define BGE_FASTBOOT_PC 0x6894 > > /* Mode control register */ > #define BGE_MODECTL_INT_SNDCOAL_ONLY 0x00000001 > > ------------------------------------------------------------------------ > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 08:26:17 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 19E6B16A4E8; Wed, 30 Aug 2006 08:26:17 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B99D43D4C; Wed, 30 Aug 2006 08:26:15 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GILOh-000MeD-3H; Wed, 30 Aug 2006 17:26:07 +0900 Message-ID: <44F54B9F.8010508@micom.mng.net> Date: Wed, 30 Aug 2006 17:26:07 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Gleb Smirnoff References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> <20060830075012.GP76666@cell.sick.ru> In-Reply-To: <20060830075012.GP76666@cell.sick.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pyun YongHyeon , oleg@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 08:26:17 -0000 Gleb, Pyun, I'm a kind of bit confused here whose patch to choose. Can you guys enlighten me in this regard? thanks, Ganbold Gleb Smirnoff wrote: > Pyun, > > On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote: > P> =================================================================== > P> RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v > P> retrieving revision 1.91.2.16 > P> diff -u -r1.91.2.16 if_bge.c > P> --- if_bge.c 10 Aug 2006 11:02:14 -0000 1.91.2.16 > P> +++ if_bge.c 30 Aug 2006 07:20:43 -0000 > P> @@ -1007,9 +1007,26 @@ > P> /* Set up the PCI DMA control register. */ > P> if (sc->bge_pcie) { > P> /* PCI Express bus */ > P> - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > P> - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > P> - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > P> + uint32_t device_ctl; > P> + > P> + /* alternative from Linux driver */ > P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_128 0x00180000 > P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_256 0x00380000 > P> + > P> + dma_rw_ctl = 0x76000000; /* XXX XXX XXX */; > P> + device_ctl = pci_read_config(sc->bge_dev, > P> + BGE_PCI_CONF_DEV_CTRL, 4); > P> + if ((device_ctl & 0x00e0) && 0) { > P> + /* > P> + * This clause is exactly what the Broadcom-supplied > P> + * Linux does; but given overall register programming > P> + * by bge(4), this larger DMA-write watermark > P> + * value causes BCM5721 chips to totally wedge. > P> + */ > P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256; > P> + } else { > P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128; > P> + } > P> } else if (sc->bge_pcix) { > > My small penny into the discussion. I was working on reviewing the > difference in initializing the PCI DMA control register in Linux tg3.c > and in bge(4). > > I was quite lost in this stuff, and so I asked for help from David > Christensen (davidch@). He has explained me all the differencies > in this register between chips and I have prepared the attached patch. > > Since I have very small collection of bge(4) cards, I avoid to commit > it. May be I will commit it after 6.2-RELEASE if several people test it > on their cards and all is OK. And it will live unmerged in HEAD until > 6.3-RELEASE. > > > ------------------------------------------------------------------------ > > Index: if_bge.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v > retrieving revision 1.139 > diff -u -p -r1.139 if_bge.c > --- if_bge.c 23 Aug 2006 11:32:54 -0000 1.139 > +++ if_bge.c 23 Aug 2006 15:18:22 -0000 > @@ -1005,36 +1005,48 @@ bge_chipinit(struct bge_softc *sc) > BGE_MEMWIN_WRITE(sc, i, 0); > > /* Set up the PCI DMA control register. */ > + dma_rw_ctl = BGE_PCIDMARWCTL_READ_CMD | BGE_PCIDMARWCTL_WRITE_CMD; > + > + /* Bits 23, 22. */ > + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || > + sc->bge_asicrev == BGE_ASICREV_BCM5701 || > + sc->bge_asicrev == BGE_ASICREV_BCM5714) > + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE | > + BGE_PCIDMARWCTL_USE_MRM; > + > + /* DMA watermarks: bits 21 - 19, 18 - 16. */ > if (sc->bge_flags & BGE_FLAG_PCIE) { > - /* PCI Express bus */ > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > + /* > + * DMA read watermark not used on PCI-E. > + * DMA write watermark set to 128 bytes. > + */ > + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > } else if (sc->bge_flags & BGE_FLAG_PCIX) { > - /* PCI-X bus */ > - if (BGE_IS_5714_FAMILY(sc)) { > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD; > - dma_rw_ctl &= ~BGE_PCIDMARWCTL_ONEDMA_ATONCE; /* XXX */ > - /* XXX magic values, Broadcom-supplied Linux driver */ > - if (sc->bge_asicrev == BGE_ASICREV_BCM5780) > - dma_rw_ctl |= (1 << 20) | (1 << 18) | > - BGE_PCIDMARWCTL_ONEDMA_ATONCE; > - else > - dma_rw_ctl |= (1 << 20) | (1 << 18) | (1 << 15); > - > - } else if (sc->bge_asicrev == BGE_ASICREV_BCM5704) > + switch (sc->bge_asicrev) { > + case BGE_ASICREV_BCM5780: > + /* XXX: Linux driver magic values. */ > + dma_rw_ctl |= (1 << 20) | (1 << 18) | > + BGE_PCIDMARWCTL_ONEDMA_ATONCE; > + break; > + case BGE_ASICREV_BCM5714: > + case BGE_ASICREV_BCM5714_A0: > + /* XXX: Linux driver magic values. */ > + dma_rw_ctl |= (1 << 20) | (1 << 18) | > + BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL; > + break; > + case BGE_ASICREV_BCM5704: > /* > * The 5704 uses a different encoding of read/write > - * watermarks. > + * watermarks: 384 bytes for write and 1536 for read. > */ > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > - else > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > - (0x3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | > - (0x0F); > + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > + break; > + default: > + /* All other chips: 384 for write and read. */ > + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > + } > > /* > * 5703 and 5704 need ONEDMA_AT_ONCE as a workaround > @@ -1047,18 +1059,20 @@ bge_chipinit(struct bge_softc *sc) > tmp = CSR_READ_4(sc, BGE_PCI_CLKCTL) & 0x1f; > if (tmp == 0x6 || tmp == 0x7) > dma_rw_ctl |= BGE_PCIDMARWCTL_ONEDMA_ATONCE; > + > + /* Set bit 23 to enable PCIX hw bug fix. */ > + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE; > } > } else > - /* Conventional PCI bus */ > - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > - (0x7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | > - (0x0F); > - > - if (sc->bge_asicrev == BGE_ASICREV_BCM5703 || > - sc->bge_asicrev == BGE_ASICREV_BCM5704 || > - sc->bge_asicrev == BGE_ASICREV_BCM5705) > - dma_rw_ctl &= ~BGE_PCIDMARWCTL_MINDMA; > + /* Conventional PCI bus: 1024 bytes for read and write. */ > + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > + (7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > + > + /* Set minimum DMA only for 5700 and 5701. */ > + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || > + sc->bge_asicrev == BGE_ASICREV_BCM5701) > + dma_rw_ctl |= 0xf; > + > pci_write_config(sc->bge_dev, BGE_PCI_DMA_RW_CTL, dma_rw_ctl, 4); > > /* > Index: if_bgereg.h > =================================================================== > RCS file: /home/ncvs/src/sys/dev/bge/if_bgereg.h,v > retrieving revision 1.52 > diff -u -p -r1.52 if_bgereg.h > --- if_bgereg.h 23 Aug 2006 11:32:54 -0000 1.52 > +++ if_bgereg.h 23 Aug 2006 15:16:12 -0000 > @@ -290,20 +290,25 @@ > #define BGE_CHIPREV_5701_AX 0x00 > > /* PCI DMA Read/Write Control register */ > +#define BGE_PCIDMARWCTL_WRITE_CMD 0x70000000 > +#define BGE_PCIDMARWCTL_READ_CMD 0x06000000 > + > #define BGE_PCIDMARWCTL_MINDMA 0x000000FF > #define BGE_PCIDMARWCTL_RDADRR_BNDRY 0x00000700 > #define BGE_PCIDMARWCTL_WRADDR_BNDRY 0x00003800 > #define BGE_PCIDMARWCTL_ONEDMA_ATONCE 0x00004000 > +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_GLOBAL 0x00004000 > +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL 0x00008000 > #define BGE_PCIDMARWCTL_RD_WAT 0x00070000 > -# define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 > +#define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 > #define BGE_PCIDMARWCTL_WR_WAT 0x00380000 > -# define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 > +#define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 > #define BGE_PCIDMARWCTL_USE_MRM 0x00400000 > #define BGE_PCIDMARWCTL_ASRT_ALL_BE 0x00800000 > #define BGE_PCIDMARWCTL_DFLT_PCI_RD_CMD 0x0F000000 > -# define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 > +#define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 > #define BGE_PCIDMARWCTL_DFLT_PCI_WR_CMD 0xF0000000 > -# define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 > +#define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 > > #define BGE_PCI_READ_BNDRY_DISABLE 0x00000000 > #define BGE_PCI_READ_BNDRY_16BYTES 0x00000100 > @@ -2075,9 +2080,6 @@ struct bge_status_block { > #define BGE_MEDIA_COPPER 0x00000010 > #define BGE_MEDIA_FIBER 0x00000020 > > -#define BGE_PCI_READ_CMD 0x06000000 > -#define BGE_PCI_WRITE_CMD 0x70000000 > - > #define BGE_TICKS_PER_SEC 1000000 > > /* > > ------------------------------------------------------------------------ > > _______________________________________________ > 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" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 08:52:55 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 9F3EE16A4DA; Wed, 30 Aug 2006 08:52:55 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE38643D49; Wed, 30 Aug 2006 08:52:54 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7U8qoTu024574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 12:52:50 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7U8qnmH024573; Wed, 30 Aug 2006 12:52:49 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 30 Aug 2006 12:52:49 +0400 From: Gleb Smirnoff To: Ganbold Message-ID: <20060830085249.GS76666@cell.sick.ru> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830075333.GQ76666@cell.sick.ru> <44F54ABF.30109@micom.mng.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <44F54ABF.30109@micom.mng.net> User-Agent: Mutt/1.5.6i Cc: pyunyh@gmail.com, oleg@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 08:52:55 -0000 On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote: G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still see G> >G> bge0: firmware handshake timed out G> >G> bge0: link state changed to DOWN G> >G> messages. G> > G> >And yesterday delphij@ have sent me patch against "firmware handshake G> >timed out". G> >It is attached. Can you please test it? G> > G> G> Applied delphij@'s patch and now "bge0: firmware handshake timed out" G> message is gone. Previously there was applied Pyun's brgphy(4) patch. Good. We probably need to commit them both soon. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 08:53:42 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 0AC4616A4E2; Wed, 30 Aug 2006 08:53:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A468643D6A; Wed, 30 Aug 2006 08:53:33 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k7U8rWr2024588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 12:53:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k7U8rV1R024587; Wed, 30 Aug 2006 12:53:31 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 30 Aug 2006 12:53:31 +0400 From: Gleb Smirnoff To: Ganbold Message-ID: <20060830085331.GT76666@cell.sick.ru> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> <20060830075012.GP76666@cell.sick.ru> <44F54B9F.8010508@micom.mng.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <44F54B9F.8010508@micom.mng.net> User-Agent: Mutt/1.5.6i Cc: Pyun YongHyeon , oleg@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 08:53:42 -0000 On Wed, Aug 30, 2006 at 05:26:07PM +0900, Ganbold wrote: G> Gleb, Pyun, G> G> I'm a kind of bit confused here whose patch to choose. G> Can you guys enlighten me in this regard? Can you please merge them? You should take all the stuff that prepares the dma_rw_ctl variable from my patch, and all the other stuff from Pyun's patch. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 10:16:29 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 515B316A4DA; Wed, 30 Aug 2006 10:16:29 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E31D443D46; Wed, 30 Aug 2006 10:16:28 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GIMNJ-0000Dd-QH; Wed, 30 Aug 2006 12:28:45 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@FreeBSD.org, freebsd-net@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Aug 2006 12:28:45 +0300 From: Danny Braniss Message-ID: Cc: Subject: tcp/udp performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 10:16:29 -0000 ever since 6.1 I've seen fluctuations in the performance of the em (Intel(R) PRO/1000 Gigabit Ethernet). motherboard OBN (On Board NIC) ---------------- ------------------ 1- Intel SE7501WV2S Intel 82546EB::2.1 2- Intel SE7320VP2D2 INTEL 82541 3- Sun Fire X4100 Server Intel(R) PRO/1000 test 1: writing to a NetApp filer via NFS/UDP FreeBSD Linux MegaBytes/sec 1- Average: 18.48 32.61 2- Average: 15.69 35.72 3- Average: 16.61 29.69 (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of around 60% on FreeBSD but none on Linux) test2: iperf using 1 as server: FreeBSD(*) Linux Mbits/sec 1- 926 905 (this machine was busy) 2- 545 798 3- 910 912 *: did a 'sysctl net.inet.tcp.sendspace=65536' So, it seems to me something is not that good in the UDP department, but I can't find what to tweek. Any help? danny From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 10:24:46 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 1A77416A4E1; Wed, 30 Aug 2006 10:24:46 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A70643D4C; Wed, 30 Aug 2006 10:24:44 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GINFL-000Nc8-K1; Wed, 30 Aug 2006 19:24:36 +0900 Message-ID: <44F56763.9040409@micom.mng.net> Date: Wed, 30 Aug 2006 19:24:35 +0900 From: Ganbold User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Gleb Smirnoff References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> <20060830075012.GP76666@cell.sick.ru> <44F54B9F.8010508@micom.mng.net> <20060830085331.GT76666@cell.sick.ru> In-Reply-To: <20060830085331.GT76666@cell.sick.ru> Content-Type: multipart/mixed; boundary="------------010704030302090107030908" Cc: Pyun YongHyeon , freebsd-stable@FreeBSD.org, oleg@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 10:24:46 -0000 This is a multi-part message in MIME format. --------------010704030302090107030908 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Gleb Smirnoff wrote: > On Wed, Aug 30, 2006 at 05:26:07PM +0900, Ganbold wrote: > G> Gleb, Pyun, > G> > G> I'm a kind of bit confused here whose patch to choose. > G> Can you guys enlighten me in this regard? > > Can you please merge them? You should take all the stuff that > prepares the dma_rw_ctl variable from my patch, and all the other > stuff from Pyun's patch. > > Ok, here it is. Let me know if I did something wrong. It also includes delphij@'s patch. Pyun's brgphy(4) patch is included too. Ganbold --------------010704030302090107030908 Content-Type: text/x-patch; name="if_bge_combined.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_bge_combined.patch" --- if_bge.c Thu Aug 10 20:02:14 2006 +++ /home/tsgan/bge/new/if_bge.c Wed Aug 30 18:41:39 2006 @@ -1005,36 +1005,48 @@ BGE_MEMWIN_WRITE(sc, i, 0); /* Set up the PCI DMA control register. */ + dma_rw_ctl = BGE_PCIDMARWCTL_READ_CMD | BGE_PCIDMARWCTL_WRITE_CMD; + + /* Bits 23, 22. */ + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || + sc->bge_asicrev == BGE_ASICREV_BCM5701 || + sc->bge_asicrev == BGE_ASICREV_BCM5714) + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE | + BGE_PCIDMARWCTL_USE_MRM; + + /* DMA watermarks: bits 21 - 19, 18 - 16. */ if (sc->bge_pcie) { - /* PCI Express bus */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + /* + * DMA read watermark not used on PCI-E. + * DMA write watermark set to 128 bytes. + */ + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); } else if (sc->bge_pcix) { - /* PCI-X bus */ - if (BGE_IS_5714_FAMILY(sc)) { - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD; - dma_rw_ctl &= ~BGE_PCIDMARWCTL_ONEDMA_ATONCE; /* XXX */ - /* XXX magic values, Broadcom-supplied Linux driver */ - if (sc->bge_asicrev == BGE_ASICREV_BCM5780) - dma_rw_ctl |= (1 << 20) | (1 << 18) | - BGE_PCIDMARWCTL_ONEDMA_ATONCE; - else - dma_rw_ctl |= (1 << 20) | (1 << 18) | (1 << 15); - - } else if (sc->bge_asicrev == BGE_ASICREV_BCM5704) + switch (sc->bge_asicrev) { + case BGE_ASICREV_BCM5780: + /* XXX: Linux driver magic values. */ + dma_rw_ctl |= (1 << 20) | (1 << 18) | + BGE_PCIDMARWCTL_ONEDMA_ATONCE; + break; + case BGE_ASICREV_BCM5714: + case BGE_ASICREV_BCM5714_A0: + /* XXX: Linux driver magic values. */ + dma_rw_ctl |= (1 << 20) | (1 << 18) | + BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL; + break; + case BGE_ASICREV_BCM5704: /* * The 5704 uses a different encoding of read/write - * watermarks. + * watermarks: 384 bytes for write and 1536 for read. */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); - else - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | - (0x0F); + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + break; + default: + /* All other chips: 384 for write and read. */ + dma_rw_ctl |= (3 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (3 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + } /* * 5703 and 5704 need ONEDMA_AT_ONCE as a workaround @@ -1047,18 +1059,20 @@ tmp = CSR_READ_4(sc, BGE_PCI_CLKCTL) & 0x1f; if (tmp == 0x6 || tmp == 0x7) dma_rw_ctl |= BGE_PCIDMARWCTL_ONEDMA_ATONCE; + + /* Set bit 23 to enable PCIX hw bug fix. */ + dma_rw_ctl |= BGE_PCIDMARWCTL_ASRT_ALL_BE; } } else - /* Conventional PCI bus */ - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | - (0x7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | - (0x7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT) | - (0x0F); - - if (sc->bge_asicrev == BGE_ASICREV_BCM5703 || - sc->bge_asicrev == BGE_ASICREV_BCM5704 || - sc->bge_asicrev == BGE_ASICREV_BCM5705) - dma_rw_ctl &= ~BGE_PCIDMARWCTL_MINDMA; + /* Conventional PCI bus: 1024 bytes for read and write. */ + dma_rw_ctl |= (7 << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | + (7 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); + + /* Set minimum DMA only for 5700 and 5701. */ + if (sc->bge_asicrev == BGE_ASICREV_BCM5700 || + sc->bge_asicrev == BGE_ASICREV_BCM5701) + dma_rw_ctl |= 0xf; + pci_write_config(sc->bge_dev, BGE_PCI_DMA_RW_CTL, dma_rw_ctl, 4); /* @@ -1148,22 +1162,20 @@ CSR_WRITE_4(sc, BGE_BMAN_DMA_DESCPOOL_HIWAT, 10); /* Enable buffer manager */ - if (!(BGE_IS_5705_OR_BEYOND(sc))) { - CSR_WRITE_4(sc, BGE_BMAN_MODE, - BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); + CSR_WRITE_4(sc, BGE_BMAN_MODE, + BGE_BMANMODE_ENABLE|BGE_BMANMODE_LOMBUF_ATTN); - /* Poll for buffer manager start indication */ - for (i = 0; i < BGE_TIMEOUT; i++) { - if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) - break; - DELAY(10); - } + /* Poll for buffer manager start indication */ + for (i = 0; i < BGE_TIMEOUT; i++) { + if (CSR_READ_4(sc, BGE_BMAN_MODE) & BGE_BMANMODE_ENABLE) + break; + DELAY(10); + } - if (i == BGE_TIMEOUT) { - device_printf(sc->bge_dev, - "buffer manager failed to start\n"); - return (ENXIO); - } + if (i == BGE_TIMEOUT) { + device_printf(sc->bge_dev, + "buffer manager failed to start\n"); + return (ENXIO); } /* Enable flow-through queues */ @@ -2309,6 +2321,13 @@ pci_write_config(dev, BGE_PCI_MISC_CTL, BGE_PCIMISCCTL_INDIRECT_ACCESS|BGE_PCIMISCCTL_MASK_PCI_INTR| BGE_HIF_SWAP_OPTIONS|BGE_PCIMISCCTL_PCISTATE_RW, 4); + + /* XXX: Broadcom Linux driver. */ + if (sc->bge_asicrev == BGE_ASICREV_BCM5752 || + sc->bge_asicrev == BGE_ASICREV_BCM5755 || + sc->bge_asicrev == BGE_ASICREV_BCM5787) { + CSR_WRITE_4(sc, BGE_FASTBOOT_PC, 0x0); + } reset = BGE_MISCCFG_RESET_CORE_CLOCKS|(65<<1); --------------010704030302090107030908 Content-Type: text/x-patch; name="if_bgereg_combined.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_bgereg_combined.patch" --- if_bgereg.h Thu Aug 10 20:02:14 2006 +++ /home/tsgan/bge/new/if_bgereg.h Wed Aug 30 18:15:08 2006 @@ -196,6 +196,15 @@ #define BGE_PCI_ISR_MBX_HI 0xB0 #define BGE_PCI_ISR_MBX_LO 0xB4 +/* XXX: + * Used in PCI-Express code for 575x chips. + * Should be replaced with checking for a PCI config-space + * capability for PCI-Express, and PCI-Express standard + * offsets into that capability block. + */ +#define BGE_PCI_CONF_DEV_CTRL 0xD8 +#define BGE_PCI_CONF_DEV_STUS 0xDA + /* PCI Misc. Host control register */ #define BGE_PCIMISCCTL_CLEAR_INTA 0x00000001 #define BGE_PCIMISCCTL_MASK_PCI_INTR 0x00000002 @@ -290,20 +299,29 @@ #define BGE_CHIPREV_5701_AX 0x00 /* PCI DMA Read/Write Control register */ +#define BGE_PCIDMARWCTL_WRITE_CMD 0x70000000 +#define BGE_PCIDMARWCTL_READ_CMD 0x06000000 + #define BGE_PCIDMARWCTL_MINDMA 0x000000FF #define BGE_PCIDMARWCTL_RDADRR_BNDRY 0x00000700 #define BGE_PCIDMARWCTL_WRADDR_BNDRY 0x00003800 #define BGE_PCIDMARWCTL_ONEDMA_ATONCE 0x00004000 +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_GLOBAL 0x00004000 +#define BGE_PCIDMARWCTL_ONEDMA_ATONCE_LOCAL 0x00008000 #define BGE_PCIDMARWCTL_RD_WAT 0x00070000 -# define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 +#define BGE_PCIDMARWCTL_RD_WAT_SHIFT 16 #define BGE_PCIDMARWCTL_WR_WAT 0x00380000 -# define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 +#define BGE_PCIDMARWCTL_WR_WAT_SHIFT 19 #define BGE_PCIDMARWCTL_USE_MRM 0x00400000 #define BGE_PCIDMARWCTL_ASRT_ALL_BE 0x00800000 #define BGE_PCIDMARWCTL_DFLT_PCI_RD_CMD 0x0F000000 -# define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 +#define BGE_PCIDMA_RWCTL_PCI_RD_CMD_SHIFT 24 #define BGE_PCIDMARWCTL_DFLT_PCI_WR_CMD 0xF0000000 -# define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 +#define BGE_PCIDMA_RWCTL_PCI_WR_CMD_SHIFT 28 + +/* PCI DMA Read/Write Control register, alternate usage for PCI-Express */ +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128 0x00180000 +#define BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256 0x00380000 #define BGE_PCI_READ_BNDRY_DISABLE 0x00000000 #define BGE_PCI_READ_BNDRY_16BYTES 0x00000100 @@ -1656,6 +1674,7 @@ #define BGE_EE_CTL 0x6840 #define BGE_MDI_CTL 0x6844 #define BGE_EE_DELAY 0x6848 +#define BGE_FASTBOOT_PC 0x6894 /* Mode control register */ #define BGE_MODECTL_INT_SNDCOAL_ONLY 0x00000001 @@ -2074,9 +2093,6 @@ #define BGE_MEDIA_UNSPEC 0x00000000 #define BGE_MEDIA_COPPER 0x00000010 #define BGE_MEDIA_FIBER 0x00000020 - -#define BGE_PCI_READ_CMD 0x06000000 -#define BGE_PCI_WRITE_CMD 0x70000000 #define BGE_TICKS_PER_SEC 1000000 --------------010704030302090107030908 Content-Type: text/x-patch; name="brgphy.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="brgphy.patch" Index: miidevs =================================================================== RCS file: /home/ncvs/src/sys/dev/mii/miidevs,v retrieving revision 1.30.2.3 diff -u -r1.30.2.3 miidevs --- miidevs 8 Aug 2006 07:51:21 -0000 1.30.2.3 +++ miidevs 30 Aug 2006 02:28:07 -0000 @@ -118,6 +118,7 @@ model xxBROADCOM BCM5400 0x0004 Broadcom 1000baseTX PHY model xxBROADCOM BCM5401 0x0005 BCM5401 10/100/1000baseTX PHY model xxBROADCOM BCM5411 0x0007 BCM5411 10/100/1000baseTX PHY +model xxBROADCOM BCM5752 0x0010 BCM5752 10/100/1000baseTX PHY model xxBROADCOM BCM5701 0x0011 BCM5701 10/100/1000baseTX PHY model xxBROADCOM BCM5703 0x0016 BCM5703 10/100/1000baseTX PHY model xxBROADCOM BCM5704 0x0019 BCM5704 10/100/1000baseTX PHY Index: brgphy.c =================================================================== RCS file: /home/ncvs/src/sys/dev/mii/brgphy.c,v retrieving revision 1.34.2.6 diff -u -r1.34.2.6 brgphy.c --- brgphy.c 8 Aug 2006 04:37:18 -0000 1.34.2.6 +++ brgphy.c 30 Aug 2006 02:28:07 -0000 @@ -126,6 +126,12 @@ } if (MII_OUI(ma->mii_id1, ma->mii_id2) == MII_OUI_xxBROADCOM && + MII_MODEL(ma->mii_id2) == MII_MODEL_xxBROADCOM_BCM5752) { + device_set_desc(dev, MII_STR_xxBROADCOM_BCM5752); + return(BUS_PROBE_DEFAULT); + } + + if (MII_OUI(ma->mii_id1, ma->mii_id2) == MII_OUI_xxBROADCOM && MII_MODEL(ma->mii_id2) == MII_MODEL_xxBROADCOM_BCM5701) { device_set_desc(dev, MII_STR_xxBROADCOM_BCM5701); return(BUS_PROBE_DEFAULT); @@ -665,6 +671,7 @@ bcm5704_load_dspcode(sc); break; case MII_MODEL_xxBROADCOM_BCM5750: + case MII_MODEL_xxBROADCOM_BCM5752: case MII_MODEL_xxBROADCOM_BCM5714: case MII_MODEL_xxBROADCOM_BCM5780: case MII_MODEL_xxBROADCOM_BCM5706C: --------------010704030302090107030908-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 10:53:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 01B6E16A4DD for ; Wed, 30 Aug 2006 10:53:27 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6051743D45 for ; Wed, 30 Aug 2006 10:53:26 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so162820wxd for ; Wed, 30 Aug 2006 03:53:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tnpFYhfyNuERPg0wv73yW9lWl/tdfCYnqab6yzeVUj50Rl2EnFDaoWeQTlKJPmp4Yt3rt9yxCXT8SReEoflo0ZmwyuABliU5mK67mTVEZSxgicP9Fhj81NF1v5AgCK+FRxXM+zfA9XNvrojBL4yZRuOGUku5yWzhKv+hag9Jnmo= Received: by 10.70.19.16 with SMTP id 16mr433275wxs; Wed, 30 Aug 2006 03:51:53 -0700 (PDT) Received: by 10.70.38.5 with HTTP; Wed, 30 Aug 2006 03:51:52 -0700 (PDT) Message-ID: Date: Wed, 30 Aug 2006 12:51:52 +0200 From: "Claus Guttesen" To: "Danny Braniss" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: tcp/udp performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 10:53:27 -0000 > test 1: writing to a NetApp filer via NFS/UDP > FreeBSD Linux > MegaBytes/sec > 1- Average: 18.48 32.61 > 2- Average: 15.69 35.72 > 3- Average: 16.61 29.69 > (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of > around 60% on FreeBSD but none on Linux) I've always used tcp when doing nfs between my (former) FreeBSD 5.3 fileserver and my FreeBSD 6.x webservers. I increased the read- and write-packetsize to 32768 and achieved the best performance using this packetsize and tcp. Using udp sometimes gave me the "server not responding", but never appeared using tcp. So stick to tcp. regards Claus From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 10:58:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 BE87F16A4DE for ; Wed, 30 Aug 2006 10:58:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 409FB43D7E for ; Wed, 30 Aug 2006 10:57:49 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so225120pye for ; Wed, 30 Aug 2006 03:57:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=KD+UT4btwfqlg41CADjiJI5qad0oYL2x7cnIEBGsgRyBTkN7fFqd2FIP1vSpnNFNXf5hPcy7HZNjKpyj9GwAikrfGQGgdoM/sOfcLC195IbwJvJ3w0bDWjHWhJzgoUY/6JDTGKeIJM4Ct1dVNyOqINYJGqfQe3/bFpEetS6/yOs= Received: by 10.35.102.1 with SMTP id e1mr754366pym; Wed, 30 Aug 2006 03:57:48 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 17sm211184nzo.2006.08.30.03.57.46; Wed, 30 Aug 2006 03:57:48 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k7UAxDEU049872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 19:59:13 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k7UAxCKZ049871; Wed, 30 Aug 2006 19:59:12 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 30 Aug 2006 19:59:12 +0900 From: Pyun YongHyeon To: Gleb Smirnoff Message-ID: <20060830105912.GC47208@cdnetworks.co.kr> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830075333.GQ76666@cell.sick.ru> <44F54ABF.30109@micom.mng.net> <20060830085249.GS76666@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060830085249.GS76666@cell.sick.ru> User-Agent: Mutt/1.4.2.1i Cc: oleg@FreeBSD.org, Ganbold , freebsd-stable@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 10:58:01 -0000 On Wed, Aug 30, 2006 at 12:52:49PM +0400, Gleb Smirnoff wrote: > On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote: > G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: > G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still see > G> >G> bge0: firmware handshake timed out > G> >G> bge0: link state changed to DOWN > G> >G> messages. > G> > > G> >And yesterday delphij@ have sent me patch against "firmware handshake > G> >timed out". > G> >It is attached. Can you please test it? > G> > > G> > G> Applied delphij@'s patch and now "bge0: firmware handshake timed out" > G> message is gone. Previously there was applied Pyun's brgphy(4) patch. > > Good. We probably need to commit them both soon. > If there is no objections, I'll commit brgphy(4) patch tomorrow. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 10:59:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 8C74216A4E1 for ; Wed, 30 Aug 2006 10:59:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FE1043D55 for ; Wed, 30 Aug 2006 10:59:26 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so225657pye for ; Wed, 30 Aug 2006 03:59:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=ZKVC2byzUyvqhzGX01y+8ovDMRr2KXKbWQUSL6Pst5mz2KoMcC1MqH4NZFM3u4b8sZ+HvsFn4JL54FRmfxZuhB7PFCD7g7+foucuBdvzC02crH31U6RYw6yM61Umi23cOUD5rHprifcPc+lxqVFBQ5ud8IVlP3RXXBXgRLGi2lg= Received: by 10.35.101.9 with SMTP id d9mr764517pym; Wed, 30 Aug 2006 03:59:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id i5sm82643nzi.2006.08.30.03.59.23; Wed, 30 Aug 2006 03:59:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k7UB0tC4049903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 20:00:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k7UB0tBJ049902; Wed, 30 Aug 2006 20:00:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 30 Aug 2006 20:00:55 +0900 From: Pyun YongHyeon To: Gleb Smirnoff Message-ID: <20060830110054.GD47208@cdnetworks.co.kr> References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830073025.GB47208@cdnetworks.co.kr> <20060830075012.GP76666@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060830075012.GP76666@cell.sick.ru> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.org, Ganbold , oleg@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 10:59:28 -0000 On Wed, Aug 30, 2006 at 11:50:12AM +0400, Gleb Smirnoff wrote: > Pyun, > > On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote: > P> =================================================================== > P> RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v > P> retrieving revision 1.91.2.16 > P> diff -u -r1.91.2.16 if_bge.c > P> --- if_bge.c 10 Aug 2006 11:02:14 -0000 1.91.2.16 > P> +++ if_bge.c 30 Aug 2006 07:20:43 -0000 > P> @@ -1007,9 +1007,26 @@ > P> /* Set up the PCI DMA control register. */ > P> if (sc->bge_pcie) { > P> /* PCI Express bus */ > P> - dma_rw_ctl = BGE_PCI_READ_CMD|BGE_PCI_WRITE_CMD | > P> - (0xf << BGE_PCIDMARWCTL_RD_WAT_SHIFT) | > P> - (0x2 << BGE_PCIDMARWCTL_WR_WAT_SHIFT); > P> + uint32_t device_ctl; > P> + > P> + /* alternative from Linux driver */ > P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_128 0x00180000 > P> +#define DMA_CTRL_WRITE_PCIE_H20MARK_256 0x00380000 > P> + > P> + dma_rw_ctl = 0x76000000; /* XXX XXX XXX */; > P> + device_ctl = pci_read_config(sc->bge_dev, > P> + BGE_PCI_CONF_DEV_CTRL, 4); > P> + if ((device_ctl & 0x00e0) && 0) { > P> + /* > P> + * This clause is exactly what the Broadcom-supplied > P> + * Linux does; but given overall register programming > P> + * by bge(4), this larger DMA-write watermark > P> + * value causes BCM5721 chips to totally wedge. > P> + */ > P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_256; > P> + } else { > P> + dma_rw_ctl |= BGE_PCIDMA_RWCTL_PCIE_WRITE_WATRMARK_128; > P> + } > P> } else if (sc->bge_pcix) { > > My small penny into the discussion. I was working on reviewing the > difference in initializing the PCI DMA control register in Linux tg3.c > and in bge(4). > > I was quite lost in this stuff, and so I asked for help from David > Christensen (davidch@). He has explained me all the differencies > in this register between chips and I have prepared the attached patch. > > Since I have very small collection of bge(4) cards, I avoid to commit > it. May be I will commit it after 6.2-RELEASE if several people test it > on their cards and all is OK. And it will live unmerged in HEAD until > 6.3-RELEASE. > Ok, I don't have BCM5752 documentation for the details. Since you've got all the secret of the magic I'd like to see the fix from you. :-) -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 14:11:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 1FB1C16A4E1 for ; Wed, 30 Aug 2006 14:11:11 +0000 (UTC) (envelope-from fehwalker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7902B43D49 for ; Wed, 30 Aug 2006 14:11:10 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by nf-out-0910.google.com with SMTP id n15so147867nfc for ; Wed, 30 Aug 2006 07:11:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=B/GGGI7hDKB/LS4WjsNQ11k2WkGHEqsHIhO3F6ZCFEaJHGIY8ELRNROIW4n78N5nfK3VP7ZYCt75Wqkl1j5Dt7YvEaqrWyQkSk/DaFOqfXWMumswA9mbMl0MuTtvWq2KNHjn2j7YzIIOy3XM4tZUYRxItYTZIqeg1U0/KMzGWuo= Received: by 10.67.105.19 with SMTP id h19mr393635ugm; Wed, 30 Aug 2006 07:11:05 -0700 (PDT) Received: by 10.66.236.7 with HTTP; Wed, 30 Aug 2006 07:11:04 -0700 (PDT) Message-ID: <35de0c300608300711j36fac4e9g31a5ba8abed849c0@mail.gmail.com> Date: Wed, 30 Aug 2006 10:11:04 -0400 From: "Bryan Fullerton" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 6.2 ETA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 14:11:11 -0000 So... the releng web page indicates that RELENG_6 is frozen as of August 25th pending a 6.2R release on October 9th. I'm guessing, since there seem to still be lots of commits and there's no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are no longer accurate. What is a valid ETA for starting the 6.2R releng process? Thanks, Bryan From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 14:37:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5905F16A4DD for ; Wed, 30 Aug 2006 14:37:07 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd3mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C26243DA3 for ; Wed, 30 Aug 2006 14:36:56 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J4T008YTF9JH610@l-daemon> for freebsd-stable@freebsd.org; Wed, 30 Aug 2006 08:36:55 -0600 (MDT) Received: from pn2ml1so.prod.shaw.ca ([10.0.121.145]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J4T00BC8F9J3NF0@pd3mr2so.prod.shaw.ca> for freebsd-stable@freebsd.org; Wed, 30 Aug 2006 08:36:55 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0J4T00IZDF9JW500@l-daemon> for freebsd-stable@freebsd.org; Wed, 30 Aug 2006 08:36:55 -0600 (MDT) Received: (qmail 30573 invoked from network); Wed, 30 Aug 2006 14:36:51 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Wed, 30 Aug 2006 14:36:51 +0000 Date: Wed, 30 Aug 2006 07:36:51 -0700 From: Colin Percival In-reply-to: <35de0c300608300711j36fac4e9g31a5ba8abed849c0@mail.gmail.com> To: Bryan Fullerton Message-id: <44F5A283.40600@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 References: <35de0c300608300711j36fac4e9g31a5ba8abed849c0@mail.gmail.com> User-Agent: Thunderbird 1.5 (X11/20060416) Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 ETA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 14:37:07 -0000 Bryan Fullerton wrote: > So... the releng web page indicates that RELENG_6 is frozen as of > August 25th pending a 6.2R release on October 9th. > > I'm guessing, since there seem to still be lots of commits and there's > no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are > no longer accurate. > > What is a valid ETA for starting the 6.2R releng process? I'm not part of the release engineering team, but I'm not aware of anything which they're waiting for before starting the freeze. I'd be surprised if RELENG_6 isn't frozen by this time next week. Colin Percival From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 18:42:03 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 DF8A716A4DA for ; Wed, 30 Aug 2006 18:42:03 +0000 (UTC) (envelope-from mohan_srinivasan@yahoo.com) Received: from web30807.mail.mud.yahoo.com (web30807.mail.mud.yahoo.com [68.142.200.150]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D61F43D6B for ; Wed, 30 Aug 2006 18:42:03 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: (qmail 4495 invoked by uid 60001); 30 Aug 2006 18:42:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4PLOylMSP1sbrQ7NwQqJJww5NNJhT67cUPMHt0UJ4teHvBPT97y1yPUJIJWfcYfC3uV77SxJM02AN/i/EZPwufIgWMmo5fgIW1m6/peFhIJ4PR+lmmpoK70NuMrc1BlnazMdHUQSjUk4kxg7DjQsqIT2j4xV/Xe6ZZMSZneIMu0= ; Message-ID: <20060830184202.4488.qmail@web30807.mail.mud.yahoo.com> Received: from [71.139.4.73] by web30807.mail.mud.yahoo.com via HTTP; Wed, 30 Aug 2006 11:42:02 PDT Date: Wed, 30 Aug 2006 11:42:02 -0700 (PDT) From: Mohan Srinivasan To: Danny Braniss , freebsd-stable@FreeBSD.org, freebsd-net@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: tcp/udp performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 18:42:04 -0000 Hi, 1) Have you made sure there are no NFS rexmits reported by nfsstat -c ? 2) I haven't run thruput tests lately, but when I tested NFS/UDP thruput a few months ago, I routinely got over 70MB/s sequential read thruput and over 80MB/s sequential write thruput (against filers). I used 32KB blocksizes. -current improves upon this significantly, by about 25%-30%. Send me private e-mail and we can discuss NFS client tunings. mohan --- Danny Braniss wrote: > > ever since 6.1 I've seen fluctuations in the performance of > the em (Intel(R) PRO/1000 Gigabit Ethernet). > > motherboard OBN (On Board NIC) > ---------------- ------------------ > 1- Intel SE7501WV2S Intel 82546EB::2.1 > 2- Intel SE7320VP2D2 INTEL 82541 > 3- Sun Fire X4100 Server Intel(R) PRO/1000 > > test 1: writing to a NetApp filer via NFS/UDP > FreeBSD Linux > MegaBytes/sec > 1- Average: 18.48 32.61 > 2- Average: 15.69 35.72 > 3- Average: 16.61 29.69 > (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of > around 60% on FreeBSD but none on Linux) > > test2: iperf using 1 as server: > FreeBSD(*) Linux > Mbits/sec > 1- 926 905 (this machine was busy) > 2- 545 798 > 3- 910 912 > *: did a 'sysctl net.inet.tcp.sendspace=65536' > > > So, it seems to me something is not that good in the UDP department, but > I can't find what to tweek. > > Any help? > > danny > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 18:45:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 D0B2116A4E2 for ; Wed, 30 Aug 2006 18:45:03 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E2AE43D79 for ; Wed, 30 Aug 2006 18:45:02 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so379764pye for ; Wed, 30 Aug 2006 11:45:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qRVaPVzZTX8V15P9R1IKf4PWxyCtEJ4kreBX2xoJzxwUAxo/gF7ow8v83upwWuB/vFTauuElJzN9gsYtzYXtkK8yuimjg4/sZUfjkkDAk41B4Dh90A1DTRwiR2dDl7ozlrbdV4S6MO0XtUfoHSPOKnukazzyKRKogKwFHapmapo= Received: by 10.35.72.6 with SMTP id z6mr1575491pyk; Wed, 30 Aug 2006 11:45:01 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Wed, 30 Aug 2006 11:45:01 -0700 (PDT) Message-ID: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> Date: Wed, 30 Aug 2006 11:45:01 -0700 From: "Jack Vogel" To: "Danny Braniss" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: tcp/udp performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 18:45:03 -0000 On 8/30/06, Danny Braniss wrote: > > ever since 6.1 I've seen fluctuations in the performance of > the em (Intel(R) PRO/1000 Gigabit Ethernet). > > motherboard OBN (On Board NIC) > ---------------- ------------------ > 1- Intel SE7501WV2S Intel 82546EB::2.1 > 2- Intel SE7320VP2D2 INTEL 82541 > 3- Sun Fire X4100 Server Intel(R) PRO/1000 > > test 1: writing to a NetApp filer via NFS/UDP > FreeBSD Linux > MegaBytes/sec > 1- Average: 18.48 32.61 > 2- Average: 15.69 35.72 > 3- Average: 16.61 29.69 > (interstingly, doing NFS/TCP instead of NFS/UDP shows an increase in speed of > around 60% on FreeBSD but none on Linux) > > test2: iperf using 1 as server: > FreeBSD(*) Linux > Mbits/sec > 1- 926 905 (this machine was busy) > 2- 545 798 > 3- 910 912 > *: did a 'sysctl net.inet.tcp.sendspace=65536' > > > So, it seems to me something is not that good in the UDP department, but > I can't find what to tweek. > > Any help? > > danny Have discussed this some internally, the best idea I've heard is that UDP is not giving us the interrupt rate that TCP would, so we end up not cleaning up as often, and thus descriptors might not be as quickly available.. Its just speculation at this point. Try this: the default is only to have 256 descriptors, try going for the MAX which is 4K. Cheers, Jack From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 19:46:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0710416A4DF for ; Wed, 30 Aug 2006 19:46:24 +0000 (UTC) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-125.synserver.de (smtp-out-44.synserver.de [217.119.50.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 4A54643D58 for ; Wed, 30 Aug 2006 19:46:20 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 9095 invoked by uid 0); 30 Aug 2006 19:46:16 -0000 X-SynServer-RemoteDnsName: port-212-202-34-169.dynamic.qsc.de X-SynServer-AuthUser: markus@trippelsdorf.de Received: from port-212-202-34-169.dynamic.qsc.de (HELO bsd.trippelsdorf.de) (212.202.34.169) by mx-10.synserver.de with SMTP; 30 Aug 2006 19:46:16 -0000 Date: Wed, 30 Aug 2006 21:46:10 +0200 From: Markus Trippelsdorf To: freebsd-stable@freebsd.org Message-ID: <20060830194610.GA656@bsd.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: kernel trap 12 with interrupts disabled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 19:46:24 -0000 Just got this panic on my amd64 smp system running stable: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x20 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff80286611 stack pointer = 0x10:0xffffffffb1921b70 frame pointer = 0x10:0x4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 14 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 (kgdb) list *0xffffffff80286611 0xffffffff80286611 is in softclock (/usr/src/sys/kern/kern_timeout.c:220). 215 curticks = softticks; 216 bucket = &callwheel[curticks & callwheelmask]; 217 c = TAILQ_FIRST(bucket); 218 while (c) { 219 depth++; 220 if (c->c_time != curticks) { 221 c = TAILQ_NEXT(c, c_links.tqe); 222 ++steps; 223 if (steps >= MAX_SOFTCLOCK_STEPS) { 224 nextsoftcheck = c; (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0x0000000000000037 in ?? () #2 0xffffffff80276e97 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #3 0xffffffff80277611 in panic (fmt=0xffffff007ba5ebe0 "\200\026\221{") at /usr/src/sys/kern/kern_shutdown.c:565 #4 0xffffffff80390e5f in trap_fatal (frame=0xffffff007ba5ebe0, eva=18446742976271029888) at /usr/src/sys/amd64/amd64/trap.c:660 #5 0xffffffff80391386 in trap (frame= {tf_rdi = -2141705632, tf_rsi = 10548215, tf_rdx = 16, tf_rcx = -1619509088, tf_r8 = -1097437156384, tf_r9 = -1619509256, tf_rax = 1, tf_rbx = 1, tf_rbp = 4, tf_r10 = 30689, tf_r11 = -1097437156384, tf_r12 = 16, tf_r13 = 4, tf_r14 = 0, tf_r15 = -2144279856, tf_trapno = 12, tf_addr = 32, tf_flags = 0, tf_err = 0, tf_rip = -2144836079, tf_cs = 8, tf_rflags = 65542, tf_rsp = -1315824768, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:238 #6 0xffffffff8037cd6b in calltrap () at /usr/src/sys/amd64/amd64/exception.S:168 #7 0xffffffff80286611 in softclock (dummy=0xffffffff80582a60) at /usr/src/sys/kern/kern_timeout.c:220 #8 0xffffffff8025d959 in ithread_loop (arg=0xffffff0000048680) at /usr/src/sys/kern/kern_intr.c:682 #9 0xffffffff8025c0f7 in fork_exit (callout=0xffffffff8025d810 , arg=0xffffff0000048680, frame=0xffffffffb1921c50) at /usr/src/sys/kern/kern_fork.c:805 #10 0xffffffff8037d0ce in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:394 #11 0x0000000000000000 in ?? () Any hints? -- Markus From owner-freebsd-stable@FreeBSD.ORG Wed Aug 30 21:07:09 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 BDE3016A4E0; Wed, 30 Aug 2006 21:07:09 +0000 (UTC) (envelope-from outi@bytephobia.de) Received: from dd2626.kasserver.com (dd2626.kasserver.com [81.209.184.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2779343D7B; Wed, 30 Aug 2006 21:07:04 +0000 (GMT) (envelope-from outi@bytephobia.de) Received: from [10.1.0.2] (pD9E35D46.dip.t-dialin.net [217.227.93.70]) by dd2626.kasserver.com (Postfix) with ESMTP id 622C91038DE; Wed, 30 Aug 2006 23:07:10 +0200 (CEST) Message-ID: <44F5FDF3.8080502@bytephobia.de> Date: Wed, 30 Aug 2006 23:06:59 +0200 From: Patrick Hurrelmann User-Agent: Thunderbird 1.5.0.5 (X11/20060730) MIME-Version: 1.0 To: pyunyh@gmail.com References: <44F4F1DE.2030907@micom.mng.net> <20060830023537.GA47208@cdnetworks.co.kr> <44F504A8.8070503@micom.mng.net> <20060830075333.GQ76666@cell.sick.ru> <44F54ABF.30109@micom.mng.net> <20060830085249.GS76666@cell.sick.ru> <20060830105912.GC47208@cdnetworks.co.kr> In-Reply-To: <20060830105912.GC47208@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Ganbold , Gleb Smirnoff , oleg@FreeBSD.org Subject: Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 21:07:09 -0000 Pyun YongHyeon wrote: > On Wed, Aug 30, 2006 at 12:52:49PM +0400, Gleb Smirnoff wrote: > > On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote: > > G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote: > > G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still see > > G> >G> bge0: firmware handshake timed out > > G> >G> bge0: link state changed to DOWN > > G> >G> messages. > > G> > > > G> >And yesterday delphij@ have sent me patch against "firmware handshake > > G> >timed out". > > G> >It is attached. Can you please test it? > > G> > > > G> > > G> Applied delphij@'s patch and now "bge0: firmware handshake timed out" > > G> message is gone. Previously there was applied Pyun's brgphy(4) patch. > > > > Good. We probably need to commit them both soon. > > > > If there is no objections, I'll commit brgphy(4) patch tomorrow. > I can also confirm, that the mentioned panic goes away when the 5752 does not attach to ukphy but brgphy. I had a local patch for this some time now (See current@). I'm happy to test the fix for "firmware handshake timeout" tommorrow. This is on Dell Latitude D620 and a Broadcom 5752 A2. -- ==================================================================== Patrick Hurrelmann | "Programming today is a race between software Mannheim, Germany | engineers striving to build bigger and better | idiot-proof programs, and the Universe trying outi@bytephobia.de | to produce bigger and better idiots. So far, www.bytephobia.de | the Universe is winning." - Rich Cook /"\ \ / ASCII Ribbon Campaign X against HTML email & vCards / \ From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 01:59:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3040516A4DF; Thu, 31 Aug 2006 01:59:52 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B42743D4C; Thu, 31 Aug 2006 01:59:51 +0000 (GMT) (envelope-from ota@j.email.ne.jp) Received: from dynabook.advok.com (pool-151-197-92-28.phil.east.verizon.net [151.197.92.28]) by mail.asahi-net.or.jp (Postfix) with ESMTP id 3CEAAE8EA; Thu, 31 Aug 2006 10:59:48 +0900 (JST) Date: Wed, 30 Aug 2006 21:59:43 -0500 From: Yoshihiro Ota To: Colin Percival Message-Id: <20060830215943.253c1cd5.ota@j.email.ne.jp> In-Reply-To: <44F5A283.40600@freebsd.org> References: <35de0c300608300711j36fac4e9g31a5ba8abed849c0@mail.gmail.com> <44F5A283.40600@freebsd.org> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Bryan Fullerton , freebsd-stable@freebsd.org Subject: Re: 6.2 ETA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 01:59:52 -0000 It may be a bit early but I switched to RELENG_6 fot that reason. After I switched, it seems the number of interrupts increased a lot. When I do 'dump -0 -f - -L /somewhere | restore -r -f', I see hight interrupt rates which I don't remember seeing in 6.1-RELEASE. Is it too early to report incidents? Hiro On Wed, 30 Aug 2006 07:36:51 -0700 Colin Percival wrote: > Bryan Fullerton wrote: > > So... the releng web page indicates that RELENG_6 is frozen as of > > August 25th pending a 6.2R release on October 9th. > > > > I'm guessing, since there seem to still be lots of commits and there's > > no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are > > no longer accurate. > > > > What is a valid ETA for starting the 6.2R releng process? > > I'm not part of the release engineering team, but I'm not aware of anything > which they're waiting for before starting the freeze. I'd be surprised if > RELENG_6 isn't frozen by this time next week. From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 06:12:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 62B2816A4DA for ; Thu, 31 Aug 2006 06:12:45 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service2.sh.cvut.cz (service2.sh.cvut.cz [147.32.127.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61F5843D58 for ; Thu, 31 Aug 2006 06:12:41 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service2.sh.cvut.cz (Postfix) with ESMTP id C2D25137C1F; Thu, 31 Aug 2006 08:12:31 +0200 (CEST) Received: from service2.sh.cvut.cz ([127.0.0.1]) by localhost (service2.sh.cvut.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02426-03; Thu, 31 Aug 2006 08:12:28 +0200 (CEST) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) by service2.sh.cvut.cz (Postfix) with ESMTP id EB5ED137C1D; Thu, 31 Aug 2006 08:12:27 +0200 (CEST) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id 913C161C2E; Thu, 31 Aug 2006 08:12:27 +0200 (CEST) Message-ID: <44F67DC2.1060900@sh.cvut.cz> Date: Thu, 31 Aug 2006 08:12:18 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF2C3365CDD349087EE844C8A" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at service2.sh.cvut.cz X-Spam-Status: No, hits=-2.6 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, AWL, TW_XB X-Spam-Level: Subject: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 06:12:45 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF2C3365CDD349087EE844C8A Content-Type: multipart/mixed; boundary="------------040405070907010802080309" This is a multi-part message in MIME format. --------------040405070907010802080309 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I found this in logs of 6.1 box that I admin this morning. The machine keeps running after that. -- wilx --------------040405070907010802080309 Content-Type: text/plain; name="log.txt" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="log.txt" K21hbGxvYyhNX1dBSVRPSykgb2YgImdfYmlvIiwgZm9yY2luZyBNX05PV0FJVCB3aXRoIHRo ZSBmb2xsb3dpbmcgbm9uLXNsZWVwYWJsZSBsb2NrcyBoZWxkOg0KK2V4Y2x1c2l2ZSBzbGVl cCBtdXRleCBpbnAgKHRjcGlucCkgciA9IDAgKDB4YzUwYzVkMzgpIGxvY2tlZCBAIC91c3Iv c3JjL3N5cy9uZXRpbmV0L3RjcF91c3JyZXEuYzoxMDI5DQorS0RCOiBzdGFjayBiYWNrdHJh Y2U6DQora2RiX2JhY2t0cmFjZShjMDhlZWY4NCxlNzhiZTg5YywxLGM0NTc1MmMwLGMxMDM1 MzgwKSBhdCBrZGJfYmFja3RyYWNlKzB4MmYNCit3aXRuZXNzX3dhcm4oNSwwLGMwODE5Y2Uw LGMwN2ZjOTA1LGMwNWVhY2ExKSBhdCB3aXRuZXNzX3dhcm4rMHgxYWMNCit1bWFfemFsbG9j X2FyZyhjMTAzNTM4MCwwLDEwMixlNzhiZThlNCxjMDc1NjJhMSkgYXQgdW1hX3phbGxvY19h cmcrMHgzZA0KK2dfYWxsb2NfYmlvKDgsYzA4MTk3NzcsYzQ1NzU0MDAsYzQ1NzUyYzAsZDM2 N2FhYzgpIGF0IGdfYWxsb2NfYmlvKzB4MjMNCitzd2FwZ2VvbV9zdHJhdGVneShkMzY3YWFj OCxjNDU3NTJjMCxjMDgxOTc3NywyNzEpIGF0IHN3YXBnZW9tX3N0cmF0ZWd5KzB4M2ENCitz d3BfcGFnZXJfc3RyYXRlZ3koZDM2N2FhYzgsMCxjMDgxOTc3Nyw0MzcsYzA3NjBlZTcpIGF0 IHN3cF9wYWdlcl9zdHJhdGVneSsweDg4DQorc3dhcF9wYWdlcl9nZXRwYWdlcyhjNzI4ZTk0 OCxlNzhiZTllYywxLDAsZTc4YmU5YjApIGF0IHN3YXBfcGFnZXJfZ2V0cGFnZXMrMHgzODIN Cit2bV9mYXVsdChjNGY5YjEyOCw4MDZiMDAwLDEsMCxjNGMwYjMwMCkgYXQgdm1fZmF1bHQr MHhiMTMNCit0cmFwX3BmYXVsdChlNzhiZWFhOCwwLDgwNmIyYzAsYzA4YTljNjAsODA2YjJj MCkgYXQgdHJhcF9wZmF1bHQrMHhmNA0KK3RyYXAoYzA4MDAwMDgsMjgsYzRjMDAwMjgsZTc4 YmViMjgsODA2YjJjMCkgYXQgdHJhcCsweDMzZQ0KK2NhbGx0cmFwKCkgYXQgY2FsbHRyYXAr MHg1DQorLS0tIHRyYXAgMHhjLCBlaXAgPSAweGMwN2I5YjE2LCBlc3AgPSAweGU3OGJlYWU4 LCBlYnAgPSAweGU3OGJlYjA4IC0tLQ0KK2dlbmVyaWNfY29weWluKGU3OGJlYzg0LGU3OGJl YjI4LDQsNCxjNTBjNWNhOCkgYXQgZ2VuZXJpY19jb3B5aW4rMHgzMg0KK3RjcF9jdGxvdXRw dXQoYzRkMWRjODQsZTc4YmVjODQsMCxjNTg5YjQwMCxlNzhiZWM2OCkgYXQgdGNwX2N0bG91 dHB1dCsweDE4Mg0KK3Nvc2V0b3B0KGM0ZDFkYzg0LGU3OGJlYzg0LGU3OGJlYzgwLGMwOGVl ZjgwLGM0YmQxNWEwKSBhdCBzb3NldG9wdCsweDM4DQora2Vybl9zZXRzb2Nrb3B0KGM0YzBi MzAwLDcsNiwxLDgwNmIyYzApIGF0IGtlcm5fc2V0c29ja29wdCsweGQ2DQorc2V0c29ja29w dChjNGMwYjMwMCxlNzhiZWQwNCwxNCwyODI3OTAwMCw1KSBhdCBzZXRzb2Nrb3B0KzB4M2UN CitzeXNjYWxsKDNiLDI4MDgwMDNiLGJmYmYwMDNiLDEsODA2YjJjMCkgYXQgc3lzY2FsbCsw eDI5NQ0KK1hpbnQweDgwX3N5c2NhbGwoKSBhdCBYaW50MHg4MF9zeXNjYWxsKzB4MWYNCist LS0gc3lzY2FsbCAoMTA1LCBGcmVlQlNEIEVMRjMyLCBzZXRzb2Nrb3B0KSwgZWlwID0gMHgy ODI3OTU5YiwgZXNwID0gMHhiZjlmZWEzYywgZWJwID0gMHhiZjlmZWE2OCAtLS0NCitTbGVl cGluZyBvbiAic3dyZWFkIiB3aXRoIHRoZSBmb2xsb3dpbmcgbm9uLXNsZWVwYWJsZSBsb2Nr cyBoZWxkOg0KK2V4Y2x1c2l2ZSBzbGVlcCBtdXRleCBpbnAgKHRjcGlucCkgciA9IDAgKDB4 YzUwYzVkMzgpIGxvY2tlZCBAIC91c3Ivc3JjL3N5cy9uZXRpbmV0L3RjcF91c3JyZXEuYzox MDI5DQorS0RCOiBzdGFjayBiYWNrdHJhY2U6DQora2RiX2JhY2t0cmFjZShjMDhlZWY4NCxl NzhiZThlMCwxLDEsMCkgYXQga2RiX2JhY2t0cmFjZSsweDJmDQord2l0bmVzc193YXJuKDUs YzA4ZmUyYTAsYzA4MDJlYjEsYzA4MTk4MzMsYzA4ZmUyYTApIGF0IHdpdG5lc3Nfd2Fybisw eDFhYw0KK21zbGVlcChjMWJiNmZlOCxjMDhmZTJhMCw0MCxjMDgxOTgzMyw0ZTIwKSBhdCBt c2xlZXArMHg1OA0KK3N3YXBfcGFnZXJfZ2V0cGFnZXMoYzcyOGU5NDgsZTc4YmU5ZWMsMSww LGU3OGJlOWIwKSBhdCBzd2FwX3BhZ2VyX2dldHBhZ2VzKzB4NDAwDQordm1fZmF1bHQoYzRm OWIxMjgsODA2YjAwMCwxLDAsYzRjMGIzMDApIGF0IHZtX2ZhdWx0KzB4YjEzDQordHJhcF9w ZmF1bHQoZTc4YmVhYTgsMCw4MDZiMmMwLGMwOGE5YzYwLDgwNmIyYzApIGF0IHRyYXBfcGZh dWx0KzB4ZjQNCit0cmFwKGMwODAwMDA4LDI4LGM0YzAwMDI4LGU3OGJlYjI4LDgwNmIyYzAp IGF0IHRyYXArMHgzM2UNCitjYWxsdHJhcCgpIGF0IGNhbGx0cmFwKzB4NQ0KKy0tLSB0cmFw IDB4YywgZWlwID0gMHhjMDdiOWIxNiwgZXNwID0gMHhlNzhiZWFlOCwgZWJwID0gMHhlNzhi ZWIwOCAtLS0NCitnZW5lcmljX2NvcHlpbihlNzhiZWM4NCxlNzhiZWIyOCw0LDQsYzUwYzVj YTgpIGF0IGdlbmVyaWNfY29weWluKzB4MzINCit0Y3BfY3Rsb3V0cHV0KGM0ZDFkYzg0LGU3 OGJlYzg0LDAsYzU4OWI0MDAsZTc4YmVjNjgpIGF0IHRjcF9jdGxvdXRwdXQrMHgxODINCitz b3NldG9wdChjNGQxZGM4NCxlNzhiZWM4NCxlNzhiZWM4MCxjMDhlZWY4MCxjNGJkMTVhMCkg YXQgc29zZXRvcHQrMHgzOA0KK2tlcm5fc2V0c29ja29wdChjNGMwYjMwMCw3LDYsMSw4MDZi MmMwKSBhdCBrZXJuX3NldHNvY2tvcHQrMHhkNg0KK3NldHNvY2tvcHQoYzRjMGIzMDAsZTc4 YmVkMDQsMTQsMjgyNzkwMDAsNSkgYXQgc2V0c29ja29wdCsweDNlDQorc3lzY2FsbCgzYiwy ODA4MDAzYixiZmJmMDAzYiwxLDgwNmIyYzApIGF0IHN5c2NhbGwrMHgyOTUNCitYaW50MHg4 MF9zeXNjYWxsKCkgYXQgWGludDB4ODBfc3lzY2FsbCsweDFmDQorLS0tIHN5c2NhbGwgKDEw NSwgRnJlZUJTRCBFTEYzMiwgc2V0c29ja29wdCksIGVpcCA9IDB4MjgyNzk1OWIsIGVzcCA9 IDB4YmY5ZmVhM2MsIGVicCA9IDB4YmY5ZmVhNjggLS0t --------------040405070907010802080309-- --------------enigF2C3365CDD349087EE844C8A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRPZ9y0NOZDESBK8FAQK+sQf9HdMrFeiQdH+H1IePzPOHVY8ILSzgYhJQ m+YERywd0ANdmC6EPGzEk9F5gdWjTYeZVeJQWxUyXidnsrNPra6/NNGNqNP+Qlks wc9PKGWiEgR1qGoODbtxKD8Q1+wY9qlgXgOx1U+1jpoaB+1cAjo4EwHnKMMPl76A QULhVR1fJF5rQ7Zf02PJCE5dKXPOom4oGdSM+FSm8FaI8x1B1CChVV+OkMIbP1Cl jAHFHrQKMLnp6NFRaY/gp39QDN3b87fMX+o55F7o/XJxSotLfmjHpqWYxYcoIWvj IdurX8P3BzctKH5XRhYQGFecwAY29LC6X7i8ag+BkiM9eh6QdjiVeQ== =D0Ag -----END PGP SIGNATURE----- --------------enigF2C3365CDD349087EE844C8A-- From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 18:08:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 EA7AA16A4DF for ; Thu, 31 Aug 2006 18:08:29 +0000 (UTC) (envelope-from psionic@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 117FC43D68 for ; Thu, 31 Aug 2006 18:08:23 +0000 (GMT) (envelope-from psionic@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so700792wxd for ; Thu, 31 Aug 2006 11:08:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Ql1YPljSWml6UhHQ9n7p+XJ2wpbNb0Sv+TfU6rljGQ8fmizEd64zoYbDu8QarM9hrkJioogS46UeXaWkv+9sV9QK9H7OVrWXms8+Jmu+25fAQqhZbaCjEm43afXP+S1WLeK1hurPZLEb5JLs5gK4sDia10X4moAyOF5fTbw+gjI= Received: by 10.70.87.9 with SMTP id k9mr833073wxb; Thu, 31 Aug 2006 11:06:44 -0700 (PDT) Received: by 10.70.11.20 with HTTP; Thu, 31 Aug 2006 11:06:44 -0700 (PDT) Message-ID: <5ad23a300608311106w2cc75145p1b1228f756f91b03@mail.gmail.com> Date: Thu, 31 Aug 2006 11:06:44 -0700 From: "Jordan Sissel" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Suspend freezes system on my Thinkpad X41 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 18:08:30 -0000 Subject says it all. Attempting FN+F4 (suspend) or acpiconf -s 3 or -s 4 all cause the system to halt. Specs: Thinkpad X41 6.1-RELEASE GENERIC Atheros 5212 Broadcom BCM5751M SATA (ICH6 SATA150) Freezes are non-recoverable. Even hardware functions (such as lcd dimming) cease. Seems like the system has half suspended, but the LCD is still on and displaying. Sleep light doesn't blink indicating sleepiness. Any help on this would be greatly appreciated :) From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 19:01:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9A84816A4DA for ; Thu, 31 Aug 2006 19:01:36 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 329F543D45 for ; Thu, 31 Aug 2006 19:01:35 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k7VJ1YrA034169 for ; Thu, 31 Aug 2006 14:01:34 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <44F7320E.6040608@centtech.com> Date: Thu, 31 Aug 2006 14:01:34 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1782/Thu Aug 31 11:54:15 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 19:01:36 -0000 Pavel, running 6.1-stable with these patches rebuilt kernel/world as of 8/28 @ 2p CST w/ these patches gjournal6_20060808.patch vfs_subr.c.3.patch the backend RAID presents 4 luns, this is how we config'd it. da1 - 8G da2 - ~897G da3 - 8G da4 - ~897G da2/4 have been partitioned in FreeBSD, then we did the following gjournal label -v /dev/da2 /dev/da1 gjournal label -v /dev/da4 /dev/da3 newfs -U -L "scr09" /dev/da2.journal newfs -U -L "scr10" /dev/da4.journal so 1 -8 G journal for each data device. now that the server is under load i'm seeing NFS not responding messages on my clients. the message corresponds to the gjournal suspend/copy operation, causing my clients to hang or give "no such file or directory". we copied 137G to /scr10 and it just finished, could this be some remains of writes from the journal? here is the time correlation Aug 31 13:55:24 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Aug 31 13:55:24 donkey kernel: GEOM_JOURNAL[1]: Switch time of da4: 0.002798s Aug 31 13:55:24 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 14.030198s Aug 31 13:55:24 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. Aug 31 13:55:33 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000013s Aug 31 13:55:44 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000013s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr09: 0.000010s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr09: 0.000009s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr09: 0.000007s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Switch time of da2: 0.002302s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr10: 0.029769s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr10: 0.035259s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr10: 10.109732s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Switch time of da4: 0.002756s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 10.182759s Aug 31 13:56:04 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. Aug 31 13:56:14 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000012s Aug 31 13:56:24 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000011s Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr09: 0.000010s Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr09: 0.000009s Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr09: 0.000007s Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Switch time of da2: 0.002364s Aug 31 13:56:46 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. from syslog server Aug 31 13:55:23 bowltest4 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:23 bowltest4 kernel: nfs: server donkey OK Aug 31 13:55:23 laybox32 kernel: nfs: server donkey OK Aug 31 13:55:29 b-115-4 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:29 b-115-4 kernel: nfs: server donkey OK Aug 31 13:55:56 b-116-16 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:56 b-204-40 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:57 b-116-16 kernel: nfs: server donkey OK Aug 31 13:55:57 lic2 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:57 b-204-40 kernel: nfs: server donkey OK Aug 31 13:55:57 lic2 kernel: nfs: server donkey OK Aug 31 13:55:57 laybox29 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:57 laybox26 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:58 laybox19 kernel: nfs: server donkey not responding, still trying Aug 31 13:55:58 laybox37 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:00 laybox19 kernel: nfs: server donkey OK Aug 31 13:56:00 laybox26 kernel: nfs: server donkey OK Aug 31 13:56:00 laybox37 kernel: nfs: server donkey OK Aug 31 13:56:00 laybox29 kernel: nfs: server donkey OK Aug 31 13:56:05 ws-119-8 amd[2640]: file server donkey20.centtech.com, type nfs, state not responding Aug 31 13:56:05 ws-119-8 amd[2640]: file server donkey20.centtech.com, type nfs, state ok Aug 31 13:56:36 b-116-17 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:36 b-116-17 kernel: nfs: server donkey OK Aug 31 13:56:40 b-210-17 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:41 b-204-41 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:41 laybox17 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:44 b-204-38 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:44 b-204-38 kernel: nfs: server donkey OK Aug 31 13:56:44 bowltest3 kernel: nfs: server donkey not responding, still trying Aug 31 13:56:46 b-210-17 kernel: nfs: server donkey OK Aug 31 13:56:46 laybox17 kernel: nfs: server donkey OK are the journal devices not large enough? is there a formula for sizing? sorry this is long. can i umount the data device, remove journaling and mount as a regular device? what are those steps? thanks and sorry for the long-winded posting.. ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 19:23:42 2006 Return-Path: X-Original-To: stable@freebsd.org 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 235FD16A4E1; Thu, 31 Aug 2006 19:23:42 +0000 (UTC) (envelope-from freebsd-stable@mlists.thewrittenword.com) Received: from mail1.thewrittenword.com (mail1.thewrittenword.com [67.95.107.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F5C243D49; Thu, 31 Aug 2006 19:23:41 +0000 (GMT) (envelope-from freebsd-stable@mlists.thewrittenword.com) Received: by mail1.thewrittenword.com (Postfix, from userid 1000) id D52102F9; Thu, 31 Aug 2006 14:23:40 -0500 (CDT) Date: Thu, 31 Aug 2006 14:23:40 -0500 From: Albert Chin To: Nikolas Britton Message-ID: <20060831192340.GA11394@mail1.thewrittenword.com> References: <44EC0B9B.5020705@withagen.nl> <003f01c6c68d$64688e60$b3db87d4@multiplay.co.uk> <20060824053618.GA7211@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: amd64@freebsd.org, stable@freebsd.org Subject: Re: suggestions for SATA RAID cards X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 19:23:42 -0000 On Thu, Aug 24, 2006 at 01:39:43AM -0500, Nikolas Britton wrote: > Their new hardware (coming soon) will have a 800MHz XScale with > DDR2-533 cache. According to http://www.areca.com.tw/products/html/pcietosata1280.htm, it's already here. -- albert chin (china@thewrittenword.com) From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 21:08:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 A94A216A4EE for ; Thu, 31 Aug 2006 21:08:02 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6413943D45 for ; Thu, 31 Aug 2006 21:08:02 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k7VL80Gh026800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Aug 2006 14:08:02 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44F74FB0.5090400@errno.com> Date: Thu, 31 Aug 2006 14:08:00 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Jordan Sissel References: <5ad23a300608311106w2cc75145p1b1228f756f91b03@mail.gmail.com> In-Reply-To: <5ad23a300608311106w2cc75145p1b1228f756f91b03@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Suspend freezes system on my Thinkpad X41 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 21:08:02 -0000 Jordan Sissel wrote: > Subject says it all. Attempting FN+F4 (suspend) or acpiconf -s 3 or -s 4 > all > cause the system to halt. > > Specs: > Thinkpad X41 > 6.1-RELEASE GENERIC > Atheros 5212 > Broadcom BCM5751M > SATA (ICH6 SATA150) > > Freezes are non-recoverable. Even hardware functions (such as lcd dimming) > cease. Seems like the system has half suspended, but the LCD is still on > and > displaying. Sleep light doesn't blink indicating sleepiness. > > Any help on this would be greatly appreciated :) "Atheros 5212" is too imprecise; please give mac+phy rev's from dmesg|grep ath. Otherwise, try taking ath out of your kernel config to see if you can suspend+resume. I've got an outstanding issue with ath in how suspend+resume is handled--for cardbus cards at least (never seen it with minipci). Sam From owner-freebsd-stable@FreeBSD.ORG Thu Aug 31 21:14:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0B35F16A4DA for ; Thu, 31 Aug 2006 21:14:57 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id C891043D55 for ; Thu, 31 Aug 2006 21:14:55 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.6/8.13.6) with ESMTP id k7VLEgvH031576; Thu, 31 Aug 2006 23:14:42 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.6/8.13.6/Submit) id k7VLEg7x031575; Thu, 31 Aug 2006 23:14:42 +0200 (CEST) (envelope-from byshenknet) Date: Thu, 31 Aug 2006 23:14:42 +0200 From: Greg Byshenk To: Michael Abbott Message-ID: <20060831211442.GQ633@core.byshenk.net> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827202803.GP633@core.byshenk.net> <20060828082047.J61842@saturn.araneidae.co.uk> <20060828100942.GF20390@deviant.kiev.zoral.com.ua> <20060829165820.F83998@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060829165820.F83998@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.4 X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on core.byshenk.net Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2006 21:14:57 -0000 On Tue, Aug 29, 2006 at 05:05:26PM +0000, Michael Abbott wrote: [I wrote] > >>>An alternative would be to update to RELENG_6 (or at least RELENG_6_1) > >>>and then try again. > So. I have done this. And I can't reproduce the problem. > # uname -a > FreeBSD venus.araneidae.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon Aug 28 > 18:32:17 UTC 2006 > root@venus.araneidae.co.uk:/usr/obj/usr/src/sys/GENERIC i386 > Hmm. Hopefully this is a *good* thing, ie, the problem really has been > fixed, rather than just going into hiding. > So, as far as I can tell, lockf works properly in this release. Just as an interesting side note, I just experienced rpc.lockd crashing. The server is not running RELENG_6, but RELENG_5 (FreeBSD 5.5-STABLE #15: Thu Aug 24 18:47:20 CEST 2006). Due to user error, someone ended up with over 1000 processes trying to lock the same NFS mounted file at the same time. The result was over 1000 "Cannot allocate memory" errors followed by rpc.lockd crashing. I guess the server is telling me it wants an update... -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 03:10:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 DF63B16A4E1 for ; Fri, 1 Sep 2006 03:10:06 +0000 (UTC) (envelope-from psionic@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3A2F43D46 for ; Fri, 1 Sep 2006 03:10:05 +0000 (GMT) (envelope-from psionic@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so861997wxd for ; Thu, 31 Aug 2006 20:10:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=FM60VVebplXB7gOsESk+51tBLYDRS1lDC+sCAkZAbYj8qD3bO/CpcuoHIRGZCr/HQrDFShbg2i0lJtAAEO4guQIxPqAP2Oirdz5YTWcGqDEAtK+pREUhZLY3obDv0cI3+klPfk5D3/wGZHW6C+FBBOGryr745Izb9Dt9nXXkdS0= Received: by 10.70.129.4 with SMTP id b4mr1618421wxd; Thu, 31 Aug 2006 20:08:24 -0700 (PDT) Received: by 10.70.11.20 with HTTP; Thu, 31 Aug 2006 20:08:24 -0700 (PDT) Message-ID: <5ad23a300608312008q4655c3acleb1d14c48f35e497@mail.gmail.com> Date: Fri, 1 Sep 2006 03:08:24 +0000 From: "Jordan Sissel" To: "Sam Leffler" In-Reply-To: <44F74FB0.5090400@errno.com> MIME-Version: 1.0 References: <5ad23a300608311106w2cc75145p1b1228f756f91b03@mail.gmail.com> <44F74FB0.5090400@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Suspend freezes system on my Thinkpad X41 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 03:10:07 -0000 ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xa0200000-0xa020ffff irq 21 at device 2.0 on pci4 ath0: Ethernet address: 00:16:ce:40:7e:41 ath0: mac 5.9 phy 4.3 radio 3.6 It's minipci. As for the video. The LCD display still shows text. If I am in X, it switches to a vty before attempting sleep. The backlight stays on and the display does not turn off. I think when I was testing earlier, I did not have X running nor if_ath loaded. I'll post more later tonight (tomorrow?) when I get a chance. To further clarify: The laptop does *NOT* successfully go to sleep. It returns to vty and locks hard. This is not a resume problem, this is a suspend problem. Attempting to hit ctrl+alt+del to reboot does nothing. -Jordan On 8/31/06, Sam Leffler wrote: > > Jordan Sissel wrote: > > Subject says it all. Attempting FN+F4 (suspend) or acpiconf -s 3 or -s 4 > > all > > cause the system to halt. > > > > Specs: > > Thinkpad X41 > > 6.1-RELEASE GENERIC > > Atheros 5212 > > Broadcom BCM5751M > > SATA (ICH6 SATA150) > > > > Freezes are non-recoverable. Even hardware functions (such as lcd > dimming) > > cease. Seems like the system has half suspended, but the LCD is still on > > and > > displaying. Sleep light doesn't blink indicating sleepiness. > > > > Any help on this would be greatly appreciated :) > > "Atheros 5212" is too imprecise; please give mac+phy rev's from > dmesg|grep ath. Otherwise, try taking ath out of your kernel config to > see if you can suspend+resume. I've got an outstanding issue with ath > in how suspend+resume is handled--for cardbus cards at least (never seen > it with minipci). > > Sam > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 09:46:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 B600E16A4DA for ; Fri, 1 Sep 2006 09:46:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D279343D45 for ; Fri, 1 Sep 2006 09:46:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 53BDC46C5F; Fri, 1 Sep 2006 05:46:03 -0400 (EDT) Date: Fri, 1 Sep 2006 10:46:03 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= In-Reply-To: <44F67DC2.1060900@sh.cvut.cz> Message-ID: <20060901104141.J4921@fledge.watson.org> References: <44F67DC2.1060900@sh.cvut.cz> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-52531061-1157103963=:4921" Cc: freebsd-stable@freebsd.org Subject: Re: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 09:46:05 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-52531061-1157103963=:4921 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 31 Aug 2006, V=E1clav Haisman wrote: > I found this in logs of 6.1 box that I admin this morning. The machine ke= eps=20 > running after that. Indeed, there does appear to be a problem in the TCP socket option code wit= h=20 respect to performing copyin/copyout while holding the inpcb lock. This=20 problem is not present in the IP layer socket option code. However, the co= de=20 between HEAD and 6-STABLE here differs significantly, so fixing this will= =20 require different changes in the two branches. Could you file a problem=20 report on this, and forward me the PR receipt? I'm on travel in India=20 currently, with mixed connectivity, so it may be a little bit before I can = get=20 to fixing the problem. In principle, the risk here is a deadlock, but the fix is a little complica= ted=20 as if we release the lock there, the state of the TCP socket can change, so= =20 when the code picks up from the copyin/copyout, it needs to validate that t= he=20 operation is still valid on the socket (i.e., the connection hasn't been re= set=20 during the system call -- perhaps while the application is blocked waiting = on=20 disk i/o for a paged out page that contains the socket option). This is ve= ry=20 unlikely to trigger in practice, the warning there is quite conservative, b= ut=20 needs to be addressed properly. Thanks for the report, Robert N M Watson Computer Laboratory University of Cambridge --0-52531061-1157103963=:4921-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 11:17:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 2015A16A4DA for ; Fri, 1 Sep 2006 11:17:40 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F2D43D45 for ; Fri, 1 Sep 2006 11:17:39 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 437605138C; Fri, 1 Sep 2006 13:17:37 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 862755133B; Fri, 1 Sep 2006 13:16:32 +0200 (CEST) Date: Fri, 1 Sep 2006 13:16:15 +0200 From: Pawel Jakub Dawidek To: Kevin Kramer Message-ID: <20060901111615.GB1819@garage.freebsd.pl> References: <44F7320E.6040608@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Content-Disposition: inline In-Reply-To: <44F7320E.6040608@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 11:17:40 -0000 --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 31, 2006 at 02:01:34PM -0500, Kevin Kramer wrote: > Pavel, >=20 > running 6.1-stable with these patches > rebuilt kernel/world as of 8/28 @ 2p CST w/ these patches >=20 > gjournal6_20060808.patch > vfs_subr.c.3.patch >=20 > the backend RAID presents 4 luns, this is how we config'd it. > da1 - 8G > da2 - ~897G > da3 - 8G > da4 - ~897G >=20 > da2/4 have been partitioned in FreeBSD, then we did the following >=20 > gjournal label -v /dev/da2 /dev/da1 > gjournal label -v /dev/da4 /dev/da3 > newfs -U -L "scr09" /dev/da2.journal > newfs -U -L "scr10" /dev/da4.journal >=20 > so 1 -8 G journal for each data device. Hmm, using SU with gjournal is really bad choice and you didn't tell file system that it is on gjournaled device. Try: # newfs -J -L scr0X /dev/daX.journal --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE+BZ/ForvXbEpPzQRAnpSAKClmIE8EvPQ0R+NcP0e9ZjHigaZkACg9dwC 05L3jWloulO8aLSwNJ5QXDM= =bZ7H -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 12:28:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 683EE16A4DE for ; Fri, 1 Sep 2006 12:28:48 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D00CE43D6E for ; Fri, 1 Sep 2006 12:28:47 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GJ88K-0008BN-Ro for freebsd-stable@freebsd.org; Fri, 01 Sep 2006 14:28:28 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Sep 2006 14:28:28 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Sep 2006 14:28:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 01 Sep 2006 14:28:12 +0200 Lines: 6 Message-ID: References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en In-Reply-To: <20060901111615.GB1819@garage.freebsd.pl> Sender: news Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 12:28:48 -0000 Pawel Jakub Dawidek wrote: > Hmm, using SU with gjournal is really bad choice and you didn't tell > file system that it is on gjournaled device. Try: I suggest this to be prominent in the documentation :) From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 13:12:23 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 A601716A4DA; Fri, 1 Sep 2006 13:12:23 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D5E343D46; Fri, 1 Sep 2006 13:12:23 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k81DCMEx007434; Fri, 1 Sep 2006 08:12:22 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <44F831B7.90807@centtech.com> Date: Fri, 01 Sep 2006 08:12:23 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> In-Reply-To: <20060901111615.GB1819@garage.freebsd.pl> X-Virus-Scanned: ClamAV 0.87.1/1784/Fri Sep 1 07:00:05 2006 on mh1.centtech.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 13:12:23 -0000 we left the journaling devices raw. do i need to newfs the journaling device? is eveything else ok besides the newfs of the daX.journal? ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com Pawel Jakub Dawidek wrote the following on 09/01/06 06:16: > On Thu, Aug 31, 2006 at 02:01:34PM -0500, Kevin Kramer wrote: > >> Pavel, >> >> running 6.1-stable with these patches >> rebuilt kernel/world as of 8/28 @ 2p CST w/ these patches >> >> gjournal6_20060808.patch >> vfs_subr.c.3.patch >> >> the backend RAID presents 4 luns, this is how we config'd it. >> da1 - 8G >> da2 - ~897G >> da3 - 8G >> da4 - ~897G >> >> da2/4 have been partitioned in FreeBSD, then we did the following >> >> gjournal label -v /dev/da2 /dev/da1 >> gjournal label -v /dev/da4 /dev/da3 >> newfs -U -L "scr09" /dev/da2.journal >> newfs -U -L "scr10" /dev/da4.journal >> >> so 1 -8 G journal for each data device. >> > > Hmm, using SU with gjournal is really bad choice and you didn't tell > file system that it is on gjournaled device. Try: > > # newfs -J -L scr0X /dev/daX.journal > > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 13:56:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 39D4516A4DA for ; Fri, 1 Sep 2006 13:56:41 +0000 (UTC) (envelope-from feijo.listas@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DAE43D68 for ; Fri, 1 Sep 2006 13:56:40 +0000 (GMT) (envelope-from feijo.listas@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1020906wxd for ; Fri, 01 Sep 2006 06:56:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ilzt+r2GDZth/HIyfDZTwVuqyVFClqxmMS1n9jQ+pI7qzsFc8FimDndCntGuA4Mr9+C4DKCshtXfqr1zqCQo5vx19xhCcGfZ7bGgWTUdS3fIOU2JhMQwLkA6UiiRF3S7qsu5fhUSLr3XUbdJ1fAjkMPxjDH4K6nR3xTLnMFWeZw= Received: by 10.70.98.17 with SMTP id v17mr2669671wxb; Fri, 01 Sep 2006 06:54:57 -0700 (PDT) Received: by 10.70.28.18 with HTTP; Fri, 1 Sep 2006 06:54:57 -0700 (PDT) Message-ID: <8a20e5000609010654n7476301fjb54bdee18d2d23f@mail.gmail.com> Date: Fri, 1 Sep 2006 10:54:57 -0300 From: chmod000 To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: /boot/loader.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 13:56:41 -0000 Hi there, I'm starting my freebsd one way trip now. I've allready installed basic system and some other stuffs via ports. Now I wish to know how to tune the loader.conf (I'm using relese 6.1) upgrading console resolution. At a linux box I can set, in the boot loader, this parameter: vga=791. Is it the same way on freebsd? Thans all of you -- []'s chmod000 "Microsoft butterfly is their way of telling you their system has a lot of @#$ bugs!" From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 14:05:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 1CD6416A4EB for ; Fri, 1 Sep 2006 14:05:02 +0000 (UTC) (envelope-from dominique.goncalves@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72F7743D6B for ; Fri, 1 Sep 2006 14:05:01 +0000 (GMT) (envelope-from dominique.goncalves@gmail.com) Received: by wr-out-0506.google.com with SMTP id 71so340970wri for ; Fri, 01 Sep 2006 07:05:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H97XW0ig/PUaZgNqWM2Y5b1JNdXue9wDP6HQaSDBwBplWTnJSw9jngr44y8wRpmQh9Z2sxyIh6/4WPZSEQ0f9hYymjXTg13cSr6KhDdaAtGOTXAjxaTPGl4uWM2MB5iKU+poPml9r5WDwc5EJCfgmYOAdt4/GoxyjLdnx6ha1XQ= Received: by 10.90.50.6 with SMTP id x6mr491259agx; Fri, 01 Sep 2006 07:05:00 -0700 (PDT) Received: by 10.90.31.3 with HTTP; Fri, 1 Sep 2006 07:04:59 -0700 (PDT) Message-ID: <7daacbbe0609010704g502549abm64a19d7cf2bfb74f@mail.gmail.com> Date: Fri, 1 Sep 2006 16:05:00 +0200 From: "Dominique Goncalves" To: chmod000 In-Reply-To: <8a20e5000609010654n7476301fjb54bdee18d2d23f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8a20e5000609010654n7476301fjb54bdee18d2d23f@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: /boot/loader.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 14:05:02 -0000 Hi, On 9/1/06, chmod000 wrote: > Hi there, > > I'm starting my freebsd one way trip now. > > I've allready installed basic system and some other stuffs via ports. > > Now I wish to know how to tune the loader.conf (I'm using relese 6.1) > upgrading console resolution. > > At a linux box I can set, in the boot loader, this parameter: vga=791. > Is it the same way on freebsd? You have to use vidcontrol(1), a small example to start http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fonts/virtual-console.html HTH > Thans all of you > > -- > []'s > chmod000 > "Microsoft butterfly is their way of telling you their system has a > lot of @#$ bugs!" > _______________________________________________ > 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" > Regards. -- There's this old saying: "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life." From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 14:13:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 067E116A4DA for ; Fri, 1 Sep 2006 14:13:32 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89DB343D45 for ; Fri, 1 Sep 2006 14:13:31 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J4X00F0H3IG7GA0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 01 Sep 2006 16:13:28 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J4X00AMH3IGOP60@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 01 Sep 2006 16:13:28 +0200 (CEST) Date: Fri, 01 Sep 2006 16:13:27 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <8a20e5000609010654n7476301fjb54bdee18d2d23f@mail.gmail.com> To: freebsd-stable@freebsd.org Message-id: <20060901161327.c9db1201.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <8a20e5000609010654n7476301fjb54bdee18d2d23f@mail.gmail.com> Subject: Re: /boot/loader.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 14:13:32 -0000 On Fri, 01 Sep 2006 10:54:57 -0300 chmod000 wrote: > Now I wish to know how to tune the loader.conf (I'm using relese 6.1) > upgrading console resolution. This is *not* done in /boot/loader.conf, but in /etc/rc.conf, see below. > > At a linux box I can set, in the boot loader, this parameter: vga=791. > Is it the same way on freebsd? No, it is not the same. See 'man vidcontrol' and 'man rc.conf' to learn more. In the rc.conf man page, search for "allscreens_flags". HTH -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 14:16:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5FBA416A4E2; Fri, 1 Sep 2006 14:16:36 +0000 (UTC) (envelope-from vovk@km.ua) Received: from fido.km.ua (fido.km.ua [195.46.36.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A749943D49; Fri, 1 Sep 2006 14:16:35 +0000 (GMT) (envelope-from vovk@km.ua) Received: from eto.tormoz.net (eto.tormoz.net [195.46.36.15]) (authenticated bits=0) by fido.km.ua (8.13.6/8.13.6/add-fido.auth) with ESMTP id k81EGVRw052094; Fri, 1 Sep 2006 17:16:33 +0300 (EEST) (envelope-from vovk@km.ua) From: Vyacheslav Vovk To: freebsd-stable@freebsd.org Date: Fri, 1 Sep 2006 17:16:29 +0300 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609011716.30749.vovk@km.ua> X-Virus-Scanned: by amavisd-new Cc: freebsd-threads@freebsd.org Subject: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 14:16:36 -0000 Hi, Search on conferences has not given the answer, only the reference to similar problems (http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026010.html), therefore I shall ask here. As well as in the above-stated reference there is highly loaded machine, which periodically panic since 5.4-RELEASE. #kgdb kernel.debug /var/crash/vmcore.4 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undef ined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: panic: vm_thread_new: kstack allocation failed cpuid = 3 Uptime: 7d4h30m58s Dumping 2046 MB (2 chunks) chunk 0: 1MB (158 pages) ... ok chunk 1: 2046MB (523744 pages) 2030 2014 1998 1982 1966 1950 1934 1918 1902 188 6 1870 1854 1838 1822 1806 1790 1774 1758 1742 1726 1710 1694 1678 1662 1646 1630 1614 1598 1582 1566 1550 1534 1518 1502 1486 1470 1454 1438 1422 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262 1246 1230 1214 1198 1182 1166 1150 1134 1118 1 102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 1 58 142 126 110 94 78 62 46 30 14 0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc04e533d in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc04e5665 in panic ( fmt=0xc0679bd6 "vm_thread_new: kstack allocation failed") at /usr/src/sys/kern/kern_shutdown.c:565 #3 0xc05f26bb in vm_thread_new (td=0xd2221780, pages=2) at /usr/src/sys/vm/vm_glue.c:347 #4 0xc04ef7c7 in thread_init (mem=0xd2221780, size=372, flags=259) at /usr/src/sys/kern/kern_thread.c:185 #5 0xc05eb29e in slab_zalloc (zone=0xc0c511e0, wait=259) at /usr/src/sys/vm/uma_core.c:861 #6 0xc05ec890 in uma_zone_slab (zone=0xc0c511e0, flags=3) at /usr/src/sys/vm/uma_core.c:2025 #7 0xc05ecac0 in uma_zalloc_bucket (zone=0xc0c511e0, flags=3) at /usr/src/sys/vm/uma_core.c:2134 #8 0xc05ec722 in uma_zalloc_arg (zone=0xc0c511e0, udata=0x0, flags=2) at /usr/src/sys/vm/uma_core.c:1942 #9 0xc04efcb7 in thread_alloc () at uma.h:275 #10 0xc04d3596 in thread_alloc_spare (td=0xd2252d80) at /usr/src/sys/kern/kern_kse.c:1046 #11 0xc04d40e6 in thread_userret (td=0xd2252d80, frame=0xffab5d38) at /usr/src/sys/kern/kern_kse.c:1437 #12 0xc05061da in userret (td=0xd2252d80, frame=0xffab5d38, oticks=0) at /usr/src/sys/kern/subr_trap.c:120 #13 0xc04cecfa in fork_return (td=0xd2252d80, frame=0xffab5d38) at /usr/src/sys/kern/kern_fork.c:834 #14 0xc04cec21 in fork_exit (callout=0xc04cece8 , arg=0xd2252d80, frame=0xffab5d38) at /usr/src/sys/kern/kern_fork.c:805 #15 0xc062909c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) f 3 #3 0xc05f26bb in vm_thread_new (td=0xd2221780, pages=2) at /usr/src/sys/vm/vm_glue.c:347 347 panic("vm_thread_new: kstack allocation failed"); (kgdb) l 342 * Get a kernel virtual address for this thread's kstack. 343 */ 344 ks = kmem_alloc_nofault(kernel_map, 345 (pages + KSTACK_GUARD_PAGES) * PAGE_SIZE); 346 if (ks == 0) 347 panic("vm_thread_new: kstack allocation failed"); 348 if (KSTACK_GUARD_PAGES != 0) { 349 pmap_qremove(ks, KSTACK_GUARD_PAGES); 350 ks += KSTACK_GUARD_PAGES * PAGE_SIZE; 351 } (kgdb) i loc ksobj = 0xd1b25a50 ks = 0 m = 0x0 ma = {0xc1abe450, 0xc26e8498, 0xd201ce20, 0xffab5b90, 0xc05eca91, 0xc0c61d20, 0xd201ce20, 0x102, 0x80, 0x0, 0xc0c61db0, 0xc0c61d20, 0x0, 0xd0d038c0, 0xc05ec539, 0xffab5bac, 0xffab5bac, 0xc04da4b3, 0x40, 0x2, 0xffab5bd0, 0xc04da579, 0xc0699c00, 0x40, 0x2, 0xc0c6caa0, 0xd2221600, 0x0, 0xc04f800a, 0xd2221754, 0x20, 0xd2221600} i = -769517696 (kgdb) #dmesg Copyright (c) 1992-2006 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 6.1-STABLE #5: Sat Jul 29 19:57:16 EEST 2006 vovk@ic.km.ua:/usr/obj/usr/src/sys/stella acpi_alloc_wakeup_handler: can't alloc wake memory ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400> Logical CPUs per core: 2 real memory = 2146304000 (2046 MB) avail memory = 2096357376 (1999 MB) 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: Changing APIC ID to 4 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xefffffff at device 0.0 o n pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 3.0 on pci0 pci2: on pcib2 em0: port 0x9000-0x901f m em 0xf7020000-0xf703ffff,0xf7000000-0xf701ffff irq 18 at device 1.0 on pci2 em0: Ethernet address: 00:11:2f:10:3e:14 pcib3: at device 28.0 on pci0 pci3: on pcib3 aac0: mem 0xf0000000-0xf3ffffff irq 25 at device 3.0 on pci3 aac0: New comm. interface enabled aac0: Adaptec Raid Controller 2.0.0-1 aacp0: on aac0 aacp1: on aac0 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.4 (no driver attached) pci0: at device 29.5 (no driver attached) pci0: at device 29.7 (no driver attached) pcib4: at device 30.0 on pci0 pci4: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x 376,0xf000-0xf00f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 ichsmb0: port 0x500-0x51f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 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 ppc0: port 0x378-0x37f,0x778-0x77b irq 7 on acpi 0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xcc000-0xd07ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 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 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, defau lt to deny, logging disabled aacd0: on aac0 aacd0: 69974MB (143307008 sectors) pass0 at aacp0 bus 0 target 0 lun 0 pass0: Fixed unknown SCSI-3 device pass0: 3.300MB/s transfers pass1 at aacp0 bus 0 target 1 lun 0 pass1: Fixed unknown SCSI-3 device pass1: 3.300MB/s transfers SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/aacd0s1a WARNING: / was not properly dismounted Periodically I update system up to -STABLE, in hope for correction of the problem, however no changes are present. Any ideas for a work around? -- wbr, slava [vovk-uanic] From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 15:00:09 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 8C50016A4DE for ; Fri, 1 Sep 2006 15:00:09 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA10F43D53 for ; Fri, 1 Sep 2006 15:00:08 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4297A51394; Fri, 1 Sep 2006 17:00:07 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id C2E025133B; Fri, 1 Sep 2006 16:59:58 +0200 (CEST) Date: Fri, 1 Sep 2006 16:59:39 +0200 From: Pawel Jakub Dawidek To: Kevin Kramer Message-ID: <20060901145939.GC1819@garage.freebsd.pl> References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zCKi3GIZzVBPywwA" Content-Disposition: inline In-Reply-To: <44F831B7.90807@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 15:00:09 -0000 --zCKi3GIZzVBPywwA Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 01, 2006 at 08:12:23AM -0500, Kevin Kramer wrote: > we left the journaling devices raw. do i need to newfs the journaling dev= ice? is eveything else ok besides the newfs of the daX.journal? Journal switch times are very long, but this could be caused by SU. Could you try to disable SU and turn on gjournal? Without "renewfsing" you could do on an unmounted file system: # tunefs -n disable -J enable /dev/daX.journal --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --zCKi3GIZzVBPywwA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE+ErbForvXbEpPzQRApdoAKCwaoS+u7rQ+xdVTuFQ0rWzLV3GGgCglRjt qdr2xkcWjw6PYesotinr480= =SNLd -----END PGP SIGNATURE----- --zCKi3GIZzVBPywwA-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 15:16:12 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 7752E16A4E0; Fri, 1 Sep 2006 15:16:12 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE88143D4C; Fri, 1 Sep 2006 15:16:09 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k81FG9e3044438; Fri, 1 Sep 2006 10:16:09 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <44F84EB9.6000006@centtech.com> Date: Fri, 01 Sep 2006 10:16:09 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> <20060901145939.GC1819@garage.freebsd.pl> In-Reply-To: <20060901145939.GC1819@garage.freebsd.pl> X-Virus-Scanned: ClamAV 0.87.1/1784/Fri Sep 1 07:00:05 2006 on mh2.centtech.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 15:16:12 -0000 I've already redone the whole thing. here are the steps i took umount /scr09 umount /scr10 gjournal stop da2.journal gjournal stop da4.journal ** had not done this on the first attempt newfs /dev/da1 newfs /dev/da3 gjournal label -v /dev/da2 /dev/da1 gjournal label -v /dev/da4 /dev/da3 newfs -J -L scr09 /dev/da2.journal newfs -J -L scr10 /dev/da4.journal mount /scr09 mount /scr10 it is looking much better so far. before, i was getting this in the debug (only on /scr10) and my mountd process was always the top process Sep 1 00:00:11 donkey kernel: fsync: giving up on dirty Sep 1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR Sep 1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 mountedher e 0xc9ebfb00 Sep 1 00:00:11 donkey kernel: flags () Sep 1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933 Sep 1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread 0xc9bd4 180 (pid 38) Sep 1 00:00:11 donkey kernel: dev ufs/scr10 Sep 1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system /scr10 ( error=35). but now i'm getting clean journal writes, while i'm rsyncing the data back. i don't have any real clients yet so i'll enable that after the rsync is completed. Sep 1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Sep 1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Switch time of da4: 0.002327s Sep 1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.011674s Sep 1 10:00:36 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr09: 0.000008s Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr09: 0.000031s Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr09: 0.000094 s Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Starting copy of journal. Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Switch time of da2: 0.002425s Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.003477s Sep 1 10:00:46 donkey kernel: GEOM_JOURNAL[1]: Data has been copied. Sep 1 10:00:56 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000014s Sep 1 10:01:06 donkey kernel: GEOM_JOURNAL[1]: Entire switch time: 0.000014s Sep 1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Msync time of /scr10: 0.002388s Sep 1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Sync time of /scr10: 0.002748s Sep 1 10:01:16 donkey kernel: GEOM_JOURNAL[1]: Suspend time of /scr10: 0.002751 s ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com Pawel Jakub Dawidek wrote the following on 09/01/06 09:59: > On Fri, Sep 01, 2006 at 08:12:23AM -0500, Kevin Kramer wrote: > >> we left the journaling devices raw. do i need to newfs the journaling device? is eveything else ok besides the newfs of the daX.journal? >> > > Journal switch times are very long, but this could be caused by SU. > Could you try to disable SU and turn on gjournal? > Without "renewfsing" you could do on an unmounted file system: > > # tunefs -n disable -J enable /dev/daX.journal > > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 15:26:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7BB7D16A4DA for ; Fri, 1 Sep 2006 15:26:29 +0000 (UTC) (envelope-from smibrahim@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0837E43D5D for ; Fri, 1 Sep 2006 15:26:28 +0000 (GMT) (envelope-from smibrahim@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so564515nzn for ; Fri, 01 Sep 2006 08:26:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer; b=D2N6NSXyCnGm+oRkdz4yiqyFM/Nv05N4CBVmK9V0G8mCSiNbjjc+X4MFjjXlR4s4WWhKgJFQZc8Izyg4qle/WI7WDJ2vaaWkazvVSecCyXMa9P+0uFD91+7YOEcXZd6nC0IjUGci7r5FCf8bwb4T9keZSJw+/Kb6JkGjv+7lKLQ= Received: by 10.65.59.17 with SMTP id m17mr2872061qbk; Fri, 01 Sep 2006 08:26:28 -0700 (PDT) Received: from shanazsoft.com ( [203.112.195.171]) by mx.gmail.com with ESMTP id p4sm1728138qba.2006.09.01.08.26.19; Fri, 01 Sep 2006 08:26:27 -0700 (PDT) From: "S. M. Ibrahim (Lavlu)" To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Ph8dlXr5NMohGgYh+Srw" Date: Fri, 01 Sep 2006 21:26:05 +0600 Message-Id: <1157124365.3048.5.camel@shanazsoft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 15:26:29 -0000 --=-Ph8dlXr5NMohGgYh+Srw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable i am totally new with freeBSD 6.1 I installed it yesterday. Everything goes ok, but problem with sound card, It's a builtin Intl HDA on gigabyte 915G-DU motherboard. I added the line=20 sound_load=3D"YES" snd_driver_load=3D"YES" snd_cmi_load=3D"YES" to /boot/loader.conf but sound is not working. Moreover how to access administrativ app from GUI. --=-Ph8dlXr5NMohGgYh+Srw Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBE+FENzpD0S6mRD54RApeoAJ9hbKsZAP530EOe1yI0t4jfPs9/LACfZf90 ARi41hdcYDxSOncLKVQw/DA= =vH85 -----END PGP SIGNATURE----- --=-Ph8dlXr5NMohGgYh+Srw-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 15:32:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 B44F916A4DA for ; Fri, 1 Sep 2006 15:32:39 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECD1A43D45 for ; Fri, 1 Sep 2006 15:32:38 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by wr-out-0506.google.com with SMTP id i2so377551wra for ; Fri, 01 Sep 2006 08:32:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SrRWdGLdDYMrPVwbgO7bnNyniBww5vInt1ItqnK0H2wdOwR4hBaYWC6e4Z8Zf2WcmIS50Hab6xovg9PUzkR7JEs19WaiuZ5cY5abF6ptWsZMrMsU00Ye+0Zl66mMsJ1kwNDHIp+wRsq9P6w/s82kUsivCynwyQXvUHz7UYslnHk= Received: by 10.65.112.5 with SMTP id p5mr2884273qbm; Fri, 01 Sep 2006 08:32:35 -0700 (PDT) Received: by 10.64.178.14 with HTTP; Fri, 1 Sep 2006 08:32:35 -0700 (PDT) Message-ID: <84dead720609010832s4cfd875fn3958c8630aa3e792@mail.gmail.com> Date: Fri, 1 Sep 2006 21:02:35 +0530 From: "Joseph Koshy" To: "S. M. Ibrahim (Lavlu)" In-Reply-To: <1157124365.3048.5.camel@shanazsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1157124365.3048.5.camel@shanazsoft.com> Cc: freebsd-stable@freebsd.org Subject: Re: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 15:32:39 -0000 > I installed it yesterday. Everything goes ok, but problem > with sound card, It's a builtin Intl HDA on gigabyte 915G-DU > motherboard. I added the line > > sound_load="YES" > snd_driver_load="YES" > snd_cmi_load="YES" > > to /boot/loader.conf but sound is not working. Things to check: - Does loading the driver module using kldload work: # kldload snd_driver.ko - What are the last few lines from `dmesg` after this step. - Do you have a /dev/sndstat? If so what does # cat /dev/sndstat reveal? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 15:54:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 3E7F916A4DA for ; Fri, 1 Sep 2006 15:54:37 +0000 (UTC) (envelope-from smibrahim@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5560E43D4C for ; Fri, 1 Sep 2006 15:54:35 +0000 (GMT) (envelope-from smibrahim@gmail.com) Received: by wr-out-0506.google.com with SMTP id i2so384012wra for ; Fri, 01 Sep 2006 08:54:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer; b=r2AfITIFlsymlJpzaA73bo6W2XXPF8yE3WB8/eDtqfkJrCFn51PMrNG+PtTXiB5ty7hRlE3iu0T6iRBnlCyfwllvFjuLSF5uaZhQmNBUhQnZEXQW2KvuZtfODcjO/+RC5vEqIkj6AJ31mvjcAhEo8617efKIXuZQrg7zLBuf0Ys= Received: by 10.65.186.18 with SMTP id n18mr1012110qbp; Fri, 01 Sep 2006 08:54:34 -0700 (PDT) Received: from shanazsoft.com ( [203.112.195.171]) by mx.gmail.com with ESMTP id e16sm1745960qbe.2006.09.01.08.54.31; Fri, 01 Sep 2006 08:54:34 -0700 (PDT) From: "S. M. Ibrahim (Lavlu)" To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-CCNRGQGqqNrGi5Ujng8b" Date: Fri, 01 Sep 2006 21:54:23 +0600 Message-Id: <1157126063.3048.10.camel@shanazsoft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: Re: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 15:54:37 -0000 --=-CCNRGQGqqNrGi5Ujng8b Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2006-09-01 at 21:02 +0530, Joseph Koshy wrote: > > I installed it yesterday. Everything goes ok, but problem > > with sound card, It's a builtin Intl HDA on gigabyte 915G-DU > > motherboard. I added the line > > > > sound_load=3D"YES" > > snd_driver_load=3D"YES" > > snd_cmi_load=3D"YES" > > > > to /boot/loader.conf but sound is not working. >=20 > Things to check: >=20 > - Does loading the driver module using kldload work: >=20 > # kldload snd_driver.ko >=20 already loaded > - What are the last few lines from `dmesg` after this > step. >=20 no changes > - Do you have a /dev/sndstat? If so what does >=20 > # cat /dev/sndstat >=20 [ibrahim@shanazsoft ~]$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: [ibrahim@shanazsoft ~]$ > reveal? >=20 in my debian, it's my card work ok with snd_hda_intl mod :( --=-CCNRGQGqqNrGi5Ujng8b Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBE+FevzpD0S6mRD54RAsqmAKCJIM4sstJ92JAOQU0tIkpIS6JXLQCggZZY 8wXni0K8SW0VP5nEeSCuO7E= =PwTP -----END PGP SIGNATURE----- --=-CCNRGQGqqNrGi5Ujng8b-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 16:06:44 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 9CD7316A4E1 for ; Fri, 1 Sep 2006 16:06:44 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2DB843D58 for ; Fri, 1 Sep 2006 16:06:43 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id F09EF6042; Fri, 1 Sep 2006 20:06:42 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id CF47F601D; Fri, 1 Sep 2006 20:06:42 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.6/8.13.6) id k81G7A5D024790; Fri, 1 Sep 2006 20:07:10 +0400 (MSD) (envelope-from ru) Date: Fri, 1 Sep 2006 20:07:10 +0400 From: Ruslan Ermilov To: "S. M. Ibrahim (Lavlu)" Message-ID: <20060901160710.GC14467@rambler-co.ru> References: <1157126063.3048.10.camel@shanazsoft.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m51xatjYGsM+13rf" Content-Disposition: inline In-Reply-To: <1157126063.3048.10.camel@shanazsoft.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable@FreeBSD.org Subject: Re: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 16:06:44 -0000 --m51xatjYGsM+13rf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 01, 2006 at 09:54:23PM +0600, S. M. Ibrahim (Lavlu) wrote: > On Fri, 2006-09-01 at 21:02 +0530, Joseph Koshy wrote: > > > I installed it yesterday. Everything goes ok, but problem > > > with sound card, It's a builtin Intl HDA on gigabyte 915G-DU > > > motherboard. I added the line > > > > > > sound_load=3D"YES" > > > snd_driver_load=3D"YES" > > > snd_cmi_load=3D"YES" > > > > > > to /boot/loader.conf but sound is not working. > >=20 > > Things to check: > >=20 > > - Does loading the driver module using kldload work: > >=20 > > # kldload snd_driver.ko > >=20 > already loaded > > - What are the last few lines from `dmesg` after this > > step. > >=20 > no changes > > - Do you have a /dev/sndstat? If so what does > >=20 >=20 > > # cat /dev/sndstat > >=20 > [ibrahim@shanazsoft ~]$ cat /dev/sndstat > FreeBSD Audio Driver (newpcm) > Installed devices: > [ibrahim@shanazsoft ~]$ >=20 > > reveal? > >=20 > in my debian, it's my card work ok with snd_hda_intl mod :( >=20 Try the OSS drivers from http://www.opensound.com/. Mine is detected but doesn't work, while you may be more lucky. :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --m51xatjYGsM+13rf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE+FquqRfpzJluFF4RAlPyAKCUkPAiRISTlJSofMYoAOrYyQa5aACeLSoT pVZsSGrsEJ+vHNSFLnSU39s= =GyxI -----END PGP SIGNATURE----- --m51xatjYGsM+13rf-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 16:21:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 DB6F516A4DD; Fri, 1 Sep 2006 16:21:46 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service2.sh.cvut.cz (service2.sh.cvut.cz [147.32.127.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC7043D58; Fri, 1 Sep 2006 16:21:27 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service2.sh.cvut.cz (Postfix) with ESMTP id 7A0081379D1; Fri, 1 Sep 2006 18:21:26 +0200 (CEST) Received: from service2.sh.cvut.cz ([127.0.0.1]) by localhost (service2.sh.cvut.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27146-10; Fri, 1 Sep 2006 18:21:19 +0200 (CEST) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) by service2.sh.cvut.cz (Postfix) with ESMTP id F05081379A1; Fri, 1 Sep 2006 18:21:18 +0200 (CEST) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id 9EB6861C32; Fri, 1 Sep 2006 18:21:18 +0200 (CEST) Message-ID: <44F85DEA.2010206@sh.cvut.cz> Date: Fri, 01 Sep 2006 18:20:58 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Robert Watson References: <44F67DC2.1060900@sh.cvut.cz> <20060901104141.J4921@fledge.watson.org> In-Reply-To: <20060901104141.J4921@fledge.watson.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC5189C888E8823AA4263F06A" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at service2.sh.cvut.cz X-Spam-Status: No, hits=-2.5 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, AWL X-Spam-Level: Cc: freebsd-stable@freebsd.org Subject: Re: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 16:21:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC5189C888E8823AA4263F06A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Robert Watson wrote, On 1.9.2006 11:46: >=20 > On Thu, 31 Aug 2006, V=C3=A1clav Haisman wrote: >=20 >> I found this in logs of 6.1 box that I admin this morning. The machine= >> keeps running after that. >=20 > Indeed, there does appear to be a problem in the TCP socket option code= > with respect to performing copyin/copyout while holding the inpcb lock.= =20 > This problem is not present in the IP layer socket option code.=20 > However, the code between HEAD and 6-STABLE here differs significantly,= > so fixing this will require different changes in the two branches.=20 > Could you file a problem report on this, and forward me the PR receipt?= =20 > I'm on travel in India currently, with mixed connectivity, so it may be= > a little bit before I can get to fixing the problem. >=20 > In principle, the risk here is a deadlock, but the fix is a little > complicated as if we release the lock there, the state of the TCP socke= t > can change, so when the code picks up from the copyin/copyout, it needs= > to validate that the operation is still valid on the socket (i.e., the > connection hasn't been reset during the system call -- perhaps while th= e > application is blocked waiting on disk i/o for a paged out page that > contains the socket option). This is very unlikely to trigger in > practice, the warning there is quite conservative, but needs to be > addressed properly. >=20 > Thanks for the report, >=20 > Robert N M Watson > Computer Laboratory > University of Cambridge Here is the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D102752 -- Vaclav Haisman --------------enigC5189C888E8823AA4263F06A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRPhd/kNOZDESBK8FAQIKtQf+JVl57cOxPsmlhjVU22tJCr/WloqCkCFK 9f4928WY+9Tgk3qRzZtg7WW/kdA6f/kUZt8AKUOFXNS1euj0JGIQKOfFOt21Wz/B mtpkCdupBdzmN5AVmSRzGwaMKPOwDeK8DVjz4jDcQR8uJweDvC5sOVyKlocS9UGk M6oSfzOxyXSg8Od7D1VX7CzCdsWqZtz5x+cE0rHvhAkoB1nL3ojbfpvBKqNtvc7d vgGu3T+DK/l2W6PD/5iQ9Kgj+Nu0CN2T1Z3oT9Q1sPU6snXsrMSfBlZw/n4MEW5J uxDAQwSCp64H+sp5TjdzutM7dNRxBq0vUfEzXLWacn7RBk8FHVepXQ== =sXi6 -----END PGP SIGNATURE----- --------------enigC5189C888E8823AA4263F06A-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 16:27:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 EA6D216A4DA; Fri, 1 Sep 2006 16:27:17 +0000 (UTC) (envelope-from prvs=julian=392b3a9d5@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE94143D58; Fri, 1 Sep 2006 16:27:16 +0000 (GMT) (envelope-from prvs=julian=392b3a9d5@elischer.org) Received: from unknown (HELO [192.168.2.3]) ([10.251.60.33]) by a50.ironport.com with ESMTP; 01 Sep 2006 09:27:16 -0700 Message-ID: <44F85F63.5020508@elischer.org> Date: Fri, 01 Sep 2006 09:27:15 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vyacheslav Vovk References: <200609011716.30749.vovk@km.ua> In-Reply-To: <200609011716.30749.vovk@km.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 16:27:18 -0000 Vyacheslav Vovk wrote: can you see how many threads thre are in the system? I think you will have to extract this information frome the zone allocator. I just realised there is no effective limit on kernel threads in the system. probably one could cause this with a fork bomb appoach using forks and thread creation. >Unread portion of the kernel message buffer: >panic: vm_thread_new: kstack allocation failed >cpuid = 3 >Uptime: 7d4h30m58s > > > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 16:28:36 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 8B00A16A4DD for ; Fri, 1 Sep 2006 16:28:36 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5C643D68 for ; Fri, 1 Sep 2006 16:28:25 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k81GSNbg017632; Fri, 1 Sep 2006 12:28:23 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Fri, 1 Sep 2006 12:27:59 -0400 User-Agent: KMail/1.6.2 References: <1157124365.3048.5.camel@shanazsoft.com> In-Reply-To: <1157124365.3048.5.camel@shanazsoft.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200609011228.08058.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1784/Fri Sep 1 08:00:05 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: "S. M. Ibrahim \(Lavlu\)" Subject: Re: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 16:28:36 -0000 On Friday 01 September 2006 11:26 am, S. M. Ibrahim (Lavlu) wrote: > i am totally new with freeBSD 6.1 > I installed it yesterday. Everything goes ok, but problem with > sound card, It's a builtin Intl HDA on gigabyte 915G-DU > motherboard. I added the line > > sound_load="YES" > snd_driver_load="YES" > snd_cmi_load="YES" > > to /boot/loader.conf but sound is not working. Intel HDA is not supported yet but there are experimental drivers floating around the net. You should be able to find them from freebsd-multimedia@ ML archive. Good luck, Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 16:42:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9773116A4DA for ; Fri, 1 Sep 2006 16:42:41 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9484643D68 for ; Fri, 1 Sep 2006 16:42:40 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id k81Ggd3w028399 for ; Fri, 1 Sep 2006 18:42:39 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k81Ggca9067259 for ; Fri, 1 Sep 2006 18:42:38 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k81Ggcup067258 for freebsd-stable@freebsd.org; Fri, 1 Sep 2006 18:42:38 +0200 (CEST) (envelope-from ry93) Date: Fri, 1 Sep 2006 18:42:38 +0200 From: "Patrick M. Hausen" To: freebsd-stable@freebsd.org Message-ID: <20060901164238.GA66726@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.10i Subject: LSI/amr driver controller cache problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 16:42:41 -0000 Hi, all! We just set a brand new Intel SSR212CC box into production. This is basically a standard server with 2 LSI SATA RAID controllers and 12 drive bays in 2 rack units height. Intel sells it as a storage product. There's a variant of Windows 2003 server that turns this box into an iSCSI target. We want to use it for disk based backup with Amanda. The system runs 6-STABLE at the moment. amr0: mem 0xfbef0000-0xfbefffff, 0xfcd00000-0xfcdfffff irq 72 at device 14.0 on pci6 amr0: Firmware 814C, BIOS H431, 128MB RAM amr1: mem 0xfbff0000-0xfbffffff, 0xfcf00000-0xfcffffff irq 96 at device 14.0 on pci8 amr1: Firmware 814C, BIOS H431, 128MB RAM amrd0: on amr0 amrd0: 1907348MB (3906248704 sectors) RAID 5 (optimal) Since the two RAID controllers come with a battery backup for their cache memory, I configured the logical drive with write back cache policy and the individual disk drives' write caches off. After cvsup and build/installworld, I noticed strange Sendmail failures (signal 11) on the box. Reinstalling Sendmail fixed the problem. Just to make sure I did installworld again, rebooted - Sendmail signal 11. Then it dawned at me that Sendmail is the last binary installed and written to the logical drive in the installworld process. I can reproduce the problem any time: installworld, reboot, Sendmail broken. Installworld or just reinstall Sendmail, don't reboot, everything's fine. No matter if I use "reboot" or "shutdown -r". Is it possible that the amr driver does not issue the necessary flush command to the controller (probably first part of the problem) and additionally the controller loses it's cache content at the following system reset despite it's BBU (second part of problem - iir controllers by ICP Vortex handle a system reset just fine, syncing the drives during boot)? And ideas? I don't have a different explanation. A coworker suggested a possible yet unknown UFS2 problem with large filesystems, but /usr is not large on this box. /var is. The last couple of writes before a system reboot are lost. Reliably. I will set the controller's cache policy back to "write through", but I'm still not sleeping well ... Thanks, Patrick P.S. As a side note: no problems at all with the em(4) driver so far on this one. -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 17:15:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 35E4416A4E0 for ; Fri, 1 Sep 2006 17:15:53 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B71F143D53 for ; Fri, 1 Sep 2006 17:15:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k81HFgu2061525; Fri, 1 Sep 2006 11:15:48 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44F86AB9.9000002@samsco.org> Date: Fri, 01 Sep 2006 11:15:37 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Patrick M. Hausen" References: <20060901164238.GA66726@hugo10.ka.punkt.de> In-Reply-To: <20060901164238.GA66726@hugo10.ka.punkt.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.5 required=3.8 tests=SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: LSI/amr driver controller cache problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 17:15:53 -0000 Patrick M. Hausen wrote: > Hi, all! > > We just set a brand new Intel SSR212CC box into production. > This is basically a standard server with 2 LSI SATA RAID > controllers and 12 drive bays in 2 rack units height. > > Intel sells it as a storage product. There's a variant > of Windows 2003 server that turns this box into an iSCSI > target. > > We want to use it for disk based backup with Amanda. > The system runs 6-STABLE at the moment. > > amr0: mem 0xfbef0000-0xfbefffff, > 0xfcd00000-0xfcdfffff irq 72 at device 14.0 on pci6 > amr0: > Firmware 814C, BIOS H431, 128MB RAM > amr1: mem 0xfbff0000-0xfbffffff, > 0xfcf00000-0xfcffffff irq 96 at device 14.0 on pci8 > amr1: > Firmware 814C, BIOS H431, 128MB RAM > amrd0: on amr0 > amrd0: 1907348MB (3906248704 sectors) RAID 5 (optimal) > > Since the two RAID controllers come with a battery backup for > their cache memory, I configured the logical drive with write > back cache policy and the individual disk drives' write caches > off. > > After cvsup and build/installworld, I noticed strange > Sendmail failures (signal 11) on the box. > > Reinstalling Sendmail fixed the problem. Just to make sure > I did installworld again, rebooted - Sendmail signal 11. > > Then it dawned at me that Sendmail is the last binary installed > and written to the logical drive in the installworld process. > I can reproduce the problem any time: installworld, reboot, > Sendmail broken. Installworld or just reinstall Sendmail, don't > reboot, everything's fine. No matter if I use "reboot" or > "shutdown -r". > > Is it possible that the amr driver does not issue the necessary > flush command to the controller (probably first part of the > problem) and additionally the controller loses it's cache > content at the following system reset despite it's BBU > (second part of problem - iir controllers by ICP Vortex handle > a system reset just fine, syncing the drives during boot)? > > And ideas? I don't have a different explanation. A coworker > suggested a possible yet unknown UFS2 problem with large > filesystems, but /usr is not large on this box. /var is. > > The last couple of writes before a system reboot are lost. > Reliably. I will set the controller's cache policy back to > "write through", but I'm still not sleeping well ... > > > Thanks, > Patrick > > P.S. As a side note: no problems at all with the em(4) driver so > far on this one. It is very arguably a bug in the LSI firmware if it is actually dumping its cache when a PCI reset occurs, especially if a battery unit is present. However, I seriously doubt that you will get anyone at LSI to listen to this problem. Do you get any messages on the console at shutdown about the amr driver flushing the cache? Also, check the cache setting on the drives itself. Maybe the drives are loosing power or getting reset while data is in their cache. It's bad practice to enable the write cache on a drive in an RAID array for just this very reason, but some vendors do it anyways in an attempt to cover up poor performance. Scott From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 18:57:13 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 9409D16A592 for ; Fri, 1 Sep 2006 18:57:13 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C710F43D72 for ; Fri, 1 Sep 2006 18:57:05 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id B305251398; Fri, 1 Sep 2006 20:57:03 +0200 (CEST) Received: from localhost (djw246.neoplus.adsl.tpnet.pl [83.24.0.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id EB82751391; Fri, 1 Sep 2006 20:56:56 +0200 (CEST) Date: Fri, 1 Sep 2006 20:56:37 +0200 From: Pawel Jakub Dawidek To: Kevin Kramer Message-ID: <20060901185637.GA6759@garage.freebsd.pl> References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> <20060901145939.GC1819@garage.freebsd.pl> <44F84EB9.6000006@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <44F84EB9.6000006@centtech.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 18:57:13 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 01, 2006 at 10:16:09AM -0500, Kevin Kramer wrote: > I've already redone the whole thing. here are the steps i took >=20 > umount /scr09 > umount /scr10 > gjournal stop da2.journal > gjournal stop da4.journal >=20 > ** had not done this on the first attempt > newfs /dev/da1 > newfs /dev/da3 This is not needed. > gjournal label -v /dev/da2 /dev/da1 > gjournal label -v /dev/da4 /dev/da3 >=20 > newfs -J -L scr09 /dev/da2.journal > newfs -J -L scr10 /dev/da4.journal >=20 > mount /scr09 > mount /scr10 Don't know how your /etc/fstab looks like, but you definiately should use 'async' mount option, which is safe to use with gjournaled file systems. > it is looking much better so far. before, i was getting this in the debug= (only on /scr10) and my mountd process was always the top process >=20 > Sep 1 00:00:11 donkey kernel: fsync: giving up on dirty > Sep 1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR > Sep 1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 mou= ntedher > e 0xc9ebfb00 > Sep 1 00:00:11 donkey kernel: flags () > Sep 1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933 > Sep 1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread = 0xc9bd4 > 180 (pid 38) > Sep 1 00:00:11 donkey kernel: dev ufs/scr10 > Sep 1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system /= scr10 ( > error=3D35). It happens sometimes under load, haven't investigated yet what exactly is happening, but you can ignore it for now, it's harmless, it just means journal switch will be done a bit later. BTW. 8GB for journals is much. You should not need more than 2GB probably. Of course it will work with 8GB just fine. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE+IJlForvXbEpPzQRAqSWAJ92yOYLIlQbJEGthTRpLhtDix+/WwCcCLW/ qzcp6QskinL3EkkXK8BUwFw= =91Hb -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 19:07:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 E8C3C16A4DA; Fri, 1 Sep 2006 19:07:39 +0000 (UTC) (envelope-from vovk@km.ua) Received: from fido.km.ua (fido.km.ua [195.46.36.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B84343D58; Fri, 1 Sep 2006 19:07:38 +0000 (GMT) (envelope-from vovk@km.ua) Received: from [10.0.0.8] (id.km.ua [195.46.36.18]) (authenticated bits=0) by fido.km.ua (8.13.6/8.13.6/add-fido.auth) with ESMTP id k81J7SjH026337; Fri, 1 Sep 2006 22:07:29 +0300 (EEST) (envelope-from vovk@km.ua) Date: Fri, 1 Sep 2006 22:07:57 +0300 From: Vyacheslav Vovk X-Mailer: The Bat! (v3.81.06 Beta) Professional X-Priority: 3 (Normal) Message-ID: <1154543100.20060901220757@km.ua> To: Julian Elischer In-Reply-To: <44F85F63.5020508@elischer.org> References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re[2]: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vyacheslav Vovk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 19:07:40 -0000 Hello Julian, Friday, September 1, 2006, 7:27:15 PM, you wrote: > Vyacheslav Vovk wrote: > can you see how many threads thre are in the system? > I think you will have to extract this information frome the zone allocator. how to do it practically? > I just realised there is no effective limit on kernel threads in the system. > probably one could cause this with a fork bomb appoach using forks and > thread creation. what can be staying in this fork bomb? -- wbr, slava [vovk-uanic] From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 19:18:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7FBEA16A4E8 for ; Fri, 1 Sep 2006 19:18:31 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id D59C943D69 for ; Fri, 1 Sep 2006 19:18:14 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so609859nzn for ; Fri, 01 Sep 2006 12:18:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=R5uENW+9T2Pg4WnZtHV5aIGcsTYt63NiqkRJ73z8JHm8JKMKGwY4Klepaq6ig3HjaEI4KE6X/GtmrcqPzrM1z33Kb31T6dzvD2rHFGrQphK8lQVerntcdngmrEX6tjQ7IClMATbfnwUBrJtji5/OGVAZmHT3J82fqVoPTlMKon4= Received: by 10.65.59.20 with SMTP id m20mr3191472qbk; Fri, 01 Sep 2006 12:18:13 -0700 (PDT) Received: by 10.65.224.1 with HTTP; Fri, 1 Sep 2006 12:18:13 -0700 (PDT) Message-ID: Date: Fri, 1 Sep 2006 12:18:13 -0700 From: "Kip Macy" To: "Julian Elischer" In-Reply-To: <44F85F63.5020508@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> Cc: Vyacheslav Vovk , freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 19:18:31 -0000 I've seen this when running stress2 with a large number of incarnations. Why don't we return an error to the user? -Kip On 9/1/06, Julian Elischer wrote: > Vyacheslav Vovk wrote: > > can you see how many threads thre are in the system? > I think you will have to extract this information frome the zone allocator. > > I just realised there is no effective limit on kernel threads in the system. > probably one could cause this with a fork bomb appoach using forks and > thread creation. > > >Unread portion of the kernel message buffer: > >panic: vm_thread_new: kstack allocation failed > >cpuid = 3 > >Uptime: 7d4h30m58s > > > > > > > _______________________________________________ > 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" > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 19:23:03 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 7105B16A4DD; Fri, 1 Sep 2006 19:23:03 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBDB343D46; Fri, 1 Sep 2006 19:23:02 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k81JN1gD067279; Fri, 1 Sep 2006 14:23:01 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <44F88896.1050204@centtech.com> Date: Fri, 01 Sep 2006 14:23:02 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> <20060901145939.GC1819@garage.freebsd.pl> <44F84EB9.6000006@centtech.com> <20060901185637.GA6759@garage.freebsd.pl> In-Reply-To: <20060901185637.GA6759@garage.freebsd.pl> X-Virus-Scanned: ClamAV 0.87.1/1785/Fri Sep 1 12:29:13 2006 on mh1.centtech.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 19:23:03 -0000 i was seeing up to 14s suspends on /scr10 prior to the reconfig causing mount point to be unresponsive on the clients. i'm using async option also. the rsync is still going so won't go live again 'til next week. thanks for the help. ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com Pawel Jakub Dawidek wrote the following on 09/01/06 13:56: > On Fri, Sep 01, 2006 at 10:16:09AM -0500, Kevin Kramer wrote: > >> I've already redone the whole thing. here are the steps i took >> >> umount /scr09 >> umount /scr10 >> gjournal stop da2.journal >> gjournal stop da4.journal >> >> ** had not done this on the first attempt >> newfs /dev/da1 >> newfs /dev/da3 >> > > This is not needed. > > >> gjournal label -v /dev/da2 /dev/da1 >> gjournal label -v /dev/da4 /dev/da3 >> >> newfs -J -L scr09 /dev/da2.journal >> newfs -J -L scr10 /dev/da4.journal >> >> mount /scr09 >> mount /scr10 >> > > Don't know how your /etc/fstab looks like, but you definiately should > use 'async' mount option, which is safe to use with gjournaled file > systems. > > >> it is looking much better so far. before, i was getting this in the debug (only on /scr10) and my mountd process was always the top process >> >> Sep 1 00:00:11 donkey kernel: fsync: giving up on dirty >> Sep 1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR >> Sep 1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 mountedher >> e 0xc9ebfb00 >> Sep 1 00:00:11 donkey kernel: flags () >> Sep 1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933 >> Sep 1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread 0xc9bd4 >> 180 (pid 38) >> Sep 1 00:00:11 donkey kernel: dev ufs/scr10 >> Sep 1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system /scr10 ( >> error=35). >> > > It happens sometimes under load, haven't investigated yet what exactly > is happening, but you can ignore it for now, it's harmless, it just > means journal switch will be done a bit later. > > BTW. 8GB for journals is much. You should not need more than 2GB > probably. Of course it will work with 8GB just fine. > > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 19:30:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0B08B16A4E2; Fri, 1 Sep 2006 19:30:19 +0000 (UTC) (envelope-from vovk@km.ua) Received: from fido.km.ua (fido.km.ua [195.46.36.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E76243DE0; Fri, 1 Sep 2006 19:29:30 +0000 (GMT) (envelope-from vovk@km.ua) Received: from [10.0.0.8] (id.km.ua [195.46.36.18]) (authenticated bits=0) by fido.km.ua (8.13.6/8.13.6/add-fido.auth) with ESMTP id k81JTPK7033682; Fri, 1 Sep 2006 22:29:26 +0300 (EEST) (envelope-from vovk@km.ua) Date: Fri, 1 Sep 2006 22:29:54 +0300 From: Vyacheslav Vovk X-Mailer: The Bat! (v3.81.06 Beta) Professional X-Priority: 3 (Normal) Message-ID: <693466338.20060901222954@km.ua> To: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org In-Reply-To: <1154543100.20060901220757@km.ua> References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> <1154543100.20060901220757@km.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: Subject: Re[3]: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vyacheslav Vovk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 19:30:19 -0000 Hello Vyacheslav, Friday, September 1, 2006, 10:07:57 PM, you wrote: > Hello Julian, > Friday, September 1, 2006, 7:27:15 PM, you wrote: >> Vyacheslav Vovk wrote: >> can you see how many threads thre are in the system? >> I think you will have to extract this information frome the zone allocator. > how to do it practically? >> I just realised there is no effective limit on kernel threads in the system. >> probably one could cause this with a fork bomb appoach using forks and >> thread creation. > what can be staying in this fork bomb? soft running on this system [19] [root@ic]~#ls /usr/local/etc/rc.d/ apache.sh mysql-server snmpd squid innd radiusd.sh snmptrapd [20] [root@ic]~#cat /etc/libmap.conf cat: /etc/libmap.conf: No such file or directory -- wbr, slava [vovk-uanic] From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 20:03:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5C8B216A4DA; Fri, 1 Sep 2006 20:03:38 +0000 (UTC) (envelope-from prvs=julian=392b3a9d5@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 203D543D45; Fri, 1 Sep 2006 20:03:37 +0000 (GMT) (envelope-from prvs=julian=392b3a9d5@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 01 Sep 2006 13:03:37 -0700 Message-ID: <44F89218.9050400@elischer.org> Date: Fri, 01 Sep 2006 13:03:36 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kip Macy References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 20:03:38 -0000 Kip Macy wrote: > I've seen this when running stress2 with a large number of > incarnations. Why don't we return an error to the user? programmer ENOTIME patch welcome! > > -Kip > > On 9/1/06, Julian Elischer wrote: > >> Vyacheslav Vovk wrote: >> >> can you see how many threads thre are in the system? >> I think you will have to extract this information frome the zone >> allocator. >> >> I just realised there is no effective limit on kernel threads in the >> system. >> probably one could cause this with a fork bomb appoach using forks and >> thread creation. >> >> >Unread portion of the kernel message buffer: >> >panic: vm_thread_new: kstack allocation failed >> >cpuid = 3 >> >Uptime: 7d4h30m58s >> > >> > >> > >> _______________________________________________ >> 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" >> > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to > "freebsd-threads-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 20:50:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 BD92216A4DA for ; Fri, 1 Sep 2006 20:50:47 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66AD243D72 for ; Fri, 1 Sep 2006 20:50:39 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so623894nzn for ; Fri, 01 Sep 2006 13:50:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lP0NsDqZWqXZ6lr9okkGfdUAopMgR+2tdFOpjcYjmjVNSKMwU8TbTmtOfL2WIOGSHdTaw/pezaPPkg9Ytm9rfhmbmwqS7IONWDQQnoXhIXy0ipbPPcsPiqf1ZEhROVfKkik+caMwZ69eMSPezoqE2AGjtyOpRgpdixAm9bR9m38= Received: by 10.65.211.13 with SMTP id n13mr3250659qbq; Fri, 01 Sep 2006 13:50:38 -0700 (PDT) Received: by 10.65.224.1 with HTTP; Fri, 1 Sep 2006 13:50:38 -0700 (PDT) Message-ID: Date: Fri, 1 Sep 2006 13:50:38 -0700 From: "Kip Macy" To: "Julian Elischer" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200609011716.30749.vovk@km.ua> <44F85F63.5020508@elischer.org> Cc: Vyacheslav Vovk , freebsd-stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: panic: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 20:50:47 -0000 On closer inspection this means that we've run out of KVA. In principle it should be handled more gracefully, but the 1GB KVA limitation is really a 32-bit artifact. It might be worth wading through the kernel memory allocations to see if a subsystem has gone beserk. -Kip On 9/1/06, Kip Macy wrote: > I've seen this when running stress2 with a large number of > incarnations. Why don't we return an error to the user? > > -Kip > > On 9/1/06, Julian Elischer wrote: > > Vyacheslav Vovk wrote: > > > > can you see how many threads thre are in the system? > > I think you will have to extract this information frome the zone allocator. > > > > I just realised there is no effective limit on kernel threads in the system. > > probably one could cause this with a fork bomb appoach using forks and > > thread creation. > > > > >Unread portion of the kernel message buffer: > > >panic: vm_thread_new: kstack allocation failed > > >cpuid = 3 > > >Uptime: 7d4h30m58s > > > > > > > > > > > _______________________________________________ > > 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" > > > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 1 23:02:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 E3DA916A4DF; Fri, 1 Sep 2006 23:02:08 +0000 (UTC) (envelope-from dandee@hellteam.net) Received: from pipa.vshosting.cz (pipa.vshosting.cz [81.0.201.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB6C743D6B; Fri, 1 Sep 2006 23:01:55 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from localhost (localhost [127.0.0.1]) by pipa.vshosting.cz (Postfix) with ESMTP id 0D4D34E791; Sat, 2 Sep 2006 01:01:56 +0200 (CEST) Received: from pipa.vshosting.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14458-08; Sat, 2 Sep 2006 01:01:55 +0200 (CEST) Received: from gandalf (unknown [81.0.245.205]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.vshosting.cz (Postfix) with ESMTP id 5B55C4E708; Sat, 2 Sep 2006 01:01:55 +0200 (CEST) From: =?iso-8859-2?Q?Daniel_Dvo=F8=E1k?= To: Date: Sat, 2 Sep 2006 01:01:53 +0200 Message-ID: <00f701c6ce1a$9d9ea810$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00F8_01C6CE2B.61277810" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AcbOGp1LGXCGck2eRB6NFWk6pbgwQQ== X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: watchdogd_flags followed by panic watchdog timeout, after reboot my rc.conf disappear X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 23:02:09 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00F8_01C6CE2B.61277810 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Hi all, =20 first of all, I=B4m sorry maybe for my bad English. =20 We have 2 routers which I maintain in our mesh wireless community = network. =20 The Router 1 has 2 atheros adapters, ath0=3Dwistron cm9, ath1=3Dwistron = cm10, of course some sisX, fxpX and so on. The Router 2 has 1 atheros adapter, ath0=3Dwistron CM10. =20 My R1 panics and even more it freezes very often. Maybe the reason for panicing and freezing is the same and maybe not. =20 This is not important now, this story is about R2. =20 I started to use "option SW_WATCHDOG" in both my custom kernels on the = R1 and R2 recently in hope, it is some walkaround for freezing at least if = not for panicing. =20 In the /etc/defaults/rc.conf there are not "watchdogd_flags=3D""" = option, but I tried to wrote it to my /etc/rc.conf in this way: =20 watchdogd_enable=3D"YES" watchdogd_flags=3D"-e ping 10.40.0.72 -s 2 -t 1" =20 I saved my rc.conf without any doubt. =20 I did so, because I wanted to instruct watchdogd to execute my command, common pinging some IP address. I was not satisfied with a trivial file system check instead. =20 After saving the rc.conf file, I restarted watchdogd deamon at once. =20 ... and ... 2 seconds ... my ssh client was disconnected ... unexpected = end of ssh session. :) =20 Okay, maybe something wrong, maybe I did a mistake and it panicked. =20 I was waitting for 3 minutes, but R2 did not react at all. =20 So I went to R2 and I powered off and powered on ... but still it was = the same. =20 After I attached monitor and keyboard, I saw that ifconfig did not = configure any interfaces. Why ? =20 Answear: Because rc.conf had 0 Bytes !!! =20 -rw-r--r-- 1 root wheel 6174 Sep 1 XX:XX rc.conf , I do not = remember time of last modification of file. =20 So the content of rc.conf was completly gone !!! =20 Is it possible at all ? =20 Now I am scared that any modification rc.conf will be mean loss of = content. =20 I have kernel dump and backtrace of panic. =20 It is in the attachment. =20 =20 If I could help with this, I will do it. =20 And please explain me somebody, how I lost the content of rc.conf file. = :-O Thank you. =20 Daniel =20 P.S.: I am not currently subscribed in the freebsd-stable mailling list, = so use my e-mail address. I am ok with freebsd-current mailling list. ------=_NextPart_000_00F8_01C6CE2B.61277810 Content-Type: text/plain; name="backtrace panic.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="backtrace panic.txt" # cd /usr/obj/usr/src/sys/mykernel/ # kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: = /usr/lib/libthread_db.so: Unde = fined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain = conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: interrupt total irq14: ata0 325735 irq16: fxp1 5 irq17: ath0 50298459 irq18: wi0 3904083 irq19: sis0 fxp0 20167051 cpu0: timer 604044908 Total 678740241 panic: watchdog timeout Uptime: 3d11h53m45s Dumping 223 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 223MB (57072 pages) 207 191 175 159 143 127 111 95 79 63 47 = 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:165 #1 0xc059c4ee in boot (howto=3D260) at = /usr/src/sys/kern/kern_shutdown.c:402 #2 0xc059c7a6 in panic (fmt=3D0xc081050d "watchdog timeout") at /usr/src/sys/kern/kern_shutdown.c:558 #3 0xc0571642 in watchdog_fire () at /usr/src/sys/kern/kern_clock.c:583 #4 0xc0571130 in hardclock (frame=3D0xc1f44780) at /usr/src/sys/kern/kern_clock.c:279 #5 0xc07a4631 in lapic_handle_timer (frame=3D {cf_vec =3D 0, cf_fs =3D 8, cf_es =3D 40, cf_ds =3D 40, cf_edi =3D = -1040320488, cf_esi =3D -1040320512, cf_ebp =3D -890192676, cf_ebx =3D = 0, cf_edx =3D 0, cf_ecx =3D -1041016416, cf_eax =3D 1000, cf_eip =3D = -1063283195, cf_cs =3D 32, cf_eflags =3D 524818, cf_esp =3D -890192644, = cf_ss =3D -1063305969}) at /usr/src/sys/i386/i386/local_apic.c:623 #6 0xc079eb30 in Xtimerint () at apic_vector.s:137 #7 0xc09f9605 in ?? () #8 0xcaf0bd04 in ?? () #9 0xc07a609f in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1134 Previous frame inner to this frame (corrupt stack?) (kgdb) quit ------=_NextPart_000_00F8_01C6CE2B.61277810-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 01:21:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 911C716A4E6; Sat, 2 Sep 2006 01:21:16 +0000 (UTC) (envelope-from dandee@hellteam.net) Received: from pipa.vshosting.cz (pipa.vshosting.cz [81.0.201.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746BE43D4C; Sat, 2 Sep 2006 01:21:14 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from localhost (localhost [127.0.0.1]) by pipa.vshosting.cz (Postfix) with ESMTP id B6CC34E794; Sat, 2 Sep 2006 03:21:14 +0200 (CEST) Received: from pipa.vshosting.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00775-03; Sat, 2 Sep 2006 03:21:12 +0200 (CEST) Received: from gandalf (unknown [81.0.245.205]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.vshosting.cz (Postfix) with ESMTP id 961BF4E790; Sat, 2 Sep 2006 03:21:11 +0200 (CEST) From: =?iso-8859-2?Q?Daniel_Dvo=F8=E1k?= To: Date: Sat, 2 Sep 2006 03:21:05 +0200 Message-ID: <001e01c6ce2e$1253ff30$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_001F_01C6CE3E.D5DCCF30" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbOGp1LGXCGck2eRB6NFWk6pbgwQQACHOdQAAK5H0A= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: atheros driver under high load, panics and even more freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 01:21:16 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Hi all, =20 first of all, I=B4m sorry maybe for my bad English. =20 We have 2 routers which I maintain in our mesh wireless community = network. =20 The Router 1 has 2 atheros adapters, ath0=3Dwistron cm9, ath1=3Dwistron = cm10, of course some sisX, fxpX and so on. The Router 2 has 1 atheros adapter, ath1=3Dwistron CM10. =20 My R1 panics and even more it freezes very often. Maybe the reason for panicing and freezing is the same and maybe not. =20 I started (only after vmcore.5, so vmcore.6 is with this option) to = use "option SW_WATCHDOG" in both my custom kernels on the R1 and R2 recently = in hope, it is some walkaround for freezing at least if not for panicing.=20 =20 This router was installed on the 1st of April 2006. =20 Statistics: =20 9 panics with 8 kernel dumps, 1 missed =20 10 freezes =20 I think that all panics some how connected to athX taskq process, page = fault in kernel panic and sbflush_locked. =20 I guess that panic comes when router transmits and receives datas at the maximum throughput for setted nominal media rate speed, exactly 24Mbps, = more I do not use, because there are problems with quagga=20 =20 ospfd packets, it is known issue. =20 Today I did a small test with throughput. =20 Router 1 executed this command: =20 # ping -i 0.001 -c 100000 -s 1472 ANY IP =20 As you see, it is not even flood ping, it is almost flood, but not = flood. =20 Throughput was about 1,13-1,2 MB/s as bmon showed me. I notice there is = not any qos and icmp.limit is so high net.inet.icmp.icmplim: 2147483647 net.ineticmp.icmplim_output: 0. =20 First 5 s latency was about 1,1-1,7 ms After it goes to 10-30, 50-70, 110-130, 270-300, up 300ms and packet = loss =20 .... some seconds .... =20 panic =20 =20 here it is: =20 # kgdb kernel.debug /var/crash/vmcore.6 [GDB will not be able to debug user-mode threads: = /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "i386-marcel-freebsd". =20 Unread portion of the kernel message buffer: =20 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc05a47bb stack pointer =3D 0x28:0xd447db18 frame pointer =3D 0x28:0xd447db3c code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 24 (ath1 taskq) trap number =3D 12 panic: page fault Uptime: 1d7h56m6s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 = 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 = 15 =20 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:165 #1 0xc056da25 in boot (howto=3D260) at = /usr/src/sys/kern/kern_shutdown.c:402 #2 0xc056dcbc in panic (fmt=3D0xc07a4185 "%s") at /usr/src/sys/kern/kern_shutdown.c:558 #3 0xc07658c8 in trap_fatal (frame=3D0xd447dad8, eva=3D12) at /usr/src/sys/i386/i386/trap.c:836 #4 0xc076562f in trap_pfault (frame=3D0xd447dad8, usermode=3D0, = eva=3D12) at /usr/src/sys/i386/i386/trap.c:744 #5 0xc076528d in trap (frame=3D {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D -979275436, = tf_esi =3D 370, tf_ebp =3D -733488324, tf_isp =3D -733488380, tf_ebx =3D -979275520, = tf_edx =3D 0, tf_ecx =3D -1012252656, tf_eax =3D 0, tf_trapno =3D 12, tf_err =3D 0, = tf_eip =3D -1067825221, tf_cs =3D 32, tf_eflags =3D 590342, tf_esp =3D 0, tf_ss =3D -733488320}) at /usr/src/sys/i386/i386/trap.c:434 #6 0xc0754a6a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05a47bb in m_copym (m=3D0x0, off0=3D1500, len=3D1480, wait=3D1) = at /usr/src/sys/kern/uipc_mbuf.c:400 #8 0xc06204b8 in ip_fragment (ip=3D0xc3aa4010, m_frag=3D0xd447dbec, mtu=3D-979275520, if_hwassist_flags=3D0, sw_csum=3D1) at /usr/src/sys/netinet/ip_output.c:975 #9 0xc0610c4e in ip_fastforward (m=3D0xc3a7ba00) at /usr/src/sys/netinet/ip_fastfwd.c:561 #10 0xc05de953 in ether_demux (ifp=3D0xc33ac400, m=3D0xc3a7ba00) at /usr/src/sys/net/if_ethersubr.c:766 #11 0xc05de715 in ether_input (ifp=3D0xc33ac400, m=3D0xc3a7ba00) at /usr/src/sys/net/if_ethersubr.c:620 #12 0xc05f5604 in ieee80211_deliver_data (ic=3D0xc33ad230, = ni=3D0xc5602000, m=3D0xc3a7ba00) at /usr/src/sys/net80211/ieee80211_input.c:717 #13 0xc05f507d in ieee80211_input (ic=3D0xc33ad230, m=3D0xc3a7ba00, ni=3D0xc5602000, rssi=3D30, rstamp=3D27616) at /usr/src/sys/net80211/ieee80211_input.c:481 #14 0xc04afd66 in ath_rx_proc (arg=3D0xc33ad000, npending=3D1) at /usr/src/sys/dev/ath/if_ath.c:2977 #15 0xc058de89 in taskqueue_run (queue=3D0xc32f4780) at /usr/src/sys/kern/subr_taskqueue.c:217 #16 0xc058e03a in taskqueue_thread_loop (arg=3D0x0) at /usr/src/sys/kern/subr_taskqueue.c:276 #17 0xc0558068 in fork_exit (callout=3D0xc058dff8 = , arg=3D0xc33adee0, frame=3D0xd447dd38) at = /usr/src/sys/kern/kern_fork.c:805 #18 0xc0754acc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) quit =20 =20 I notice packets were send out through ath0, so I expect ath0 taskq, = through ath1 I was logged in the box. =20 I can reproduce it with ping command, with high load. =20 =20 There are earlier kernel dumps which is connected to high load some how, = but kgdb does not work with them. =20 # kgdb kernel.debug /var/crash/vmcore.0 kgdb: kvm_read: invalid address (0x18) kgdb: kvm_read: invalid address (0x18) kgdb: kvm_read: invalid address (0x18) ^C =20 # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.2 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.3 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.4 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.5 kgdb: cannot read PTD =20 I have info=B4s files, here they are in attachments. =20 =20 I guess it is about mem_buf, ath.c, ath taskq, something about memory, = when there is HIGH LOAD. =20 ANY HELP IS VERY APPRECIATED. =20 Daniel =20 P.S.: I am not currently subscribed in the freebsd-stable mailling list, = so use my e-mail address. I am ok with freebsd-current mailling list. ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="info.0-5, kgdb not worked on them.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="info.0-5, kgdb not worked on them.txt" # kgdb kernel.debug /var/crash/vmcore.0 kgdb: kvm_read: invalid address (0x18) kgdb: kvm_read: invalid address (0x18) kgdb: kvm_read: invalid address (0x18) ^C # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.1 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.2 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.3 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.4 kgdb: cannot read PTD # kgdb kernel.debug /var/crash/vmcore.5 kgdb: cannot read PTD # cat info.0 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Mon May 22 01:24:01 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE #0: Wed May 10 14:02:17 CEST 2006 Panic String: page fault Dump Parity: 3252354328 Bounds: 0 Dump Status: good # cat info.1 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Fri Jun 16 18:01:27 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p2 #2: Fri Jun 16 02:17:00 CEST 2006 Panic String: ffs_blkfree: freeing free block Dump Parity: 3481480040 Bounds: 1 Dump Status: good # cat info.2 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Wed Jun 28 23:08:28 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p2 #4: Mon Jun 26 14:36:29 CEST 2006 Panic String: sbflush_locked: cc 0 || mb 0xc23e7500 || mbcnt 2304 Dump Parity: 2760206361 Bounds: 2 Dump Status: good # cat info.3 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Thu Jun 29 09:25:44 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p2 #4: Mon Jun 26 14:36:29 CEST 2006 Panic String: page fault Dump Parity: 1992958036 Bounds: 3 Dump Status: good # cat info.4 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Sat Jul 1 14:02:53 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p2 #4: Mon Jun 26 14:36:29 CEST 2006 Panic String: page fault Dump Parity: 1663968596 Bounds: 4 Dump Status: good # cat info.5 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Sat Aug 12 03:01:25 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p2 #4: Mon Jun 26 14:36:29 CEST 2006 Panic String: page fault Dump Parity: 1801608788 Bounds: 5 Dump Status: good ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="info.6-7, kgdb worked.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="info.6-7, kgdb worked.txt" # cat info.6 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 536412160B (511 MB) Blocksize: 512 Dumptime: Fri Sep 1 21:44:58 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p5 #0: Tue Aug 29 03:09:23 CEST 2006 Panic String: page fault Dump Parity: 2714335061 Bounds: 6 Dump Status: good # cat info.7 Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 536412160B (511 MB) Blocksize: 512 Dumptime: Fri Sep 1 21:49:55 2006 Hostname: Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-RELEASE-p5 #0: Tue Aug 29 03:09:23 CEST 2006 Panic String: watchdog timeout Dump Parity: 4123728435 Bounds: 7 Dump Status: good ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="kgdb backtrace vmcore.6 and 7.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="kgdb backtrace vmcore.6 and 7.txt" # kgdb kernel.debug /var/crash/vmcore.6 [GDB will not be able to debug user-mode threads: = /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain = conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc05a47bb stack pointer =3D 0x28:0xd447db18 frame pointer =3D 0x28:0xd447db3c code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 24 (ath1 taskq) trap number =3D 12 panic: page fault Uptime: 1d7h56m6s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 = 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 = 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:165 #1 0xc056da25 in boot (howto=3D260) at = /usr/src/sys/kern/kern_shutdown.c:402 #2 0xc056dcbc in panic (fmt=3D0xc07a4185 "%s") at = /usr/src/sys/kern/kern_shutdown.c:558 #3 0xc07658c8 in trap_fatal (frame=3D0xd447dad8, eva=3D12) at = /usr/src/sys/i386/i386/trap.c:836 #4 0xc076562f in trap_pfault (frame=3D0xd447dad8, usermode=3D0, = eva=3D12) at /usr/src/sys/i386/i386/trap.c:744 #5 0xc076528d in trap (frame=3D {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D -979275436, = tf_esi =3D 370, tf_ebp =3D -733488324, tf_isp =3D -733488380, tf_ebx =3D = -979275520, tf_edx =3D 0, tf_ecx =3D -1012252656, tf_eax =3D 0, = tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -1067825221, tf_cs =3D 32, = tf_eflags =3D 590342, tf_esp =3D 0, tf_ss =3D -733488320}) at /usr/src/sys/i386/i386/trap.c:434 #6 0xc0754a6a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05a47bb in m_copym (m=3D0x0, off0=3D1500, len=3D1480, wait=3D1) = at /usr/src/sys/kern/uipc_mbuf.c:400 #8 0xc06204b8 in ip_fragment (ip=3D0xc3aa4010, m_frag=3D0xd447dbec, = mtu=3D-979275520, if_hwassist_flags=3D0, sw_csum=3D1) at = /usr/src/sys/netinet/ip_output.c:975 #9 0xc0610c4e in ip_fastforward (m=3D0xc3a7ba00) at = /usr/src/sys/netinet/ip_fastfwd.c:561 #10 0xc05de953 in ether_demux (ifp=3D0xc33ac400, m=3D0xc3a7ba00) at = /usr/src/sys/net/if_ethersubr.c:766 #11 0xc05de715 in ether_input (ifp=3D0xc33ac400, m=3D0xc3a7ba00) at = /usr/src/sys/net/if_ethersubr.c:620 #12 0xc05f5604 in ieee80211_deliver_data (ic=3D0xc33ad230, = ni=3D0xc5602000, m=3D0xc3a7ba00) at = /usr/src/sys/net80211/ieee80211_input.c:717 #13 0xc05f507d in ieee80211_input (ic=3D0xc33ad230, m=3D0xc3a7ba00, = ni=3D0xc5602000, rssi=3D30, rstamp=3D27616) at = /usr/src/sys/net80211/ieee80211_input.c:481 #14 0xc04afd66 in ath_rx_proc (arg=3D0xc33ad000, npending=3D1) at = /usr/src/sys/dev/ath/if_ath.c:2977 #15 0xc058de89 in taskqueue_run (queue=3D0xc32f4780) at = /usr/src/sys/kern/subr_taskqueue.c:217 #16 0xc058e03a in taskqueue_thread_loop (arg=3D0x0) at = /usr/src/sys/kern/subr_taskqueue.c:276 #17 0xc0558068 in fork_exit (callout=3D0xc058dff8 = , arg=3D0xc33adee0, frame=3D0xd447dd38) at = /usr/src/sys/kern/kern_fork.c:805 #18 0xc0754acc in fork_trampoline () at = /usr/src/sys/i386/i386/exception.s:208 (kgdb) quit # kgdb kernel.debug /var/crash/vmcore.7 [GDB will not be able to debug user-mode threads: = /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain = conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: interrupt total irq14: ata0 34029 irq17: ath0 329111 irq18: ath1 165989 irq19: rl0 15153 irq21: uhci0 ehci0 735 irq23: vr0 110085 cpu0: timer 443218 Total 1098320 panic: watchdog timeout Uptime: 3m42s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 = 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 = 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:165 #1 0xc056da25 in boot (howto=3D260) at = /usr/src/sys/kern/kern_shutdown.c:402 #2 0xc056dcbc in panic (fmt=3D0xc07ae613 "watchdog timeout") at = /usr/src/sys/kern/kern_shutdown.c:558 #3 0xc0543e86 in watchdog_fire () at /usr/src/sys/kern/kern_clock.c:583 #4 0xc05439a5 in hardclock (frame=3D0xc3884900) at = /usr/src/sys/kern/kern_clock.c:279 #5 0xc075a68d in lapic_handle_timer (frame=3D {cf_vec =3D 0, cf_fs =3D 8, cf_es =3D 40, cf_ds =3D 40, cf_edi =3D = -1015050576, cf_esi =3D -1018397184, cf_ebp =3D -660935872, cf_ebx =3D = -1018397184, cf_edx =3D 116, cf_ecx =3D -1065296032, cf_eax =3D = -1416560640, cf_eip =3D -1067795618, cf_cs =3D 32, cf_eflags =3D 663, = cf_esp =3D -1015530112, cf_ss =3D -1014478592}) at /usr/src/sys/i386/i386/local_apic.c:623 #6 0xc0755050 in Xtimerint () at apic_vector.s:137 #7 0xc05abb5e in sbcompress (sb=3D0xc37f8eb0, m=3D0xc34c7e00, = n=3D0xc34c7e00) at /usr/src/sys/kern/uipc_socket2.c:1091 #8 0xc05ab2fb in sbappendstream_locked (sb=3D0xc37f8eb0, = m=3D0xc34c7e00) at /usr/src/sys/kern/uipc_socket2.c:745 #9 0xc05ab345 in sbappendstream (sb=3D0xc37f8eb0, m=3D0xc34c7e00) at = /usr/src/sys/kern/uipc_socket2.c:761 #10 0xc0630fc0 in tcp_usr_send (so=3D0xc37f8de8, flags=3D0, = m=3D0xc34c7e00, nam=3D0x0, control=3D0x0, td=3D0xc3884900) at = /usr/src/sys/netinet/tcp_usrreq.c:665 #11 0xc05a7c0b in sosend (so=3D0xc37f8de8, addr=3D0x0, uio=3D0xd89aecbc, = top=3D0xc34c7e00, control=3D0x0, flags=3D0, td=3D0xc3884900) at /usr/src/sys/kern/uipc_socket.c:836 #12 0xc0596152 in soo_write (fp=3D0xab910000, uio=3D0xd89aecbc, = active_cred=3D0xc3783d80, flags=3D0, td=3D0xc3884900) at = /usr/src/sys/kern/sys_socket.c:118 #13 0xc05908bb in dofilewrite (td=3D0xc3884900, fd=3D3, fp=3D0xc37f9000, = auio=3D0xd89aecbc, offset=3DUnhandled dwarf expression opcode 0x93 ) at file.h:246 #14 0xc059075f in kern_writev (td=3D0xc3884900, fd=3D3, = auio=3D0xd89aecbc) at /usr/src/sys/kern/sys_generic.c:402 #15 0xc0590685 in write (td=3D0xc3884900, uap=3D0xc080df60) at = /usr/src/sys/kern/sys_generic.c:326 #16 0xc0765bdf in syscall (frame=3D {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 134715936, = tf_esi =3D 134681128, tf_ebp =3D -1077943096, tf_isp =3D -660935324, = tf_ebx =3D 671931192, tf_edx =3D 134681128, tf_ecx =3D 3, tf_eax =3D 4, = tf_trapno =3D 0, tf_err =3D 2, tf_eip =3D 674475811, tf_cs =3D 51, = tf_eflags =3D 646, tf_esp =3D -1077943124, tf_ss =3D 59}) at /usr/src/sys/i386/i386/trap.c:981 #17 0xc0754abf in Xint0x80_syscall () at = /usr/src/sys/i386/i386/exception.s:200 #18 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) quit ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="sysctl.conf - R1.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="sysctl.conf - R1.txt" # cat /etc/sysctl.conf # $FreeBSD: src/etc/sysctl.conf,v 1.8 2003/03/13 18:43:50 mux Exp $ # # This file is read when going to multi-user and its contents piped = thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for = details. # # Uncomment this to prevent users from seeing information about = processes that # are being run under another UID. #security.bsd.see_other_uids=3D0 # IFS parametry Atheros distance 1730m and 3440m dev.ath.0.slottime=3D15 dev.ath.0.acktimeout=3D33 dev.ath.0.ctstimeout=3D33 dev.ath.0.txantenna=3D1 dev.ath.0.rxantenna=3D1 dev.ath.0.diversity=3D0 #dev.ath.0.tpscale=3D0 #dev.ath.0.tpc=3D0 dev.ath.1.slottime=3D21 dev.ath.1.acktimeout=3D45 dev.ath.1.ctstimeout=3D45 dev.ath.1.txantenna=3D1 dev.ath.1.rxantenna=3D1 dev.ath.1.diversity=3D0 #dev.ath.1.tpscale=3D0 #dev.ath.1.tpc=3D0 kern.ipc.maxsockbuf=3D2097152 #net.inet6.ip6.forwarding=3D1 net.inet.ip.fastforwarding=3D1 net.inet.tcp.sendspace=3D65536 #net.inet.tcp.rfc1323=3D1 net.inet.icmp.icmplim=3D2147483647 net.inet.icmp.icmplim_output=3D0 net.inet.ip.random_id=3D1 ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="ifconfig - R1.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ifconfig - R1.txt" # ifconfig -v ath0: flags=3D8843 mtu 1500 inet6 fe80::20b:6bff:fe35:509a%ath0 prefixlen 64 scopeid 0x1 inet 10.40.192.17 netmask 0xfffffffc broadcast 10.40.192.19 ether 00:0b:6b:35:50:9a media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11a = (OFDM/24Mbps) status: associated ssid PtPa channel 100 (5500) bssid 00:00:00:00:00:00 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 38 txpower 63 rtsthreshold 2346 mcastrate 1 fragthreshold 2346 pureg protmode OFF wme burst roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ath1: flags=3D8843 mtu 1500 inet6 fe80::20b:6bff:fe2a:b8d5%ath1 prefixlen 64 scopeid 0x2 inet 10.40.64.17 netmask 0xfffffffc broadcast 10.40.64.19 ether 00:0b:6b:2a:b8:d5 media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11a = (OFDM/24Mbps) status: associated ssid PtP channel 108 (5540) bssid 00:00:00:00:00:00 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 37 txpower 63 rtsthreshold 2346 mcastrate 1 fragthreshold 2346 pureg protmode OFF wme burst roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="uname - R1.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="uname - R1.txt" # uname -a FreeBSD * 6.1-RELEASE-p5 FreeBSD 6.1-RELEASE-p5 #0: Tue Aug 29 03:09:23 = CEST 2006 *:/usr/obj/usr/src/sys/* i386 ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="pciconf - R1.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="pciconf - R1.txt" this ath0 is old CM9: ath0@pci0:14:0: class=3D0x020000 card=3D0x1012185f chip=3D0x0013168c = rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class =3D network subclass =3D ethernet this ath1 is new CM10: ath1@pci0:19:0: class=3D0x020000 card=3D0x1600185f chip=3D0x001b168c = rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' class =3D network subclass =3D ethernet BTW: Does somebody know where device information is ? :) ------=_NextPart_000_001F_01C6CE3E.D5DCCF30 Content-Type: text/plain; name="dmesg -a - R1.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg -a - R1.txt" Copyright (c) 1992-2006 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 6.1-RELEASE-p5 #0: Tue Aug 29 03:09:23 CEST 2006 *:/usr/obj/usr/src/sys/* Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) (800.03-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x631 Stepping =3D 1 = Features=3D0x183fbff AMD Features=3D0xc0440800,MMX+,3DNow+,3DNow> real memory =3D 536805376 (511 MB) avail memory =3D 515940352 (492 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 netsmb_dev: loaded ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, = RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem = 0xe0000000-0xe1ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) ath0: mem 0xdfff0000-0xdfffffff irq 17 at device 6.0 on = pci0 ath0: Ethernet address: 00:0b:6b:35:50:9a ath0: mac 5.9 phy 4.3 radio 3.6 ath1: mem 0xdffe0000-0xdffeffff irq 18 at device 7.0 on = pci0 ath1: Ethernet address: 00:0b:6b:2a:b8:d5 ath1: mac 10.5 phy 6.1 radio 6.3 rl0: port 0xec00-0xecff mem = 0xdffdff00-0xdffdffff irq 19 at device 8.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:50:fc:e4:c4:b6 uhci0: port 0xe800-0xe81f irq 21 at device = 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ehci0: mem 0xdffdfe00-0xdffdfeff irq 21 = at device 16.3 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 2 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 vr0: port 0xe400-0xe4ff mem = 0xdffdfd00-0xdffdfdff irq 23 at device 18.0 on pci0 miibus1: on vr0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:0c:76:1c:aa:b7 acpi_button1: on acpi0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcb7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ugen0: American Power Conversion Back-UPS RS 500 FW:30.j5.I USB FW:j5, = rev 1.10/0.06, addr 2 Timecounter "TSC" frequency 800032669 Hz quality 800 Timecounters tick every 1.000 msec IPv6 packet filtering initialized, default to accept, logging limited to = 100 packets/entry ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding = enabled, default to accept, logging limited to 100 packets/entry by = default ad0: 76319MB at ata0-master UDMA100 Trying to mount root from ufs:/dev/ad0s1a ------=_NextPart_000_001F_01C6CE3E.D5DCCF30-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 02:19:27 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 D1B5816A4DE for ; Sat, 2 Sep 2006 02:19:27 +0000 (UTC) (envelope-from ariff@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D5EB43D46; Sat, 2 Sep 2006 02:19:27 +0000 (GMT) (envelope-from ariff@FreeBSD.org) Received: from misaki (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with SMTP id k822JPOx080437; Sat, 2 Sep 2006 02:19:26 GMT (envelope-from ariff@FreeBSD.org) Date: Sat, 2 Sep 2006 10:18:51 +0800 From: Ariff Abdullah To: "S. M. Ibrahim (Lavlu)" Message-Id: <20060902101851.16b9f7be.ariff@FreeBSD.org> In-Reply-To: <1157124365.3048.5.camel@shanazsoft.com> References: <1157124365.3048.5.camel@shanazsoft.com> Organization: FreeBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sat__2_Sep_2006_10_18_51_+0800_l4ZhX6xceunT6D=w" Cc: freebsd-stable@FreeBSD.org Subject: Re: sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 02:19:27 -0000 --Signature=_Sat__2_Sep_2006_10_18_51_+0800_l4ZhX6xceunT6D=w Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 01 Sep 2006 21:26:05 +0600 "S. M. Ibrahim (Lavlu)" wrote: > i am totally new with freeBSD 6.1 > I installed it yesterday. Everything goes ok, but problem with sound > card, It's a builtin Intl HDA on gigabyte 915G-DU motherboard. > I added the line=20 >=20 > sound_load=3D"YES" > snd_driver_load=3D"YES" > snd_cmi_load=3D"YES" >=20 > to /boot/loader.conf but sound is not working. >=20 > Moreover how to access administrativ app from GUI. >=20 Intel HDA isn't supported, yet. A proper driver is in the making. In the meantime, you can try free driver from http://www.opensound.com/ . Stay tune. -- Ariff Abdullah FreeBSD --Signature=_Sat__2_Sep_2006_10_18_51_+0800_l4ZhX6xceunT6D=w Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE+OoQlr+deMUwTNoRAt+gAJ9ysspjC8kiXsxEyd6QmMCdjwHDAACgzJGV +0gtGlP3DoILUleJm4R66TY= =EXtp -----END PGP SIGNATURE----- --Signature=_Sat__2_Sep_2006_10_18_51_+0800_l4ZhX6xceunT6D=w-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 03:59:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9ECC516A4DA; Sat, 2 Sep 2006 03:59:54 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3005243D46; Sat, 2 Sep 2006 03:59:54 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.199] ([10.0.0.199]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k823xqYO037249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Sep 2006 20:59:53 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44F901B9.3040309@errno.com> Date: Fri, 01 Sep 2006 20:59:53 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: dandee@volny.cz References: <001e01c6ce2e$1253ff30$6508280a@tocnet28.jspoj.czf> In-Reply-To: <001e01c6ce2e$1253ff30$6508280a@tocnet28.jspoj.czf> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, current@freebsd.org Subject: Re: atheros driver under high load, panics and even more freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 03:59:54 -0000 Daniel Dvoøák wrote: > Hi all, > > first of all, I´m sorry maybe for my bad English. > > We have 2 routers which I maintain in our mesh wireless community network. > > The Router 1 has 2 atheros adapters, ath0=wistron cm9, ath1=wistron cm10, of > course some sisX, fxpX and so on. > The Router 2 has 1 atheros adapter, ath1=wistron CM10. > > My R1 panics and even more it freezes very often. Maybe the reason for > panicing and freezing is the same and maybe not. > > I started (only after vmcore.5, so vmcore.6 is with this option) to use > "option SW_WATCHDOG" in both my custom kernels on the R1 and R2 recently in > hope, it is some walkaround for freezing at least if not for panicing. > > This router was installed on the 1st of April 2006. > > Statistics: > > 9 panics with 8 kernel dumps, 1 missed > > 10 freezes > > I think that all panics some how connected to athX taskq process, page fault > in kernel panic and sbflush_locked. Why? > > I guess that panic comes when router transmits and receives datas at the > maximum throughput for setted nominal media rate speed, exactly 24Mbps, more > I do not use, because there are problems with quagga > > ospfd packets, it is known issue. > > Today I did a small test with throughput. > > Router 1 executed this command: > > # ping -i 0.001 -c 100000 -s 1472 ANY IP > > As you see, it is not even flood ping, it is almost flood, but not flood. > > Throughput was about 1,13-1,2 MB/s as bmon showed me. I notice there is not > any qos and icmp.limit is so high net.inet.icmp.icmplim: 2147483647 > net.ineticmp.icmplim_output: 0. > > > First 5 s latency was about 1,1-1,7 ms > After it goes to 10-30, 50-70, 110-130, 270-300, up 300ms and packet loss > > .... some seconds .... > > panic <...lots of stuff deleted...> Sounds like a resource leak to me. You've got crash dumps, look at memory usage with vmstat and/or netstat. Past that it sounds like you're running 6.1 RELEASE which is now 6+ months old. Many bugs have been fixed including, I believe, some resource-related ones. Please try 6-STABLE. Sam From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 04:31:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 4C40616A4DE for ; Sat, 2 Sep 2006 04:31:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 471FB43D49 for ; Sat, 2 Sep 2006 04:31:49 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 6776 invoked by uid 399); 2 Sep 2006 04:31:48 -0000 Received: from localhost (HELO ?192.168.0.10?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 2 Sep 2006 04:31:48 -0000 Message-ID: <44F9093A.5040001@FreeBSD.org> Date: Fri, 01 Sep 2006 21:31:54 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Fwd: cvs commit: src/libexec/save-entropy save-entropy.sh] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 04:31:50 -0000 FYI, I just MFC'ed this change to RELENG_6. I do not plan to MFC it to RELENG_5. I believe this will help avoid the symptoms of the most common user errors that we see complaints about on the mailing list, and my personal mailbox. I tested the changes thoroughly on both HEAD and RELENG_6, so I do not anticipate any problems, but please consider this a mini-heads up. Doug -- This .signature sanitized for your protection -------- Original Message -------- Subject: cvs commit: src/libexec/save-entropy save-entropy.sh Date: Mon, 28 Aug 2006 06:41:50 +0000 (UTC) From: Doug Barton To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org dougb 2006-08-28 06:41:50 UTC FreeBSD src repository Modified files: libexec/save-entropy save-entropy.sh Log: 1. Attempt to take one bullet out of the foot-shooting gun by silently ignoring errors when sourcing rc.conf* files. The most common error occurs when users put a command of some sort into those files. (ifconfig is a popular choice) 2. Make the file rotation logic simpler by starting one down from the "top" of the list, rather than at the top. 3. Try to make file rotation more secure by calling unlink(1) on all new file names before rotating an old file to the new name, rather than merely calling 'rm -f' on any files that exceed the number of files to save. Revision Changes Path 1.4 +10 -10 src/libexec/save-entropy/save-entropy.sh http://www.FreeBSD.org/cgi/cvsweb.cgi/src/libexec/save-entropy/save-entropy.sh.diff?&r1=1.3&r2=1.4&f=h From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 09:23:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 CE53416A4DA for ; Sat, 2 Sep 2006 09:23:26 +0000 (UTC) (envelope-from umbilical.blisters@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBC0D43D4C for ; Sat, 2 Sep 2006 09:23:25 +0000 (GMT) (envelope-from umbilical.blisters@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1633587pye for ; Sat, 02 Sep 2006 02:23:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=ZnNYDfsgV9AEmDwpE5vmdFSSuGPgTlcC2cyh3mJIYNu3TtCsmabHCDBjcRJpph/W2pCIdfQvSvVbZExCtF8Yy24QJoi9+e1UsTTqdK1w4gWyylOFAkKIurhOhegG55Dfx94FnFwDXWaqW10UBMI9882dHtpnDR+b0tWe+mLIdDk= Received: by 10.35.94.1 with SMTP id w1mr5000802pyl; Sat, 02 Sep 2006 02:23:21 -0700 (PDT) Received: by 10.35.126.16 with HTTP; Sat, 2 Sep 2006 02:23:21 -0700 (PDT) Message-ID: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> Date: Sat, 2 Sep 2006 04:23:21 -0500 From: "Alex Salazar" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-current@freebsd.org Subject: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 09:23:27 -0000 Apologies for the long message, and thanks in advance for any response. I've just bought one of those new generation Dell servers, specifically, the PowerEdge 1950. This is a dual Intel Dual Core Xeon 5050, 3.0 GHz, 667MHz FSB, 1GB 533MHz RAM, system. This server has a LSI Logic SAS 5/i integrated adapter and dual embedded Broadcom NetXtreme II 5708 Gigabit Ethernet NIC. When I tried to install from a FreeBSD 6.0-RELEASE i386 CD I had at hand, no hard disc was detected. After finding out that SAS controller was not supported on that release, I grabbed the most recent 6.1-STABLE i386 snapshot (200608) and tried again. This time, the hard disc was detected properly. The installation succeeded and, after the post-install configuration, the system was restarted. The OS booted up and the SAS controller was now detected and supported by the mpt(4) driver: --- mpt0: port 0xec00-0xecff mem 0xfc4fc000-0xfc4fffff, 0xfc4e0000-0xfc4effff irq 64 at device 8.0 on pci2 mpt0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xec00 mpt0: Reserved 0x4000 bytes for rid 0x14 type 3 at 0xfc4fc000 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.12.0 --- And the related errors showed up immediately, for the first time: --- mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: MPI_EVENT_SAS_DEVICE_STATUS_CHANGE mpt0: mpt_cam_event: MPI_EVENT_SAS_DEVICE_STATUS_CHANGE mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). -- When the bootstrap process reached the SCSI probe, there were no activity on the screen for about five minutes, so I was forced to use the power off button, and after rebooting, the same symptoms were evident, so I rebooted the machine once again, this time in verbose mode. This debug information was being printed on the screen, one character at time, at about 1 char/sec: (probe8:mpt0:0:8:0): error 22 (probe8:mpt0:0:8:0): Unretryable Error (probe8:mpt0:0:8:0): error 22 (probe8:mpt0:0:8:0): Unretryable Error (probe0:mpt0:0:0:1): error 22 (probe0:mpt0:0:0:1): Unretryable Error (probe1:mpt0:0:8:1): Unexpected Bus Free (probe1:mpt0:0:8:1): Retrying Command ... (probe0:mpt0:0:8:7): Unexpected Bus Free (probe0:mpt0:0:8:7): Retrying Command (probe0:mpt0:0:8:7): Unexpected Bus Free (probe0:mpt0:0:8:7): Retrying Command (probe0:mpt0:0:8:7): Unexpected Bus Free (probe0:mpt0:0:8:7): Retrying Command (probe0:mpt0:0:8:7): Unexpected Bus Free (probe0:mpt0:0:8:7): Retrying Command (probe0:mpt0:0:8:7): Unexpected Bus Free (probe0:mpt0:0:8:7): error 5 (probe0:mpt0:0:8:7): Retries Exausted After 18 (eighteen) minutes, the error messages ceased, and the boot process continued as usually: --- pass0 at mpt0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-5 device pass0: Serial Number K40C1Q5K pass0: 300.000MB/s transfers, Tagged Queueing Enabled pass1 at mpt0 bus 0 target 8 lun 0 pass1: Fixed Enclosure Services SCSI-5 device pass1: 300.000MB/s transfers, Tagged Queueing Enabled ses0 at mpt0 bus 0 target 8 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers, Tagged Queueing Enabled ses0: SCSI-3 SES Device GEOM: new dida0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: Serial Number K40C1Q5K da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 70007MB (143374650 512 byte sectors: 255H 63S/T 8924C) --- As a workaround, I disabled the APICs (hint.apic.0.disabled), and that ~15 minutes delay at boot up, now was gone. Fine. (BTW, 7-CURRENT has the same problem, but without that huge delay) Once I was logged in the server, I proceeded to populate my ports tree, by using portsnap(8), so, when I extracted the tarball (portsnap extract), there was a lot of the following error message, at about 1 message per second: mpt0: Unhandled Event Notify Frame. Event 0xe (ACK not required). Once in a while, an error message like below, showed up: -- (da0:mpt0:0:0:0): WRITE(10). CDB: 2a 0 1 55 6f 5f 0 0 20 0 (da0:mpt0:0:0:0): CAM Status: SCSI Status Error (da0:mpt0:0:0:0): SCSI Status: Check Condition (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 (da0:mpt0:0:0:0): Scsi bus reset occurred -- After running some diagnostics included on some utilities CDs shipped with this server, I concluded this was a software issue: -- Device Name : SAS Disk 0:0 Description : SAS MAXTOR ATLAS15K2_073SAS Test Name : Disk Self Test Passes : 1 Result : passed Start Time : Mon Aug 21 02:04:06 2006 Completion Time : Mon Aug 21 02:26:12 2006 Result Event : The test operation completed successfully -- In order to perform those diagnostics, I had to install a SuSe Linux Enterprise Server 9, which was also shipped with this machine) After reinstalling FreeBSD, I logged remotely into the server, via ssh, and fetched the ports snapshot again and extracted once more. Suddenly, the screen activity ceased and the network connection timed out. Locally, on the server, there was a lot of mpt(4) errors and warnings. --- (da0:mpt0:0:0:0): CAM Status 0x18 (da0:mpt0:0:0:0): Retrying Command (... and about 500 more lines like those...) --- Then, some bce(4) errors, which caused the network interface to be shutdown: --- bce0: ../../../dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting bce0: link state changed to DOWN bce0: Gigabit link up bce0: link state changed to UP bce0: ../../../dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting --- And finally, those errors from mpt(4): --- request 0xc4c4a080:44717 timed out for ccb 0xc4e41400 (req->ccb 0xc4e41400) request 0xc4c4b430:44718 timed out for ccb 0xc4ca5800 (req->ccb 0xc4ca5800) request 0xc4c4cd80:44719 timed out for ccb 0xc4c52800 (req->ccb 0xc4c52800) (... and about 300 more lines like those ...) --- which were followed by the same number of lines like these: --- mpt0: completing timedout/aborted req 0xc4c4a080:44717 mpt0: completing timedout/aborted req 0xc4c4b430:44718 mpt0: completing timedout/aborted req 0xc4c4cd80:44719 --- and finishing with this line: --- mpt0: Timedout requests already complete. Interrupts may not be functioning. --- After one hour and a half, the system was still unstable and I was forced to reboot it. Those are the main issues (mpt(4) and bce(4)) regarding this hardware configuration and FreeBSD (6-STABLE and 7-CURRENT), however, two problems were showing up, as well. 1. The first network interface (labeled "Gb 1", on server's case) was detected as bce1, and the second one (Gb 2), as bce0. --- bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci8 bce0: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0xf4000000 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: on bce0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce0: bpf attached bce0: Ethernet address: 00:13:72:f9:xx:xx bce0: [MPSAFE] ... bce1: mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci4 bce1: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0xf8000000 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus1: on bce1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce1: bpf attached bce1: Ethernet address: 00:13:72:f9:xx:xx bce1: [MPSAFE] --- According to this log, bce0 is on pci8, while bce1 is on pci4. 2. Sometimes, the server refuses to be halted or rebooted via shutdown(8) or reboot(8). Any hint will be appreciated :) /var/run/dmesg.boot (verbose log) http://bsdero.tripod.com/dmesg.boot.txt /var/log/messages (with remarks) http://bsdero.tripod.com/messages.txt pciconf -lv output http://bsdero.tripod.com/pciconf.txt -- Alex Salazar From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 10:42:21 2006 Return-Path: X-Original-To: stable@FreeBSD.org 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 85BC416A4E0; Sat, 2 Sep 2006 10:42:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CD5C43D49; Sat, 2 Sep 2006 10:42:21 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CBCE846DC6; Sat, 2 Sep 2006 06:42:20 -0400 (EDT) Date: Sat, 2 Sep 2006 11:42:20 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: stable@FreeBSD.org In-Reply-To: <20060816120709.N45647@fledge.watson.org> Message-ID: <20060902113521.P84468@fledge.watson.org> References: <20060816120709.N45647@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: trustedbsd-audit@TrustedBSD.org, freebsd-security@FreeBSD.org Subject: Re: Warning: MFC of security event audit support RELENG_6 in the next 2-3 weeks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 10:42:21 -0000 On Wed, 16 Aug 2006, Robert Watson wrote: > Dear 6-STABLE users, > > In the next 2-3 weeks, I plan to MFC support for CAPP security eventing > auditing from 7-CURRENT to 6-STABLE. The implementation has been running > quite nicely in -CURRENT for several months. Right now, I'm just waiting on > a confirmation from Sun regarding formal allocation of a BSM header version > number so as to avoid accidental version number conflicts in the future, > which I hope to get this week, as well as a bug fix in the handling of > per-pipe preselection, which Christian Peron is currently working on. The > audit implementation will be considered an experimental feature in > 6.2-RELEASE, but in practice runs quite well, so is ready for more > wide-spread deployment. Dear 6-STABLE users, After a couple of weeks of settling, polishing, etc, the MFC of audit support is about to begin. Over the next couple of days, the 6-STABLE build may be briefly broken as inter-dependent components are merged. I do not anticipate any serious disruption, but some caution is called for. In principle, all the potentially tricky kernel ABI dependencies, etc, were dealt with before 6.0-RELEASE, such as changes in the size of the kernel system call data structures. The approximate merge plan, run by re@ a few days ago, is as follows: - Merge OpenBSM contrib subtree detached from build. - Merge kernel trees (src/sys/bsm, src/sys/security/audit), attach to build. - Merge kernel audit event hooks across the kernel. In principle, we've reserved space in the syscall table, etc, so that there is no disruptive kernel ABI change for critical data structures. - Merge OpenBSM library and command line tools build, as well as install of /etc/security, /etc/rc.d files. - Merge kernel man pages (src/share/man/man4/audit*). - Merge user space tool changes, such as to login, sshd, su, etc, so that events are audited. - Loose ends, such as make.conf man page, etc. - Update Handbook to indicate that Audit applies to 6.x and 7.x. I will send out a status e-mail once the merge is completed, and send out a notice if any problems are encountered. If you experience any problems, especially problems not related to the build (which will likely get picked up and fixed quickly, if they occur), please let me know. I'm especially interested in any issues relating to changes in ability to log in, programs exiting due to using unrecognized system calls (SIGSYS), etc. As I said above, these sorts of problems are unlikely to occur, but if they do occur, I'd like to fix them as quickly as possible. I would like to have the merge largely done by 4 September 2006, although it's possible a few straggling tweaks will come in after that. Thanks, Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 13:26:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 723EA16A4DF for ; Sat, 2 Sep 2006 13:26:54 +0000 (UTC) (envelope-from dandee@hellteam.net) Received: from pipa.vshosting.cz (pipa.vshosting.cz [81.0.201.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF9443D5D for ; Sat, 2 Sep 2006 13:26:51 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from localhost (localhost [127.0.0.1]) by pipa.vshosting.cz (Postfix) with ESMTP id D997E4E797; Sat, 2 Sep 2006 15:26:51 +0200 (CEST) Received: from pipa.vshosting.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21002-01; Sat, 2 Sep 2006 15:26:51 +0200 (CEST) Received: from gandalf (unknown [81.0.245.205]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.vshosting.cz (Postfix) with ESMTP id 7E4244E790; Sat, 2 Sep 2006 15:26:51 +0200 (CEST) From: =?utf-8?Q?Daniel_Dvo=C5=99=C3=A1k?= To: "'Sam Leffler'" Date: Sat, 2 Sep 2006 15:26:48 +0200 Message-ID: <000001c6ce93$72a247b0$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbOREItelFmOGtDT5yOHxja97zIAwATJ5ww In-Reply-To: <44F901B9.3040309@errno.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz Cc: freebsd-stable@freebsd.org Subject: RE: atheros driver under high load, panics and even more freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 13:26:54 -0000 Ok, I will upgrade my boxes and I will do simple ping tests again. Did you see my sysctl.conf file ? I mean these options: kern.ipc.maxsockbuf=3D2097152 net.inet.ip.fastforwarding=3D1 net.inet.tcp.sendspace=3D65536 Could be this connected with increasing latency up to 500ms ? I tested this issue on another box, box of my friend, you know him too. --- 10.27.128.13 ping statistics --- 10000 packets transmitted, 10000 packets received, 0% packet loss round-trip min/avg/max/stddev =3D 0.932/1.101/9.657/0.433 ms There is nice avg 1,1ms. In his sysctl.conf, there are not these maxsockbuf, fastforwarding and = sendscpace. It is ironic, because it was he, who advised me these values. You wrote me "look at memory usage with vmstat and/or netstat". Ok, bud you did not told me what I should to search for ... And I do not know how the command write with vmstat and netstat, there = are many switches. :) What to find ? Thank you. Daniel > -----Original Message----- > From: Sam Leffler [mailto:sam@errno.com]=20 > Sent: Saturday, September 02, 2006 6:00 AM > To: dandee@volny.cz > Cc: freebsd-stable@freebsd.org; current@freebsd.org > Subject: Re: atheros driver under high load, panics and even=20 > more freezes >=20 > Daniel Dvo=C3=B8=C3=A1k wrote: > > Hi all, > > =20 > > first of all, I=C2=B4m sorry maybe for my bad English. > > =20 > > We have 2 routers which I maintain in our mesh wireless=20 > community network. > > =20 > > The Router 1 has 2 atheros adapters, ath0=3Dwistron cm9, = ath1=3Dwistron=20 > > cm10, of course some sisX, fxpX and so on. > > The Router 2 has 1 atheros adapter, ath1=3Dwistron CM10. > > =20 > > My R1 panics and even more it freezes very often. Maybe the=20 > reason for=20 > > panicing and freezing is the same and maybe not. > > =20 > > I started (only after vmcore.5, so vmcore.6 is with this=20 > option) to=20 > > use "option SW_WATCHDOG" in both my custom kernels on the R1 and R2=20 > > recently in hope, it is some walkaround for freezing at=20 > least if not for panicing. > > =20 > > This router was installed on the 1st of April 2006. > > =20 > > Statistics: > > =20 > > 9 panics with 8 kernel dumps, 1 missed > > =20 > > 10 freezes > > =20 > > I think that all panics some how connected to athX taskq=20 > process, page=20 > > fault in kernel panic and sbflush_locked. >=20 > Why? >=20 > > =20 > > I guess that panic comes when router transmits and receives=20 > datas at=20 > > the maximum throughput for setted nominal media rate speed, exactly=20 > > 24Mbps, more I do not use, because there are problems with quagga > > =20 > > ospfd packets, it is known issue. > > =20 > > Today I did a small test with throughput. > > =20 > > Router 1 executed this command: > > =20 > > # ping -i 0.001 -c 100000 -s 1472 ANY IP > > =20 > > As you see, it is not even flood ping, it is almost flood,=20 > but not flood. > > =20 > > Throughput was about 1,13-1,2 MB/s as bmon showed me. I=20 > notice there=20 > > is not any qos and icmp.limit is so high net.inet.icmp.icmplim:=20 > > 2147483647 > > net.ineticmp.icmplim_output: 0. > >=20 > > =20 > > First 5 s latency was about 1,1-1,7 ms After it goes to=20 > 10-30, 50-70,=20 > > 110-130, 270-300, up 300ms and packet loss > > =20 > > .... some seconds .... > > =20 > > panic >=20 > <...lots of stuff deleted...> >=20 > Sounds like a resource leak to me. You've got crash dumps,=20 > look at memory usage with vmstat and/or netstat. Past that=20 > it sounds like you're running 6.1 RELEASE which is now 6+=20 > months old. Many bugs have been fixed including, I believe,=20 > some resource-related ones. Please try 6-STABLE. >=20 > Sam >=20 >=20 From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 17:21:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7F91516A4DA for ; Sat, 2 Sep 2006 17:21:58 +0000 (UTC) (envelope-from dandee@hellteam.net) Received: from pipa.vshosting.cz (pipa.vshosting.cz [81.0.201.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0AB543D5C for ; Sat, 2 Sep 2006 17:21:57 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from localhost (localhost [127.0.0.1]) by pipa.vshosting.cz (Postfix) with ESMTP id B4D3D4E79B; Sat, 2 Sep 2006 19:21:57 +0200 (CEST) Received: from pipa.vshosting.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00529-06; Sat, 2 Sep 2006 19:21:57 +0200 (CEST) Received: from gandalf (unknown [81.0.245.205]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.vshosting.cz (Postfix) with ESMTP id 653E94E799; Sat, 2 Sep 2006 19:21:57 +0200 (CEST) From: =?iso-8859-2?Q?Daniel_Dvo=F8=E1k?= To: "'Sam Leffler'" Date: Sat, 2 Sep 2006 19:21:54 +0200 Message-ID: <000001c6ceb4$4a33c620$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbORV8Ws7zrV8/eQpG4RohCVQAwLQAaZrMg In-Reply-To: <44F9039C.7060001@errno.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz Cc: freebsd-stable@freebsd.org Subject: RE: atheros driver: countrycode and athdebug X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 17:21:58 -0000 > You can override the country code but the potential values=20 > depends on the regdomain. I thought hw.ath.countrycode was=20 > r/w but it appears you can only set via the tunable api (kenv=20 > hw.ath.countrycode=3DXXX). The dev.ath mib must be r/o since=20 > you cannot (yet) change this after attaching the device (the=20 > driver does not implement it). Adding support to do this is=20 > not a big deal but hasn't been done; feel free to supply a patch. >=20 Ok, I tried to set via the tunable api kenv through loader, but this is = the result: # ifconfig ath0 ifconfig: interface ath0 does not exist # ifconfig ath1 ifconfig: interface ath1 does not exist ath0: mem 0x80000000-0x8000ffff irq 12 at device 13.0 on = pci0 ath0: unable to collect channel list from hal; regdomain likely 96 = country code 203 device_attach: ath0 attach returned 22 ath1: mem 0x800c0000-0x800cffff irq 9 at device 17.0 on = pci0 ath1: unable to collect channel list from hal; regdomain likely 96 = country code 203 device_attach: ath1 attach returned 22 ath0: mem 0x80000000-0x8000ffff irq 12 at device 13.0 on = pci0 ath0: unable to collect channel list from hal; regdomain likely 96 = country code 203 device_attach: ath0 attach returned 22 ath1: mem 0x800c0000-0x800cffff irq 9 at device 17.0 on = pci0 ath1: unable to collect channel list from hal; regdomain likely 96 = country code 203 device_attach: ath1 attach returned 22 # sysctl hw.ath hw.ath.hal.version: 0.9.17.2 hw.ath.hal.dma_brt: 2 hw.ath.hal.sw_brt: 10 hw.ath.hal.swba_backoff: 0 hw.ath.dwell: 200 hw.ath.calibrate: 30 hw.ath.outdoor: 1 hw.ath.xchanmode: 1 hw.ath.countrycode: 203 hw.ath.regdomain: 0 -- not setted to 96 ???? hw.ath.rxbuf: 40 hw.ath.txbuf: 100 So ? I don=B4t know. :) From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 19:21:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0984E16A4DE for ; Sat, 2 Sep 2006 19:21:04 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A81643D68 for ; Sat, 2 Sep 2006 19:20:50 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1408260wxd for ; Sat, 02 Sep 2006 12:20:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uRnDY+WFcpFcn1zGm0FyqrNm6V3iV0ENmPjjCDcCgTwZbaClzcKmpYvyfikXd16UJNW319fpX8Un1B6jCe5mp3LhaiK45NV7S+DirVN/UU8K8acXGKqmSvCkbWyTBRr1TgR9yG12zs6H/N85fWXcqBoDRaFlsljFhuHU4/0Pa44= Received: by 10.90.50.6 with SMTP id x6mr969829agx; Sat, 02 Sep 2006 12:20:49 -0700 (PDT) Received: by 10.90.70.14 with HTTP; Sat, 2 Sep 2006 12:20:48 -0700 (PDT) Message-ID: <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> Date: Sat, 2 Sep 2006 12:20:49 -0700 From: "Matthew Jacob" To: "Alex Salazar" In-Reply-To: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 19:21:04 -0000 > > The OS booted up and the SAS controller was now detected and supported by > the mpt(4) driver: > --- > mpt0: port 0xec00-0xecff mem 0xfc4fc000-0xfc4fffff, > 0xfc4e0000-0xfc4effff irq 64 at device 8.0 on pci2 > mpt0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xec00 > mpt0: Reserved 0x4000 bytes for rid 0x14 type 3 at 0xfc4fc000 > mpt0: [GIANT-LOCKED] > mpt0: MPI Version=1.5.12.0 > --- > > And the related errors showed up immediately, for the first time: > --- > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > mpt0: mpt_cam_event: 0x12 > mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). > mpt0: mpt_cam_event: MPI_EVENT_SAS_DEVICE_STATUS_CHANGE > mpt0: mpt_cam_event: MPI_EVENT_SAS_DEVICE_STATUS_CHANGE > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > -- These are device arrival events. > > When the bootstrap process reached the SCSI probe, there were > no activity on the screen for about five minutes, so I was forced to use > the power off button, and after rebooting, the same symptoms were evident, > so I rebooted the machine once again, this time in verbose mode. > > This debug information was being printed on the screen, one character at time, > at about 1 char/sec: > > (probe8:mpt0:0:8:0): error 22 What's at target 8? It isn't happy for a variety of reasons. Oh- I see from below- it's an SES instance that drops dead if given something at > lun 0. > (probe8:mpt0:0:8:0): Unretryable Error > --- > pass0 at mpt0 bus 0 target 0 lun 0 > pass0: Fixed Direct Access SCSI-5 device > > As a workaround, I disabled the APICs (hint.apic.0.disabled), > and that ~15 minutes delay at boot up, now was gone. Fine. > > (BTW, 7-CURRENT has the same problem, but without that huge delay) Do you have APIC disabled for 7-CURRENT also? > > Once I was logged in the server, I proceeded to populate my ports tree, > by using portsnap(8), so, when I extracted the tarball (portsnap extract), > there was a lot of the following error message, at about 1 message per second: > > mpt0: Unhandled Event Notify Frame. Event 0xe (ACK not required). Queue Full events from the SAS firmware. > > Once in a while, an error message like below, showed up: > -- > (da0:mpt0:0:0:0): WRITE(10). CDB: 2a 0 1 55 6f 5f 0 0 20 0 > (da0:mpt0:0:0:0): CAM Status: SCSI Status Error > (da0:mpt0:0:0:0): SCSI Status: Check Condition > (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 > (da0:mpt0:0:0:0): Scsi bus reset occurred Somebody is reseeting the bus periodically. We (freebsd) aren't volitionally doing this that I'm aware of here. > In order to perform those diagnostics, I had to install a SuSe Linux > Enterprise Server 9, which was also shipped with this machine) Which is a good way of saying that LSI-Logic support isn't very evident on FreeBSD. > > After reinstalling FreeBSD, I logged remotely into the server, via ssh, > and fetched the ports snapshot again and extracted once more. > > Suddenly, the screen activity ceased and the network connection timed out. > > Locally, on the server, there was a lot of mpt(4) errors and warnings. > --- > (da0:mpt0:0:0:0): CAM Status 0x18 > (da0:mpt0:0:0:0): Retrying Command > (... and about 500 more lines like those...) Hmm. > --- >> > And finally, those errors from mpt(4): > > --- > request 0xc4c4a080:44717 timed out for ccb 0xc4e41400 (req->ccb 0xc4e41400) > request 0xc4c4b430:44718 timed out for ccb 0xc4ca5800 (req->ccb 0xc4ca5800) > request 0xc4c4cd80:44719 timed out for ccb 0xc4c52800 (req->ccb 0xc4c52800) > (... and about 300 more lines like those ...) > --- > > which were followed by the same number of lines like these: > --- > mpt0: completing timedout/aborted req 0xc4c4a080:44717 > mpt0: completing timedout/aborted req 0xc4c4b430:44718 > mpt0: completing timedout/aborted req 0xc4c4cd80:44719 > --- > > and finishing with this line: > --- > mpt0: Timedout requests already complete. Interrupts may not be functioning. > --- > I've seen this on Supermicro EM64T in the past on 7-current, but that went away about 3-4 weeks ago. It really seemed to me that this was indeed an interrupt related problem. Yup, sounds like a mess here. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 2 23:59:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 9EEEC16A4DA for ; Sat, 2 Sep 2006 23:59:30 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0A3143D46 for ; Sat, 2 Sep 2006 23:59:29 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1460745wxd for ; Sat, 02 Sep 2006 16:59:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Qi92lZJNCEpO5adkgjaQ5yyCrA9Xf+rtu4krM1WgVJoCcfLHQ40Lz6Z23UdLvD2/mGAPLY5T6kTCRzGT6MS/Mz2+CvyCIuB5mOK96dv9YeVuKX/Lmhhhp2s4guulMo70mSK3WCn7xsE3p0fb6eGpv5iv0Y9vP0pQeLOySvZTSw8= Received: by 10.70.123.14 with SMTP id v14mr5282638wxc; Sat, 02 Sep 2006 16:59:29 -0700 (PDT) Received: by 10.70.38.5 with HTTP; Sat, 2 Sep 2006 16:59:29 -0700 (PDT) Message-ID: Date: Sun, 3 Sep 2006 01:59:29 +0200 From: "Claus Guttesen" To: "Matthew Jacob" In-Reply-To: <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> Cc: Alex Salazar , freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2006 23:59:30 -0000 > > mpt0: Timedout requests already complete. Interrupts may not be functioning. > > > I've seen this on Supermicro EM64T in the past on 7-current, but that > went away about 3-4 weeks ago. It really seemed to me that this was > indeed an interrupt related problem. > > Yup, sounds like a mess here. But is there a solution or workaround rather than just concluding? regards Claus