FreeBSD 6.2 kernel parameters (Was Re: reboot after panic)
I got a couple requests for the tuning settings I've been using; it seems I'm not the only one who's had problems with FreeBSD 6.x stability as compared to 4.x. I don't understand the kernel well enough to say whether any of these are to any extent right, but despite being pure voodoo, they seem to have helped substantially in performance and stability. I picked some of them off the discussion about tuning required to get ZFS running stably, ditto for discussion of ggatec/ggated. (The first 3 settings in sysctl - through kern.ipc.somaxconn - were carried over from my 4.x config.) Here's what I've got, and any solid recommendations from the kernel developers will I'm sure get close attention, and not only from me. I.e. if you can authoritatively tell me I'm an idiot, and some of these aren't really helping, or tell me what will, great. As I say, they seem to help. Ditto if someone can really say authoritatively whether 6.3 is in practice more stable and higher performance than 6.2; with all the discussed problems on list, and the discussions of known fixes not being committed, I have not felt confident about making such a move. /boot/loader.conf: kern.ipc.nmbclusters=32768 vm.kmem_size=512M vm.kmem_size_max=512M kern.maxvnodes=40 /etc/sysctl.conf: # 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. # # TUNING VALUES confirmed by Cal's mailserver testing kern.maxfiles=16384 kern.maxfilesperproc=16384 # Speculative: enlarge listen queue for large number of incoming TCP conns # Default listen queue size = 128, 1024 recommended for busy webservers kern.ipc.somaxconn=1024 # From FreeBSD mailing list, reported on improving stability with # ggatec/ggated. net.inet.tcp.sendspace=1048576 net.inet.tcp.recvspace=1048576 kern.ipc.maxsockbuf=2049152 # Disable hyperthreading logical CPUs machdep.hlt_logical_cpus=1 -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2/6.3/7.0 install CD boot panic
Hello, I tried to install FreeBSD-6.2/6.3/7.0 on Dell E520. When it get boot install CD, ask me language selection then panic. I mean keyboard, mouse no response, only can power off. Dell hasn't any serial port for debug. Only I use digital camera to capture screen. I tried to all boot options 1,2,3,4,5. When I try to boot using without ACPI and got general proctection fault. Please find attached screen. Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2/6.3/7.0 install CD boot panic
Hello, I tried to install FreeBSD-6.2/6.3/7.0 on Dell E520. When it get boot install CD, ask me language selection then panic. I mean keyboard, mouse no response, only can power off. Dell hasn't any serial port for debug. Only I use digital camera to capture screen. I tried to all boot options 1,2,3,4,5. When I try to boot using without ACPI and got general proctection fault. Please find attached screen. Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2/6.3/7.0 install CD boot panic
Hello, I tried to install FreeBSD-6.2/6.3/7.0 on Dell E520. When it get boot install CD, ask me language selection then panic. I mean keyboard, mouse no response, only can power off. Dell hasn't any serial port for debug. Only I use digital camera to capture screen. I tried to all boot options 1,2,3,4,5. When I try to boot using without ACPI and got general proctection fault. Please find attached screen. Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, February 29, 2008 6:18 PM To: Kevin K Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails On 29/02/2008, Kevin K [EMAIL PROTECTED] wrote: I have cvsupped my src - cvsup stable-supfile / RELENG_7 cvsup5,3,4.freebsd.org many times and I keep failing @ make buildworld : . . . . magic, 67922: Warning offset `@@' invalid magic, 67922: Warning type `@@' invalid mkmagic: Printf format ` *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error That was done w/ make buildworld -j9, im currently doing a make buildworld with no -j and will paste the results here. Off the top of my multiply contused head, do you have a stale /usr/obj lying around (which may require deletion)? I cleaned out /usr/obj but I still get a failure on make buildworld : (these warnings go much further, I didn't paste the whole thing) magic, 67776: Warning offset ` RELENG_7:1.1.1.1.0.26' invalid magic, 67776: Warning type `RELENG_7:1.1.1.1.0.26' invalid magic, 6: Warning offset ` RELENG_7_BP:1.1.1.1' invalid magic, 6: Warning type `RELENG_7_BP:1.1.1.1' invalid magic, 67778: Warning offset ` file_4_21:1.1.1.1' invalid magic, 67778: Warning type `file_4_21:1.1.1.1' invalid magic, 67779: Warning offset ` file_4_19:1.1.1.1' invalid magic, 67779: Warning type `file_4_19:1.1.1.1' invalid magic, 67780: Warning offset ` RELENG_6_2_0_RELEASE:1.1.1.1' invalid magic, 67780: Warning type `RELENG_6_2_0_RELEASE:1.1.1.1' invalid magic, 67781: Warning offset ` RELENG_6_2:1.1.1.1.0.24' invalid magic, 67781: Warning type `RELENG_6_2:1.1.1.1.0.24' invalid magic, 67782: Warning offset ` RELENG_6_2_BP:1.1.1.1' invalid magic, 67782: Warning type `RELENG_6_2_BP:1.1.1.1' invalid magic, 67783: Warning offset ` file_4_17_A:1.1' invalid magic, 67783: Warning type `file_4_17_A:1.1' invalid magic, 67784: Warning offset ` file_4_17:1.1.1.1' invalid magic, 67784: Warning type `file_4_17:1.1.1.1' invalid magic, 67785: Warning offset ` RELENG_5_5_0_RELEASE:1.1.1.1' invalid magic, 67785: Warning type `RELENG_5_5_0_RELEASE:1.1.1.1' invalid magic, 67786: Warning offset ` RELENG_5_5:1.1.1.1.0.22' invalid magic, 67786: Warning type `RELENG_5_5:1.1.1.1.0.22' invalid magic, 67787: Warning offset ` RELENG_5_5_BP:1.1.1.1' invalid magic, 67787: Warning type `RELENG_5_5_BP:1.1.1.1' invalid magic, 67788: Warning offset ` RELENG_6_1_0_RELEASE:1.1.1.1' invalid magic, 67788: Warning type `RELENG_6_1_0_RELEASE:1.1.1.1' invalid magic, 67789: Warning offset ` RELENG_6_1:1.1.1.1.0.20' invalid magic, 67789: Warning type `RELENG_6_1:1.1.1.1.0.20' invalid magic, 67790: Warning offset ` RELENG_6_1_BP:1.1.1.1' invalid magic, 67790: Warning type `RELENG_6_1_BP:1.1.1.1' invalid magic, 67791: Warning offset ` RELENG_6_0_0_RELEASE:1.1.1.1' invalid magic, 67791: Warning type `RELENG_6_0_0_RELEASE:1.1.1.1' invalid magic, 67792: Warning offset ` RELENG_6_0:1.1.1.1.0.18' invalid magic, 67792: Warning type `RELENG_6_0:1.1.1.1.0.18' invalid magic, 67793: Warning offset ` RELENG_6_0_BP:1.1.1.1' invalid magic, 67793: Warning type `RELENG_6_0_BP:1.1.1.1' invalid magic, 67794: Warning offset ` RELENG_6:1.1.1.1.0.16' invalid magic, 67794: Warning type `RELENG_6:1.1.1.1.0.16' invalid magic, 67795: Warning offset ` RELENG_6_BP:1.1.1.1' invalid magic, 67795: Warning type `RELENG_6_BP:1.1.1.1' invalid magic, 67796: Warning offset ` RELENG_5_4_0_RELEASE:1.1.1.1' invalid magic, 67796: Warning type `RELENG_5_4_0_RELEASE:1.1.1.1' invalid magic, 67797: Warning offset ` RELENG_5_4:1.1.1.1.0.14' invalid magic, 67797: Warning type `RELENG_5_4:1.1.1.1.0.14' invalid magic, 67798: Warning offset ` RELENG_5_4_BP:1.1.1.1' invalid magic, 67798: Warning type `RELENG_5_4_BP:1.1.1.1' invalid magic, 67799: Warning offset ` RELENG_4_11_0_RELEASE:1.1.1.1.2.1' invalid magic, 67799: Warning type `RELENG_4_11_0_RELEASE:1.1.1.1.2.1' invalid magic, 67800: Warning offset ` file_4_12:1.1.1.1' invalid magic, 67800: Warning type `file_4_12:1.1.1.1' invalid magic, 67801: Warning offset ` RELENG_4_11:1.1.1.1.2.1.0.18' invalid magic, 67801: Warning type `RELENG_4_11:1.1.1.1.2.1.0.18' invalid magic, 67802: Warning offset ` RELENG_4_11_BP:1.1.1.1.2.1' invalid magic, 67802: Warning type `RELENG_4_11_BP:1.1.1.1.2.1' invalid magic, 67803: Warning offset ` RELENG_5_3_0_RELEASE:1.1.1.1' invalid magic, 67803: Warning type `RELENG_5_3_0_RELEASE:1.1.1.1' invalid magic, 67804: Warning offset ` RELENG_5_3:1.1.1.1.0.12' invalid magic, 67804: Warning type `RELENG_5_3:1.1.1.1.0.12' invalid magic, 67805: Warning offset ` RELENG_5_3_BP:1.1.1.1' invalid magic, 67805: Warning type `RELENG_5_3_BP:1.1.1.1' invalid magic, 67806: Warning offset ` RELENG_5:1.1.1.1.0.10' invalid
Re: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
On Fri, Feb 29, 2008 at 06:12:52PM -0500, Kevin K wrote: I have cvsupped my src - cvsup stable-supfile / RELENG_7 cvsup5,3,4.freebsd.org many times and I keep failing @ make buildworld : magic, 67702: Warning type `log' invalid magic, 67703: Warning offset [EMAIL PROTECTED] files no longer part of the vendor's file(1).' invalid magic, 67703: Warning type [EMAIL PROTECTED] files no longer part of the vendor's file(1).' invalid magic, 67704: Warning offset `@' invalid magic, 67704: Warning type `@' invalid magic, 67705: Warning offset `text' invalid magic, 67705: Warning type `text' invalid magic, 67706: Warning offset `@@' invalid magic, 67706: Warning type `@@' invalid magic, 67709: Warning type `.1.1.1.4.1' invalid magic, 67710: Warning offset `log' invalid magic, 67710: Warning type `log' invalid magic, 67711: Warning offset [EMAIL PROTECTED]: file version 3.41' invalid magic, 67711: Warning type [EMAIL PROTECTED]: file version 3.41' invalid It looks like you did something wrong when using cvsup, and did not check out RELENG_7, but instead got a copy of the whole CVS repository - which cannot be compiled from directly. Remove all the contents of your current /usr/src/, fix your supfile, and try again. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
-Original Message- It looks like you did something wrong when using cvsup, and did not check out RELENG_7, but instead got a copy of the whole CVS repository - which cannot be compiled from directly. Remove all the contents of your current /usr/src/, fix your supfile, and try again. I'll try removing /usr/src/* re-cvsupping. Here is my stable-supfile, however : # Defaults that apply to all the collections # # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/doc/handbook/mirrors.html. *default host=cvsup4.FreeBSD.org *default base=/var/db *default prefix=/usr # The following line is for 7-stable. If you want 6-stable, 5-stable, # 4-stable, 3-stable, or 2.2-stable, change to RELENG_6, RELENG_5, # RELENG_4, RELENG_3, or RELENG_2_2 respectively. *default release=cvs tag=RELENG_7 *default delete use-rel-suffix # If you seem to be limited by CPU rather than network or disk bandwidth, try # commenting out the following line. (Normally, today's CPUs are fast enough # that you want to run compression.) *default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the src-all # mega-collection. It includes all of the individual src-* collections. # Please note: If you want to track -STABLE, leave this uncommented. src-all ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
On Sat, Mar 01, 2008 at 11:00:11AM -0500, Kevin K wrote: I'll try removing /usr/src/* re-cvsupping. I would recommend you also nuke relevant directories or files in /usr/sup (or if you're using csup, /var/db/sup). I tend to recommend using /usr/share/examples/cvsup/ports-supfile and stable-supfile. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
`@' invalid magic, 67887: Warning type `@' invalid magic, 67906: Warning offset `@' invalid magic, 67906: Warning type `@' invalid magic, 67909: Warning type `.1.1.1' invalid magic, 67910: Warning offset `log' invalid magic, 67910: Warning type `log' invalid magic, 67911: Warning offset [EMAIL PROTECTED] import of FILE 3.32' invalid magic, 67911: Warning type [EMAIL PROTECTED] import of FILE 3.32' invalid magic, 67912: Warning offset `@' invalid magic, 67912: Warning type `@' invalid magic, 67913: Warning offset `text' invalid magic, 67913: Warning type `text' invalid magic, 67914: Warning offset `@@' invalid magic, 67914: Warning type `@@' invalid magic, 67917: Warning type `.1.1.1.2.1' invalid magic, 67918: Warning offset `log' invalid magic, 67918: Warning type `log' invalid magic, 67919: Warning offset [EMAIL PROTECTED]: Christos Zoulas's FILE 3.33' invalid magic, 67919: Warning type [EMAIL PROTECTED]: Christos Zoulas's FILE 3.33' invalid magic, 67920: Warning offset `@' invalid magic, 67920: Warning type `@' invalid magic, 67921: Warning offset `text' invalid magic, 67921: Warning type `text' invalid magic, 67922: Warning offset `@@' invalid magic, 67922: Warning type `@@' invalid mkmagic: Printf format ` *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error That was done w/ make buildworld -j9, im currently doing a make buildworld with no -j and will paste the results here. DMESG is as follows : Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #5: Fri Sep 28 14:14:16 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CK WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1804.10-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 259981312 (247 MB) avail memory = 240680960 (229 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: IntelR AWRDACPI 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: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845G (845G GMCH) SVGA controller mem 0xe000-0xe7ff,0xee00-0xee07 irq 16 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xd800-0xd81f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xd400-0xd41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 0xee08-0xee0803ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: Intel 82801DB/L/M (ICH4) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 rl0: RealTek 8139 10/100BaseTX port 0xc000-0xc0ff mem 0xed005000-0xed0050ff irq 18 at device 6.0 on pci1 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:30:1b:ac:61:61 rl0: [GIANT-LOCKED] fwohci0: VIA Fire II (VT6306) port 0xc400-0xc47f mem 0xed004000-0xed0047ff irq 19 at device 7.0 on pci1 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:30
Re: FreeBSD 6.2 -- cvsup to 7.0 + make buildworld fails
On 29/02/2008, Kevin K [EMAIL PROTECTED] wrote: I have cvsupped my src - cvsup stable-supfile / RELENG_7 cvsup5,3,4.freebsd.org many times and I keep failing @ make buildworld : . . . . magic, 67922: Warning offset `@@' invalid magic, 67922: Warning type `@@' invalid mkmagic: Printf format ` *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error That was done w/ make buildworld -j9, im currently doing a make buildworld with no -j and will paste the results here. Off the top of my multiply contused head, do you have a stale /usr/obj lying around (which may require deletion)? -- -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
Hello All,
After I follow below instruction it boot kernel, but then give me error says
/etc/fstab not found etc.,
I will attach it next email.
Balgaa
- Original Message -
From: Alexandre Sunny Kovalenko [EMAIL PROTECTED]
To: Balgansuren Batsukh [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Sent: Tuesday, December 04, 2007 12:19 PM
Subject: Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 2007-12-03 at 21:31 +0800, Balgansuren Batsukh wrote:
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully
finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot
file
from TFTP server,
then trying to load kernel image from TFTP server.
After 10-20 minutes it give me error message can't load kernel, I tried
many times load boot/kernel/kernel, but same result.
I guess PXE boot read much longer time to load kernel file and suddenly
give
me error message.
I followed instruction on http://www.hack.org/mc/freebsd-x60.html
I made X60LAN switchTFTP/DHCP/NFS server and even tried
X60---cross-over cableTFTP/DHCP/NFS server.
Is there any suggestion?
I have built my X60 from such a setup and then used it as the FixIt
environment more then a few times. Here are relevant bits from the
server (watch out for the line wrapping):
=== /usr/local/etc/dhcpd.conf (I am using isc-dhcp3-server-3.0.5_2)
option domain-name rabbitslawn.verizon.net;
option domain-name-servers rabbitslawn.verizon.net;
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
log-facility local7;
server-name twinhead;
server-identifier 10.0.3.236;
next-server 10.0.3.236;
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path /SHARED/tftpboot;
filename boot/pxeboot;
}
=== /etc/exports (excerpt)
/SHARED -alldirs
=== /etc/inetd.conf (excerpt)
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
=== /etc/rc.conf (excerpt)
nfs_server_enable=YES
rpcbind_enable=YES
=== /SHARED/tftpboot
Contains fairly old (February 2007) snapshot of then 7-CURRENT with two
modifications
=== /SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom=ufs:/dev/md0c
boot
=== /SHARED/tftpboot/mfsroot
Is the decompressed version of /SHARED/tftpboot/boot/mfsroot.gz.
I can confirm that stopping NFS on the server will give the symptoms
roughly corresponding to the ones you are describing, so the first thing
I would recommend checking is the ability to mount your equivalent of
the /SHARED/tftpboot above.
Hopefully this is all I have done to get this to work -- I have picked
most of it from someone's web page, but I could not find original URL
ATM.
Regards,
Balgaa
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Alexandre Sunny Kovalenko [EMAIL PROTECTED]
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.13/1165 - Release Date:
12/2/2007 8:34 PM
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-6.2, 7.0-BETA1 on X60
Hello All, I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish my attempt. When it start PXE boot it get IP address from DHCP, download PXE boot file from TFTP server, then trying to load kernel image from TFTP server. After 10-20 minutes it give me error message can't load kernel, I tried many times load boot/kernel/kernel, but same result. I guess PXE boot read much longer time to load kernel file and suddenly give me error message. I followed instruction on http://www.hack.org/mc/freebsd-x60.html I made X60LAN switchTFTP/DHCP/NFS server and even tried X60---cross-over cableTFTP/DHCP/NFS server. Is there any suggestion? Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
try monitoring the traffic (tcpdump/wireshark), this should give you a good starting point. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, Dec 03, 2007 at 09:31:55PM +0800, Balgansuren Batsukh wrote: Hello All, I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish my attempt. When it start PXE boot it get IP address from DHCP, download PXE boot file from TFTP server, then trying to load kernel image from TFTP server. After 10-20 minutes it give me error message can't load kernel, I tried many times load boot/kernel/kernel, but same result. I guess PXE boot read much longer time to load kernel file and suddenly give me error message. I followed instruction on http://www.hack.org/mc/freebsd-x60.html I made X60LAN switchTFTP/DHCP/NFS server and even tried X60---cross-over cableTFTP/DHCP/NFS server. Is there any suggestion? First, there's a manpage for all this: diskless(8). I've tried this before myself (on all sorts of different hardware), and I've never gotten it to work on RELENG_6 or RELENG_7 -- I reach the same point and receive the same error you do. It appears to me that that an NFS server is *absolutely* necessary for all of this to work; TFTP by itself doesn't suffice, it appears. I've tried setting LOADER_TFTP_SUPPORT=yes in make.conf (forcing the entire process to avoid using NFS), but believe it or not, a part of the booting process still continues to use NFS-related code (or at least the debugging messages state it's trying to do NFS). I was able to get some pxeboot-related debugging output (to see the aforementioned) by setting PXE_DEBUG=true in make.conf (see src/sys/boot/i386/libi386/pxe.c for details on that). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 3 Dec 2007 21:31:55 +0800 Balgansuren Batsukh wrote: I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish my attempt. When it start PXE boot it get IP address from DHCP, download PXE boot file from TFTP server, then trying to load kernel image from TFTP server. Did you look at /var/log/xferlog? Is there something interesting? After 10-20 minutes it give me error message can't load kernel, I tried many times load boot/kernel/kernel, but same result. You may try tcpdump/wireshark at the server side (as someone has already suggested). I guess PXE boot read much longer time to load kernel file and suddenly give me error message. I followed instruction on http://www.hack.org/mc/freebsd-x60.html There are many ways to run diskless. I found FreeBSD docs very useful: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html diskless(8), /usr/share/examples/diskless/clone_root I made X60LAN switchTFTP/DHCP/NFS server and even tried X60---cross-over cableTFTP/DHCP/NFS server. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 3 Dec 2007 07:41:49 -0800 Jeremy Chadwick wrote: I've tried this before myself (on all sorts of different hardware), and I've never gotten it to work on RELENG_6 or RELENG_7 -- I reach the same point and receive the same error you do. We use diskless setup in production. It works just fine. Even with pxelinux to select an OS and it's version to boot (the default is to load memtest86). I found very useful /var/log/xferlog to debug errors while booting a diskless station. It appears to me that that an NFS server is *absolutely* necessary for all of this to work; TFTP by itself doesn't suffice, it appears. Yes. I've tried setting LOADER_TFTP_SUPPORT=yes in make.conf (forcing the entire process to avoid using NFS), but believe it or not, a part of the booting process still continues to use NFS-related code (or at least the debugging messages state it's trying to do NFS). I was able to get some pxeboot-related debugging output (to see the aforementioned) by setting PXE_DEBUG=true in make.conf (see src/sys/boot/i386/libi386/pxe.c for details on that). Seems that you slightly misunderstood the meaning of the LOADER_TFTP_SUPPORT option. It is used only to boot a custom kernel (when at stage 2, diskless(8)). Without this option your diskless station should load your servers' kernel. The stage 3 always uses NFS to mount the root directory. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 on X60
On Mon, 2007-12-03 at 21:31 +0800, Balgansuren Batsukh wrote:
Hello All,
I tried to install FreeBSD on X60 using PXE boot, but unsuccessfully finish
my attempt.
When it start PXE boot it get IP address from DHCP, download PXE boot file
from TFTP server,
then trying to load kernel image from TFTP server.
After 10-20 minutes it give me error message can't load kernel, I tried
many times load boot/kernel/kernel, but same result.
I guess PXE boot read much longer time to load kernel file and suddenly give
me error message.
I followed instruction on http://www.hack.org/mc/freebsd-x60.html
I made X60LAN switchTFTP/DHCP/NFS server and even tried
X60---cross-over cableTFTP/DHCP/NFS server.
Is there any suggestion?
I have built my X60 from such a setup and then used it as the FixIt
environment more then a few times. Here are relevant bits from the
server (watch out for the line wrapping):
=== /usr/local/etc/dhcpd.conf (I am using isc-dhcp3-server-3.0.5_2)
option domain-name rabbitslawn.verizon.net;
option domain-name-servers rabbitslawn.verizon.net;
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
log-facility local7;
server-name twinhead;
server-identifier 10.0.3.236;
next-server 10.0.3.236;
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path /SHARED/tftpboot;
filename boot/pxeboot;
}
=== /etc/exports (excerpt)
/SHARED -alldirs
=== /etc/inetd.conf (excerpt)
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
=== /etc/rc.conf (excerpt)
nfs_server_enable=YES
rpcbind_enable=YES
=== /SHARED/tftpboot
Contains fairly old (February 2007) snapshot of then 7-CURRENT with two
modifications
=== /SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom=ufs:/dev/md0c
boot
=== /SHARED/tftpboot/mfsroot
Is the decompressed version of /SHARED/tftpboot/boot/mfsroot.gz.
I can confirm that stopping NFS on the server will give the symptoms
roughly corresponding to the ones you are describing, so the first thing
I would recommend checking is the ability to mount your equivalent of
the /SHARED/tftpboot above.
Hopefully this is all I have done to get this to work -- I have picked
most of it from someone's web page, but I could not find original URL
ATM.
Regards,
Balgaa
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Alexandre Sunny Kovalenko [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
--- Kevin Oberman [EMAIL PROTECTED] wrote: From: Tom Evans [EMAIL PROTECTED] Date: Thu, 29 Nov 2007 12:42:35 + Sender: [EMAIL PROTECTED] On Thu, 2007-11-29 at 03:28 -0800, Unga wrote: --- Michael Proto [EMAIL PROTECTED] wrote: Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. Thanks for all the replies. It may be a hardware issue. This is a more than four year old computer. Btw, I forgot to mention this is not a server, its running KDE, trying to use as a desktop. Any one of the hangs do not develop any core dump or /var/crash/kernel.0 or /var/crash/vmcore.0. Just the cursor disappear and keyboard does not respond. Only switch off and on can bring the machine up. Are there any hardware analyzing software that I can run on FreeBSD, so that I could narrow down the cause? Unga Can you verify that the machine is actually dead? Do you have another machine that you can hook up either to a serial console, or ssh into the dead box? Weird X symptoms could lead to an unresponsive keyboard, with the machine running just fine underneath X. Just to re-enforce this, I have a colleague who is seeing this on his Radeon-based Lenovo T43 (m300). The display blanks and cannot be resurrected, even CTRL-ALT-BS does not help, but the system is alive. Oddly, I also have a Lenovo T43 based system and it has never shown this problem. It might be something in your xorg setup that is triggering it. If your system is a Radeon, you might try booting with no xorg.conf file. I have found that worked well for my system. Other possibilities include hw.acpi.reset_video=1 (sysctl.conf) and acpi_video_load=YES (loader.conf). I would like to figure out why my system has no issues while others go off to never-never land. Mine is also an ATI Radeon card: ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1 Chipset ATI Radeon 9200PRO 5960 (AGP) I cannot ssh to the machine while its freezes. It says 'no route to host'. That is, the machine is completely dead. The other thing is, FreeBSD installer has not installed an xorg.conf. I have created an xorg.conf using Xorg -configure and moved to /etc/X11/. Adjusted the HorizSync and VertRefresh to match the monitor, driver I used ati, added Modes and an DRI section with Mode 0666. If it crashes again I'll let the list know. Unga Get easy, one-click access to your favorites. Make Yahoo! your homepage. http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
Unga wrote: Mine is also an ATI Radeon card: ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1 Chipset ATI Radeon 9200PRO 5960 (AGP) I cannot ssh to the machine while its freezes. It says 'no route to host'. That is, the machine is completely dead. The other thing is, FreeBSD installer has not installed an xorg.conf. I have created an xorg.conf using Xorg -configure and moved to /etc/X11/. Adjusted the HorizSync and VertRefresh to match the monitor, driver I used ati, added Modes and an DRI section with Mode 0666. If it crashes again I'll let the list know. Just a thought, but you might also want to try using the VESA X driver for a while and see if the same symptoms persist. Its slower than a native driver but can also be used to identify if the X driver is in fact causing problems. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
--- Michael Proto [EMAIL PROTECTED] wrote: Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. Thanks for all the replies. It may be a hardware issue. This is a more than four year old computer. Btw, I forgot to mention this is not a server, its running KDE, trying to use as a desktop. Any one of the hangs do not develop any core dump or /var/crash/kernel.0 or /var/crash/vmcore.0. Just the cursor disappear and keyboard does not respond. Only switch off and on can bring the machine up. Are there any hardware analyzing software that I can run on FreeBSD, so that I could narrow down the cause? Unga Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
On Thu, 2007-11-29 at 03:28 -0800, Unga wrote: --- Michael Proto [EMAIL PROTECTED] wrote: Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. Thanks for all the replies. It may be a hardware issue. This is a more than four year old computer. Btw, I forgot to mention this is not a server, its running KDE, trying to use as a desktop. Any one of the hangs do not develop any core dump or /var/crash/kernel.0 or /var/crash/vmcore.0. Just the cursor disappear and keyboard does not respond. Only switch off and on can bring the machine up. Are there any hardware analyzing software that I can run on FreeBSD, so that I could narrow down the cause? Unga Can you verify that the machine is actually dead? Do you have another machine that you can hook up either to a serial console, or ssh into the dead box? Weird X symptoms could lead to an unresponsive keyboard, with the machine running just fine underneath X. signature.asc Description: This is a digitally signed message part
Re: FreeBSD 6.2-RELEASE always hang
From: Tom Evans [EMAIL PROTECTED] Date: Thu, 29 Nov 2007 12:42:35 + Sender: [EMAIL PROTECTED] On Thu, 2007-11-29 at 03:28 -0800, Unga wrote: --- Michael Proto [EMAIL PROTECTED] wrote: Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. Thanks for all the replies. It may be a hardware issue. This is a more than four year old computer. Btw, I forgot to mention this is not a server, its running KDE, trying to use as a desktop. Any one of the hangs do not develop any core dump or /var/crash/kernel.0 or /var/crash/vmcore.0. Just the cursor disappear and keyboard does not respond. Only switch off and on can bring the machine up. Are there any hardware analyzing software that I can run on FreeBSD, so that I could narrow down the cause? Unga Can you verify that the machine is actually dead? Do you have another machine that you can hook up either to a serial console, or ssh into the dead box? Weird X symptoms could lead to an unresponsive keyboard, with the machine running just fine underneath X. Just to re-enforce this, I have a colleague who is seeing this on his Radeon-based Lenovo T43 (m300). The display blanks and cannot be resurrected, even CTRL-ALT-BS does not help, but the system is alive. Oddly, I also have a Lenovo T43 based system and it has never shown this problem. It might be something in your xorg setup that is triggering it. If your system is a Radeon, you might try booting with no xorg.conf file. I have found that worked well for my system. Other possibilities include hw.acpi.reset_video=1 (sysctl.conf) and acpi_video_load=YES (loader.conf). I would like to figure out why my system has no issues while others go off to never-never land. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpqIaJVupZbV.pgp Description: PGP signature
Radeon/X freezes (was Re: FreeBSD 6.2-RELEASE always hang)
On Thu, Nov 29, 2007 at 08:37:05AM -0800, Kevin Oberman wrote: ... Can you verify that the machine is actually dead? Do you have another machine that you can hook up either to a serial console, or ssh into the dead box? Weird X symptoms could lead to an unresponsive keyboard, with the machine running just fine underneath X. Just to re-enforce this, I have a colleague who is seeing this on his Radeon-based Lenovo T43 (m300). The display blanks and cannot be resurrected, even CTRL-ALT-BS does not help, but the system is alive. Oddly, I also have a Lenovo T43 based system and it has never shown this problem. It might be something in your xorg setup that is triggering it. FWIW, I have also seen seemingly identical symptoms a couple times on a Debian server I set up a couple weeks ago at work, also using a Radeon card (Radeon 9250) and xorg. The console goes away (freezes completely), Control-Alt-Backspace doesn't work to restore it, but the system is still accessible via ssh. This leads me to suspect the reported problem may not be a FreeBSD issue per se but an xorg Radeon driver issue. Reducing the maximum sync setting may have helped, but I don't consider it confirmed yet. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2-RELEASE always hang
Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? How is the stability of the upcoming 7.0? Best Regards Unga I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
Hi, Unga wrote: Hi all I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, 512MB Ram computer. Its very irritatingly hangs very frequently, more than 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? I simply cannot use it for any serious use, not even to send a mail, other than browsing web. I find it mostly when I try to move the mouse it hangs. Upward and downward cursor keys press and hold also hangs, but not always. These may be just coincidental. How do I find why it hangs? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html should help you how to start finding out why :) How is the stability of the upcoming 7.0? You should try it on your hardware and see how it will perform. it can be more stable .. or less :) but it have to be faster :) Best Regards Unga Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now. http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-RELEASE always hang
On Nov 28, 2007 5:15 PM, Unga [EMAIL PROTECTED] wrote: 10 times a day. Do others find FreeBSD 6.2-RELEASE always hangs? no coincidental. How do I find why it hangs? hardware problem, i suppose. broken cpu fan? -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Dimitry Andric wrote: Andreas Rudisch wrote: [...] There's no floppy drive in the X series ThinkPads, so you'll end up using an USB floppy drive. This will probably lead to the same BTX loader problem as with USB CD-ROM drives. The same is probably applicable to booting from USB sticks, and I'm not even sure FreeBSD supports booting off those. About a year ago I created USB stick with GRUB instead of BTX loader for booting on CD-ROM less Sun Fire servers. It works well. So this is the possible way to go. You can create just bootable USB stick from miniboot ISO (30MB) and then install from internal CD-ROM or from network (FTP, NFS...). Or you can create completely working instalation media with packeges etc on USB stick bigger than 512MB. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Hello All, Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM drive on Lenovo X60. It give kind of assembler code non-stop flow over screen. Can't boot system and some times give BTX halted message after CPU register code ES=, Is there any way to boot/install FreeBSD-6.2/7.0-BETA on X60? Regards, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Balgansuren Batsukh wrote: Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM drive on Lenovo X60. It give kind of assembler code non-stop flow over screen. This is a well-known issue with the USB support of some BIOSes (these days, actually most of them). The BIOS uses protected mode, while BTX also does, and this clashes. You'll need to wire up an IDE or SATA optical drive, or fiddle with PXE to get FreeBSD installed. On my X41, which is the predecessor to your X60, I installed OpenBSD instead... :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
On Sun, 4 Nov 2007 23:49:13 +0800 Balgansuren Batsukh [EMAIL PROTECTED] wrote: Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM drive on Lenovo X60. Can't boot system and some times give BTX halted message after CPU register code ES=, Take a look at this: http://hack.org/mc/freebsd-x60.html or try the boot floopies: ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/floppies/ ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/7.0-BETA2/floppies/ Andreas -- GnuPG key : 0x2A573565 | http://cyb.websimplex.de/pubkey.asc Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpVXrYvfCmLI.pgp Description: PGP signature
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
Andreas Rudisch wrote: or try the boot floopies: ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/floppies/ ftp://ftp7.freebsd.org/pub/FreeBSD/releases/i386/7.0-BETA2/floppies/ There's no floppy drive in the X series ThinkPads, so you'll end up using an USB floppy drive. This will probably lead to the same BTX loader problem as with USB CD-ROM drives. The same is probably applicable to booting from USB sticks, and I'm not even sure FreeBSD supports booting off those. AFAIK the only non-PXE alternative is using the UltraBase docking station, which has an optical drive bay connected via ATAPI. But it's rather expensive; here in .nl, it's about EUR 175 for the dock, and EUR 130 for the CD-RW/DVD drive (not even a DVD writer!!). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-6.2, 7.0-BETA1 boot on Lenovo X60
On Sun, 2007-11-04 at 23:49 +0800, Balgansuren Batsukh wrote:
Hello All,
Last few days I try to boot FreeBSD-6.2, 7.0-BETA1 boot CD using USB CDROM
drive on Lenovo X60.
It give kind of assembler code non-stop flow over screen.
Can't boot system and some times give BTX halted message after CPU register
code ES=,
Is there any way to boot/install FreeBSD-6.2/7.0-BETA on X60?
If you have another box on the network, PXE is the way to go. I have
used it to troubleshoot my X60, when I have rendered it unbootable,
enough times to justify time spent. I have acquired UltraBase since
then, but it is still *much more convenient* to boot with PXE in need.
Below are relevant pieces of the information from the server (its name
is 'twinhead', its IP is 10.0.3.236 and install CD is copied into
'/SHARED/tftpboot', tftp user with access to the setup is named 'sunny'
-- you will have to adjust it accordingly):
=== excerpt from /usr/local/etc/dhcpd.conf (I am
using isc-dhcp3-server-3.0.5_2):
server-name twinhead;
server-identifier 10.0.3.236;
next-server 10.0.3.236;
# This is a very basic subnet declaration.
subnet 10.0.3.0 netmask 255.255.255.0 {
range 10.0.3.33 10.0.3.64;
option routers 10.0.3.242;
option domain-name-servers 10.0.3.242;
option root-path /SHARED/tftpboot;
filename boot/pxeboot;
}
/SHARED/tftpboot/boot/loader.rc
echo Loading Kernel...
load /boot/kernel/kernel
echo Loading mfsroot...
load -t mfs_root /mfsroot
echo booting...
echo \007\007
echo initializing h0h0magic...
set vfs.root.mountfrom=ufs:/dev/md0c
boot
excerpt from /etc/inetd.conf
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -u
sunny -l -s /SHARED/tftpboot
I have also gunzip'ed /SHARED/tftpboot/boot/mfsroot.gz and placed it
into /SHARED/tftpboot/.
I don't think there was much else needed doing before you can attempt
booting your X60. Once you boot, you can switch to FTP install, so
version, you are booting from, does not need exactly match whatever you
want installed.
Note: you need to make sure there are no other active DHCP servers on
your network -- I have spend few hours hunting down that one ;)
Regards,
Balgaa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Alexandre Sunny Kovalenko
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 EoL =~ s/January/May/
Hello Everyone, In light of the longer-than-expected window between 6.2-RELEASE and 6.2-RELEASE, the End-of-Life date for FreeBSD 6.2 has been adjusted from January 31st, 2008 to May 31st, 2008. As a result, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will all cease to be supported at the end of May 2008. FreeBSD users should plan on upgrading to either FreeBSD 6.3 or FreeBSD 7.0 once those have been released (hopefully by the end of December). FreeBSD 6.3 will be supported until the end of 2009, while FreeBSD 7.0 will be supported until the end of 2008. Colin Percival FreeBSD Security Officer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 EoL =~ s/January/May/
FreeBSD Security Officer wrote: Hello Everyone, In light of the longer-than-expected window between 6.2-RELEASE and 6.2-RELEASE, ^^^ This should read between 6.2-RELEASE and 6.3-RELEASE, of course... the End-of-Life date for FreeBSD 6.2 has been adjusted from January 31st, 2008 to May 31st, 2008. As a result, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will all cease to be supported at the end of May 2008. FreeBSD users should plan on upgrading to either FreeBSD 6.3 or FreeBSD 7.0 once those have been released (hopefully by the end of December). FreeBSD 6.3 will be supported until the end of 2009, while FreeBSD 7.0 will be supported until the end of 2008. Colin Percival FreeBSD Security Officer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 6.2 and booting from iSCSI
The Presence wrote: 1) I can do a bare-metal restore very simply. 2) I can easily change base system by just changing the TOE parameters in BIOS. 3) I can have multiple systems have access to the same data without having to have multiple copies of the data, but do this in block mode instead of file mode. man diskless As for #3 you can do this with a software initiator once the system boots. -- Robert Blayzor INOC [EMAIL PROTECTED] http://www.inoc.net/~rblayzor/ telnet: Unable to connect to remote host: Connection refused ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd 6.2 and booting from iSCSI
I recently deployed a NetAPP S300 device, and I want to be able to load system OS from it. I have several HP DL380 G3 systems that I want to be able to boot from iSCSI, but I am not sure how to proceed. NetAPP states that the adapters I would want to do this are the QLA405x and QLA406x lines. Since the HP DL380 G3s use PCI-X I need the QLA-4050 or the QLA-4052 adapters. Unfortunately, QLogic states that they only support Windows, RHEL, and SuSE. Firstly, has anyone had any luck booting from any system with FreeBSD. My main drivers here are: 1) I can do a bare-metal restore very simply. 2) I can easily change base system by just changing the TOE parameters in BIOS. 3) I can have multiple systems have access to the same data without having to have multiple copies of the data, but do this in block mode instead of file mode. Secondly, has anyone actually had this work with the HP DL380 G3? If so what HBA did you use to do it? Since the QLogic network cards start at around $800 or so, I don't want to make this a trial and error effort, if its avoidable. Kevin _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 6.2 and booting from iSCSI
On Fri, Oct 05, 2007 at 12:56:08PM -0600, The Presence wrote: I recently deployed a NetAPP S300 device, and I want to be able to load system OS from it. I have several HP DL380 G3 systems that I want to be able to boot from iSCSI, but I am not sure how to proceed. NetAPP states that the adapters I would want to do this are the QLA405x and QLA406x lines. Since the HP DL380 G3s use PCI-X I need the QLA-4050 or the QLA-4052 adapters. Unfortunately, QLogic states that they only support Windows, RHEL, and SuSE. Firstly, has anyone had any luck booting from any system with FreeBSD. My main drivers here are: 1) I can do a bare-metal restore very simply. 2) I can easily change base system by just changing the TOE parameters in BIOS. 3) I can have multiple systems have access to the same data without having to have multiple copies of the data, but do this in block mode instead of file mode. Secondly, has anyone actually had this work with the HP DL380 G3? If so what HBA did you use to do it? Since the QLogic network cards start at around $800 or so, I don't want to make this a trial and error effort, if its avoidable. I think we don't support QLogic HBAs 4xxx. -Kirill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Rare / random hangs with FreeBSD 6.2-RELEASE-p4
Hi Running a FreeBSD 6.2 with mainly MySQL, Apache and PHP (kept up to date with manual freebsd-update / portupgrade). The hardware is SuperMicro SuperServer 5015MT+ with 2GB of ECC RAM and a Intel Core 2 Quad 6700. Running a BIOS assisted soft mirror with SATA disks... After aprox 2 weeks the server hangs. There is no dumps at /var/crash as the server seems to lock up while dumping. Details below - unfortunately I don't always get a picture of the console as I'm not always the rebooter. There is no hang-related notes i FreeBSD logs, and nothing at all in IPMI and BIOS logs. Earlier I had the server running with HTTP Accept Filters on, but then it reboots 4-5 times a day! I've also been running xcache (php accelrator), but that was disabled during the latest hang. Do You have any suggestions? Does this seems to be hardware or software related? Anything I could try to figure out what is going on? Unfortunately the server is in production. Thank You for any help. Regards Gert Lynge Hang 1 panic: vm_fault: fault on nofault entry, addr: e92cf000 cpuid = 3 Uptime: 10d0h24m25s Dumping 2046 MB (2 chunks) chunk 0: 1MB (150 pages) ... Ok chunk 1: 2046MB (523744 pages)_ --- Hang 2: Fatal trap 12: page fault while in kernel mode Cupid = 2; apic id = 2 Fault virtual address = 0x5a Fault code = supervisor read, page not present Instruction pointer = 0x20:0xc07e40a3 Stack pointer = 0x28:0xe6a35b74 Frame pointer = 0x28:0xe6a35c40 Code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 Processor eflags = interrupt enabled, resume, IOPL = 0 Current process = 44 (pagezero) Trap number = 12 Panic: page fault Cupid = 2 Uptime 17d22h47m51s Dumping 2048 MB (2 chunks) Chunk 0: 1MB (150 pages)ipfw: ipfw: xx --- uname -a FreeBSD x.x.x 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 --- cat /etc/rc.conf defaultrouter=x.x.x.x font8x14=cp865-8x14 font8x16=cp865-8x16 font8x8=cp865-8x8 hostname=x.x.x ifconfig_em1=inet x.x.x.x netmask x.x.x.x saver=daemon usbd_enable=YES keymap=danish.cp865 keyrate=fast sshd_enable=YES firewall_enable=YES firewall_type=x firewall_logging=YES ntpd_enable=YES ntpd_sync_on_start=YES mysql_enable=YES apache22_enable=YES #apache22_http_accept_enable=YES inetd_enable=YES clear_tmp_enable=YES #log_in_vain=1 sendmail_enable=YES rsyncd_enable=YES syslogd_flags=-a x.x.x.x/x:* clamav_freshclam_enable=YES local_startup=/usr/local/etc/rc.d dumpdev=/dev/ar0s1b --- cat /var/run/dmesg.boot Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz (2660.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,b9,CX16,b14,b15 AMD Features=0x2000LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 2146304000 (2046 MB) avail memory = 2095165440 (1998 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 17 at device 28.0 on pci0 pci9: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci9 pci10: ACPI PCI bus on pcib3 pci9: base peripheral, interrupt controller at device 0.1 (no driver attached) pcib4: ACPI PCI-PCI bridge irq 17 at device 28.4 on pci0 pci13: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port 0x4000-0x401f mem 0xe020-0xe021 irq 16 at device 0.0 on pci13 em0: Ethernet address: 00:30:48:8d:1f:5e pcib5: ACPI PCI-PCI bridge irq 16 at device 28.5 on pci0 pci14: ACPI PCI bus on pcib5 em1: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port 0x5000-0x501f mem 0xe030
net-snmpd/ucd-snmp: issues under FreeBSD 6.2 amd64 ? (physmem: Cannot allocate memory)
Hello, I'm trying to start net-snmpd or ucd-snmp on a brand new amd64-system (hp dl360g5, 4GB ram, dual xeon), and all I get is the message: Sep 14 08:11:02 db3 snmpd[64634]: sysctl: physmem: Cannot allocate memory on start with net-snmpd, and this with ucd-snmpd: [EMAIL PROTECTED] ~]# /usr/local/etc/rc.d/snmpd start Starting snmpd. nlist err: neither nproc nor _nproc found. sysctl: physmem: Cannot allocate memory nlist err: neither total nor _total found. nlist err: neither proc nor _proc found. improper port specification /var/run/snmpd.pid Server Exiting with code 1 [EMAIL PROTECTED] ~]# sysctl -a |grep physmem hw.physmem: 4281905152 I have no problems like that with snmpd on other servers, but they are all running an i386-version of Freebsd: problem seems related to amd64 ? There are some posts, all still without answers, about this problem on the same platform: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/ 2004-11/2994.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/ 2004-11/1375.html etc. Any suggestion? I'd be glad to help solving this problem, if possible... regards, Olivier ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Patch for FreeBSD 6.2 fstat(1) to support unionfs (at least a little bit)
Hi! fstat(1) from FreeBSD 6.2 can not display information about files which reside in a unionfs[1], as can be seen in this example[2]: USER CMD PID FD MOUNT INUM MODE SZ|DV R/W pi less 31028 root - - ?(unionfs)- pi less 31028 wd - - ?(unionfs)- pi less 31028 jail - - ?(unionfs)- pi less 31028 text - - ?(unionfs)- pi less 310280 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310281 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310282 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310283 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 r pi less 310284 - - ?(unionfs)- This patch[3] fixes it, as can be seen in this other example[4]: USER CMD PID FD MOUNT INUM MODE SZ|DV R/W pi less 31028 root /vserv/vserv3.nepustil.net 4804764 drwxrwxr-x 512 r unionupper /usr pi less 31028 wd /vserv/vserv3.nepustil.net 5042109 drwx-- 1536 r unionupper /usr pi less 31028 jail /vserv/vserv3.nepustil.net 4804764 drwxrwxr-x 512 r unionupper /usr pi less 31028 text /vserv/vserv3.nepustil.net 5159119 -r-xr-xr-x 109300 r unionlower /usr pi less 310280 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310281 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310282 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 rw pi less 310283 /vserv/vserv3.nepustil.net/dev109 crw--w ttyp5 r pi less 310284 /vserv/vserv3.nepustil.net 5042526 -rw--- 702 r unionupper /usr The filesytems involved: f6# df [...] Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1e 43938150 20634736 1978836251%/usr [...] below:/vserv/template/stage2 87876300 64572886 1978836277% /vserv/vserv3.nepustil.net devfs 110 100% /vserv/vserv3.nepustil.net/dev [...] were mounted with the following command: /sbin/mount -t unionfs -o noatime,below,copymode=transparent /vserv/template/stage2 /vserv/vserv3.nepustil.net /sbin/mount_devfs devfs /vserv/vserv3.nepustil.net How to apply: cd /tmp/ fetch http://c0mplx.org/src/fstat-unionfs-patch/patch-20070812 cd /usr patch /tmp/patch-20070812 cd /usr/src/usr.bin/fstat/ make install TODO: support other filesystems besides UFS as lower filesystems [1] http://people.freebsd.org/~daichi/unionfs/ [2] http://c0mplx.org/src/fstat-unionfs-patch/before [3] http://c0mplx.org/src/fstat-unionfs-patch/patch-20070812 [4] http://c0mplx.org/src/fstat-unionfs-patch/after See also: http://c0mplx.org/src/fstat-unionfs-patch/ -- [EMAIL PROTECTED] +49 171 310137213 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2-STABLE crash under moderate disk activity
FreeBSD 6.2-RELEASE and 6.2-STABLE both repeatedly crash with moderate
disk activity. The problem occurs with two different disk drives,
controller documented as supported. When disk is empty, everything
works; filling disk with data makes crash inevietable.
Here is my backtrace
Unread portion of the kernel message buffer:
ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout -
completing request directly
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=18829695
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x28
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0695b74
stack pointer = 0x28:0xd568ec28
frame pointer = 0x28:0xd568ec30
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 18 (thread taskq)
trap number = 12
panic: page fault
Uptime: 38m41s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (160 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 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06827ea in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0682a80 in panic (fmt=0xc08f6895 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc08985f4 in trap_fatal (frame=0xd568ebe8, eva=40) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc089835b in trap_pfault (frame=0xd568ebe8, usermode=0, eva=40)
at /usr/src/sys/i386/i386/trap.c:745
#5 0xc0897f99 in trap (frame=
{tf_fs = -1064435704, tf_es = -714604504, tf_ds = -1064239064,
tf_edi = -1004877952, tf_esi = 0, tf_ebp = -714544080, tf_isp =
-714544108, tf_ebx = -1004877952, tf_edx = 2, tf_ecx = -1019514112,
tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1066837132, tf_cs =
32, tf_eflags = 590406, tf_esp = -1004877952, tf_ss = 0}) at
/usr/src/sys/i386/i386/trap.c:435
#6 0xc08856ca in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0695b74 in devclass_sysctl_init (dc=0x0) at
/usr/src/sys/kern/subr_bus.c:215
#8 0xc0695cf0 in device_sysctl_init (dev=0xc41ac780) at
/usr/src/sys/kern/subr_bus.c:280
#9 0xc0697b7a in device_attach (dev=0xc41ac780) at
/usr/src/sys/kern/subr_bus.c:2375
#10 0xc0697b64 in device_probe_and_attach (dev=0xc41ac780)
at /usr/src/sys/kern/subr_bus.c:2346
#11 0xc069844a in bus_generic_attach (dev=0x0) at
/usr/src/sys/kern/subr_bus.c:2883
#12 0xc04c6814 in ata_identify (dev=0xc3404080) at
/usr/src/sys/dev/ata/ata-all.c:718
#13 0xc04c7462 in ata_sata_phy_event (context=0xc3cc6de0, dummy=1)
at /usr/src/sys/dev/ata/ata-chipset.c:273
#14 0xc06a1e9b in taskqueue_run (queue=0xc3301d00) at
/usr/src/sys/kern/subr_taskqueue.c:257
#15 0xc06a22d6 in taskqueue_thread_loop (arg=0x0) at
/usr/src/sys/kern/subr_taskqueue.c:376
#16 0xc066c9d4 in fork_exit (callout=0xc06a2268 taskqueue_thread_loop,
arg=0xc09f8ba8,
frame=0xd568ed38) at /usr/src/sys/kern/kern_fork.c:830
#17 0xc088572c in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
dmesg.boot:
Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-STABLE #0: Thu Jul 26 10:27:14 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DBILL
ACPI APIC Table: GBTAWRDACPI
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU)
Origin = GenuineIntel Id = 0xf24 Stepping = 4
Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,
HTT,TM
real memory = 536805376 (511 MB)
avail memory = 515887104 (491 MB)
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: GBT AWRDACPI on motherboard
acpi0: Power Button (fixed)
cpu0: ACPI CPU on acpi0
acpi_button0: Power Button on acpi0
acpi_button1: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x4000-0x40bf on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82845G host to AGP bridge mem 0xd000-0xd7ff at
device 0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xb800-0xb81f
irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801DB (ICH4) USB
install activestate komodo in freebsd 6.2
I'm very interesting in this article: http://www.kiffinsblog.com/archives...lling_komo.html I searched Googled but could not find linux libcpp5 tarball. Could anyone give me the link of it? Tnx The article is as below: Installing Komodo IDE 4.0 on FreeBSD ~ FreeBSD After struggling awhile with the installation of Komodo on my FreeBSD 6.2 system, I *finally* was successful in getting it up-and-running. Therefore I would like to share my experiences in the hopes that in the future it may be helpful for some other fellow FreeBSD-er. Installation: 1. Download the linux libcpp5 tarball. 2. Unpack and cd into extracted dirtectory. 3. As root run ./install.sh 4. Choose install directory: /usr/compat/linux/opt/Komodo-IDE-4.0 5. As root cd /usr/compat/linux/opt/Komodo-IDE-4.0 6. For the bin, share and lib directories do the following: 1. chmod -R +x dirname 2. chmod -R -s dirname 3. chmod -R -t dirname 4. chmod -R +r dirname 7. Download the license and install on Windows or Linux (not FreeBSD) 8. Copy ~/.ActiveState/ActiveState.lic and place in ~/.ActiveState directory 9. Komodo can now be started as: /usr/compat/linux/opt/Komodo-IDE-4.0/bin/komodo You can now create a quick launcher by using one of the images found in: /usr/compat/linux/opt/Komodo-IDE-4.0/share/icons/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-6.2 USB promlem
Hi ! We have two Dell PowerEdge 2950 which only have USB mouse keyboard, therefore I'm using a USB to PS/2 converter to get the KVM switch to work with the servers. When I boot default FreeBSD-6.2 kernel then the system detects the usb converter : ukbd0: CHESEN PS2 to USB Converter, rev 1.10/0.10, addr 2, iclass 3/1 kbd2 at ukbd0 ums0: CHESEN PS2 to USB Converter, rev 1.10/0.10, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. If I build a new kernel with GENERIC configuration, then the converter isn't detected and the keyboard doesn't work. :-( FreeBSD 6.2-STABLE #0: Tue Jul 17 10:46:46 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Here is more information form dmesg -a : uhci0: UHCI (generic) USB controller port 0xcce0-0xccff irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0xccc0-0xccdf irq 20 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: UHCI (generic) USB controller port 0xcca0-0xccbf irq 21 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: UHCI (generic) USB controller on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xfc800400-0xfc8007ff irq 21 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered And here is some from usbdevs -v : Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, product 0x6560(0x6560), vendor 0x04b4(0x04b4), rev 0.0b port 1 powered port 2 powered port 3 powered port 4 powered port 6 powered The usb to ps/2 converter is on the /dev/usb3 port 5. Is the support for this converter removed from the kernel or is this a bug ? Regards Roar ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Problem in FreeBSD 6.2-RELEASE-p5
Hi, I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Thanks in advance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
WAS: misc/113825: WARN Error in FreeBSD 6.2-STABLE (/usr/src/lib/libc/rpc/getpublickey.c)
Sigh . . .
Here are the patches I was trying to upload when the PR was closed
without mercy. :)
jmc
# Patch for misc/113825 for csup
#
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this patch file as input.
#
# If you do not have 'applypatch', it is part of the 'makepatch' package
# that you can fetch from the Comprehensive Perl Archive Network:
# http://www.perl.com/CPAN/authors/Johan_Vromans/makepatch-x.y.tar.gz
# In the above URL, 'x' should be 2 or higher.
#
# To apply this patch without the use of 'applypatch':
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'patch' program with this file as input.
#
End of Preamble
Patch data follows
diff -c 'contrib/csup/proto.c.old' 'contrib/csup/proto.c'
Index: ./contrib/csup/proto.c.old
*** ./contrib/csup/proto.c.old Tue Jun 19 04:29:42 2007
--- ./contrib/csup/proto.c Tue Jun 19 05:31:31 2007
***
*** 68,74
};
static voidkiller_start(struct killer *, struct mux *);
! static void *killer_run(void *);
static voidkiller_stop(struct killer *);
static int proto_waitconnect(int);
--- 68,74
};
static voidkiller_start(struct killer *, struct mux *);
! static voidkiller_run(void *);
static voidkiller_stop(struct killer *);
static int proto_waitconnect(int);
***
*** 963,968
--- 963,970
/* Start the killer thread. It is used to protect against some signals
during the multi-threaded run so that we can gracefully fail. */
+ typedef void *(*start_routine)(void *);
+
static void
killer_start(struct killer *k, struct mux *m)
{
***
*** 976,988
sigaddset(k-sigset, SIGTERM);
sigaddset(k-sigset, SIGPIPE);
pthread_sigmask(SIG_BLOCK, k-sigset, NULL);
! error = pthread_create(k-thread, NULL, killer_run, k);
if (error)
err(1, pthread_create);
}
/* The main loop of the killer thread. */
! static void *
killer_run(void *arg)
{
struct killer *k;
--- 978,991
sigaddset(k-sigset, SIGTERM);
sigaddset(k-sigset, SIGPIPE);
pthread_sigmask(SIG_BLOCK, k-sigset, NULL);
! error = pthread_create(k-thread, NULL, (start_routine)killer_run, k);
if (error)
err(1, pthread_create);
}
/* The main loop of the killer thread. */
!
! static void
killer_run(void *arg)
{
struct killer *k;
End of Patch data
ApplyPatch data follows
# Data version: 1.0
# Date generated : Tue Jun 19 06:52:53 2007
# Generated by: makepatch 2.03
# Recurse directories : Yes
# Excluded files : (\A|/).*\~\Z
# (\A|/).*\.a\Z
# (\A|/).*\.bak\Z
# (\A|/).*\.BAK\Z
# (\A|/).*\.elc\Z
# (\A|/).*\.exe\Z
# (\A|/).*\.gz\Z
# (\A|/).*\.ln\Z
# (\A|/).*\.o\Z
# (\A|/).*\.obj\Z
# (\A|/).*\.olb\Z
# (\A|/).*\.old\Z
# (\A|/).*\.orig\Z
# (\A|/).*\.rej\Z
# (\A|/).*\.so\Z
# (\A|/).*\.Z\Z
# (\A|/)\.del\-.*\Z
# (\A|/)\.make\.state\Z
# (\A|/)\.nse_depinfo\Z
# (\A|/)core\Z
# (\A|/)tags\Z
# (\A|/)TAGS\Z
# p 'contrib/csup/proto.c.old' 25477 1182245491 0100644
End of ApplyPatch data
End of Patch kit [created: Tue Jun 19 06:52:53 2007]
Patch checksum: 96 2948 4469
Checksum: 114 3601 58469
# Patch for misc/113825 for ggated
#
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this patch file as input.
#
# If you do not have 'applypatch', it is part of the 'makepatch' package
# that you can fetch from the Comprehensive Perl Archive Network:
# http://www.perl.com/CPAN/authors/Johan_Vromans/makepatch-x.y.tar.gz
# In the above URL, 'x' should be 2 or higher.
#
# To apply this patch without the use of 'applypatch':
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'patch' program with this file as input.
#
End of Preamble
Patch data follows
diff -c 'sbin/ggate/ggated/ggated.c.old' 'sbin/ggate/ggated/ggated.c'
Index: ./sbin/ggate/ggated/ggated.c.old
*** ./sbin/ggate/ggated/ggated.c.oldMon Jun 18 23:05:16 2007
--- ./sbin/ggate/ggated/ggated.cMon Jun 18 23:08:02 2007
***
*** 756,761
--- 756,762
error = pthread_mutex_unlock(outqueue_mtx);
assert(error == 0);
}
+ return arg;
}
static void *
***
*** 810,815
WAS: misc/113825: WARN Error in FreeBSD 6.2-STABLE (/usr/src/lib/libc/rpc/getpublickey.c)
Maybe you would like unified diff's better? Sorry . . .
jmc
# misc/113825
#
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this patch file as input.
#
# If you do not have 'applypatch', it is part of the 'makepatch' package
# that you can fetch from the Comprehensive Perl Archive Network:
# http://www.perl.com/CPAN/authors/Johan_Vromans/makepatch-x.y.tar.gz
# In the above URL, 'x' should be 2 or higher.
#
# To apply this patch without the use of 'applypatch':
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'patch' program with this file as input.
#
End of Preamble
Patch data follows
diff -ruN 'contrib/csup/proto.c.old' 'contrib/csup/proto.c'
Index: ./contrib/csup/proto.c.old
--- ./contrib/csup/proto.c.old Tue Jun 19 04:29:42 2007
+++ ./contrib/csup/proto.c Tue Jun 19 05:31:31 2007
@@ -68,7 +68,7 @@
};
static void killer_start(struct killer *, struct mux *);
-static void*killer_run(void *);
+static void killer_run(void *);
static void killer_stop(struct killer *);
static int proto_waitconnect(int);
@@ -963,6 +963,8 @@
/* Start the killer thread. It is used to protect against some signals
during the multi-threaded run so that we can gracefully fail. */
+typedef void *(*start_routine)(void *);
+
static void
killer_start(struct killer *k, struct mux *m)
{
@@ -976,13 +978,14 @@
sigaddset(k-sigset, SIGTERM);
sigaddset(k-sigset, SIGPIPE);
pthread_sigmask(SIG_BLOCK, k-sigset, NULL);
- error = pthread_create(k-thread, NULL, killer_run, k);
+ error = pthread_create(k-thread, NULL, (start_routine)killer_run, k);
if (error)
err(1, pthread_create);
}
/* The main loop of the killer thread. */
-static void *
+
+static void
killer_run(void *arg)
{
struct killer *k;
End of Patch data
ApplyPatch data follows
# Data version: 1.0
# Date generated : Tue Jun 19 07:31:02 2007
# Generated by: makepatch 2.03
# Recurse directories : Yes
# Excluded files : (\A|/).*\~\Z
# (\A|/).*\.a\Z
# (\A|/).*\.bak\Z
# (\A|/).*\.BAK\Z
# (\A|/).*\.elc\Z
# (\A|/).*\.exe\Z
# (\A|/).*\.gz\Z
# (\A|/).*\.ln\Z
# (\A|/).*\.o\Z
# (\A|/).*\.obj\Z
# (\A|/).*\.olb\Z
# (\A|/).*\.old\Z
# (\A|/).*\.orig\Z
# (\A|/).*\.rej\Z
# (\A|/).*\.so\Z
# (\A|/).*\.Z\Z
# (\A|/)\.del\-.*\Z
# (\A|/)\.make\.state\Z
# (\A|/)\.nse_depinfo\Z
# (\A|/)core\Z
# (\A|/)tags\Z
# (\A|/)TAGS\Z
# p 'contrib/csup/proto.c.old' 25477 1182245491 0100644
End of ApplyPatch data
End of Patch kit [created: Tue Jun 19 07:31:02 2007]
Patch checksum: 73 2412 32655
Checksum: 91 3047 19426
# misc/113825
#
# To apply this patch:
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'applypatch' program with this patch file as input.
#
# If you do not have 'applypatch', it is part of the 'makepatch' package
# that you can fetch from the Comprehensive Perl Archive Network:
# http://www.perl.com/CPAN/authors/Johan_Vromans/makepatch-x.y.tar.gz
# In the above URL, 'x' should be 2 or higher.
#
# To apply this patch without the use of 'applypatch':
# STEP 1: Chdir to the source directory.
# STEP 2: Run the 'patch' program with this file as input.
#
End of Preamble
Patch data follows
diff -ruN 'sbin/ggate/ggated/ggated.c.old' 'sbin/ggate/ggated/ggated.c'
Index: ./sbin/ggate/ggated/ggated.c.old
--- ./sbin/ggate/ggated/ggated.c.oldMon Jun 18 23:05:16 2007
+++ ./sbin/ggate/ggated/ggated.cMon Jun 18 23:08:02 2007
@@ -756,6 +756,7 @@
error = pthread_mutex_unlock(outqueue_mtx);
assert(error == 0);
}
+ return arg;
}
static void *
@@ -810,6 +811,7 @@
}
free(req);
}
+ return arg;
}
static void
End of Patch data
ApplyPatch data follows
# Data version: 1.0
# Date generated : Tue Jun 19 07:35:00 2007
# Generated by: makepatch 2.03
# Recurse directories : Yes
# Excluded files : (\A|/).*\~\Z
# (\A|/).*\.a\Z
# (\A|/).*\.bak\Z
# (\A|/).*\.BAK\Z
# (\A|/).*\.elc\Z
# (\A|/).*\.exe\Z
# (\A|/).*\.gz\Z
# (\A|/).*\.ln\Z
# (\A|/).*\.o\Z
# (\A|/).*\.obj\Z
#
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
kern.securelevel: -1 and the permessions on /bin and / is the correct :[ 2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]: On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote: My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Could be caused by some filesystem mount options you've got set, maybe incorrect permissions on /bin (no execute bit?), or possibly a secure runlevel setting (which I believe was the cause of your last issue you reported here). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
I do chflags noschg /bin and its work :) 2007/6/15, ExTaZyTi [EMAIL PROTECTED]: kern.securelevel: -1 and the permessions on /bin and / is the correct :[ 2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]: On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote: My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Could be caused by some filesystem mount options you've got set, maybe incorrect permissions on /bin (no execute bit?), or possibly a secure runlevel setting (which I believe was the cause of your last issue you reported here). -- | Jeremy Chadwickjdc at parodius.com| | Parodius Networking http://www.parodius.com/| | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
ExTaZyTi wrote: Hi, My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Stop in /usr/src/bin/cat. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. If someone can help me. Thanks in advance. It could be caused /tmp is mounted with noexec, or by securelevel settings. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with installworld in FreeBSD 6.2-RELEASE-p5
Hi, My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Stop in /usr/src/bin/cat. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. If someone can help me. Thanks in advance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote: My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Could be caused by some filesystem mount options you've got set, maybe incorrect permissions on /bin (no execute bit?), or possibly a secure runlevel setting (which I believe was the cause of your last issue you reported here). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 ExTaZyTi wrote: Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: [...] ..now example for nptdate: [EMAIL PROTECTED] (~)]: ntpdate otel.net Try using -b switch: # ntpdate -b otel.net HTH, Karol - -- Karol Kwiatkowski karol.kwiat at gmail dot com OpenPGP 0x06E09309 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGbl0ZezeoPAwGIYsRCEdWAJwMAQosHGupsVGApRe9MBP8W8H3hwCfWe3T kfA7L+jxaclQIK+MAVryiIQ= =1/PV -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [format recovered, please don't top-post] [also keep @freebsd-stable in cc] ExTaZyTi wrote: 2007/6/12, Karol Kwiatkowski [EMAIL PROTECTED]: ExTaZyTi wrote: Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: [...] ..now example for nptdate: [EMAIL PROTECTED] (~)]: ntpdate otel.net Try using -b switch: # ntpdate -b otel.net oh this again return 4 minutes different :( Hmmm... strange. Do you have ntpd running? What does those commands say: # ps aux | grep ntp # ntpq -np - -- Karol Kwiatkowski karol.kwiat at gmail dot com OpenPGP 0x06E09309 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGbmGSezeoPAwGIYsRCF3YAJ0b1GVju6wHCYl0hXBPtyzJ7caB/QCeM0cD a/YGiqwcjeLzr5d+2uMkjtc= =T70Z -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
Hi all, Karol Kwiatkowski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [format recovered, please don't top-post] [also keep @freebsd-stable in cc] ExTaZyTi wrote: 2007/6/12, Karol Kwiatkowski [EMAIL PROTECTED]: ExTaZyTi wrote: Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: [...] ..now example for nptdate: [EMAIL PROTECTED] (~)]: ntpdate otel.net Try using -b switch: # ntpdate -b otel.net oh this again return 4 minutes different :( Hmmm... strange. Do you have ntpd running? What does those commands say: # ps aux | grep ntp # ntpq -np After private conversation with ExTaZyTi : The problem with time was because of kern.securelevel = 2 ;) hardware DDoS .. well it's just a DoS in his case. -cut- -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
There are some problems, first DDoS (hardware DDoS) in the system. I compile some program and when start it my system blocks and restart (tested and on other system 6.2-stable and again this DDoS). To prevent users from DDoS some systems i not going to upload this program in the web. The next DDoS (I don't know about his..) somebody (..any h4x0r) send every day to me hardware DDoS attack .. then my system full block and drop my interner connection, when i try to RE-ENABLE my connection to the DHCP server it's says connecting.. without any answer i think it's becouse my server is full blocked.. I have open this ports : 53(domain..standart..), 25(mail servers..), 80(apache), 110(mail servers..), 113(identd), 443(apache), (ircd), 6667(ircd), 7000(ircd), 9000(ircd) .. i can't find the DDoS.. please somebody to help me this hardware DDoS to my system. Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: [EMAIL PROTECTED] (~)]: date 0706111826.40 date: can't reach time daemon, time set locally Mon Jun 11 18:26:40 EEST 2007 [EMAIL PROTECTED] (~)]: date Mon Jun 11 18:23:55 EEST 2007 [EMAIL PROTECTED] (~)]: ..now example for nptdate: [EMAIL PROTECTED] (~)]: ntpdate otel.net 11 Jun 18:25:08 ntpdate[5157]: step time server 212.36.8.133 offset 218.607216 sec [EMAIL PROTECTED] (~)]: date Mon Jun 11 18:25:09 EEST 2007 but the original world time for my country is: 18:28:58... can somebody help me to fix this errors.. please! Thanks in advance. Best regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On 06/11/07 17:30, ExTaZyTi wrote: There are some problems, first DDoS (hardware DDoS) in the system. 'hardware DDoS'... funny thing! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
ExTaZyTi wrote this message on Mon, Jun 11, 2007 at 18:30 +0300: There are some problems, first DDoS (hardware DDoS) in the system. I compile some program and when start it my system blocks and restart (tested and on other system 6.2-stable and again this DDoS). Please email the FreeBSD security team w/ the program as per: http://www.freebsd.org/security/#how [...] Next problem is the clock, have e 4 minuts different from the world time for my country. I try to fix this with a ntpdate otel.net for example .. this again return 4 minutes different. I try and the date command but it's NOT WORK..You can see: This is because the timezone you are using is incorrect. FreeBSD stores the system time in UTC and then converts to the local timezone. If you use the correct timezone (you can set this by running tzsetup) this should not be a problem. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Jun 11, 2007, at 10:46 AM, Kevin K. wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS I'm not sure what the OP meant, but I can provide examples of a hardware DDoS. Way back when, certain machines were equipped with a Motorola/TI 56001 DSP, which had three separate, parallel execution units, and was an early example of SIMD/VLIW design. It turns out that if you issued an instruction to all three pipelines [1] which loaded or saved to the same memory address, you would fry the DSP chip. The compiler used to generate the code for the 56K DSP chip would prevent this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) -- -Chuck [1] IIRC, it could deal with two pipelines hitting the same address, but not all three. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On 6/11/07, Kevin K. [EMAIL PROTECTED] wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k It's very clear that English isn't his mother language, and he may means the DDoS he gets kills his box cpu ..etc. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Is your example not just a plain old Denial of Service (DoS) ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
Abdullah Ibn Hamad Al-Marri wrote: On 6/11/07, Kevin K. [EMAIL PROTECTED] wrote: There are some problems, first DDoS (hardware DDoS) in the system. I'd like to know what you mean by hardware DDoS ~k It's very clear that English isn't his mother language, and he may means the DDoS he gets kills his box cpu ..etc. May be because Otel.net is in Bulgaria I have the feeling that his mother language is bulgarian .. and his age is 11? :) Shame that google now hide the IP of the sender :( Now, if you explain little more about your problem and forget for the hardware DDOS we can help ? :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Jun 11, 2007, at 1:57 PM, Mike Tancsa wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Yes, it is. Is your example not just a plain old Denial of Service (DoS) ? Yes, as it stands. But if you ship this code to other machines, perhaps it would then qualify as being _Distributed_? :-) / 2 -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Monday 11 June 2007 18:05:59 Chuck Swiger wrote: On Jun 11, 2007, at 1:57 PM, Mike Tancsa wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Yes, it is. Is your example not just a plain old Denial of Service (DoS) ? Yes, as it stands. But if you ship this code to other machines, perhaps it would then qualify as being _Distributed_? :-) / 2 clever switch but still wrong ... DDoS is ONE target and multi-source but not multi-target and local source :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
* Mike Tancsa [EMAIL PROTECTED] [070611 13:58] wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Is your example not just a plain old Denial of Service (DoS) ? Well it takes 3 execution pipelines... -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd 6.2 Interrupted system call (4) when exit from mc
Hi ALL When I start mc, and do Ctrl+o,and then write exit - I got... Sometime this heppend when I close some shell-aplication with Ctrl+C/D I setup FreeBSD 6.2RC1 and FreeBSD 6.2-stable... When I have 6.1 - I dont catch this 6.2-RELEASE-p4:server/exit read (subshell_pty...): Interrupted system call (4) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd 6.2 Interrupted system call (4) when exit from mc
When I start mc, and do Ctrl+o,and then write exit - I got... Sometime this heppend when I close some shell-aplication with Ctrl+C/D I setup FreeBSD 6.2RC1 and FreeBSD 6.2-stable... When I have 6.1 - I dont catch this If I get it right, it should be midnight commander? Exits fine with F10. On my nokia 770 I go out with just escape 0. Yes, I see some issue with xchm from mc, but ctrl l resolves it. Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
Hi, FreeBSD 6.2 Kernel don't support Broadcom NIC BCM 5708S model. One need to patch kernel Source to make it live. Below i written steps i took. 1, Download patch http://people.freebsd.org/~dwhite/patches/bce-serdes-20070111.tar.gz 2, cd /usr/src/sys/i386/conf 3, cp GENRIC MYKERNEL 4, mkdir /root/kernels 5, cp GENRIC /root/kernels/MYKERNEL 6. ln -s /root/kernels/MYKERNEL 7, cd /usr/src 8, make buildkernel KERNCONF=MYKERNEL 9 make installkernel KERNCONF=MYKERNEL Now Reboot !! Sachin Sharma Sr. Engineer Systems (Linux) Net4India Ltd. D-25 Sector 3 Noida-201301 INDIA Tel: 0120-5323500 Fax: 0120-5323520 URL: http://www.net4.in This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. Scott Long wrote: Sachin Sharma wrote: Hi All, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. Thanks Support for this card has been added since 6.2 was released. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
2007/5/16, Sachin Sharma [EMAIL PROTECTED]: Hi, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. it works with 6.2-STABLE. download a 6.2 snapshot and install it. works fine here -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
On Thu, May 17, 2007 at 07:08:39PM +0530, Sachin Sharma wrote: Hi, FreeBSD 6.2 Kernel don't support Broadcom NIC BCM 5708S model. One need to patch kernel Source to make it live. Below i written steps i took. 1, Download patch http://people.freebsd.org/~dwhite/patches/bce-serdes-20070111.tar.gz 2, cd /usr/src/sys/i386/conf 3, cp GENRIC MYKERNEL 4, mkdir /root/kernels 5, cp GENRIC /root/kernels/MYKERNEL 6. ln -s /root/kernels/MYKERNEL 7, cd /usr/src 8, make buildkernel KERNCONF=MYKERNEL 9 make installkernel KERNCONF=MYKERNEL Now Reboot !! The code/patch in question was committed to the RELENG_6 tree a while ago. All you need to do is cvsup/csup your sourcecode to the most recent snapshot/version of 6.2 (not what's on the CD, and not 6.2-RELEASE), and that should suffice. For instructions on how to do this, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Note that 6, however, comes with a tool called csup (the C version of cvsup), which performs identically and does not require you to install ports/net/cvsup. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
Hi All, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. Thanks -- Sachin Sharma Sr. Engineer Systems (Linux) Net4India Ltd. D-25 Sector 3 Noida-201301 INDIA Tel: 0120-5323500 Fax: 0120-5323520 URL: http://www.net4.in This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
On Wed, 2007-05-16 at 19:42 +0530, Sachin Sharma wrote: Hi All, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. Thanks Please provide output of /usr/sbin/pciconf -lv and contents of /var/log/dmesg.boot after rebooting in verbose mode (at loader, choose loader prompt and enter 'boot -v'. signature.asc Description: This is a digitally signed message part
Re: NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server
Sachin Sharma wrote: Hi All, NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server. I need FreeBSD in these server . Please help me. Thanks Support for this card has been added since 6.2 was released. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 frequent crashes (IPv6 related?)
We commisioned a new box running FreeBSD 6.2 Stable (as of Sunday
afternoon UK time), to replace a broken 4.x box.
It has been crashing around once per day since then. I have gathered a
couple of cores so far and it looks like it's the same thing causing the
crash. I'm no expert in reading these things, but it looks like it's
happening the IPv6 stack? This host is IPv6 connected whereas our other
6.x boxes aren't..
The stack traces are attached below. Any help would be much appreciated.
Thanks
Jake
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:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x104
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0512029
stack pointer = 0x28:0xf388b88c
frame pointer = 0x28:0xf388b8a0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 682 (named)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1d4h14m2s
Dumping 3839 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 3839MB (982743 pages) 3823 3807 3791 3775 3759 3743 3727 3711 3695
3679 3663 3647 3631 3615 3599 3583 3567 3551 3535 3519 3503 3487 3471 3455 3439
3423 3407 3391 3375 3359 3343 3327 3311 3295 3279 3263 3247 3231 3215 3199 3183
3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959 2943 2927
2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703 2687 2671
2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463 2447 2431 2415
2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159
2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903
1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647
1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391
1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135
1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847
831 815 799 783 767 751 735 719
703 687 671 655 639 623 607 591 575 559 543 527 511 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
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc051c88e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc051cc3f in panic (fmt=0xc06f2b48 %s)
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0xc06cd925 in trap_fatal (frame=0xf388b84c, eva=0)
at /usr/src/sys/i386/i386/trap.c:837
#4 0xc06cd00d in trap (frame=
{tf_fs = -1067581432, tf_es = -209190872, tf_ds = -922091480, tf_edi =
-919646848, tf_esi = 4, tf_ebp = -209143648, tf_isp = -209143688, tf_ebx =
-917625596, tf_edx = 6, tf_ecx = 3, tf_eax = 1, tf_trapno = 12, tf_err = 0,
tf_eip = -1068425175, tf_cs = 32, tf_eflags = 65538, tf_esp = -917625596, tf_ss
= -917667672}) at /usr/src/sys/i386/i386/trap.c:270
#5 0xc06b694a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc0512029 in _mtx_lock_sleep (m=0xc94e2504, tid=3375320448, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:546
#7 0xc05ece2e in nd6_output (ifp=0xc90a6800, origifp=0x1, m0=0xc9824b00,
dst=0xc92d001c, rt0=0xc94e2528) at /usr/src/sys/netinet6/nd6.c:2010
#8 0xc05e6036 in ip6_output (m0=0xf388ba60, opt=0xc95f2500, ro=0xf388ba60,
flags=0, im6o=0x0, ifpp=0x0, inp=0xc94df438)
at /usr/src/sys/netinet6/ip6_output.c:994
#9 0xc05f626c in udp6_output (in6p=0xc94df438, m=0xc9824b00,
addr6=0xc9824ba8, control=0x0, td=0xc92f4d80)
at /usr/src/sys/netinet6/udp6_output.c:322
#10 0xc05f7afc in udp6_send (so=0xc94e7c84, flags=1, m=0xc9824b00,
addr=0xc926ad20, control=0x0, td=0xc92f4d80)
at /usr/src/sys/netinet6/udp6_usrreq.c:794
#11 0xc0561094 in sosend (so=0xc94e7c84, addr=0xc926ad20, uio=0xf388bc30,
top=0xc9824b00, control=0x0, flags=0, td=0xc92f4d80)
at /usr/src/sys/kern/uipc_socket.c:836
#12 0xc0567be4 in kern_sendit (td=0xc92f4d80, s=31, mp=0xf388bca8, flags=0,
control=0x1, segflg=UIO_SYSSPACE) at /usr/src/sys/kern/uipc_syscalls.c:772
#13 0xc0567a6d in sendit (td=0x1, s=1, mp=0xf388bca8, flags=1)
at /usr/src/sys/kern/uipc_syscalls.c:712
#14 0xc0567f64 in sendmsg (td=0x1, uap=0xf388bd04)
at /usr/src/sys/kern/uipc_syscalls.c:920
#15 0xc06cdd0c in syscall (frame=
{tf_fs = 135987259, tf_es = 163446843
make buildworld on Freebsd 6.2 amd64 stops on ifconfig.l
Hi the following occurs when trying to make buildworld once cvsup'd to
stable, any idea's?
Environment:
FreeBSD xxx.xxx.xxx.xxx 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #1: Wed Apr 18
10:29:35 WST 2007 [EMAIL PROTECTED] :/usr/src/sys/amd64/compile/PHEONIX
amd64
Description:
ld -dc -r -o fdisk.lo fdisk_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/fdisk/fdisk.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/fdisk/geom_mbr_enc.o
crunchide -k _crunched_fdisk_stub fdisk.lo
echo int _crunched_dhclient_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} dhclient_stub.c
cc -O2 -fno-strict-aliasing -pipe -c dhclient_stub.c
ld -dc -r -o dhclient.lo dhclient_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/dhclient.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/clparse.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/alloc.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/dispatch.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/hash.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/bpf.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/options.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/tree.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/conflex.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/errwarn.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/inet.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/packet.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/convert.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/tables.o
/usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/parse.o /usr/o
bj/usr/src/rescue/rescue//usr/src/sbin/dhclient/privsep.o
crunchide -k _crunched_dhclient_stub dhclient.lo
echo int _crunched_gzip_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} gzip_stub.c
cc -O2 -fno-strict-aliasing -pipe -c gzip_stub.c
ld -dc -r -o gzip.lo gzip_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/gzip/gzip.o
crunchide -k _crunched_gzip_stub gzip.lo
echo int _crunched_bzip2_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} bzip2_stub.c
cc -O2 -fno-strict-aliasing -pipe -c bzip2_stub.c
ld -dc -r -o bzip2.lo bzip2_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/bzip2/bzip2.o
crunchide -k _crunched_bzip2_stub bzip2.lo
echo int _crunched_tar_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} tar_stub.c
cc -O2 -fno-strict-aliasing -pipe -c tar_stub.c
ld -dc -r -o tar.lo tar_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/bsdtar.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/getdate.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/matching.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/read.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/tree.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/util.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/tar/write.o
crunchide -k _crunched_tar_stub tar.lo
echo int _crunched_vi_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);} vi_stub.c
cc -O2 -fno-strict-aliasing -pipe -c vi_stub.c
ld -dc -r -o vi.lo vi_stub.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_bsd.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_funcs.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_main.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_read.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_screen.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cl_term.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/cut.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/delete.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/exf.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/key.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/line.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/log.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/main.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/mark.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/msg.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/options.o /usr/obj/usr/
src/rescue/rescue//usr/src/usr.bin/vi/options_f.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/put.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/screen.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/search.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/seq.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/recover.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/util.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_abbrev.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_append.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_args.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_argv.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_at.o
/usr/obj/usr/src/rescue/rescue//usr/src/usr.bin/vi/ex_bang.o
/usr/obj/usr/src/rescue/rescue//usr/src
Re: Clamav-90_2 Lockup with freebsd 6.2
Martin Blapp [EMAIL PROTECTED] writes: Hi, I just fixed those issues with the port. Thanks for reporting ! So we can safely use libpthread.so again? No need to use libmap.conf? -- One cannot sell the earth upon which the people walk Tacunka Witco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Clamav-90_2 Lockup with freebsd 6.2
Hi, I am not sure why. But my dual xeon with libthr on clamav-90.1 still gives very high cpu usage. Is it fixed yet? Di -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Blapp Sent: Saturday, 17 March 2007 1:00 AM To: Laurent Frigault Cc: Rob MacGregor; clamav-devel@lists.clamav.net; freebsd-stable@freebsd.org Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Hi, I just fixed those issues with the port. Thanks for reporting ! Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Clamav-90_2 Lockup with freebsd 6.2
Hi, I am not sure why. But my dual xeon with libthr on clamav-90.1 still gives very high cpu usage. It's the same case here. What happens if you limit kern.smp.maxcpus to 1 ? Does it still use the same amount cpu time ? What happens if you link clamd against libc_r ? -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imap-uw on FreeBSD 6.2
Václav Haisman wrote: Willy Offermans wrote: The following error appears regularly on my FreeBSD 6.2 server called sun. The frequency of appearance is higher than on FreeBSD 6.1, where I had this error from time to time. The error is not critical, since a new instance of the imap program is started upon the crash, I guess. At least the client users are not complaining about errors or interruptions of the mail client. Mar 13 09:51:10 sun kernel: pid 46336 (imapd), uid 1012: exited on signal 6 Mar 13 09:51:10 sun imapd Mar 13 09:51:10 sun in free(): Mar 13 09:51:10 sun error: Mar 13 09:51:10 sun chunk is already free I use imap-uw on FreeBSD 6.2. I get the same error occasionally, too. It doesn't seem to affect functionality. I advise you against using IMAP UW, unless you know your mailboxes won't grow beyond just few megabytes or that there will be only few of them. Their reading and rewriting of whenever you make changes can stress server quite a lot. I'm not specifically advising against UW imapd, but I've been using dovecot (ports/mail/dovecot) for several years without any problems. It was absolutely painless to install and configure, and it's humming along perfectly fine. So if you decide to change to a different imapd, I recommend that you have a look at dovecot. Just my two cents. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Hi, I just fixed those issues with the port. Thanks for reporting ! Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imap-uw on FreeBSD 6.2
Hi, I recommend that you have a look at dovecot. Yeah, and consider maildir instead of mbox. Have a great weekend. Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
imap-uw on FreeBSD 6.2
Dear FreeBSD friends, The following error appears regularly on my FreeBSD 6.2 server called sun. The frequency of appearance is higher than on FreeBSD 6.1, where I had this error from time to time. The error is not critical, since a new instance of the imap program is started upon the crash, I guess. At least the client users are not complaining about errors or interruptions of the mail client. Mar 13 09:51:10 sun kernel: pid 46336 (imapd), uid 1012: exited on signal 6 Mar 13 09:51:10 sun imapd Mar 13 09:51:10 sun in free(): Mar 13 09:51:10 sun error: Mar 13 09:51:10 sun chunk is already free I use imap-uw on FreeBSD 6.2. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imap-uw on FreeBSD 6.2
Willy Offermans wrote: Dear FreeBSD friends, The following error appears regularly on my FreeBSD 6.2 server called sun. The frequency of appearance is higher than on FreeBSD 6.1, where I had this error from time to time. The error is not critical, since a new instance of the imap program is started upon the crash, I guess. At least the client users are not complaining about errors or interruptions of the mail client. Mar 13 09:51:10 sun kernel: pid 46336 (imapd), uid 1012: exited on signal 6 Mar 13 09:51:10 sun imapd Mar 13 09:51:10 sun in free(): Mar 13 09:51:10 sun error: Mar 13 09:51:10 sun chunk is already free I use imap-uw on FreeBSD 6.2. I get the same error occasionally, too. It doesn't seem to affect functionality. I advise you against using IMAP UW, unless you know your mailboxes won't grow beyond just few megabytes or that there will be only few of them. Their reading and rewriting of whenever you make changes can stress server quite a lot. -- VH signature.asc Description: OpenPGP digital signature
Re: imap-uw on FreeBSD 6.2
On Thu, Mar 15, 2007 at 12:29:48PM +0100, Václav Haisman wrote: Willy Offermans wrote: Dear FreeBSD friends, The following error appears regularly on my FreeBSD 6.2 server called sun. The frequency of appearance is higher than on FreeBSD 6.1, where I had this error from time to time. The error is not critical, since a new instance of the imap program is started upon the crash, I guess. At least the client users are not complaining about errors or interruptions of the mail client. Mar 13 09:51:10 sun kernel: pid 46336 (imapd), uid 1012: exited on signal 6 Mar 13 09:51:10 sun imapd Mar 13 09:51:10 sun in free(): Mar 13 09:51:10 sun error: Mar 13 09:51:10 sun chunk is already free I use imap-uw on FreeBSD 6.2. I get the same error occasionally, too. It doesn't seem to affect functionality. I advise you against using IMAP UW, unless you know your mailboxes won't grow beyond just few megabytes or that there will be only few of them. Their reading and rewriting of whenever you make changes can stress server quite a lot. Dear Václav Haisman, Thnx for the response. Indeed the error does not seem to affect the functionality. You are right that the imapd starts to consume a significant amount of CPU time. I have noticed this quite recently. Maybe it is about time to move to another imap daemon. I will have a look to this. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Imap-use] Re: imap-uw on FreeBSD 6.2
On Thu, 15 Mar 2007, Willy Offermans wrote: On Thu, Mar 15, 2007 at 12:29:48PM +0100, Václav Haisman wrote: I advise you against using IMAP UW, unless you know your mailboxes won't grow beyond just few megabytes or that there will be only few of them. Their reading and rewriting of whenever you make changes can stress server quite a lot. The problem with taking advice from a sorcerer's apprentice is that often the advice is only half-right, or based upon incomplete knowledge. The large I/O situation described by Václav Haisman is indeed a characteristic of the 1970s vintage traditional UNIX mailbox format which is the default mailbox format in UW imapd. The traditional UNIX mailbox format requires that the program using it read every byte of the mailbox in order to locate the From internal header line, and thus to locate and identify messages. The traditional UNIX mailbox format requires that message metadata as variable-length lines in the message headers. Alteration of that metadata often requires rewriting the remainder of the file as data is slid up or down. I say often, since UW imapd insert a modest amount of padding data so that some alterations can be done that only require rewriting the message data and nothing else. Another problem, endemic to all flat file mailbox formats, is that an expunge operation also requires sliding down subsequent messages on top of the message being expunged. However, please note that these are characteristics of a mailbox FORMAT, and not of the IMAP server software. UW imapd supports several mailbox formats, most notably: . The mbx mailbox format is a flat file format with preallocated message metadata and message pointers. The read-every-byte open of traditional UNIX mailbox format becomes a per-message seek and 64 byte read in mbx format. mbx was a great choice in the mid 1990s when it was designed, but it has gotten long in the tooth. . The new mix format is an indexed format in which all the message metadata is stored and maintained in a separate index. Opens are 1 to 2 orders of magnitude faster than mbx, which in turn is faster than traditional UNIX. Messages are distributed into multiple data files, so there are no large files. Mix is the format that large sites in the UW imapd community have either deployed or are moving to deploy. What this all means is that, yes, switching your IMAP server to another server will probably help your performance -- because that other IMAP server will change your mailbox format to something else! You can, however, change your mailbox format to something else in UW imapd without switching your IMAP server, and achieve the same benefit. Traditional UNIX format is the UW imapd default -- UW imapd pays considerable attention to compatibility and interoperability with existing legacy services -- but most UW imapd sites quickly switch formats to a newer technology format. This is what I meant by half-right advice and incomplete knowledge. Your performance problem is due to mailbox format, not the server software. Change your mailbox format, and your problems will be solved (at least until your usage grows to fill the greater capacity provided by the new mailbox format...). If you do decide to switch servers anyway, the two competing servers which you should consider are Cyrus and Dovecot. The developers of those servers are active participants in the IMAP protocol standards community, and all of us (UW, Cyrus, Dovecot) talk with each other and go to considerable effort to make our respective implementations interoperable and compliant. I will leave it to the Cyrus and Dovecot folks to toot their own horns. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote.___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: imap-uw on FreeBSD 6.2
On Mar 15, 2007, at 6:29 AM, Václav Haisman wrote: I advise you against using IMAP UW, unless you know your mailboxes won't grow beyond just few megabytes or that there will be only few of them. Their reading and rewriting of whenever you make changes can stress server quite a lot. This is only true if you use one of the deprecated mailbox formats such as mbox (unix). However, if you use the recommended mailbox format, mbx, you will have no problems with large mailboxes. See http://www.washington.edu/imap/documentation/formats.txt.html I have little problem with mbx files containing tens of thousands of messages. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
[snip patch] Does this patch make the libmap.conf hack unneeded? I frist thought so, but no, the more threads are running concurrently the slower libpthreads behaves, as it gets more lock contention. Until this is addressed somehow, use libthr.so FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. It's an easier to detect and manage situation, but if you're counting on clamav's presence, I strongly recommend the use of an external watchdog process. Best Regards, Kevin Way Inside Systems, Inc. smime.p7s Description: S/MIME Cryptographic Signature
Re: [Imap-use] Re: imap-uw on FreeBSD 6.2
Mark Crispin wrote: . The new mix format is an indexed format in which all the message metadata is stored and maintained in a separate index. Opens are 1 to 2 orders of magnitude faster than mbx, which in turn is faster than traditional UNIX. Messages are distributed into multiple data files, so there are no large files. Mix is the format that large sites in the UW imapd community have either deployed or are moving to deploy. Hmm, the version of imap-uw in FreeBSD ports is 2004g, and it looks like it doesn't support the mix format. Port: imap-uw-2004g_1,1 Path: /usr/ports/mail/imap-uw Info: University of Washington IMAP4rev1/POP2/POP3 mail servers Maint: anders/FreeBSD.org B-deps: cclient-2004g,1 R-deps: cclient-2004g,1 WWW:http://www.washington.edu/imap/ Is mix in the current release version of UW imapd? signature.asc Description: OpenPGP digital signature
Re: Clamav-90_2 Lockup with freebsd 6.2
At 01:52 PM 3/15/2007, Kevin Way wrote: FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. Hi, I think there are other bugs in the current clamd, the main one that we run into is when it tries to reload the database, and it somehow confuses itself and exits. http://lurker.clamav.net/message/20070314.170629.9118e704.en.html ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Mike Tancsa unleashed the infinite monkeys on 15/03/2007 19:58 producing: At 01:52 PM 3/15/2007, Kevin Way wrote: FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. Hi, I think there are other bugs in the current clamd, the main one that we run into is when it tries to reload the database, and it somehow confuses itself and exits. http://lurker.clamav.net/message/20070314.170629.9118e704.en.html At least on FreeBSD 5.4 I think I've tracked the problem down to -lthr: http://www.freebsd.org/cgi/query-pr.cgi?pr=110352 Using either -lpthread or simply not using -lthr clamd (for me) doesn't crash (well, not yet :). Only happens to me with 0.90.1 in daemon mode. With 0.90_x or 0.90.1 in foreground mode it stays running afer the selfcheck. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
On Thu, Mar 15, 2007 at 08:28:10PM +, Rob MacGregor wrote: FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. Hi, I think there are other bugs in the current clamd, the main one that we run into is when it tries to reload the database, and it somehow confuses itself and exits. http://lurker.clamav.net/message/20070314.170629.9118e704.en.html At least on FreeBSD 5.4 I think I've tracked the problem down to -lthr: http://www.freebsd.org/cgi/query-pr.cgi?pr=110352 Using either -lpthread or simply not using -lthr clamd (for me) doesn't crash (well, not yet :). Only happens to me with 0.90.1 in daemon mode. With 0.90_x or 0.90.1 in foreground mode it stays running afer the selfcheck. I have seen several clamd locks under 5.5 + libthr with 0.90.1 . No problem under 5.5 with pthread . See the 2nd part of http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/110334 regards, -- Laurent Frigault | url:http://www.agneau.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [hylafax-users] notify script on FreeBSD 6.2
On Tue, Mar 13, 2007 at 08:23:15AM -0400, Aidan Van Dyk wrote: * Willy Offermans [EMAIL PROTECTED] [070313 07:51]: Dear hylaFAX friends, Running HylaFAX 4.3.2 on FreeBSD 6.2 produces following error: nawk -f bin/b64-encode.awk /tmp/tmp-50791/body.txt The encoding ends up in a loop! The workaround is to use gawk instead of nawk on FreeBSD for the b64-encoding. I forgot about the differences between awk, nawk and gawk on FreeBSD, but it could be related to a special implementation of awk under FreeBSD. I will try to replace nawk by gawk in setup.cache. If I don't post a next message you can assume that it works. Any chance I could get access to a freebsd account with nawk? We'ld certainly like to get it working. But seeing as you're using the fallback awk encoder, is it true that you don't have any of mimencode, base64-encode, or uuencode installed on your system? If you do, did you re-run faxsetup? a. Dear Aidan, Sure you can have access to the FreeBSD machine. If I can contribute to the ``development'' of hylaFAX, although in a very passive manner, I'm always willing to do so. If you can send me your IP address and possible username in private, I can make an account for you. However I have to tell you that this is a production machine and although it is only a small network, it is very precious to me and the users. If you need an account, be cautious. Indeed I found a possible error in setup.cache MIMENCODE='base64-encode' I do not have a program called base64-encode, it is called base64 under FreeBSD, I guess. So I will play with the settings for AWK='/usr/local/bin/gawk' or AWK='/usr/bin/nawk' and MIMENCODE='base64-encode'. How can I trigger that base64 is used instead of bin/b64-encode.awk? Probably I find myself a solution if I look carefully. mimencode is neither installed nor a FreeBSD port. It could be part of a port, I will look it up. uuencode is properly installed. Some googling learned met that nawk is a newer awk. An enhanced version of AWK, with dynamic regular expressions, additional built-ins ... Most probably you can install it on a linux machine as well, assuming that you have access to a linux machine. It seems __not__ to be a FreeBSD implementation of awk. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [hylafax-users] notify script on FreeBSD 6.2
Dear Aidan, On Tue, Mar 13, 2007 at 09:38:46AM -0400, Aidan Van Dyk wrote: * Willy Offermans [EMAIL PROTECTED] [070313 09:27]: Dear Aidan, Sure you can have access to the FreeBSD machine. If I can contribute to the ``development'' of hylaFAX, although in a very passive manner, I'm always willing to do so. If you can send me your IP address and possible username in private, I can make an account for you. However I have to tell you that this is a production machine and although it is only a small network, it is very precious to me and the users. If you need an account, be cautious. Of course - I'll be coming from testbed.hylafax.org, and would use the following SSH key: ssh-rsa B3NzaC1yc2EBIwAAAQEA8+JLWJF/OP9niTz0fQYqg/T5tF/xQMBLlk+QNq3YXKtoiRhBMwLT1NPySqJzii9BpiSo04Kne62Ij7Q09boLBznmjWp9V7k4ocwqm9xBJ2w8KzYa4zRYcL1417iKsQh5AU7+ZZtavTNPhif0jHFetljnK1gkMZvLTYAjwOtyS4dTs4ygT18NlmPd4/v9o7on7RlFvZSQOI1eeN4RGOR1xwCY7CBos7qPk2t+ijbXbbMnsU8+ackfLjcY3eKb3/46yBol+4Yl5o8jPabPc+PQiH+yAl6rlhTPQMhpQgdxR7JpQqbQFnphanlEU6G6A/pFBIAcpvILo+viswk9OzdI3Q== [EMAIL PROTECTED] I need some time to change the firewall, please be patient. Indeed I found a possible error in setup.cache MIMENCODE='base64-encode' I do not have a program called base64-encode, it is called base64 under FreeBSD, I guess. So I will play with the settings for AWK='/usr/local/bin/gawk' or AWK='/usr/bin/nawk' and MIMENCODE='base64-encode'. How can I trigger that base64 is used instead of bin/b64-encode.awk? Probably I find myself a solution if I look carefully. mimencode is neither installed nor a FreeBSD port. It could be part of a port, I will look it up. uuencode is properly installed. Hmm.. We only check for base64-encode, not base64. But we can add a check for base64 as well. If you set BASE64ENCODE=/usr/bin/base64 (or the correct path) in setup.cache, then the mime encode functions in common-functions should use it. I encounter some problems with that: sun# grep BASE64ENCODE bin/* bin/common-functions:# rather than separate $BASE64ENCODE and $QPENCODE bin/common-functions: if [ -n $BASE64ENCODE ]; then bin/common-functions: # $BASE64ENCODE may contain parameters bin/common-functions: cmd=`programOfCommand $BASE64ENCODE` bin/common-functions: (eval $BASE64ENCODE) $1 2$ERRORSTO sun# grep BASE64ENCODE etc/* It looks like I have an old setup.cache file, although I have run faxsetup. Aha indeed I have to add BASE64ENCODE='/usr/local/bin/base64' to the etc/setup.cache file. That works! So probably you have to test for base64 as well! Does your uuencode support the -m flag to do base64 mime encoding? Basically, in faxsetup, we look for: 1) mimencode 2) base64-encode 3) uuencode -m if any of these are found, BASE64ENCODE is set to what was found. In common functions, if BASE64ENCODE is good, we use it, and if it isn't, we fall back to the awk based b64-encode.awk, which we hoped would work on anything ;-) Ohoh, setting BASE64ENCODE='/usr/bin/uuencode -m' in etc/setup.cache did produce a notification e-mail, but the attached pdf file is totally empty. So this does not work either. Some googling learned met that nawk is a newer awk. An enhanced version of AWK, with dynamic regular expressions, additional built-ins ... Most probably you can install it on a linux machine as well, assuming that you have access to a linux machine. It seems __not__ to be a FreeBSD implementation of awk. It doesn't seem to be packaged for debian. Resume, there is some work to do with respect to BASE64ENCODE and nawk, base64 and uuencode under FreeBSD. mimencode still needs to be tested. I will contact you as soon as possible dear Aidan. -- Aidan Van Dyk [EMAIL PROTECTED] Senior Software Developer +1 215 825-8700 x8103 iFAX Solutions, Inc.http://www.ifax.com/ -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: [EMAIL PROTECTED] Powered by (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Hi, [snip patch] Does this patch make the libmap.conf hack unneeded? I frist thought so, but no, the more threads are running concurrently the slower libpthreads behaves, as it gets more lock contention. Until this is addressed somehow, use libthr.so -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
On Sat, 10 Mar 2007, Mike Jakubik wrote: Martin Blapp wrote: Clamd with libpthread.so is still broken. Please use libthr.so. I'm currently investigating why libpthreads.so has problems with clamd, and it looks to me like a library bug. This may be related to a problem i had with Mysql on a large server recently. Mysql threads would start eating a lot of CPU and staying around forever. I switched to libthr and the problem went away. Sorry, i don't have any more info than this, because it is a production server i cant mess around with it any more. I've seen the high-cpu stuff with ClamAV_0.90_3, even with libthr. Anyone got a fix? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Hi,
Don't use it, it's broken.
-trog
Nope, it looks like a race in cli_scanmail() which deadlocks somewhere
with libpthread.so. This workaround fixes the problem for me. I'm still
investigating where the real cause for this problem is.
--- libclamav/scanners.cTue Feb 13 02:06:28 2007
+++ libclamav/scanners.cSat Mar 10 12:00:16 2007
@@ -38,6 +38,9 @@
#include netinet/in.h
#endif
+# include pthread.h
+static pthread_mutex_t extractmail_mutex = PTHREAD_MUTEX_INITIALIZER;
+
#if HAVE_MMAP
#if HAVE_SYS_MMAN_H
#include sys/mman.h
@@ -1652,12 +1655,16 @@
/*
* Extract the attachments into the temporary directory
*/
+pthread_mutex_lock(extractmail_mutex);
if((ret = cli_mbox(dir, desc, ctx))) {
- if(!cli_leavetemps_flag)
+ if(!cli_leavetemps_flag) {
+ pthread_mutex_unlock(extractmail_mutex);
cli_rmdirs(dir);
+ }
free(dir);
return ret;
}
+pthread_mutex_unlock(extractmail_mutex);
ret = cli_scandir(dir, ctx);
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
And even more narrowed down ...
--- libclamav/mbox.c.orig Tue Feb 13 14:06:57 2007
+++ libclamav/mbox.cSat Mar 10 14:09:09 2007
@@ -413,6 +413,7 @@
#ifdef CL_THREAD_SAFE
static pthread_mutex_t tables_mutex = PTHREAD_MUTEX_INITIALIZER;
+static pthread_mutex_t body_mutex = PTHREAD_MUTEX_INITIALIZER;
#endif
#ifndefO_BINARY
@@ -1494,6 +1495,7 @@
/*
* Write out the last entry in the mailbox
*/
+ pthread_mutex_lock(body_mutex);
if((retcode == CL_SUCCESS) messageGetBody(body)) {
messageSetCTX(body, ctx);
switch(parseEmailBody(body, NULL, mctx, 0)) {
@@ -1505,6 +1507,7 @@
break;
}
}
+ pthread_mutex_unlock(body_mutex);
/*
* Tidy up and quit
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Martin Blapp wrote: Clamd with libpthread.so is still broken. Please use libthr.so. I'm currently investigating why libpthreads.so has problems with clamd, and it looks to me like a library bug. This may be related to a problem i had with Mysql on a large server recently. Mysql threads would start eating a lot of CPU and staying around forever. I switched to libthr and the problem went away. Sorry, i don't have any more info than this, because it is a production server i cant mess around with it any more. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Renato Botelho [EMAIL PROTECTED] writes: I found the problem, a bad REINPLACE_CMD was changing wrong var on configure scripts, don't respecting PTHREAD_LIBS. It's fixed now on 0.90_3. No, It's not. Today I added a new server with fresh clamav-0.90_3 package. Sockstat again started to jump to the sky. -- One cannot sell the earth upon which the people walk Tacunka Witco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
