Re: VIMAGE: Freed UMA keg was not empty
Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net a écrit On Wed, 17 Nov 2010, Thierry Herbelot wrote: As promised, here are the full logs (in attachment) This is a serial console log showing the command loop that triggers the bug on a debug kernel and ensuing DDB session. the obvious problem line is : routetbl 2684 303890K 3469 (further tests showed an increase of the routetbl malloc zone by 4MBytes for each vnet jail creation/destruction cycle) Hmm, I had fixed that (somewhere). I'll see where the patch went. You are on 8.1-RELEASE or -STABLE? This will be for a -release, thus 8.1 for now, but we will switch to 8.2 ASAP Thanks TfH /bz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: VIMAGE: Freed UMA keg was not empty
Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net a écrit On Thu, 18 Nov 2010, Thierry Herbelot wrote: Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net a écrit On Wed, 17 Nov 2010, Thierry Herbelot wrote: As promised, here are the full logs (in attachment) This is a serial console log showing the command loop that triggers the bug on a debug kernel and ensuing DDB session. the obvious problem line is : routetbl 2684 303890K 3469 (further tests showed an increase of the routetbl malloc zone by 4MBytes for each vnet jail creation/destruction cycle) Hmm, I had fixed that (somewhere). I'll see where the patch went. You are on 8.1-RELEASE or -STABLE? This will be for a -release, thus 8.1 for now, but we will switch to 8.2 ASAP Well wait; I am not sure the changes are in SVN at all. I'll get back to you. OK for us : we are still in the process of deploying the solution, but still we will test any patch you can forward ;-) TfH /bz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: VIMAGE: Freed UMA keg was not empty
Thierry Herbelot thierry.herbe...@free.fr a écrit Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net a écrit On Wed, 17 Nov 2010, Thierry Herbelot wrote: Hi, first of all freebsd-virtualization@ is the better list for this; Cc:ed. (in fact, I did not know where else to send this message : -net, ... ? thanks for the CC) We are using FreeBSD + VIMAGE at work, and we have seen an annoying problem : there seems to be a memory leak in the kernel, which eventually causes a panic. (yes, we have seen the following message : WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.) Configuring a network interface in a jail with vnet enabled, then removing that jail causes these messages. In dmesg: [...] Freed UMA keg was not empty (203 items). Lost 1 pages of memory. Freed UMA keg was not empty (36 items). Lost 2 pages of memory. The issue happens in a GENERIC FreeBSD 8.1 kernel, with VIMAGE enabled (with attached VIMAGE kernel config file). The following commands reproduce the bug: jail -l -u root -c path=/ name=foo persist vnet jexec foo ifconfig lo0 127.0.0.1/8 jail -r foo Running it too many times exhausts kernel memory and crashes the machine. The probleme is seen on 8.1-release kernel, 8-stable from SVN and SVN -head. The problem has been present since day 1 and is still present up to HEAD. This is about type stability and teardown. So far we are no able to actually free TCP (and UDP in SVN) states as they might still be accesses after free. It's a general problem in the network stack and has been implemented as a measure to circumvent panics in those cases. I am not sure if that's actually what's biting you wrt to memory or if it's something else. Unfortunately boot logs and kernel configs don't help much; enable ddb and get show uma and show malloc reports after the crash (or watch vmstat -z and vmstat -m) after every 50 jail restarts. I might have some patches for a couple of things but cannot (yet) help with the additional (duplicate) UMA zones showing up at each iteration (for the -z case). The context for our problem is that VIMAGE jails are mant to be used in production for automated tests, thus are likely to be multiple on one physical host, and are likely to be started and stopped according to our needs. We have tried more classical virtualization solutions (qemu, kvm, ... , normal jails with individual FIBs, ...) but only FreeBSD with VIMAGE seems to be the correct answer. (for other reasons, an i386 version of the kernel must be used) The point of my original email was to simplify the configuration for a test setup : any machine with the attached configuration file and the above sequence of commands creating and deleting jails, running in a loop, will eventually panic. Anyway, I will follow up with the logs you mentioned. As promised, here are the full logs (in attachment) This is a serial console log showing the command loop that triggers the bug on a debug kernel and ensuing DDB session. the obvious problem line is : routetbl 2684 303890K 3469 (further tests showed an increase of the routetbl malloc zone by 4MBytes for each vnet jail creation/destruction cycle) Cheers Thierry Cheers (and thanks for the quick feedback) Thierry Herbelot /bz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org [r...@waldorf ~]# while jail -l -u root -c path=/ name=foo persist vnet jexe c foo ifconfig lo0 127.0.0.1/8 jail -r foo ; do continue ; done lock order reversal: 1st 0xc0bed490 allprison (allprison) @ kern/kern_jail.c:914 2nd 0xc0d5c56c vnet_sysinit_sxlock (vnet_sysinit_sxlock) @ net/vnet.c:618 KDB: stack backtrace: db_trace_self_wrapper(c0ab1220,e9867a08,c05fc285,c05ec9db,c0ab40dc,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c05ec9db,c0ab40dc,c6d2d138,c6d30c88,e9867a64,...) at kdb_backtrace+0x29 _witness_debugger(c0ab40dc,c0d5c56c,c0abf638,c6d30c88,c0abf794,...) at _witness_debugger+0x25 witness_checkorder(c0d5c56c,1,c0abf78b,26a,0,...) at witness_checkorder+0x839 _sx_slock(c0d5c56c,0,c0abf78b,26a,0,...) at _sx_slock+0x85 vnet_sysinit(c7acf000,c0bb5d00,6180,0,c0b80888,...) at vnet_sysinit+0x2b vnet_alloc(c6f73028,c0aa9de6,0,10,c0aa5dc0,...) at vnet_alloc+0x9e kern_jail_set(c77ed000,c767b380,1,c767b380,280930fc,...) at kern_jail_set+0x179a jail_set(c77ed000,e9867cf8,c0ae5dd0,c0ab4ea5,c77e87f8,...) at jail_set+0x50 syscall(e9867d38) at syscall+0x220 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (507, FreeBSD ELF32, jail_set), eip = 0x280eae1b, esp = 0xbf7feb7c, ebp = 0xbf7fec38 --- Freed UMA keg was not empty (203 items). Lost 1 pages of memory. Freed
VIMAGE: Freed UMA keg was not empty
Hello, We are using FreeBSD + VIMAGE at work, and we have seen an annoying problem : there seems to be a memory leak in the kernel, which eventually causes a panic. (yes, we have seen the following message : WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.) Configuring a network interface in a jail with vnet enabled, then removing that jail causes these messages. In dmesg: [...] Freed UMA keg was not empty (203 items). Lost 1 pages of memory. Freed UMA keg was not empty (36 items). Lost 2 pages of memory. The issue happens in a GENERIC FreeBSD 8.1 kernel, with VIMAGE enabled (with attached VIMAGE kernel config file). The following commands reproduce the bug: jail -l -u root -c path=/ name=foo persist vnet jexec foo ifconfig lo0 127.0.0.1/8 jail -r foo Running it too many times exhausts kernel memory and crashes the machine. The probleme is seen on 8.1-release kernel, 8-stable from SVN and SVN -head. Attachments: dmesg log and kernel config. cheers Thierry Herbelot # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.10.2.1 2010/06/14 02:09:06 kensmith Exp $ cpu I486_CPU cpu I586_CPU cpu I686_CPU ident VIMAGE options VIMAGE # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env GENERIC.env makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol 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 UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD# Network Lock Manager 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_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary
Re: VIMAGE: Freed UMA keg was not empty
Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net a écrit On Wed, 17 Nov 2010, Thierry Herbelot wrote: Hi, first of all freebsd-virtualization@ is the better list for this; Cc:ed. (in fact, I did not know where else to send this message : -net, ... ? thanks for the CC) We are using FreeBSD + VIMAGE at work, and we have seen an annoying problem : there seems to be a memory leak in the kernel, which eventually causes a panic. (yes, we have seen the following message : WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.) Configuring a network interface in a jail with vnet enabled, then removing that jail causes these messages. In dmesg: [...] Freed UMA keg was not empty (203 items). Lost 1 pages of memory. Freed UMA keg was not empty (36 items). Lost 2 pages of memory. The issue happens in a GENERIC FreeBSD 8.1 kernel, with VIMAGE enabled (with attached VIMAGE kernel config file). The following commands reproduce the bug: jail -l -u root -c path=/ name=foo persist vnet jexec foo ifconfig lo0 127.0.0.1/8 jail -r foo Running it too many times exhausts kernel memory and crashes the machine. The probleme is seen on 8.1-release kernel, 8-stable from SVN and SVN -head. The problem has been present since day 1 and is still present up to HEAD. This is about type stability and teardown. So far we are no able to actually free TCP (and UDP in SVN) states as they might still be accesses after free. It's a general problem in the network stack and has been implemented as a measure to circumvent panics in those cases. I am not sure if that's actually what's biting you wrt to memory or if it's something else. Unfortunately boot logs and kernel configs don't help much; enable ddb and get show uma and show malloc reports after the crash (or watch vmstat -z and vmstat -m) after every 50 jail restarts. I might have some patches for a couple of things but cannot (yet) help with the additional (duplicate) UMA zones showing up at each iteration (for the -z case). The context for our problem is that VIMAGE jails are mant to be used in production for automated tests, thus are likely to be multiple on one physical host, and are likely to be started and stopped according to our needs. We have tried more classical virtualization solutions (qemu, kvm, ... , normal jails with individual FIBs, ...) but only FreeBSD with VIMAGE seems to be the correct answer. (for other reasons, an i386 version of the kernel must be used) The point of my original email was to simplify the configuration for a test setup : any machine with the attached configuration file and the above sequence of commands creating and deleting jails, running in a loop, will eventually panic. Anyway, I will follow up with the logs you mentioned. Cheers (and thanks for the quick feedback) Thierry Herbelot /bz ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
SMP in GENERIC !
Hello, this is just to send a big bravo to all involved : a new GENERIC kernel is running my old BP6 as an SMP machine : multi% uname -a FreeBSD multi 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Nov 8 02:40:50 CET 2003 [EMAIL PROTECTED]:/files3/obj/files3/src/sys/GENERIC i386 multi% sysctl -a | grep cpu kern.threads.virtual_cpu: 2 kern.ccpu: 1948 kern.smp.cpus: 2 hw.ncpu: 2 machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 multi% (and ACPI is quite broken on this machine) and now, the same on the bi-Xeon machine at work ! TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR report
Hello, with a recent -Current, I see while mak'ing world : # lock order reversal 1st 0xc34969d4 vm object (vm object) @ /files3/src/sys/vm/swap_pager.c:1319 2nd 0xc0941900 swap_pager swhash (swap_pager swhash) @ /files3/src/sys/vm/ swap_pager.c:1832 3rd 0xc103565c vm object (vm object) @ /files3/src/sys/vm/uma_core.c:876 Stack backtrace: backtrace(c084cde1,c103565c,c0860340,c0860340,c0861206) at backtrace+0x17 witness_lock(c103565c,8,c0861206,36c,1) at witness_lock+0x672 _mtx_lock_flags(c103565c,0,c0861206,36c,1) at _mtx_lock_flags+0xba obj_alloc(c101f9a0,1000,cdd2e9f7,101,c090fe48) at obj_alloc+0x3f slab_zalloc(c101f9a0,1,c0861206,68c,c101f9b4) at slab_zalloc+0xb3 uma_zone_slab(c101f9a0,1,c0861206,68c,c101fa50) at uma_zone_slab+0xd6 uma_zalloc_internal(c101f9a0,0,1,5c1,728,c09111a8) at uma_zalloc_internal+0x3e uma_zalloc_arg(c101f9a0,0,1,728,2) at uma_zalloc_arg+0x3b9 swp_pager_meta_build(c34969d4,1,0,2,0) at swp_pager_meta_build+0x1b4 swap_pager_putpages(c34969d4,cdd2ebd0,1,0,cdd2eb40) at swap_pager_putpages +0x32d default_pager_putpages(c34969d4,cdd2ebd0,1,0,cdd2eb40) at default_pager_putpages+0x2e vm_pageout_flush(cdd2ebd0,1,0,eb,cdd2ebac) at vm_pageout_flush+0x17a vm_pageout_clean(c126a878,0,c0861018,32a,0) at vm_pageout_clean+0x305 vm_pageout_scan(0,0,c0861018,5a9,1388) at vm_pageout_scan+0x669 vm_pageout(0,cdd2ed48,c08476c8,314,4) at vm_pageout+0x31b fork_exit(c079d2b0,0,cdd2ed48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdd2ed7c, ebp = 0 --- with : # ident /files3/src/sys/vm/swap_pager.c /files3/src/sys/vm/swap_pager.c: $FreeBSD: src/sys/vm/swap_pager.c,v 1.235 2003/10/27 05:58:15 alc Exp $ # ident /files3/src/sys/vm/uma_core.c /files3/src/sys/vm/uma_core.c: $FreeBSD: src/sys/vm/uma_core.c,v 1.85 2003/09/21 07:39:16 jeff Exp $ # uname -a FreeBSD XXX 5.1-CURRENT FreeBSD 5.1-CURRENT #207: Mon Oct 27 13:51:31 CET 2003 [EMAIL PROTECTED]:/files3/obj/files3/src/sys/SMP i386 this is on a bi-celeron BP6 TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc related -current upgrade problems
Le Saturday 26 July 2003 00:46, John a écrit : . /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use poisoned malloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:63:25: attempt to use poisoned calloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:64:25: attempt to use poisoned realloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:65:25: attempt to use poisoned strdup mkdep: compile failed Hello, I've seen yesterday the exact same error : (maybe some bad wave coming to us from the outer space ?) one one machine (A). What was surprising in my case was that this error was systematic : I've tried three compilations in a succession to be sure it was not an error due to bad hardware. Then I've transferred the hard disk to another machine (B), and relaunched the make buildworld to check that the compiler and the sources on the disk were good (and indeed the make buildworld an make buildkernel succeeded on machine B) then I've re-transferred back the disk to the first machine, and I could then make buildworld - big surprise ? the first machine uses a Pentium-4 mobile (a real P-IV, not a Banias) and the second machine uses a Pentium-III TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing on IBM BladeCenter HS20 (usb keyboard)
Le Thursday 17 July 2003 09:56, Geoff Buckingham a écrit : Installing from floppy or PXE boot fails as syscons detects an at keyboard (probably to keep windows happy) and does not use the usb keyboard. Hello, you might want to try an automatic install with à la jumpstart, as described in http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html you will have to make some adaptations, as the man page is written for 4.x and not 5.x (there is at least an issue with the nfsclient.ko kernel driver). you can also keep the described procedure and at least install 4.8 (safer) TfH PS : do not forget to google a bit, as there are other interesting articles on the subject ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3D graphic cards
Le Saturday 28 June 2003 14:28, Julian St. a écrit : Hello, is there any list that provides information about what graphic cards on FreeBSD have supported 3D acceleration? (I need only X-Video support in particular, but it seems tied to 3D acceleration). Hello, you may want to have a look at NVidia boards - even the XFree Open Source has XVideo support (3D support only comes with the binary NVidia driver). TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
kld issue for NFS install of FreeBSD 5.1-Release
Hello, sysinstall seems to be broken when the install media is set to NFS : the nfsclient.ko kernel module is not loaded, and the mount_nfs server:/share /dist command fails. one workaround is to forcibly load the kernel module from the loader.rc file (I did it for a PXE/netboot install). TfH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Low swap kernel panic
Hello, while recompiling all of my ports (portupgrade -a -f), I've had my notebook panic with the following messages (see at the bottom). I have a limited amount of swap (paging out of a 64Meg file : swapfile=/usr/swap0 in /etc/rc.conf), and I was running KDE at the time : noticing a konqueror window had been closed, I have relaunched one konqueror, then boom ! there was also a lock order reversal with : $FreeBSD: src/sys/kern/kern_synch.c,v 1.211 2003/02/17 09:55:09 julian Exp $ $FreeBSD: src/sys/vm/vm_pageout.c,v 1.226 2003/02/09 20:40:36 alc Exp $ the kernel and userland are in sync and have been cvsuped and recomplied on the day before yesterday : FreeBSD XXX 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Mon Feb 24 23:11:57 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 the kernel config file is plain GENERIC. /var/log/messages extract : -- Feb 26 21:15:16 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:15:16 portable-cur last message repeated 109 times Feb 26 21:15:16 portable-cur kernel: pid 59119 (kdeinit), uid 1001, was killed: out of swap space Feb 26 21:20:14 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:20:18 portable-cur last message repeated 144 times Feb 26 21:20:18 portable-cur kernel: pid 63079 (kdesktop_lock), uid 1001, was killed: out of swap space Feb 26 21:26:04 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:26:08 portable-cur last message repeated 97 times Feb 26 21:26:09 portable-cur kernel: pid 67198 (kdesktop_lock), uid 1001, was killed: out of swap space Feb 26 21:31:57 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:33:19 portable-cur syslogd: kernel boot file is /boot/kernel/kernel Feb 26 21:33:20 portable-cur kernel: /usr/src/sys/kern/kern_synch.c:152: sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184 Feb 26 21:33:20 portable-cur kernel: /usr/src/sys/kern/kern_synch.c:152: sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184 Feb 26 21:33:20 portable-cur kernel: panic: sleeping thread owns a mutex Feb 26 21:33:20 portable-cur kernel: Feb 26 21:33:20 portable-cur kernel: syncing disks, buffers remaining... panic:bremfree: bp 0xc5b6dfe0 not locked Feb 26 21:33:20 portable-cur kernel: Uptime: 1d21h22m41s Feb 26 21:33:20 portable-cur kernel: Terminate ACPI Feb 26 21:33:20 portable-cur kernel: Automatic reboot in 15 seconds - press a key on the console to abort Feb 26 21:33:20 portable-cur kernel: Rebooting... /var/run/dmesg.boot : [741 swap_pager_getswapspace: failed lines deleted] swap_pager_getswapspace: failed swap_pager_getswapspace: failed swap_pager_getswapspace: failed pid 75533 (kdesktop_lock), uid 1001, was killed: out of swap space /usr/src/sys/kern/kern_synch.c:152: sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184 /usr/src/sys/kern/kern_synch.c:152: sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184 panic: sleeping thread owns a mutex syncing disks, buffers remaining... panic: bremfree: bp 0xc5b6dfe0 not locked Uptime: 1d21h22m41s Terminate ACPI Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #10: Mon Feb 24 23:11:57 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc070a000. Preloaded elf module /boot/kernel/snd_ds1.ko at 0xc070a0a8. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc070a154. Preloaded elf module /boot/kernel/firewire.ko at 0xc070a200. Preloaded elf module /boot/kernel/sbp.ko at 0xc070a2b0. Preloaded elf module /boot/kernel/acpi.ko at 0xc070a358. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 595574279 Hz CPU: Intel Pentium III (595.57-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 201261056 (191 MB) avail memory = 187871232 (179 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: SONY K1 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fdf40 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone 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 82443BX (440 BX) host to PCI bridge mem 0x4000-0x40ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.VID0 -
Re: How to create a device in current
Le Friday 07 February 2003 21:24, Kevin Oberman a écrit : I maintain a port for FreeBSD that I am trying to fix to run on V5. The port is the mWave modem software for some IBM laptop internal modems and it needs to create a /dev entry which I previously did with a simple mknod. This doesn't work under 5.0, so I am trying to figure out how to get the device node created in the rc script for the port. The command I used in V4 is mknod /dev/mwave c 96 0. Where so I read up on creating something like this with devfs? could this paper be relevant : http://www.usenix.org/publications/library/proceedings/bsdcon02/full_papers/kamp/kamp_html/index.html (it may require some rewriting of the device driver code) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 RC3 now available
Le Monday 13 January 2003 18:22, Andy Farkas a écrit : [SNIP] # pkg_add cvsup-without-gui-16.1f.tgz /usr/libexec/ld-elf.so.1: Shared object libssl.so.2 not found # Why does pkg_install now need libssl? indeed : (see http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/add/Makefile#rev1.15) machine# ldd /usr/sbin/pkg_add /usr/sbin/pkg_add: libfetch.so.3 = /usr/lib/libfetch.so.3 (0x28074000) libmd.so.2 = /usr/lib/libmd.so.2 (0x2808) libssl.so.2 = /usr/lib/libssl.so.2 (0x2808a000) libcrypto.so.2 = /usr/lib/libcrypto.so.2 (0x280b9000) libc.so.5 = /usr/lib/libc.so.5 (0x2817f000) machine# uname -a FreeBSD YYY 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Fri Jan 10 14:11:57 CET 2003 XXX@YYY:/files3/obj/usr/src/sys/SMP i386 machine# whereas : other_mach% ldd /usr/sbin/pkg_add /usr/sbin/pkg_add: libfetch.so.3 = /usr/lib/libfetch.so.3 (0x2806f000) libmd.so.2 = /usr/lib/libmd.so.2 (0x28079000) libc.so.4 = /usr/lib/libc.so.4 (0x28082000) other_mach% uname -a FreeBSD ZZZ 4.7-STABLE FreeBSD 4.7-STABLE #0: Sat Jan 4 12:51:32 CET 2003 XXX@ZZZ:/usr/obj/usr/src/sys/ZZZ i386 other_mach% TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
LOR report
Hello, with a recent -Current : % uname -a FreeBSD YYY 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Jan 1 15:18:16 CET 2003 XXX@YYY:/files3/obj/usr/src/sys/multi-cur i386 % upgrade done around 01/01 via : cd /usr cvs -r co -P src/ (cd src ; make buildworld make buildkernel KERNCONF=multi-cur) the kernel is just a stock GENERIC with SMP enabled. when rebooting after mergemaster : lock order reversal 1st 0xc4260950 process lock (process lock) @ /usr/src/sys/kern/vfs_mount.c:1143 2nd 0xc4cfc634 filedesc structure (filedesc structure) @ /usr/src/sys/kern/vfs_mount.c:1150 when rebooting : lock order reversal 1st 0xc421f5c0 process lock (process lock) @ /usr/src/sys/kern/kern_descrip.c:2101 2nd 0xc41b3e34 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern_descrip.c:2108 Happy new hacking year TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
lock order reversal report
Hello, while removing all local packages related to XFree86, I've had the following message : lock order reversal 1st 0xc49eaa68 vnode interlock (vnode interlock) @/files3/src/sys/nfsclient/nfs_vnops.c:2629 2nd 0xc05398a0 vm page queue mutex (vm page queue mutex) @ /files3/src/sys/vm/vm_kern.c:424 $FreeBSD: src/sys/nfsclient/nfs_vnops.c,v 1.189 2002/10/11 14:58:32 mike Exp $ $FreeBSD: src/sys/vm/vm_kern.c,v 1.87 2002/08/25 00:22:31 alc Exp $ this is on a recent world+kernel from FreeBSD 5.0-CURRENT #0: Sat Nov 23 13:55:22 CET 2002 TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X11, KDE, WM, Gnome and current
FWIW, I recently build KDE3 on a 5.0-DP2 notebook. I just copied the /etc/X11/XF86Config from the working 4.7-Stable partition, kld-loaded the pcm sound, and voilà, everything works fine. do you know if your XF86Config is correct ? have you loaded the sound driver ? Cheers, TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sysinstall + swap partition requirement
Hello, I semed to notice also a -minor- limitation in DP2's sysinstall : it did not reuse the swap partition from a co-existing -Stable slice (installation anew of -Current in ad0s3, and the swap partition was ad0s4b) I had to delete, then recreate, the swap partition in the disklabel menu of sysinstall in order to share the disk space. Cheers TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP stability ? [was Re: more info from panic from running
Le Wednesday 20 November 2002 11:25, Joel M. Baldwin a écrit : I haven't had any Hard Locks since I upgraded the BIOS on my BP6 from LP to RU and cvsup/buildworld/installworld again. I'll upgrade my BIOS ASAP At the moment I'm thinking that my system is stable again, but won't feel comfortable with that until I do some more stress testing. I've gotten a panic, but I think its unrelated. ( that's made this harder, multiple issues causing problems ) In the meantime, I'm also making some progresses : I've disabled ACPI from the loader (exec=unset ACPI_LOAD in /boot/loader.conf) and so far, the machine seems to be happy making the world (and this WE, building some ports) TfH [SNIP] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP stability ? [was Re: more info from panic from running
Le Tuesday 19 November 2002 22:35, Nate Lawson a écrit : I have a couple BP6's running -stable and was having hard lock problems under heavy IO until I dropped back to ATA33 on the drives (I moved them to the onboard Intel controller instead of the HPT366). sos@ informed me that the HPT366 has a buggy DMA controller and that ATA66 on them wouldn't work. After moving to ATA33 in early 2001, I haven't had any more hard locks. This was under -stable, but you might want to check your ATA drive setup before proceeding. Hello, I also had a lockup this morning, with both /usr/src and /usr/obj on the local dma33 IDE disk, hooked on the BX ata canal (instead of the HPT366). the BP6 is on a serial console, but I still have to look how to get back to DDB when it is frozen (I run a plain vanilla GENERIC+SMP, so I may have to add other specific options - later) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SMP stability ? [was Re: more info from panic from running dnet on SMP kernel]
Le Sunday 17 November 2002 10:50, Joel M. Baldwin a écrit : running dnet on a SMP kernel causes the kernel to panic. [Hijacking another thread ?] I haven't been able to complete a full buildworld with an SMP on a Abit BP6 (bi-celeron) board for two weeks (the kernel config is just a full GENERIC with SMP and APICIO options enabled). The same machine runs happily strings of make -j48 buildworld's when running with the straight GENERIC UP kernel, so I think the hardware seems to be working OK. Even make -j1 buildworld with the SMP kernel ends with a complete freeze of the machine (the kernel does not go to a panic where I could try a backtrace) The hardware config of the machine is pretty dull (see dmesg later). One point that could be better is that the sources are NFS mounted from a 4.7-Stable server, over an rl(4) board, which may be unstable (/usr/obj is local, on the Maxtor drive) TfH PS : the machine was re-installed anew from the 5.0-20021027-CURRENT snapshot, then upgraded via make buildworld/buildkernel and mergemaster PS2 : full dmesg (when running the stable, UP, GENERIC) Copyright (c) 1992-2002 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.0-CURRENT #17: Sat Nov 16 19:16:25 CET 2002 XXX@YYY:/usr/obj/files2/src-free/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0662000. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 334092192 Hz CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 536870912 (512 MB) avail memory = 514818048 (490 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface Using $PIR table, 8 entries at 0xc00fdef0 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd000-0xd01f irq 10 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) 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 pci0: bridge, PCI-unknown at device 7.3 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xd400-0xd4ff mem 0xe500-0xe5ff irq 10 at device 17.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:40:95:30:38:36 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: HighPoint HPT366 ATA66 controller port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 11 at device 19.0 on pci0 ata2: at 0xd800 on atapci1 atapci2: HighPoint HPT366 ATA66 controller port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 11 at device 19.1 on pci0 ata3: at 0xe400 on atapci2 orm0: Option ROMs at iomem 0xc6800-0xc7fff,0xc-0xc5fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0a03 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0400 can't assign resources (port) unknown: PNP0501 can't assign resources (port) Timecounters tick every 10.000 msec ad0: 6149MB Maxtor 86480D6 [13328/15/63] at ata0-master UDMA33 acd0: CDROM NEC CD-ROM DRIVE:28B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SMP stability ? [was Re: more info from panic from running dnet on SMP kernel]
Le Sunday 17 November 2002 20:46, Robert Watson a écrit : I've seen several reports that using a serial break to get into ddb is now quite a bit more reliable than a keyboard break. If you're not already using a serial console, you might want to give it a try (make sure to turn on BREAK_TO_DEBUGGER and/or ALT_BREAK_TO_DEBUGGER). OK, I'll do so TfH PS : I think one other BP6 user is Grog To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: About 5.0 and Nvidia drivers
Le Saturday 03 August 2002 22:09, Matthew N. Dodd a écrit : On Sat, 3 Aug 2002, Alp ATICI wrote: And what's the latest about the Nvidia drivers? It's mentioned that Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to know what's going on in that issue too. Any day now. wow ! what will this driver know to do ? (any URL to begin RTFMing ?) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Martin Blapp wrote: Hi, I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. is it enough to setenv GCC=/usr/local/bin/gcc31, then make install ? TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
compilation failure (in the kernel SCSI code)
Hello, the import of GCC3.1 seems to reveal old bugs : (while cross-compiling a new kernel atfer cross-compiling a new -Current world under a fresh -Stable) (the %b flag is not recognized in the printf()s of scsi_low.c) %- cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/files2/SrcCurrent/src/sys -I/files2/SrcCurrent/src/sys/dev -I/files2/SrcCurrent/src/sys/contrib/dev/acpica -I/files2/SrcCurrent/src/sys/contrib/ipfilter -I/files2/SrcCurrent/src/sys/../include -D_KERNEL -ffreestanding -include opt_global.h -fno-common -mpreferred-stack-boundary=2 -ffreestanding -Werror /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c cc1: warnings being treated as errors /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c: In function `scsi_low_calcf_show': /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4661: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4661: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c: In function `scsi_low_print': /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4896: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4896: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4916: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4916: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4929: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4929: warning: too many arguments for format *** Error code 1 Stop in /files2/obj/files2/SrcCurrent/src/sys/multi-Cur. *** Error code 1 Stop in /files2/SrcCurrent/src. *** Error code 1 Stop in /files2/SrcCurrent/src. portable# pwd %- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
slight patch to ata-all.c
Hello
[on a very recent -Current]
wtih the Werror compile flag, I can't compile src/sys/dev/ata/ata-all.c
on a PC with nothing more than a single IDE disk
TfH
patch enclosed
--- ata-all.c Sun Mar 10 21:32:21 2002
+++ ata-all.c.new Sun Mar 10 20:44:15 2002
-274,10 +274,12
ataioctl(dev_t dev, u_long cmd, caddr_t addr, int32_t flag, struct thread *td)
{
struct ata_cmd *iocmd = (struct ata_cmd *)addr;
+#if defined(DEV_ATAPICD) || defined(DEV_ATAPIFD) || defined(DEV_ATAPIST)
struct ata_device *atadev;
+caddr_t buf;
+#endif
struct ata_channel *ch;
device_t device = devclass_get_device(ata_devclass, iocmd-channel);
-caddr_t buf;
int error, s;
if (cmd != IOCATA)
error message
is the following message serious ? Mar 10 21:49:17 multi kernel: witness_get: witness exhausted is there anything special to do ? this is on a newly cvsuped, very lightly loaded, -Current (4 minutes after booting the machine) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-CURRENT makebuild world fails
Philip M. Gollucci wrote: For about the past 2 weeks or so, I've gotten the below error and I don't know what to do about it. This is on a FBSD4.5-RELEASE system w/ custom kernel. Hello, with must be a local error : I've built a -Current world+kernel last week, without any problem (but this was from a very recent 4.5-Stable world+kernel : that is update a -Stable machine up to the very latest sources, then upgrade to -Current) cc: Internal compiler error: program cc1 got fatal signal 11 a signal 11 is generally linked to bad memory chips TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Are there periodic GOOD tags in CVS for -CURRENT?
Hello, What I've done this WE was updating a very recent -Stable box to -Current (as described in UPDATING): this sems mostly not risky : as long as the make buildworld + make buildkernel does not succeed, you keep your valid -Stable machine. this is for the upgrade to a -Current. Afterwards, there is a paper by Matt Dillon (subject My Recommended Development/Testing environment for -current, on -current, which mwlucas could include in the official doc tree), which seems to give good guidelines to update a -Current machine from a -Stable one : this is what I intend to do, but with the same box, dual-booting between -Stable and -Current) As a thread on -current indicated, the state of -Current is surpisingly good : I'm now port-compiling Gnome (KDE couldn't compile, though) TfH PS : this is on an SMP box, of course ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: options HZ [MFC for pr=28143]
David Hill wrote: Hello - Could someone please document options HZ into LINT?. I found it while reading the dummynet(4) manpage. Thanks - David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message this was already submitted as a PR (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28143) maybe time to call for an MFC ? [CC added] -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VN bug or pilot error ?
Hello, I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. I've switched to Stable and I can mount the exact same image. TfH PS : it seems it's possible to vn-mount a file located on an NFS server, when the man page says it is not possible (which is right ?) -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
thanks a lot : that was it ! Peter Jeremy wrote: On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot [EMAIL PROTECTED] wrote: I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. Change "vn0c" to "vn0". I believe this is the result of PHK's change in mid-December which added cloning to vn. Peter -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
Poul-Henning Kamp wrote: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices If I may, two more questions : - the 4.2 man page for vn says the file must be stored locally (I have tried vn-mounting a NFS file and it worked : certainly the man page could be corrected - or I was lucky ?) - under 4.2-Release, I have trouble using a larger than 20 Megs MD partition (I have increased MDNsect to 8, but I still can't store more the 20 Megs : a "cp" with a 35 Megs file stays blocked, and always at the same place - I will give more details) TfH Poul-Henning In message [EMAIL PROTECTED], Thierry Herbelot writes: thanks a lot : that was it ! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rpc.lockd and true NFS locks?
Hello,
I've recently seen in the NetBSD 1.5 release Notes that *they* claim to
have a fully functional rpc.lockd manager : "Server part of NFS locking
(implemented by rpc.lockd(8)) now works."
could someone have a look at what our cousins have done and perhaps
import it in -current ?
TfH
--
Thierry Herbelot
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_xl module at startup
Hello, Well, this is exactly what I've conluded : don't use the loader for now (I've recompiled my kernel). I had a mail exchange with Mike Smith (on -Current) and I told him I would very much like to have a committer add a comment in /boot/loader.conf telling newbies about with little problem (don't know if I was heard) TfH Sheldon Hearn [EMAIL PROTECTED] on 23/02/2000 12:09:53 To: Thierry HERBELOT/FR/ALCATEL@ALCATEL cc: [EMAIL PROTECTED] Subject: Re: can't load if_xl module at startup On Mon, 21 Feb 2000 18:47:48 +0100, [EMAIL PROTECTED] wrote: When I load the if_xl module "by hand", all is well : the miibus is also loaded and everything's fine (xl0 appears in ifconfig -a ...) When I try to load the if_xl and miibus modules via the loader, the loader spins in : I'm answering because you don't seem to have gotten any other (public) answers, not because I'm sure of my facts. Quite a few people have reported problems loading modules from the loader (different modules, mind you). I'm pretty sure that I saw a clueful person suggest loading them out of /etc/rc.local for now. I can't check the archives to validate this, so you might want to think about it more than I have. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
Mike Smith wrote: I've yesterday sent a post on this list (from my work email) about the impossibility of loading the if_xl and miibus modules with the loader (it works well with kldload, afterwards) This is a known problem with modules that have dependancies; if you load the miibus module first it shouldn't happen (I haven't tested this). it does : I've tried loading miibus alone : works fine loading miibus, then if_xl : loops in loading miibus Ok. We know that hurts, don't do that. 8) fine, could there be a note in /boot/loader.conf, so that l^Husers don't get burn trying to load things which won't work (no code change : just a word of caution) TfH -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't load if_xl module at startup
Hello, I've just added a 3c900 NIC in my 4.0 machine. Not wanting to recompile my kernel, I've tried to kldload the if_xl module. When I load the if_xl module "by hand", all is well : the miibus is also loaded and everything's fine (xl0 appears in ifconfig -a ...) When I try to load the if_xl and miibus modules via the loader, the loader spins in : "/modules/miibus.ko text= data= syms=[] loading required module 'if_miibus' " at infinitum my loader.conf : # -- sysinstall generated deltas -- # userconfig_script_load="YES" miibus_load="YES" # miibus support, needed for some drivers if_xl_load="YES" My system version : pc-bsd103% uname -a FreeBSD pc-bsd103..telspace.alcatel.fr 4.0-2214-CURRENT FreeBSD 4.0-2 214-CURRENT #1: Mon Feb 21 18:36:37 CET 2000 [EMAIL PROTECTED] telspace.alcatel.fr:/usr/src/sys/compile/P5-ep i386 pc-bsd103% Net result : one more kernel recompile (this time, it works !) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
Hello, I've yesterday sent a post on this list (from my work email) about the impossibility of loading the if_xl and miibus modules with the loader (it works well with kldload, afterwards) This is with 4.0 - RC1. TfH (The loader loops trying to load the miibus module) Mike Smith wrote: Vladimir Kushnir wrote: Hello, I dont't know if this is some HW problem, but after the last update system became unbootable if I load modules by /boot/loader rather them kldload. That seems to be a bug -- I'd just load the modules via /etc/rc.conf for now. Other people have reported problems when loading modules via the boot loader. My advice would be to just load them via /etc/rc.conf This is entirely incorrect, and if you're having trouble loading modules with the loader there's something wrong that needs to be fixed. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.
Mike Smith wrote: Hello, I've yesterday sent a post on this list (from my work email) about the impossibility of loading the if_xl and miibus modules with the loader (it works well with kldload, afterwards) This is a known problem with modules that have dependancies; if you load the miibus module first it shouldn't happen (I haven't tested this). it does : I've tried loading miibus alone : works fine loading miibus, then if_xl : loops in loading miibus Strange ! TfH We tried to get some code to fix this into 4.x, but were thwarted by the freeze. Other modules should, however, work fine. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Quirk in the latest 4.0-RC install disk ?
Hello, I've just installed 4.0 from the latest Release Candidate (iso image gotten from the freebsd ftp and burned this morning) the install itself went smooth, but I can't start X11 : there seems to be a bug in the dynamic libraries : % ldd `which xinit` /usr/X11R6/bin/xinit: libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x28066000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x28078000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x280c) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x280c9000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x280de000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x280ea000) libxpg4.so.2 = /usr/lib/libxpg4.so.2 (0x28189000) libc.so.4 = /usr/lib/libc.so.4 (0x2818d000) libXThrStub.so.6 = not found (0x0) libXThrStub.so.6 = not found (0x0) % what's this libXThrStub.so.6 ? % uname -a FreeBSD XX.alcatel.fr 4.0-2208-CURRENT FreeBSD 4.0 % TfH dmesg : Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-2208-CURRENT #0: Thu Feb 10 16:08:11 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/P5-lnc Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 74539288 Hz CPU: Pentium/P54C (74.54-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping = 6 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 33554432 (32768K bytes) config q avail memory = 29990912 (29288K bytes) Preloaded elf kernel "kernel" at 0xc029d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc029d09c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 lnc0: PCNet/PCI Ethernet adapter port 0xfce0-0xfcff mem 0xfedffc00-0xfedffc1f irq 9 at device 8.0 on pci0 lnc0: PCnet-PCI II address 08:00:09:bb:26:57 lnc0: driver is using old-style compatability shims vga-pci0: S3 Trio graphics accelerator mem 0xfe00-0xfe7f at device 13. 0 on pci0 isab0: Intel 82371FB PCI to ISA bridge at device 15.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX ATA controller port 0xfcd0-0xfcdf at device 15.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 devclass_alloc_unit: lnc0 already exists, using next available unit number fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port plip0: PLIP network interface on ppbus0 lnc1: not probed (disabled) ep0: 3Com 3C509-Combo EtherLink III at port 0x280-0x28f irq 5 on isa0 ep0: Ethernet address 00:60:08:78:98:cb ad0: 814MB WDC AC2850F [1654/16/63] at ata0-master using PIO3 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata1
In order to have a prompt answer, you should at least send the relevant parts of 3.4 dmesg and 4.0 dmesg (to let know to the driver maintainer which board you use, for example) The problem report you have sent is useless without this info TfH Klaus Herrmann wrote: Hello! I just upgraded my 3.4-Stable system to a 4.0-current. It is running fine - with one exeption: the kernel seems to have problems with my 2nd ide/ata controller. when it is enabled, the system displays at boot time that it cannot find a driver vor the CDROM-Drive on ata1. On the 2nd ide channel are actually 2 devices: one noname-atapi-24x-cdrom and an atapi-cd-recorder. i don't really know whether the problem is the controller or the cd-drive. my kernel-config says: - device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices --- i also tried using device ata with isa options but no change. btw, this problem also appears when i boot fron the 2127-bootdisks. i think i do have MAKEDEVed all necessary devices - ad0-ad3 are all complete. some data on my pc: k6-2-300 cpu via-chipsatz, via-ide-controller thanks, Klaus -- Klaus Herrmann [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[LONG] Successful install report
Hello, I've installed a recent snapshot on an oldish P5-75 HP PC : here is the verbose dmesg (at the end, there seems to be some problems linked to ipsec) Jan 31 19:20:23 pc249 /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Jan 31 19:20:23 pc249 /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 31 19:20:23 pc249 /kernel: The Regents of the University of California. All rights reserved. Jan 31 19:20:23 pc249 /kernel: FreeBSD 4.0-2127-CURRENT #0: Wed Jan 31 19:11 :17 CET 1990 Jan 31 19:20:23 pc249 /kernel: [EMAIL PROTECTED]:/usr/s rc/sys/compile/P5-lnc Jan 31 19:20:23 pc249 /kernel: Calibrating clock(s) ... TSC clock: 75003346 Hz, i8254 clock: 1193236 Hz Jan 31 19:20:23 pc249 /kernel: CLK_USE_I8254_CALIBRATION not specified - using d efault frequency Jan 31 19:20:23 pc249 /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 31 19:20:23 pc249 /kernel: CLK_USE_TSC_CALIBRATION not specified - using old calibration method Jan 31 19:20:23 pc249 /kernel: Timecounter "TSC" frequency 75000774 Hz Jan 31 19:20:23 pc249 /kernel: CPU: Pentium/P54C (75.00-MHz 586-class CPU) Jan 31 19:20:23 pc249 /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Jan 31 19:20:23 pc249 /kernel: Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 Jan 31 19:20:23 pc249 /kernel: real memory = 25165824 (24576K bytes) Jan 31 19:20:23 pc249 /kernel: Physical memory chunk(s): Jan 31 19:20:23 pc249 /kernel: 0x1000 - 0x0009efff, 647168 bytes (158 pages) Jan 31 19:20:23 pc249 /kernel: 0x002bb000 - 0x017fdfff, 22294528 bytes (5443 pag es) Jan 31 19:20:23 pc249 /kernel: config q Jan 31 19:20:23 pc249 /kernel: avail memory = 21901312 (21388K bytes) Jan 31 19:20:23 pc249 /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd710 Jan 31 19:20:23 pc249 /kernel: bios32: Entry = 0xfd6e0 (c00fd6e0) Rev = 0 Len = 1 Jan 31 19:20:23 pc249 /kernel: pcibios: PCI BIOS entry at 0xd720 Jan 31 19:20:23 pc249 /kernel: pnpbios: Found PnP BIOS data at 0xc00f0c90 Jan 31 19:20:23 pc249 /kernel: pnpbios: Entry = f:b1d Rev = 1.0 Jan 31 19:20:23 pc249 /kernel: Other BIOS signatures found: Jan 31 19:20:23 pc249 /kernel: ACPI: Jan 31 19:20:23 pc249 /kernel: Preloaded elf kernel "kernel" at 0xc02a2000. Jan 31 19:20:23 pc249 /kernel: Preloaded userconfig_script "/boot/kernel.conf" a t 0xc02a209c. Jan 31 19:20:23 pc249 /kernel: Intel Pentium detected, installing workaround for F00F bug Jan 31 19:20:23 pc249 /kernel: md0: Malloc disk Jan 31 19:20:23 pc249 /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x8 068 Jan 31 19:20:23 pc249 /kernel: pci_open(1a):mode1res=0x8000 (0x8000) Jan 31 19:20:23 pc249 /kernel: pci_cfgcheck:device 0 [class=06] [hdr=00] is there (id=00071004) Jan 31 19:20:23 pc249 /kernel: npx0: math processor on motherboard Jan 31 19:20:23 pc249 /kernel: npx0: INT 16 interface Jan 31 19:20:24 pc249 /kernel: i586_bzero() bandwidth = 79032640 bytes/sec Jan 31 19:20:24 pc249 /kernel: bzero() bandwidth = 39791492 bytes/sec Jan 31 19:20:24 pc249 /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x0 000 Jan 31 19:20:24 pc249 /kernel: pci_open(1a):mode1res=0x8000 (0x8000) Jan 31 19:20:24 pc249 /kernel: pci_cfgcheck:device 0 [class=06] [hdr=00] is there (id=00071004) Jan 31 19:20:24 pc249 /kernel: pcib0: Host to PCI bridge on motherboard Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1004, dev=0x0007, revid=0x01 Jan 31 19:20:24 pc249 /kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1004, dev=0x0008, revid=0x01 Jan 31 19:20:24 pc249 /kernel: class=06-01-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1013, dev=0x00a8, revid=0xfc Jan 31 19:20:24 pc249 /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: map[10]: type 1, range 32, base fd00, size 24 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1022, dev=0x2000, revid=0x02 Jan 31 19:20:24 pc249 /kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: intpin=a, irq=10 Jan 31 19:20:24 pc249 /kernel: map[10]: type 1, range 32, base ffe0, size 5 Jan 31 19:20:24 pc249 /kernel: found- vendor=0x1095, dev=0x0640, revid=0x02 Jan 31 19:20:24 pc249 /kernel: class=01-01-00, hdrtype=0x00, mfdev=0 Jan 31 19:20:24 pc249 /kernel: subordinatebus=0 secondarybus=0 Jan 31 19:20:24 pc249 /kernel: intpin=a, irq=14 Jan 31 19:20:24 pc249 /kernel: pci0: PCI bus on pcib0 Jan 31 19:20:24 pc249 /kernel: isab0: PCI to ISA bridge (vendor=1004 device=000 8) at device 1.0 on pci0 Jan 31 19:20:24 pc249 /kernel: isa0: ISA bus on isab0 Jan 31 19:20:24 pc249 /kernel: vga-pci0: Cirrus Logic GD5434 SVGA controller m em
Re: SMP kernel panics after calling acquire_timer0
hello, You may want to upgrade to a more recent source tree : I've cvsupped from a 4.0-19991229-CURRENT snapshot to the sources around 01/05 21h00 GMT and SMP works fine on my machine (I have seen strange things with the snapshot : cvs did not want to check out the source tree ! not a pleasant discovery when wanting to update the sources) Is your machine specific in some ways ? (Compaq, for example) You may also post excerpts from your dmesg when booting as UP. TfH Mohit Aron wrote: Hi, I'm using FreeBSD-current (snapshot from Jan 3rd) which is configured with both SMP and APIC_IO support. This version panics upon calling acquire_timer0() (to modify the interrupt frequency of the 8254). On the other hand, if the kernel is not configured as an SMP, then it works fine. The panic reports some problem with some SMP lock - I can get more details if someone is interested in looking at the problem. - Mohit To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error messages while loading the kernel
"Robert C. Noland III" wrote:
I have seen that as well... It seems to be caused by svr4_enable="YES"
in rc.conf. or rather the specified module.
I'd say any module :
multi% kldstat
Id Refs AddressSize Name
12 0xc010 1c4b58 kernel
41 0xc1155000 2000 blank_saver.ko
multi%
I don't use the svr4 emulation
TfH
robert.
Thierry Herbelot writes:
I've just remade the world and a new kernel with sources supped around
21h00 GMT today, and I've got error messages in the kernel loading phase
(on an SMP machine : bi-celeron BP6)
link_elf: symbol zfree undefined
link_elf: symbol zfree undefined
full dmesg available upon request, if necessary
FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0:
Wed Jan 5 23:15:23 CET 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/multi i386
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Weird interaction between cvs and a recent kernel
Hello, I'm rebuilding my -Current box. it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT snapshot. I have on another box the full repository of FreeBSD (source, ports, docs, ...) on another box, running 3.3-Stable and exporting the repository via NFS. I've tried to remake the world to the latest sources I had (got on 12/31 around 4PM GMT). I can't get the "cvs co src" to finish properly : each time I launch "cvs co src", the kernel crashes with page fault while in supervisor mode : page not present (I don't have a serial console, so this is not the full message). The instruction address for the faulting instruction is always the same, in the "generic_bzero" (from a "nm" run on the kernel). The running process is always "cvs". I have been able to check the sources out (one subdirectory after another) and the machine has completed a full make world. I also run the corresponding kernel. with the new sources, there is the same problem with cvs : I have not been able to check out the ports tree in one step (same error, in the same routine). The machine works fine : I have just completed a X11 3.3.5 build. As I have got plenty of RAM, I'm not quite sure a full crash dump would be usable. Open to any suggestions TfH PS : dmesg for the box : Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 2 10:07:04 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/multiUP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8, APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 402653184 (393216K bytes) config q avail memory = 387637248 (378552K bytes) Preloaded elf kernel "kernel" at 0xc02be000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02be09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: NVidia model 002d graphics accelerator irq 5 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 12 chip1: Intel 82371AB Power management controller at device 7.3 on pci0 ed0: NE2000 PCI Ethernet (RealTek 8029) irq 10 at device 13.0 on pci0 ed0: address 00:4f:49:08:17:72, type NE2000 (16 bit) ata-pci1: HighPoint HPT366 ATA controller irq 11 at device 19.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0xd800 irq 11 on ata-pci1 ata-pci2: HighPoint HPT366 ATA controller irq 11 at device 19.1 on pci0 ata-pci2: Busmastering DMA supported devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 ed1: not probed (disabled) unknown: PNP can't assign resources unknown0: PNP0200 at port 0-0xf,0x81-0x83,0x87,0x89-0x8b, 0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown1: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown2: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown: PNP0800 can't assign resources unknown3: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown4: PNP0c01 at iomem 0-0x9,0xfffe-0x, 0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x17ff on isa0 unknown5: PNP0c02 at iomem 0xf-0xf3fff,0xf4000-0xf7fff, 0xf8000-0xf,0xd1800-0xd3fff on isa0 unknown6: PNP0a03 at port 0x294-0x297,0x4d0-0x4d1,0xcf8-0xcff, 0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0 unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources ad0: IBM-DTTA-351010/T56OA73A
False alarm ? (was Re: Weird interaction between cvs and a recent kernel)
Bonsoir, Well, I don't remember indulging (Lagavulin, Glen Deveron, what else ...), but I'm stumped : I can't reproduce what I've seen : a full "cvs co" of the ports and src has been running ok till its normal end. more after some make world's TfH Thierry Herbelot wrote: Hello, I'm rebuilding my -Current box. it's been reinstalled anew from the FreeBSD 4.0-19991229-CURRENT snapshot. I have on another box the full repository of FreeBSD (source, ports, docs, ...) on another box, running 3.3-Stable and exporting the repository via NFS. I've tried to remake the world to the latest sources I had (got on 12/31 around 4PM GMT). I can't get the "cvs co src" to finish properly : each time I launch "cvs co src", the kernel crashes with page fault while in supervisor mode : page not present (I don't have a serial console, so this is not the full message). The instruction address for the faulting instruction is always the same, in the "generic_bzero" (from a "nm" run on the kernel). The running process is always "cvs". I have been able to check the sources out (one subdirectory after another) and the machine has completed a full make world. I also run the corresponding kernel. with the new sources, there is the same problem with cvs : I have not been able to check out the ports tree in one step (same error, in the same routine). The machine works fine : I have just completed a X11 3.3.5 build. As I have got plenty of RAM, I'm not quite sure a full crash dump would be usable. Open to any suggestions TfH PS : dmesg for the box : [SNIP] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BP6 (Was Re: Success with ATA drivers and UDMA66)
"Dave J. Boers" wrote: On Tue, Dec 21, 1999 at 11:22:12PM +0100, Thierry Herbelot wrote: Let's start a thread on the BP6 ? (the release of the board was carefully synchronized with stable SMP releases of FreeBSD : kudos to the FreeBSD release engineering team ;-)) I second that! Running -current since October and never had a serious SMP problem. I was not really serious, but the nearly simultaneous release of a "stable" SMP FreeBSD and a very inexpensive Dual MoBo was a very pleasant surprise. [SNIP] I think the PS is pressed to its limits because if I add just one more drive (5400 RPM IDE disk) it's over the edge. Those Celeron's must be eating lot's of power (they are 400 Mhz ones running at 75 Mhz bus speed). Is it possible to directly boot from the HPT-366 controller ? (I know the BIOS is ok, but is there any problem with the new ata driver ?) I'm doing it currently. Very fine [SNIP] I would like to know how HOT other people's processors get. In the stationary situation I have a system core (= processor average) temperature of 46 and a case temperature of 50 degrees Celcius/Centigrade. What do you use for temp. watching ? (I fetched a little hack which is called wmtempmon). My temps are somewhat lower : around 35/36 °C, as I've installed "Alpha" coolers, bought from www.3dfx.com. One colleague at work uses the same sink/fan combo, but with peltier and a monstrous PSU to get to 572MHz. I've also loaded the latest BIOS from Abit. TfH Don't ask why case temperature is higher than core temperature! I don't get it either. The hard drives are not even above 30 degrees. Maybe it's the graphics board (viper 550 agp): it's doing 1600x1200@85Hz. I once clocked the system at 500 Mhz (83 Mhz bus), which runs fine but then things get way too hot. Regards, Dave Boers. -- God, root, what's the difference? [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP
Emre wrote: Hi people, I went to ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-19991218-CURRENT/README.TXT and read that document. Most hardware that I need to use is supported on that list, but I have a question: is SMP enabled in the GENERIC kernel in FreeBSD 4.0-current? we have a server that has dual 500Mhz P-III's and 2GB RAM...it's a waste to run Linux on it :\ You have to recompile the kernel to enable SMP : it's a matter of erasing four "#"s in the GENERIC config file. You may have to read a few pages of the handbook to see how to recompile your kernel (begin with http://www.freebsd.org/handbook/kernelconfig.html) TfH PS : could you break your lines at 72 chars ? Thanks! (PS: please reply in private as I am not subscribed to this list yet :) -- Emre Yildirim DH/DSS KeyID: 0xA007E75C | RSA KeyID: 0xFD5FD2C7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Success with ATA drivers and UDMA66
"Dave J. Boers" wrote: Hi all, I just wanted to let you know that I enabled UDMA66 (by plugging in an 80 conductor cable) on my WDC AC418000D today. The mainboard is an ABit BP6 with builtin Highpoint HPT366 ATA controller. The system works very nicely. I did some heavy testing in single user mode by moving several 300 Mb files around between the IDE disk and my other SCSI disk (which got me a sustained transfer rate of over 10 Mb/sec). Then I made world. Everything works great (softupdates enabled on all filesystems except "/"). If someone wants me to do some specific testing, let me know. Do you boot from the UDMA66 drive ? What is your BIOS revision ? How many SDARM DIMMs do you use ? What is the rating of your Power supply ? Do you use an AGP graphics board ? (I also have a BP6 and I'm mildly satisfied by its stability up to now, I'm looking for ways to upgrade it and hints to increase the reliability) TfH Regards, Dave Boers. -- God, root, what's the difference? [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stuck with ~year old current
"Daniel C. Sobral" wrote: Taavi Talvik wrote: Only alternative to get these from outside is to upgrade graduall.. but who knows which intermediate source repository dates are good for it? Mike once said (and, ergo, can be found on the mailing list archives): "We do not support upgrading to -current from anything else than the latest -stable." Does this still hold after the recent signal changes ? TfH (I assume Yes, if one first upgrade the kernel, then the world) There's your answer. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)
Soren Schmidt wrote: [SNIP] Have you tried putting disks on the UDMA66 channel ?? I think it should work in upto WDMA mode now with the ata driver... I have first to install 4.0 and from my wd2 (I've got a little help from RNordier, I should make do) Then, I'll get a UDMA-66 drive (any recommendation ?) TfH -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)
Soren Schmidt wrote: [SNIP] That can't be true, at least not for the IBM DeskStars I own, I've NEVER EVER seen them do that, one proof should be: same here wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): IBM-DTTA-351010, DMA, 32-bit, multi-block-16 wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): IBM-DTTA-351010, DMA, 32-bit, multi-block-16 wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S This is on my (very lightly loaded) home NFS server TfH (trying to upgrade one BP6 to 4.0) 11:22PM up 105 days, 4:18, 1 user, load averages: 1.06, 0.94, 0.91 dmesg snippet: wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S And none of the other machines I have with semilar or newer IBM's have ever done this, in fact I've yet to see one of them fail in any way.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
Hello, Let's remember a motto of J. Pournelle of the late Byte : one User, more than one CPU (let people hog their workstation as much as they want ...) And another good resolution : no shell accounts for normal users on sensitive servers (no lusers which could want to DoS the servers allowed) Every base covered ? Cheers TfH Matthew Dillon wrote: : :It should be possible to prevent a user from hogging a system if the system's :naive scheduler is improved. : : Amancio No, it isn't. For a very simple reason: The resources users need to do real work are very similar to the resources users need to hog the system. Saying that the system should somehow be able to magically make the distinction between the two is a pipedream. It takes a human to make the distinction. Short of restricting the resources you give to users to the point where they can't even start a mail or news client, there is just no way to prevent said users from loading down the machine if they choose to. -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: correction for find(1)'s man page
Jon Hamilton wrote: In message 199901180357.taa22...@vashon.polstra.com, John Polstra wrote: } In article 36a0fc11.8b22d...@cybercable.fr, } Thierry Herbelot herbe...@cybercable.fr wrote: } Hello } } I was reading the man page for find(1), looking for the precise option } to follow symbolic links. } } This option is -follow, of course, but it is not described in the man } page } } Huh? The correct options are the first three options described in } the man page: } -H The -H option causes the file information and file type (see }stat(2)) returned for each symbolic link specified on the command }line to be those of the file referenced by the link, not the link }itself. If the referenced file does not exist, the file informa- }tion and type will be for the link itself. File information of }all symbolic links not on the command line is that of the link }itself. What this doesn't explicitly say is that it causes find(1) to actually follow the symlink and recursively descend the target tree (if the link points to a directory); I assume that's the behavior the original poster wanted. Exactly, but this is not clear in he man page (furthermore, -follow is still a valid option and is not documented). TfH Near the bottom of the find(1) manpage (on my -stable system), is this: Historically, the -d, -h and -x options were implemented using the pri- maries ``-depth'', ``-follow'', and ``-xdev''. These primaries always ``-h'' there should read ``-H''; -h is an unknown option to find(1). -- Jon Hamilton hamil...@pobox.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
correction for find(1)'s man page
Hello I was reading the man page for find(1), looking for the precise option to follow symbolic links. This option is -follow, of course, but it is not described in the man page (I do not find in the cgi query : http://www.freebsd.org/cgi/man.cgi?query=findapropos=0sektion=0manpath=FreeBSD+3.0-currentformat=html ) What if someone reread the man page ? TfH To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
