RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5commit
Vinod, That patch worked. Received a clean buildkernel, installkernel and boot with the patch you supplied. Thanks, Kev -Original Message- From: Vinod Kashyap [mailto:[EMAIL PROTECTED] Sent: Friday, January 21, 2005 2:23 PM To: [EMAIL PROTECTED]; freebsd-stable@freebsd.org Subject: RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit Let me know if the attached patch works for you too. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, January 21, 2005 8:36 AM To: freebsd-stable@freebsd.org Subject: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49UTC RELENG_5 commit I also have the same problem with the new 3ware drivers 9.1.5.2 in -STABLE but I am using the i386 platform with a Xeon 3.0Ghz processor. I have one RAID-1 array and one RAID-5 array on the 9500s controller. /var and /usr/local on the RAID-5 Following the FreeBSD instructions to build -STABLE make -j8 buildworld make buildkernel KERNCONF=mykernelconf make installkernel KERNCONF=mykernelconf reboot And it worked. All was fine. Then mergemaster -p make installworld mergemaster reboot Then I could not get to the server via SSH. Found that the console had the exactly the same symptoms describe in the thread. I rebooted and at the Daemon Logo I did a boot kernel.old which worked with no problem. The dmesgs are below. First, 3Ware 9.1.5.2 driver kernel and the second is the kernel.old boot. --/etc/make.conf- # -- use.perl generated deltas -- # # Created: Thu Nov 25 08:12:18 2004 # Setting to use base perl from ports: PERL_VER=5.8.5 PERL_VERSION=5.8.5 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo CPUTYPE=p4 CFLAGS= -O2 -pipe -funroll-loops -ffast-math #CFLAGS= -pipe -funroll-loops -ffast-math COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math --Kernel With 3Ware 9.1.5.2 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Thu Jan 20 17:54:09 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BarsMail ACPI APIC Table: IntelR AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SE P,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,P BE Hyperthreading: 2 logical CPUs real memory = 1072562176 (1022 MB) avail memory = 1040035840 (991 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface 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 cpu1: 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 pcib1: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xa000-0xa01f mem 0xf100-0xf101,0xf102-0xf103 irq 18 at device 1.0 on pci1 em0: Ethernet address: 00:11:2f:5a:7e:df em0: Speed:N/A Duplex:N/A pcib2: ACPI PCI-PCI bridge at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: 3ware 9000 series Storage Controller port 0xb000-0xb0ff mem 0xf300-0xf37f,0xf380-0xf38000ff irq 27 at device 2.0 on pci2 twa0: 8 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: [GIANT-LOCKED] uhci0: UHCI (generic) USB controller port 0xd400-0xd41f irq 16 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 0xd000-0xd01f irq 19 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 pci0: base peripheral at device 29.4 (no driver attached) pci0: base peripheral, interrupt controller at device 29.5 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI
VMWare Workstation - burncd/DMA Mode
Hi, I'm having trouble burning CD's from FreeBSD 5.3 guest through WinXP host on VMWare Workstation 4.5.2 My VMWare workstation is complaining about DMA mode when I run: burncd -s 10 -f /dev/acd0 data test.iso fixate The error message from VMWare I get is: Your virtual machine has sent an ATAPI (CD-ROM) command that is only supported when programming the drive via DMA. You will need to configure your guest operating system to use DMA when communicating with DVD/CD-ROM devices. Note that some operating systems will report DMA is available without actually using it. In those cases, normal CD-ROM operations will still be available, but special features will only be available if you re-configure the virtual device as a SCSI device. FreeBSD gives the follwing: burncd: ioctl(CDRIOCINITTRACK): Input/output error I have the following lines in my loader.conf: hw.ata.atapi_dma=1 hw.ata.ata_dma=1 and have also tried configuring dma when system is up by running: atacontrol mode 1 udma4 udma4 Any Ideas? Many thanks in advance, Radster ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 stack overflow on a old cyrix p200+ 32MB RAM?
Hello to all, I'm trying to install 5.3 in a old pc (p200+ 32MB) but it stops booting from cd with a stack overflow. I have installed NetBSD 2.0 without problems just as a workaround. I've googled and I saw lot with people with the same problem with old pcs. I have not tryed 4.10 yet. Any opinions? Does FreeBSD no more old computers compatible? Yours, NUno Teixeira -- SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange ucom (uplcom) error
At Thu, 20 Jan 2005 14:18:30 +0100, Michal Mertl wrote: I wrote: Emanuel Strobl wrote: Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately also breakes the 2.02 version :( Perhaps there's a goog guy out there who can refurbish the uplcom driver with this information (akiyama?)? Thanks a lot, I've just recently been looking into this too. I used the mentioned patch and also linux driver source and have come with the attached patch. It contains one more change but I don't know if it's correct. It works for both chips on CURRENT for serial console. It detects if the chip is rev 3.00 and aplies the patch only for it. The author of the patch mentions it isn't binary safe - sometimes the chip stops working. I planned to test it with binary transfers (ppp) today, check if it's working and submit it (with some cleanup) for inclusion in FreeBSD. Michal Mertl I tested my patch for binary safety on CURRENT yesterday (dialed with ppp) and didn't notice any problem. I'm attaching my patch again because some recipients didn't probably receive it yesterday. Michal Good work! I've updated your patch. If attached patch works correctly with new revision chip, I'll commit this. Please test attached patch, and tell me the result. Regards, -- Shunsuke Akiyama [EMAIL PROTECTED] [EMAIL PROTECTED] uplcom.c-diff Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
correct value for LANG variable
I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. setenv LANG de_DE.ISO8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ÚWXYÝ] setenv LANG de_DE.ISO-8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF UVWXYZ perl perl: warning: Setting locale failed. [lot of indignation about locale settings] I am suspicious that de_DE.UTF-8 would work correct with most software. Is it the only solution to don't use localization currently at all or should it be my ambition to fix this? What should be the correct value? I would prefer the notation ISO-8859-1, but even the almighty perl does not. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct value for LANG variable
On Sat, Jan 22, 2005 at 04:52:45PM +0100, Bj?rn K?nig wrote: I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. setenv LANG de_DE.ISO8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ?WXY?] For better or worse, this is not the correct way to perform case conversion in non-ASCII locales on FreeBSD 5 and later. See the COMPATIBILITY section of the tr(1) manpage for more information. setenv LANG de_DE.ISO-8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF UVWXYZ perl perl: warning: Setting locale failed. [lot of indignation about locale settings] FreeBSD uses the name de_DE.ISO8859-1 instead of de_DE.ISO-8859-1. Most base system utilities don't complain if LANG or the related LC_* variables are invalid. I am suspicious that de_DE.UTF-8 would work correct with most software. Is it the only solution to don't use localization currently at all or should it be my ambition to fix this? What should be the correct value? I would prefer the notation ISO-8859-1, but even the almighty perl does not. Setting LANG to de_DE.ISO8859-1 should work. The alternative is UTF-8, which is understood by most text-processing utilities in the base system (ls, wc, grep, sed, ...). However, at this stage neither sh nor vi work correctly with UTF-8, so you would need to replace these with (for example) bash and vim. Tim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct value for LANG variable
On Saturday, 22. January 2005 16:52, Björn König wrote: I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. setenv LANG de_DE.ISO8859-1 echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ÚWXYÝ] This is the correct locale name, but don't use tr like that, you can't rely on that to work correctly with charsets which aren't symmetric in loweruppercase characters (it used to work at some point for the ISO8859-1 [5] locales but ceased after a POSIX related modification to tr). Use tr [:lower:] [:upper:] instead. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpILG8oAmJGV.pgp Description: PGP signature
Re: correct value for LANG variable
Tim Robbins wrote: For better or worse, this is not the correct way to perform case conversion in non-ASCII locales on FreeBSD 5 and later. See the COMPATIBILITY section of the tr(1) manpage for more information. Thanks a lot for this hint. I will pay more attention to this section. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct value for LANG variable
Michael Nottebrock schrieb: Use tr [:lower:] [:upper:] instead. I was wondering about a third-party script which always worked for years with Solaris. I just didn't realized that this issue concerns a difference between SysV and BSD. I tried to set another LANG string and it worked, but now I see that it will work this way with an arbitrary string, because it's invalid. ;-) Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
hang at fxp0 with RELENG_5
I upgraded a dual xeon from 5.3 to RELENG_5 a few days ago and the boot hangs after probing fxp0. Should I compile kernel debugger in and look for a stack trace or is there a known issue? This on intel 7505 board. Pete ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
LAN over Bluetooth failure with 5.3-STABLE
I'm trying to connect WinXP with 5.3-STABLE via Bluetooth using USB dongles. I followed Handbook, set up and started rc.bluetooth, hcsecd, sdpd and rfcomm_pppd. My dongle is recognized, pairing goes well. Connection from WinXP to FreeBSD can be always established but when I'm trying to send any data over this connection, it drops very soon with the following diagnostics: Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=124. Queue full Jan 22 21:34:49 elrond last message repeated 3 times Jan 22 21:34:49 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x4, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=124. Queue full Jan 22 21:47:37 elrond last message repeated 2 times Jan 22 21:47:37 elrond kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x6, len=13. Queue full Jan 22 21:47:46 elrond kernel: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 Jan 22 21:47:46 elrond kernel: ng_l2cap_l2ca_receive: ubt0l2cap - unexpected L2CAP data packet. Invalid channel state, cid=75, state=5 I tried to reduce MTU and MRU for ppp down to 512. It helped a bit - connection was alive a bit longer. Then again, connection dropped with the above diagnostics. Just have no idea where to dig further. Regards, Petr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AAAA queries (was: Realtek 8139 (rl) very poor performance)
Have you used dig(1) or other diagnostic tools to confirm that your DNS server is really not handling queries? This is really a a sign that the DNS server is seriously broken. has been a standard for years and any server that does not understand it is probably in very bad shape. Thanks for your answer. I followed your advice, and that are the facts: Using dig hostname @my-isp-dnsserver A seems to work pretty fine. However, if I type: dig hostname @my-isp-dnsserver sometimes miss (timeout) and, when it works, I get different results (no ip address, only pointer to an authoritative DNS server). I've also done some tests using lynx (ipv6) and links (only ipv4). When I use links, it always works: it performs and A query and gets a result back. Then, the HTTP conversation starts. However, using lynx, it performs first of all an query. When it works (not always do), I get a response but no IP address into that response. Then, sometimes it tries again with an A query, and then works. However, timeouts are killin' my patience :/ I've tested this issue with two different name servers. Could I confirm that is a DNS server's fault? Is my fault? Does exist any workaround about it? Thank you. -- Imobach González Sosa imobachgs en banot punto net osoh en jabber.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot build kernel with options WITNESS
I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys /kern/subr_witness.c /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/OMNI2. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. THE KERNEL CONFIG FILE : machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions #options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device em device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI-USB interface device ohci # OHCI PCI-USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # Human Interface Devices device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da # FireWire support device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=1 options IPFIREWALL_DEFAULT_TO_ACCEPT device snp
Re: Cannot build kernel with options WITNESS
look in /usr/src/UPDATING *** 20040710: A revamp of the debugging code in the kernel with some visible changes beyond just the debugging experience: o The DDB option is now specific to the DDB debugger backend and should not be used any more for conditional compilation of debugging code for when debugging is enabled. Use the KDB option for this. o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED respectively. This is in line with the first bullet. o The remote GDB support has been untangled from DDB and needs to be enabled separately now. Use the GDB option for this. o The GDB_REMOTE_CHAT option has been removed. Support for this homegrown feature is discontinued. The GDB remote protocol supports console output and it makes sense to use that. o The DDB_NOKLDSYM option has been removed. The DDB debugger now supports both direct symbol table lookups as well as KLD symbol lookups through the linker. *** Best Regards fofo I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys /kern/subr_witness.c /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/OMNI2. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. THE KERNEL CONFIG FILE : machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions #options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII
Re: Cannot build kernel with options WITNESS
On Sat, 22 Jan 2005, Artem Kuchin wrote: I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: This occurs when building WITNESS without DDB in the kernel, which was not a tested build case when I added show alllocks, and apparently is a relatively uncommon configuration as you're the first person to bump into it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't fix the problem for you. Thanks! Robert N M Watson cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys /kern/subr_witness.c /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/OMNI2. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. THE KERNEL CONFIG FILE : machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions #options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device em device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory disks #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device bpf
Re: Cannot build kernel with options WITNESS
On Sat, 22 Jan 2005, Artem Kuchin wrote: I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: This occurs when building WITNESS without DDB in the kernel, which was not a tested build case when I added show alllocks, and apparently is a relatively uncommon configuration as you're the first person to bump into it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't fix the problem for you. It fixed the problem. I am actually stuggling with unpredictable weird lock ups, when the host can be pinged but i cannot connect via ssh/telnet or httpd or anything else. It happens w/o any visible reason. I am running several jails with mysql and apache in each and canot make the whole system stable yet. Regards, Artem Kuchin IT Legion Ltd. Russia, Moscow www.itlegion.ru [EMAIL PROTECTED] +7 095 232-0338 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot build kernel with options WITNESS
On Sun, 23 Jan 2005, Artem Kuchin wrote: On Sat, 22 Jan 2005, Artem Kuchin wrote: I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: This occurs when building WITNESS without DDB in the kernel, which was not a tested build case when I added show alllocks, and apparently is a relatively uncommon configuration as you're the first person to bump into it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't fix the problem for you. It fixed the problem. I am actually stuggling with unpredictable weird lock ups, when the host can be pinged but i cannot connect via ssh/telnet or httpd or anything else. It happens w/o any visible reason. I am running several jails with mysql and apache in each and canot make the whole system stable yet. This is typically a sign of one of two problems: - The system is live locked due to very high load, so the ithread, netisrs, etc, in the kernel run fine, but user processes don't get a chance to run. - The system is dead locked due to user space processes getting wedged on common locks, but the kernel ithreads and netisrs can keep on responding. I generally assume that it's a deadlock as opposed to a live lock. I'd compile a kernel with DDB, KDB, WITNESS, and BREAK_TO_DEBUGGER. When the system appears to wedge, break into the debugger using a console or serial break (FYI: serial break is more reliable, and you get the benefit of being able to easily copy and paste debugging output using the serial console for DDB). Use show alllocks and show lockedvnods to examine most of the system's locking state. Changes are, either all the interesting processes are stacked up on VFS or VM locks, since those kinds of deadlocks produce the exact symptoms you describe: ping works fine because it only hits the netisr, but when you open TCP connections, the sshd (etc) block on VM or VFS locks attempting to fork new children or access a file in the file system name space. At first, the TCP connections will establish but there will be no application data; after a bit, they will not even return a SYN/ACK because the listen queue for the listen socket has filled. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PF rule statistics (hits) on individual rules....
I'm migrating one of my systems to PF from IPFW. In so doing and planning, I've reviewed the manpages and some online docs. I've become dependent upon ipfw -t to determine hits on various spam rules I've implemented - some of them large lists of /24's. I've not been able to determine that there is an equivalent in PF - though I imagine there must be some method to accomplish this. I'd appreciate if someone could help point in the right direction. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PF rule statistics (hits) on individual rules....
Forrest Aldrich wrote: I've not been able to determine that there is an equivalent in PF - though I imagine there must be some method to accomplish this. I'd appreciate if someone could help point in the right direction. You want to label rules; a 'pfctl -sl' will then get you information on each label. See Schwartz' article in Sys Admin magazine from March '04. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: correct value for LANG variable
On Sat, Jan 22, 2005 at 06:29:29PM +0100, Bj?rn K?nig wrote: Michael Nottebrock schrieb: Use tr [:lower:] [:upper:] instead. I was wondering about a third-party script which always worked for years with Solaris. I just didn't realized that this issue concerns a difference between SysV and BSD. The current behaviour of range expressions in tr was required by the Single Unix Specification Version 2 (SUSv2). Version 3 loosened this requirement by making these expressions unspecified in locales other than POSIX. This means you can't use tr with range expressions in any script intending to be portable without first setting LANG to POSIX. For reference, the systems I know of that sort range expressions according to the current locale are FreeBSD 5 (and later), AIX, and Tru64. The systems I know of that don't sort are FreeBSD 4 (and earlier), GNU (coreutils), and NetBSD. Tim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
