FreeBSD 13.0 terrible performance in KVM
> I hope some other folks out there running FreeBSD on KVM as well. I set up a > base VM while doing so I noticed that the disk operations are very slow. Many > times I edit a file in vim or try to run a command there is a huge lag. I noticed this on Ramnode--my VPS--and tech support there has told me it is due to their container set up with Docker(?). They made some adjustments and then it worked fine. Rob ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13.0 terrible performance in KVM
> I hope some other folks out there running FreeBSD on KVM as well. I set up a base VM while doing so I noticed that the disk operations are very slow. Many times I edit a file in vim or try to run a command there is a huge lag. I noticed this on Ramnode--my VPS--and tech support there has told me it is due to their container set up with Docker(?). They made some adjustments and then it worked fine. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.0-RELEASE-p4 kernel panic on i386 boot
This morning, RELEASE-p5 came about. I did a freebsd-update without issue. However, as I said, I am running amd64 and not i386 on my server. So there must be something more involved here. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.0-RELEASE-p4 kernel panic on i386 boot
Possibly same issue on amd64 server in my VPS but my laptop updated just fine. vm_fault_hold: fault on nofault entry, addr: 0 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic (gpf) in early boot after upgrading FreeBSD 10.4 -> 11.2 on Ganeti
On Mon, 12 Nov 2018 01:58:12 -0500, Konstantin Belousov wrote: > On Sun, Nov 11, 2018 at 11:24:48PM -0500, Rob Austein wrote: > > > > panic: general protection fault > > cpuid = 0 > > KDB: stack backtrace: > > #0 0x80b3d587 at kdb_backtrace+0x67 > > #1 0x80af6b27 at vpanic+0x177 > > #2 0x80af69a3 at panic+0x43 > > #3 0x80f77fdf at trap_fatal+0x35f > > #4 0x80f7759e at trap+0x5e > > #5 0x80f57fbc at calltrap+0x8 > > #6 0x810ec5f3 at apic_setup_io+0x53 > > #7 0x80a92898 at mi_startup+0x118 > > #8 0x8031002c at btext+0x2c > > > Try to issue the following commands at the loader prompt: > set hw.x2apic_enable=0 > boot That worked. Added to loader.conf. Thank you! ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic (gpf) in early boot after upgrading FreeBSD 10.4 -> 11.2 on Ganeti
Belated upgrade (don't ask) of a pair of FreeBSD 10.4 VMs to 11.2. Each VM got as far as: freebsd-update -r 11.2-RELEASE update freebsd-update install reboot Each VM got an immediate kernel panic after the reboot (log below). The two VMs are basically identical at the system level, but run in separate Ganeti clusters on opposite coasts, so no hardware in common. A dozen or so other VMs run in each cluster without issues (including at least one other FreeBSD 11.2 VM), and the VMs I'm trying to upgrade have also been just fine until now, so the problem seems unlikely to be hardware per se. GENERIC, amd64, UFS2, no non-/boot/kernel modules, one CPU per VM. The only things even slightly unusual about these VMs are: * They're running in Ganeti clusters: * Ganeti version 2.15.2 * KVM hypervisor * They use virtio, so: * Disk is vtbd0 * Net is vtnet0 Log of attempted boot with new kernel: /boot/kernel/kernel text=0x1547d48 data=0x144138+0x4e9818 syms=[0x8+0x16aef8+0x8+0x183f99] Booting... Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-RELEASE-p4 #0: Thu Sep 27 08:16:24 UTC 2018 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(vga): text 80x25 CPU: QEMU Virtual CPU version 2.1.2 (2666.81-MHz K8-class CPU) Origin="GenuineIntel" Id=0x663 Family=0x6 Model=0x6 Stepping=3 Features=0x783fbfd Features2=0x80a02001 AMD Features=0x20100800 AMD Features2=0x1 Hypervisor: Origin = "KVMKVMKVM" real memory = 4294967296 (4096 MB) avail memory = 4088406016 (3899 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x810e9ae6 stack pointer = 0x28:0x82272c20 frame pointer = 0x28:0x82272c80 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process = 0 (swapper) trap number = 9 panic: general protection fault cpuid = 0 KDB: stack backtrace: #0 0x80b3d587 at kdb_backtrace+0x67 #1 0x80af6b27 at vpanic+0x177 #2 0x80af69a3 at panic+0x43 #3 0x80f77fdf at trap_fatal+0x35f #4 0x80f7759e at trap+0x5e #5 0x80f57fbc at calltrap+0x8 #6 0x810ec5f3 at apic_setup_io+0x53 #7 0x80a92898 at mi_startup+0x118 #8 0x8031002c at btext+0x2c Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. Goggling turned up a few theories about bad memory and incompatible changes to video drivers, none of which seem likely to apply here. Cluebat, please, somebody? Thanks for reading. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GENERIC make buildkernel error / fails - posix_fadvise
On Sat, 14 Jan 2012 23:37:50 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: On Sun, Jan 15, 2012 at 02:24:41AM -0500, Rob Clark wrote: On Thu, 12 Jan 2012 08:15:50 -0500 John Baldwin j...@freebsd.org wrote: On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote: System: Dell 600sc Currently running: 8.2-RELEASE In attempting to update this system to 8-STABLE I did what I usually do to update a system (see below). make buildworld completes successfully, but make buildkernel does not. I usually create a custom kernel, but for this system I went with GENERIC as is. The error message is: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 This sounds like you have an incomplete tree that only got part of a change (specifically, /usr/src/sys/sys/sysproto.h seems stale). Have you tried a different cvsup mirror? -- John Baldwin Sorry for the late follow-up, just got the system up and running yesterday. It appears that choosing a different mirror did the trick. Can you please disclose what cvsup mirror you were using? This kind of problem may be affecting other people, so you may want to report it to freebsd-h...@freebsd.org to make the maintainer of the mirror aware. Otherwise, corruption (for lack of better term) between what's in /var/db/sup and what's on your filesystem is something I've seen before, particularly when changing release tags in a supfile. | Jeremy Chadwick j...@parodius.com | Absolutely, the mirror initially used when I received the error (see above) during buildkernel was: cvsup17.FreeBSD.org Using cvsup11.FreeBSD.org I had no issues. Of course, I am not saying that cvsup17 was at fault here, just that buildkernel worked following a csup with cvsup11 (in my case anyway). -- Rob Clark rpcl...@tds.net cc: freebsd-h...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GENERIC make buildkernel error / fails - posix_fadvise
On Thu, 12 Jan 2012 08:15:50 -0500 John Baldwin j...@freebsd.org wrote: On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote: System: Dell 600sc Currently running: 8.2-RELEASE In attempting to update this system to 8-STABLE I did what I usually do to update a system (see below). make buildworld completes successfully, but make buildkernel does not. I usually create a custom kernel, but for this system I went with GENERIC as is. The error message is: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 This sounds like you have an incomplete tree that only got part of a change (specifically, /usr/src/sys/sys/sysproto.h seems stale). Have you tried a different cvsup mirror? -- John Baldwin Sorry for the late follow-up, just got the system up and running yesterday. It appears that choosing a different mirror did the trick. Thanks for all the positive insight from everyone who responded. I learned some valuable information, and new ways of doing things along the way. Have A Great Week! Rob -- Rob Clark rpcl...@tds.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GENERIC make buildkernel error / fails - posix_fadvise
On Wed, 11 Jan 2012 21:52:28 -0600 Andre Goree an...@drenet.info wrote: On Wed, Jan 11, 2012 at 3:11 PM, Rob Clark rpcl...@tds.net wrote: System: Dell 600sc Currently running: 8.2-RELEASE In attempting to update this system to 8-STABLE I did what I usually do to update a system (see below). make buildworld completes successfully, but make buildkernel does not. I usually create a custom kernel, but for this system I went with GENERIC as is. The error message is: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 I found this pertaining to posix_fadvise in /usr/src/UPDATING: 20120106: A new VOP_ADVISE() was added to support posix_fadvise(2). All filesystem modules must be recompiled. Not sure what 'filesystem modules' is or referring to here. Also, am I not already recompiling 'All filesystem modules' during make buildworld? What I did (and usually do): csup -L 2 /root/stable-supfile rm -rf /etc.old cp -Rp /etc /etc.old adjkerntz -i cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src /usr/bin/time -h make buildworld || exit build world finishes successfully. Then: cd /usr/src make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC This fails with error: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Following attempts: Attempt 2: I tried using 'make buildkernel' (without specifying KERNCONF) make buildkernel fails with same error. Attempt 3: Started from the beginning (same process as above) with new csup (sources) -- make buildkernel still failed with same error. Any help here would be greatly appreciated. In way over my head here. I have all logs from all attempts of the above if needed. Thanks, Rob Clark rpcl...@tds.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Perhaps two 'make cleandir' inside /usr/src will help. Run it just after removing everything within /usr/obj. FWIW, I usually run this simple bash script before building world on my machines: #!/bin/bash chflags -R noschg /usr/obj/usr rm -rf /usr/obj/usr cd /usr/src ; make cleandir ; make cleandir exit 0 Thanks Andre, I'll make note of that one. Rob -- Rob Clark rpcl...@tds.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GENERIC make buildkernel error / fails - posix_fadvise
On Thu, 12 Jan 2012 08:15:50 -0500 John Baldwin j...@freebsd.org wrote: On Wednesday, January 11, 2012 4:11:10 pm Rob Clark wrote: System: Dell 600sc Currently running: 8.2-RELEASE In attempting to update this system to 8-STABLE I did what I usually do to update a system (see below). make buildworld completes successfully, but make buildkernel does not. I usually create a custom kernel, but for this system I went with GENERIC as is. The error message is: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 This sounds like you have an incomplete tree that only got part of a change (specifically, /usr/src/sys/sys/sysproto.h seems stale). Have you tried a different cvsup mirror? -- John Baldwin Good point. Didn't try that, I'll give it a go. Rob -- Rob Clark rpcl...@tds.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
GENERIC make buildkernel error / fails - posix_fadvise
System: Dell 600sc Currently running: 8.2-RELEASE In attempting to update this system to 8-STABLE I did what I usually do to update a system (see below). make buildworld completes successfully, but make buildkernel does not. I usually create a custom kernel, but for this system I went with GENERIC as is. The error message is: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 I found this pertaining to posix_fadvise in /usr/src/UPDATING: 20120106: A new VOP_ADVISE() was added to support posix_fadvise(2). All filesystem modules must be recompiled. Not sure what 'filesystem modules' is or referring to here. Also, am I not already recompiling 'All filesystem modules' during make buildworld? What I did (and usually do): csup -L 2 /root/stable-supfile rm -rf /etc.old cp -Rp /etc /etc.old adjkerntz -i cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src /usr/bin/time -h make buildworld || exit build world finishes successfully. Then: cd /usr/src make buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC This fails with error: /usr/src/sys/kern/init_sysent.c:568: error: invalid application of 'sizeof' to incomplete type 'struct posix_fadvise_args' /usr/src/sys/kern/init_sysent.c:568: error: 'posix_fadvise' undeclared here (not in a function) *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Following attempts: Attempt 2: I tried using 'make buildkernel' (without specifying KERNCONF) make buildkernel fails with same error. Attempt 3: Started from the beginning (same process as above) with new csup (sources) -- make buildkernel still failed with same error. Any help here would be greatly appreciated. In way over my head here. I have all logs from all attempts of the above if needed. Thanks, Rob Clark rpcl...@tds.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [SOLVED] Re: labelling root file system (RELENG_8)
On Wed, Jun 8, 2011 at 10:05 AM, Jeremy Chadwick free...@jdc.parodius.com wrote: Interestingly enough, the long procedure I originally described is probably what was causing the problem. Not sure how to phrase it. I don't have a reference for this, but I'm pretty sure it was on one of the mailing lists at some point. The kernel reads the super-block into memory and uses that copy when the file system is mounted. If you have the it mounted rw, then at unmount it is written back out to the disk. If it's mounted ro, the in-memory copy is thrown out and the disk isn't changed. If you upgrade a file system from ro to rw, it does not re-read the on disk copy. tunefs directly modifies on the on-disk copy regardless of mount status, so when you unmount a rw file system, anything it has done is overwritten. The only way to modify / (without alternate boot media) is what you've described below: boot single user, leave it ro, tunefs, then reboot while still ro. Also, I've seen the sysctl kern.geom.debugflags=16 thing in zfs tutorials and such, but haven't seen where it's actually necessary. I think this is outdated and changed circa 8.0. -- Rob Farmer The exact procedure which worked was: - Start system - Boot into single-user - Hit enter at prompt (choose /bin/sh) - mount --- shows root filesystem mounted read-only (normal) - tunefs -t enable /dev/ada0s1a --- says it enabled TRIM support - tunefs -p /dev/ada0s1a --- shows TRIM support enabled - reboot - After system starts, as root: tunefs -p /dev/ada0s1a --- shows TRIM enabled So the extra rigmarole I was doing somehow caused the problem. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: installworld: check your date/time - Installworld NOT possible...
On Thu, Dec 30, 2010 at 16:06, Chris H chr...@1command.com wrote: Greetings, I've spent the morning grooming a fresh kernel on a freshly installed 8.1 amd64, from the DVD. I cvsup'd src ports last night. Build world kernel installkernel went as anticipated. HOWEVER, a reboot to single user, followed by a mergemaster -p, followed by cd /usr/src make installworld, returned: /usr/src/Makefile, line 177: check your date/time: current date and time here WTF? Should I simply comment lines 174-178? Why does make(1) refuse to installworld? My date and time are correct (in sync). Any insight into this error would be GREATLY appreciated. Did you run adjkerntz -i to set your timezone in single user? It starts up with the assumption that your hardware clock is UTC - depending on where you are (east/west of that), this can lead to files created in the future, which confuses make. -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel/World Upgrade causes Hang
On Mon, Dec 27, 2010 at 17:05, Troy t...@twisted.net wrote: # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability What is this? Do you actually need it? nforce 3 is pretty old - maybe it got broken somewhere along the way? It is, IMHO, the strangest thing in your kernel vs. GENERIC, which you said works. -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: /sbin/reboot
On Thu, Dec 9, 2010 at 21:35, Adam Vande More amvandem...@gmail.com wrote: On Thu, Dec 9, 2010 at 11:10 PM, Mark Andrews ma...@isc.org wrote: Why would you want it to be? One really shouldn't be running /sbin/reboot directly as part of normal operations. shutdown does a graceful reboot if and when operators need to perform reboot. AFAIK, the only functional difference between the two is shutdown(8) notifies other logged in users of the impending shutdown. I've used reboot(8) for a long time with no ill effects so I'd be interested to hear what you meant there. Since an operator can use shutdown(8) to initiate the same shutdown sequence reboot(8) uses, it wouldn't seems to be a security based decision. Shutdown runs rc.shutdown (stops all rc.d scripts). Also, halt/reboot have options like -n and -q which can disrupt things worse than an unintended clean reboot. -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: /sbin/reboot
On Thu, Dec 9, 2010 at 22:46, Adam Vande More amvandem...@gmail.com wrote: shutdown also give operator more possibilities than a clean shutdown some which could be very bad. I haven't thought about the situation in any detail, but nothing jumps out at me from the manpage. You could do a denial of service thing by kicking people off or endlessly rebooting the system, but intervention to stop that should be easy enough. With reboot, you could require fsck of the filesystem, plus any fallout from databases not stopping properly, etc. Of course, this is all (or should be) academic, since people in limited admin groups like operator should be presumed able to escalate to root. I think operator is allowed to run dump, among other things. A big Windows security flaw is adding people to Power Users, as if that stops anything beyond clumsy mistakes. -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: TTY task group scheduling
On Thu, Nov 18, 2010 at 10:39, Chuck Swiger cswi...@mac.com wrote: Frankly, I'm also turned off by the attempt to popup a full page ad in addition to the rest of the advertising content which surrounds what is nominally supposed to be the real content. That doesn't mean there is anything wrong with the patch or the notion of adjusting the scheduler, but I don't see any value added from these phoronix.com links. Most stuff on Phoronix is of dubious value, and they have outright lied about stuff in the past, in order to drum up advertising business (such as Steam on Linux, which Value has consistently said isn't happening). -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Cross-build failure on sparc64 for TARGET=amd64
On Fri, Oct 29, 2010 at 12:38, Nathaniel W Filardo n...@cs.jhu.edu wrote: Running sudo make TARGET_ARCH=amd64 TARGET=amd64 DESTDIR=/usr/x86_64 -j4 buildworld on FreeBSD sparcslave.priv.oc.ietfng.org 8.1-STABLE FreeBSD 8.1-STABLE #2 r214092=9050e7b-dirty: Thu Oct 21 01:25:54 UTC 2010 r...@t@sparcslave.priv.oc.ietfng.org:/usr/obj/usr/src/sys/SLAVKERN sparc64 I tried this about a year ago - it didn't work then and I suspect it never has. I'm not sure what the cause is. In any case, sparc's are almost always a lot slower than just building natively on amd64 hardware, so you probably aren't going to get people too excited about fixing it without tracking down the exact problem and/or sending a patch. -- Rob Farmer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
AMD64 Buildworld error in i386-elf
Source is current as at 0030 on 2nd Sept. and I'm seeing this buildworld error: === gnu/lib/csu (obj,depend,all,install) sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.o /usr/obj/usr/src/lib32/usr/lib32/crtbegin.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.o /usr/obj/usr/src/lib32/usr/lib32/crtend.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbeginT.o /usr/obj/usr/src/lib32/usr/lib32/crtbeginT.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.So /usr/obj/usr/src/lib32/usr/lib32/crtbeginS.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.So /usr/obj/usr/src/lib32/usr/lib32/crtendS.o === lib/csu/i386-elf (obj,depend,all,install) ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 -o gcrt1.o -r crt1_s.o gcrt1_c.o ld: Relocatable linking with relocations from format elf64-x86-64 (gcrt1_c.o) to format elf32-i386-freebsd (gcrt1.o) is not supported *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 /usr/src % uname -a FreeBSD aylee.number6 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Jul 27 08:48:05 EST 2010 r...@aylee.number6:/usr/obj/usr/src/sys/AYLEE amd64 thanks in advance rob ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.6 The Configuration File out of date?
Hi, I wonder if somebody add/remove the kernel options that came went with FreeBSD 8.0. For example: Those that seemed to have disappeared: machinei386 options GEOM_GPT options COMPAT_43 options ADAPTIVE_GIANT New ones that appeared in GENERIC (at least: they are not discussed in the Handbook, 8.6): optionsSCTP options UFS_GJOURNAL options GEOM_PART_GPT options GEOM_LABEL options COMPAT_43TTY options COMPAT_FREEBSD6 options COMPAT_FREEBSD7 options STACK options P1003_1B_SEMAPHORES options PRINTF_BUFR_SIZE=128 Regards, R. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.6 The Configuration File out of date?
Garrett Cooper wrote: machinei386 What architecture was this for -- amd64, i386, etc? But this line is not at all present in the GENERIC configuration of FreeBSD 8.0 release options COMPAT_43 Eh...? This still should be in there according to NOTES. It's not in the GENERIC kernel configuration... There is, however: options COMPAT_43TTY Is that a mistake then? R. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.6 The Configuration File out of date?
Freddie Cash wrote: No, it's been moved to DEFAULTS, along with a handful of other things that should always be present in an i386 kernel (isa, npx, mem, io, etc). Is the DEFAULTS configuration automagically included into a custom kernel configuration file, or does it then require an extra line: include DEFAULTS to have these defaults included? Is this documented somewhere? Thanks. R. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: today's build is causing errors for me
Hi Jeremy, I used Mergemaster. Thats what I mean't when I said that I carefully merged /usr/src/etc/ with /etc. But like I said, no files were replaced that contained my own configuration, e.g. group. I will say this- that I have always considered Mergemaster a confusing mess, despite the dogma on the lists. I have been running FreeBSD and installing it since 1998, so I have some experience- but this is new behavior beyond my previous experiences. Sincerely, Rob. On 5/15/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 04:44:57PM -0700, Rob Lytle wrote: First I am running 7.0-Stable and just cvsup'd today. Then I built the system, new kernel, and installed them. Second I am using the GENERIC KERNEL. Sysctl.conf is empty. I will put my /etc/rc.conf at the end. I tried to do a very careful job of merging /usr/src/etc with /etc. I didn't touch any files that I or the computer configured. But I am getting these errors upon bootup: 1. eval: /etc/rc.d/cleanvar: Permission Denied 2. syslogd: bind: Can't assign requested address. (repeated twice) 3. syslogd: child pid 134 exited with return code 1 4. /etc/rc: Warning: Dump device does not exist. Savecore will not run. (this always worked before) 5. /etc/rc.d/securelevel: /etc/rc.d/sysctl: Permission denied. 6. My computer says Amnesiac yet the host name is clearly in rc.conf 7. My WiFi no longer starts up by myself. I have to do it all manually using ifconfig and dhclient. You should have followed the instructions in /usr/src/Makefile. You don't merge things by hand. You can use mergemaster for that. Please use it, as I'm willing to bet there's a portion of your rc framework which is broken in some way. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: today's build is causing errors for me / Fixed for now
Hi Jeremy, I always back up /etc before I upgrade the system. The old /etc works just fine. I will eventually go back in and check out the new /etc to see what is wrong. Sincerely, Rob. On Thu, May 15, 2008 at 11:17 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 11:04:34PM -0700, Rob Lytle wrote: Hi Jeremy, I used Mergemaster. Thats what I mean't when I said that I carefully merged /usr/src/etc/ with /etc. But like I said, no files were replaced that contained my own configuration, e.g. group. I will say this- that I have always considered Mergemaster a confusing mess, despite the dogma on the lists. I have been running FreeBSD and installing it since 1998, so I have some experience- but this is new behavior beyond my previous experiences. Permission denied could imply that the rc scripts aren't set to executable. Possibly a umask problem? Additionally, mergemaster isn't a confusing mess. If anything, it's one of the most simple tools there is for managing /etc. The part you probably find confusing, which is the same part I did when I started using it, is the side-by-side interactive diff. It's very easy to use; r means use the text shown on the right, and l means use the text shown on the left. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: today's build is causing errors for me
Hi Jeremy, You were correct. Somehow some files in /etc/rc.d had permissions of 644. Setting the new permissions to that of the old fixed the problem. Thanks. Rob. On Thu, May 15, 2008 at 11:17 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 11:04:34PM -0700, Rob Lytle wrote: Hi Jeremy, I used Mergemaster. Thats what I mean't when I said that I carefully merged /usr/src/etc/ with /etc. But like I said, no files were replaced that contained my own configuration, e.g. group. I will say this- that I have always considered Mergemaster a confusing mess, despite the dogma on the lists. I have been running FreeBSD and installing it since 1998, so I have some experience- but this is new behavior beyond my previous experiences. Permission denied could imply that the rc scripts aren't set to executable. Possibly a umask problem? Additionally, mergemaster isn't a confusing mess. If anything, it's one of the most simple tools there is for managing /etc. The part you probably find confusing, which is the same part I did when I started using it, is the side-by-side interactive diff. It's very easy to use; r means use the text shown on the right, and l means use the text shown on the left. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
just one last question about /etc/rc.d file permissions
Hi Jeremy, I noticed that most all of the files in my old /etc/rc.d had 555 permissions. There were 4 or 5 that had 644 permissions in my old /etc/rc.d. What I am wondering is if all the files in rc.d should be 555? So far I am not experiencing any problems with anything with a very few 644 files. Thanks, Rob. On 5/16/08, Rob Lytle [EMAIL PROTECTED] wrote: Hi Jeremy, You were correct. Somehow some files in /etc/rc.d had permissions of 644. Setting the new permissions to that of the old fixed the problem. Thanks. Rob. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
today's build is causing errors for me
First I am running 7.0-Stable and just cvsup'd today. Then I built the system, new kernel, and installed them. Second I am using the GENERIC KERNEL. Sysctl.conf is empty. I will put my /etc/rc.conf at the end. I tried to do a very careful job of merging /usr/src/etc with /etc. I didn't touch any files that I or the computer configured. But I am getting these errors upon bootup: 1. eval: /etc/rc.d/cleanvar: Permission Denied 2. syslogd: bind: Can't assign requested address. (repeated twice) 3. syslogd: child pid 134 exited with return code 1 4. /etc/rc: Warning: Dump device does not exist. Savecore will not run. (this always worked before) 5. /etc/rc.d/securelevel: /etc/rc.d/sysctl: Permission denied. 6. My computer says Amnesiac yet the host name is clearly in rc.conf 7. My WiFi no longer starts up by myself. I have to do it all manually using ifconfig and dhclient. Any help would be appreciated. I'm kind of lost as some of it makes no sense to me, esp #6 and 7. Has the default rc.conf format changed??? Thanks, Sincerely, Rob -- My rc.conf file # -- sysinstall generated deltas -- # Sun Oct 28 11:36:26 2007 # Created: Sun Oct 28 11:36:26 2007 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=xenon # for DHCP linux_enable=YES #moused_enable=YES sshd_enable=YES usbd_enable=YES lpd_enable=YES kern_securelevel_enable=NO dumpdev=AUTO dumpdir=/var/crash cron_enable=YES performance_cx_lowest=LOW performance_cpu_freq=HIGH economy_cx_lowest=LOW economy_cpu_freq=LOW ipfilter_enable=YES ipfilter_rules=/etc/ipfw.rules ipmon_enable=YES ipmon_flags=-Ds watchdogd_enable=YES powerd_enable=YES mixer_enable=YES #ifconfig_ath0=WPA DHCP channel 3 #ifconfig_msk0=DHCP ifconfig_ath0=DHCP ssid leighmorlock channel 6 # added by mergebase.sh local_startup=/usr/local/etc/rc.d ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A little story of failed raid5 (3ware 8000 series)
Artem Kuchin unleashed the infinite monkeys on 20/08/2007 23:38 producing: ---SNIP--- But i don't understand how and why it happened. ONly 6 hours ago (a night before) all those files were backed up fine w/o any read error. And now, right after replacing the driver and starting rebuild it said that there are bad sectors all over those file. I've had that happen on a RAID1 setup before. Because all the bad sectors were in different positions the array worked fine until one of the disks failed. As I'm fond of saying at work, RAID is no substitute for regular, tested, backups. Regarding your problem - you can download the (very detailed) manuals for the 3Ware cards and their software from the 3Ware website. A quick scan suggests you need the mediascan command (P48). Newer controllers (9000 series) support scheduling of their equivalent. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Rob Crommentuijn/Adimec is out of the office.
I will be out of the office starting 16-07-2007 and will not return until 06-08-2007. I will respond to your message when I return. In the mean time contact [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Mike Tancsa unleashed the infinite monkeys on 15/03/2007 19:58 producing: At 01:52 PM 3/15/2007, Kevin Way wrote: FWIW, we have several machines running with the libmap.conf hack. clamav no longer locks up, but has instead taken to occasionally dying altogether. Hi, I think there are other bugs in the current clamd, the main one that we run into is when it tries to reload the database, and it somehow confuses itself and exits. http://lurker.clamav.net/message/20070314.170629.9118e704.en.html At least on FreeBSD 5.4 I think I've tracked the problem down to -lthr: http://www.freebsd.org/cgi/query-pr.cgi?pr=110352 Using either -lpthread or simply not using -lthr clamd (for me) doesn't crash (well, not yet :). Only happens to me with 0.90.1 in daemon mode. With 0.90_x or 0.90.1 in foreground mode it stays running afer the selfcheck. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Diskless PXEboot crashes at kernel loading.
Hi, I already described in detail what I've been doing with the FreeBSD server and the Compaq HP client PC here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/142116.html The Bootp exchange seems to be fine and the client gets the kernel from the server. However, during the kernel loading, the client PC implodes and starts from BIOS boot up again. The boot messages are given below. The crash messages scroll too fast over the screen to see the details with the bare eye. I recorded it with a digital camera and a snapshot of it is here: http://www.lahaye.dds.nl/pxeboot/crash.jpg The whole boot process in plain text goes as follows: -- Attempting Boot From Intel(R) Boot Agent Version 3.0.05 (PnP Device) Initializing Intel(R) Boot Agent Version 3.0.05 PXE 2.0 Build 078 (WfM 2.0), RPL V2.73 Intel(R) Boot Agent Version 3.0.05 Copyright (C) 1997-2000, Intel Corporation CLIENT MAC ADDR: 00 02 A5 93 F7 44 GUID: 67862AE2-117C-D511-BFE9-F3C48B4FB125 DHCP./ BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point 09db8:8186 BIOS a573kB/268896kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 pxe_open: server addr: 192.168.123.1 pxe_open: server path: / pxe_open: gateway ip: 192.168.123.254 Welcome to FreeBSD! [ Boot option menu 1 to 7 ] FreeBSD-ascii-cartoon /boot/kernel/kernel text=0x4d568c / int=.. err= ef11= eip= -- And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Thanks, Rob. Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEboot fails at kernel (text) loading
Hi, I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT When all this is in place, and I reboot the client PC, the PXE works fine and I get the Welcome to FreeBSD! window, that allows me to choose from a list of options: 1. Boot FreeBSD [default] 2. Boot FreeBSD with ACPI enabled 3. Boot FreeBSD in Safe Mode 4. Boot FreeBSD in single user mode 5. Boot FreeBSD with verbose logging 6. Escape to loader prompt 7. Reboot Now whatever option (1 to 5) I choose here, I always get: /boot/kernel/kernel text=0x4d568c / and the last slash is rotating for a very tiny while after which the system kind of implodes, blanks the screen and reboots from BIOS. Apparently something goes very, very wrong when loading the text part of the kernel. On the server, I've checked the /var/log/xferlog, which has entries like this: read request for //pxeboot: success read request for /boot/loader.rc: success read request for /boot/loader.4th: success read request for /boot/support.4th: success read request for /boot/beastie.4th: success read request for /boot/screen.4th: success read request for /boot/frames.4th: success read request for /boot/kernel/kernel: success read request for /boot/kernel/kernel: success Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Thanks, Rob. We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: php apache2 config
Try commenting out the line for 'doc_root' in your php.ini Matthew Herzog wrote: When I load a file named php4.info I can see all my php build information. If I change that same file's name to phpinfo.php, I get a premature end of script headers error. The file contains this text only: ?php phpinfo(); ? and is owned by apache. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] cheers, -- Rob Dosogne Systems Administrator http://www.truthsolo.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
/usr/local/etc/rc.d scripts not starting after update to -stable, also /etc/rc.d syntax error
Hi, Yesterday I updated to -stable. I think that I did a decent job merging the /etc files and configuring rc.conf but I am getting some errors. First, the scripts in /usr/local/etc/rc.d are not starting. I do have the following line in rc.conf: local_startup=/usr/local/etc/rc.d The syntax error reported on bootup is: /etc/rc.d/Makefile: 44: Syntax error: ( unexpected. Perhaps that error is what is causing the local startup scripts not to execute. Thanks for any help you can give me. Rob Lytle -- --- http://www.roblytle.org Rob Lytle Home Page ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
installworld: Error 'audit group' missing ; UPDATING is incomplete!
Hi, I have uploaded today 6-Stable. The 'make installworld' fails with an error message on a missing 'audit group' and refers to /usr/src/UPDATING. However, there's no information in UPDATING about this issue! Please add. Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-prerelease: boot loader pause timer hangs
Rob wrote: Hi, I am keeping in sync with 6-Stable every now and then. At present I have a problem with the pause timer of the boot loader. In /boot/loader.conf I have: autoboot_delay=3 and as soon as the pause timer is supposed to count down, it kind of hangs; actually, the cursor seems to jump as if the number 3 is continuously printed instead of a countdown. This 'hang' continues until I hit the return key, after which the boot process continues as usual. When I remove the delay line in loader.conf, then the loader displays a pause timer of 10, but actually *immediately* continues as if the pause timer is zero (so no delay at all). I believe there's something wrong with the boot loader in 6.1-Prerelease. Or has my PC become buggy? Any idea what's the problem? Anybody else sees this? Just for the record: I have found the problem and reply my own solution to the problem here: I had changed my /boot.config from -P to -D and I checked the boot-up on the video console (not serial). Meanwhile the serial port was connected to a data acquisition equipement, which obviously confused the boot-up communication. This, however, I did not realize while watching the peculiar boot-up on the console. My conclusion: do not use -D in /boot.config, unless the serial port is either not connected, or connected to a remote terminal. Using -P here is safer. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 5.4-STABLE hangs every few days
When we last met our heroes on 04 March 2006 23:15, Brad Waite was heard to say: How do I determine if it's a hardware issue, namely RAM or CPU? Can breaking into the debugger tell me that, or do I have to start swapping pieces out? memtest86 can help diagnose RAM problems. I'm not aware of any free programs for testing the CPU etc though (I've only used PC-Check before - it's good, but it isn't cheap). Worth trying to see if there's anything that the freezes have in common - busy system, particular program, time of day, etc. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-prerelease: boot loader pause timer hangs
Hi, I am keeping in sync with 6-Stable every now and then. At present I have a problem with the pause timer of the boot loader. In /boot/loader.conf I have: autoboot_delay=3 and as soon as the pause timer is supposed to count down, it kind of hangs; actually, the cursor seems to jump as if the number 3 is continuously printed instead of a countdown. This 'hang' continues until I hit the return key, after which the boot process continues as usual. When I remove the delay line in loader.conf, then the loader displays a pause timer of 10, but actually *immediately* continues as if the pause timer is zero (so no delay at all). I believe there's something wrong with the boot loader in 6.1-Prerelease. Or has my PC become buggy? Any idea what's the problem? Anybody else sees this? Regards, Rob. - /boot/loader.conf has following lines: autoboot_delay=3 # 3 seconds pause timer if_rl_load=YES # PCI Ethernet random_load=YES # Pseudo device for SSH sio_load=YES # Serial (COM) ports - /boot.config has this: -D kernel config file has following: machine i386 cpu I686_CPU ident MYKERNEL options SCHED_4BSD options INET options INET6 options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options COMPAT_43 options COMPAT_FREEBSD4 options COMPAT_FREEBSD5 options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV device pci device ata device atadisk options ATA_STATIC_ID device scbus device da device pass device atkbdc device atkbd device psm device vga device splash device sc device pmtimer device loop device ether device pty device md device bpf options SC_DISABLE_REBOOT options TCP_DROP_SYNFIN options DEVICE_POLLING options HZ=1000 --- __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with mounting USB stick as user
At 12:27 AM 9/02/2006, Oliver Fromme wrote: To enable user mounts, there are three conditions: 1. sysctl vfs.usermount=1 2. The user must have read+write permission on the device which is to be mounted. This is usually accomplished by creating a special group for this device. 3. The user must _own_ the mountpoint (r/w permission is not sufficient). That fixed it ... thanks. Rob ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with mounting USB stick as user
Hi all, Got a small problem thats just driving me nuts. I have an MP3 player that appears as a memory stick - from dmesg: umass0: iRiver Limited. iRiver Internet Audio Player IFP-700, rev 2.00/0.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: iriver MassStorage Disc Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 500MB (1024001 512 byte sectors: 64H 32S/T 500C) (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 The mount-point is owned by root:operator, and my user is a member of the operator group. I have vfs.usermount=1 in sysctl.conf. I have a devfs.rules file: [riff_usb=10] # Make USB drives readable to those in the operator group add path 'da*' mode 0660 group operator and it is referenced in rc.conf. But .. [EMAIL PROTECTED] ~ % mount /flash mount_msdosfs: /dev/da0: Operation not permitted [EMAIL PROTECTED] ~ % ls -la /dev/da0 crw-rw 1 root operator0, 122 Feb 8 22:24 /dev/da0 Can anyone shed some light on what is happening here? Cheers, rob ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient in 6.0
At 07:02 PM 6/02/2006, Matt Dawson wrote: On Sunday 05 February 2006 06:04, you wrote: The problem is that the integration of the modern wlan (802.11) code has never been done in the if_wi code and it does not report state back to wlan adequately to make the OpenBSD client function correctly. Here's something odd ... this works (mostly) fine for me. I did have to resort to the (ugly) /etc/start_if.wi0 script rather than keeping everything in /etc/rc.conf, but hey Actually, even the simple dhclient.conf files have forced me to look at other ways of doing things. Some of them, such as DDNS from the DHCP server, have turned out to be more elegant and secure than manually configuring dhclient.conf on every machine. Certainly, having the dhclient process for a particular card commit suicide when someone pops out the NIC rather than sitting there sulking is a bonus, too. The thing I found with DDNS was getting the darn client to return the correct hostname. For some reason, without setting it in dhclient.conf, the DNS would not update, even if I have configured the DHCP server to do the updates. Cheers, Rob ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sendmail_enable=NO
On Saturday, December 31, 2005 10:38 PM when we last met our heroes, [EMAIL PROTECTED] was heard to say: Isn't this supposed to tell FreeBSD not to start up the sendmail daemon processes? You want NONE. This isn't documented in the defaults file, but is apparent when you look at the startup script. I've a feeling it's documented somewhere else, but can't remember right now. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ports security branch
On Tuesday, December 20, 2005 6:26 AM when we last met our heroes, [EMAIL PROTECTED] was heard to say: Sorry if this is a bit OT. I've already asked this on freebsd-questions@ but they told me there's no such thing at all. And they were correct. The overhead of managing such a thing correctly would be significant, probably more than the overhead of managing the base port itself. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Release schedule for 2006
Gary Kline wrote: On Fri, Dec 16, 2005 at 12:04:05AM -0700, Scott Long wrote: All, The following is the approximate schedule for FreeBSD releases in 2006: Jan 30: Freeze RELENG_5 and RELENG_6 Mar 20: Release FreeBSD 6.1 Apr 3: Release FreeBSD 5.5 Jun 12: Freeze RELENG_6 Jul 31: Release FreeBSD 6.2 Oct 23: Freeze RELENG_6 Dec 11: Release FreeBSD 6.3 A 'freeze' means that the tree will be closed to changes except with specific approval, and the focus will be on producing, testing, and fixing release candidates. The release dates are targets that we hope to make, but we will continue with the policy of only releasing once all of the showstoppers are cleared, i.e. we will release when it is ready. FreeBSD 5 5.5 will be the final release from the RELENG_5 tree. We are doing it to provide support for users who have committed to FreeBSD 5 and who need more time to transition to FreeBSD 6. However, in order to keep forward progress with FreeBSD 6, we will produce this in parallel with the 6.1 release, and thus it will not be our main focus. Users who are using FreeBSD 5 are strongly encouraged to evaluate FreeBSD 6. After this final release, the security team will provide security update support through 2007. Sounds like an ambitious schedule... All my FBSD servers are at least up to 5.3; my laptop is happy at 5.4. I have what I believe to be a rationalquestion. Why should I go beyond v5.5? More to the point, why can't minor security tweaks be maintained indefinitely for 5.5? What will releases -6 and -7 offer that can;t reasonably be dropped into -5? A me too here for 5-Stable. I have a test PC, that was running 5-Stable using an additional swapfile to extend swap space. Never any problems at all with 5. After upgrading to 6-stable, I got regular hang-ups of the system (endless loop?) when swapspace is used extensively. Never happened with 5. I wild guess of mine is that there's problem with the 'enhanced filesystem access' in 6. I've reported this issue, and also provided backtraces of kernel dumps, although I'm not an expert in kernel debugging. However, no reponse so far. For me 6, as of now, is not yet as stable as 5 used to be. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HP zd8000 laptop reboots on its own with FreeBSD 6.0 release
Hi, I have had several spontaneous reboots with the 6.0 release installed off of the iso CD. I am wondering if I should upgrade to stable? I have had problems with this laptop in Linux where it would not get through the ACPI part of the boot process. I would have to reboot it several times before it would go all the way through. After I first installed FreeBSD, I thought I might be having some problem with Mozilla as it tends to create zombie processes. Firefox starts to eat up 100% cpu on the first WWW page visited. But then it could be an Xorg or Enlightenment problem as well. I wonder if anyone else uses this type laptop, and if they have had problems? Maybe before upgrading to stable I should try disabling ACPI and/or hyperthreading and see what happens. But I don't like waiting for problems to happen if someone else has found the solution already. Thanks a lot, Rob Lytle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
tx underrun ? (add entry into xl manpage)
Vincent Blondel wrote: Hello all, When having a look at log files on my web servers, I regulary see next output on the 3COM ethernet interfaces : xl1: transmission error: 90 xl1: tx underrun, increasing tx start threshold to 120 bytes xl1: transmission error: 90 xl1: tx underrun, increasing tx start threshold to 180 bytes xl1: promiscuous mode enabled xl1: promiscuous mode disabled Can somebody explain me what it is and if this situation is normal ? Rumours are that these messages are harmless, but if someone can explain these messages properly, it would be nice to add an entry to the DIAGNOSTICS section of the xl manpage (hence, this mail also goes to doc mailinglist) I see these messages too on my router/gateway: xl1: transmission error: 90 xl1: tx underrun, increasing tx start threshold to 120 bytes xl1: transmission error: 90 xl1: tx underrun, increasing tx start threshold to 180 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl1: transmission error: 90 xl1: tx underrun, increasing tx start threshold to 240 bytes Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
Peter Jeremy wrote: On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote: The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours When the first deadlock occurs, you have a fully populated set of kernel objects (though possibly some of them are in the buffer case rather than on disk). You should be able to quickly reproduce the panic by running: # cd /usr/obj/usr/src/sys/KERNEL # make I have cvsup'ed the sources to STABLE as of Nov. 23rd 2005. After recompiling/installing world and debug-kernel, I again get a kernel deadlock when using swapfile: http://surfion.snu.ac.kr/~lahaye/swapfile2.txt Previous deadlocks are still documented here http://surfion.snu.ac.kr/~lahaye/swapfile.txt I hope this is of use for fixing this bug in 6. If further investigation is needed, then please let me know. Regards, Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
Rob wrote: --- Peter Jeremy PeterJeremy at optushome.com.au wrote: Basically, wait until your system deadlocks. BREAK into DDB. As a start, run 'show lockedvnods', 'ps'. My guess is that you'll see a lock that has a number of waiters which is probably the culprit. Use 'panic' to get a crashdump and then you can use kgdb to rummage around once you reboot If in doubt, post the output from the above commands here and someone will hopefully provide further input. The output is here: http://surfion.snu.ac.kr/~lahaye/swapfile.txt Has this kernel debug output been of any use? Or was this analysis not helping much as to why 6 has problems with swapfiles? I can dig further into the problem, if I get some more hints how to do so. Regards, Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why device sk (PCI Gigabit Ethernet) cannot use polling?
Xin LI wrote: On 11/18/05, Rob [EMAIL PROTECTED] wrote: Hi, The sk device has no polling support, neither in 5 nor in 6. Is there a particular reason (maybe because it's a Gigabit device) ? Or is polling not supported because it simply has not yet been coded? If so, would it be straightforward to add the code? That would not be very hard if you own some hardware, so if you have the hardware, give it a try! :-) I do have the hardware: an sk integrated on the motherboard, but this is on a production server. Also, I don't know anything about coding the polling stuff; I use it on other PCs (rl, xl) and was wondering why not with sk. If I have a piece of code that is 99.9 % sure to work, then in that case I could try it out on the production server in a test over the weekend. BTW. Since glebius@ has some recent work on polling(4), you may want to ask him for some in-depth advises. Who is glebius? Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
Lars Kristiansen wrote: Hello again, I am the me too-guy with console-access. Hi Lars, I'm the one who started this thread, when I could not compile a new kernel after I upgraded to 6 (Pentium-1, 150 MHz, 32 MB Ram). How do you trigger the deadlock? The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours If you have a different (and possibly quicker) way to trigger the deadlock, I would like to try that also on my system. Please let me know. Regards, Rob. - Yahoo! FareChase - Search multiple travel sites in one click. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
Peter Jeremy wrote: On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote: The only way I know of how to trigger the deadlock, is to compile a new kernel and the 'linking kernel' stage will lock-up the PC. With a regular kernel, this takes 2.5 hours until deadlock, but with a fully equipped debug kernel it takes about 8 hours When the first deadlock occurs, you have a fully populated set of kernel objects (though possibly some of them are in the buffer case rather than on disk). You should be able to quickly reproduce the panic by running: # cd /usr/obj/usr/src/sys/KERNEL # make I'm doing this right now... Although I have not got into the deadlock yet, I do get these lines in the serial console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 12333, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22990, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22928, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22625, size: 8192 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22990, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22784, size: 8192 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23233, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23404, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 23154, size: 4096 A typical snapshot of 'swapinfo' at this time is: Device 1K-blocks UsedAvail Capacity /dev/ad0s1b 398483984039848 100% /dev/md0 13107254136 13107241% Total 170920939767694455% (By the way, notice that the 'Avail' column of /dev/ad0s1b and /dev/md0 is wrong; for Total it's correct. Is this a general bug in 6 or only on my PC? ) Googling on the above swap_pager lines, I found this conversation: http://lists.freebsd.org/pipermail/freebsd-current/2005-September/00.html which claims that DragonFly has fixed this problem. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-Stable: swapinfo has wrong output?
Hi, I have upgraded to 6-Stable. The swapinfo command gives wrong output: Device1K-blocks UsedAvail Capacity /dev/md0 13107211848 131072 9% I guess, the math should be: 1K-blocks = Used + Avail However, 1K-blocks = Avail, irrespective of what is used. In case of more than one swap device, then the Total line shows the right numbers. Is this a bug? Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: Basically, wait until your system deadlocks. BREAK into DDB. As a start, run 'show lockedvnods', 'ps'. My guess is that you'll see a lock that has a number of waiters which is probably the culprit. Use 'panic' to get a crashdump and then you can use kgdb to rummage around once you reboot If in doubt, post the output from the above commands here and someone will hopefully provide further input. The output is here: http://surfion.snu.ac.kr/~lahaye/swapfile.txt A swapfile is only swap device: /swapfile of 128 MB on /dev/ad0s1a as /dev/md0 At time of deadlock: swapdevice used 13% Serial console gets exactly this line every few seconds: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4317, size: 4096 Do you understand this? Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Kris Kennaway [EMAIL PROTECTED] wrote: I commented on it elsewhere in this thread. Do you mean your comment on the swap_pager error: Quote: AFAICT that is just a trigger-happy timer..it's supposed to detect when a swap operation took too long to complete, but it also triggers on swapfiles since they're so much less efficient (i.e. slower) than swapping onto a bare device. EndQuote. Remains the question: using this swapfile always worked very well with 5-Stable, but suddenly with 6 I run into these troubles. I hoped that the debugger output made some sense to an expert as to why this happens with 6, but never with 5 Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Why device sk (PCI Gigabit Ethernet) cannot use polling?
Hi, The sk device has no polling support, neither in 5 nor in 6. Is there a particular reason (maybe because it's a Gigabit device) ? Or is polling not supported because it simply has not yet been coded? If so, would it be straightforward to add the code? Thanks, Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Why device sk (PCI Gigabit Ethernet) cannot use polling?
Hi, The sk device has no polling support, neither in 5 nor in 6. Is there a particular reason (maybe because it's a Gigabit device) ? Or is polling not supported because it simply has not yet been coded? If so, would it be straightforward to add the code? Thanks, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote: makeoptions DEBUG=-g options INVARIANTS options WITNESS options WITNESS_KDB options KDB options DDB options DDB_NUMSYM options GDB Is that enough? If your system is headless, you probably want 'options BREAK_TO_DEBUGGER' as well. First question is: Does the system still deadlock? INVARIANTS and WITNESS will have added sanity checks which might have picked up the problem. Indeed, I have this in my DEBUG kernel config: makeoptions DEBUG=-g options INVARIANT_SUPPORT options INVARIANTS options WITNESS options WITNESS_KDB options KDB options DDB options DDB_NUMSYM options GDB options BREAK_TO_DEBUGGER and the deadlock disappears. Does that already give a hint what's wrong? If not, then what should I remove/keep from the above list, to allow the deadlock to reappear and still be able to debug the problem? According to your info above, I would say I'd remove INVARIANT_SUPPORT, INVARIANTS, WITNESS and WITNESS_KDB; leave the others in there and try again with such a debug kernel. Right? Thanks, Rob. Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: Since your /home is almost empty, how about (temporarily) moving the contents into /usr and swapping onto ad0s1e rather than into a swapfile. This should at least enable you to build a debug kernel. I'm now indeed building a new kernel, without using a swapfile. I have following in the kernel config: makeoptions DEBUG=-g options INVARIANTS options WITNESS options WITNESS_KDB options KDB options DDB options DDB_NUMSYM options GDB Is that enough? First I used 128 MB swapfile on root partition; then tried again with a 128 MB swapfile on /var. However, exactly the same deadlock occurs: Have you pre-allocated the swapfile or is it being allocated as necessary? If the latter, try dd if=/dev/zero of=swapfile bs=1m count=128 Yes, I always 'zero' the swapfile this way, before adding. Because I have used this swapfile construct extensively with previous 5-Stable on the same PC, I assume that harddisk and hardware are OK. Therefore my conclusion is, that there's some problem related to swapfile with 6. I will try to debug as much as I can, to find out why the machine becomes dead at a particular point while using a swapfile (fortunately this is very reproducible). I have never debugged a kernel, so I may ask soon for some assistance. Already now I wonder: 1) Can I debug a kernel that does not crash, but just hangs in a deadlock? Everything seems to be frozen, except pinging the PC 2) Is such debugging possible on a headless PC without a keyboard attached? I do have serial console access. Thanks, Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
One more thing, for those who are reading this thread. Concerning my kernel locking up while using a swapfile: I had an infinite while loop running during the kernel compilation, printing out 'swapinfo' every 15 seconds. The last output before the machine goes dead is this: /dev/ad0s1b 39848118203984830% /dev/md0 131072 5908 131072 5% Total 17092017728 15319210% which means that swap space is OK right before the freeze, but within 15 seconds from here, the kernel locks up Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote: makeoptions DEBUG=-g options INVARIANTS options WITNESS options WITNESS_KDB options KDB options DDB options DDB_NUMSYM options GDB Is that enough? If your system is headless, you probably want 'options BREAK_TO_DEBUGGER' as well. If I merge all these options into the GENERIC kernel config file, the kernel compilation ends with error: $ make buildkernel KERNCONF=DEBUGKERNEL [...snip...] cc -c -O -pipe ... /usr/src/sys/dev/ata/atapi-cd.c /usr/src/sys/dev/ata/atapi-cd.c: In function `acd_geom_attach': /usr/src/sys/dev/ata/atapi-cd.c:181: warning: implicit declaration of function `_sx_assert' /usr/src/sys/dev/ata/atapi-cd.c:181: warning: nested extern declaration of `_sx_assert' *** Error code 1 Stop in /usr/obj/usr/src/sys/MYKERNEL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- In /etc/make.conf, I have: CFLAGS= -O -pipe NO_PROFILE=true NO_PF=true RUBY_VER=1.8 PERL_VER=5.8.7 PERL_VERSION=5.8.7 Hence, so far no luck with building a debug kernel with 6. Any ideas what's wrong here? Thanks, Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6?
--- Peter Jeremy [EMAIL PROTECTED] wrote: On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote: 2) Is such debugging possible on a headless PC without a keyboard attached? I do have serial console access. Yes. See above URL. The advantage is that you can (hopefully) capture a log of your debug session. Send a serial BREAK and you should get a DDB prompt. What is this serial BREAK? How do I send a serial BREAK at the serial console? Is this some magic key combination? And, eh, at the moment of deadlock, there is no response at all from the serial console; will the serial BREAK not be bothered by that? Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg-clients conflicts with xterm (patch)
James Long wrote:
Then I noticed:
=== xorg-clients-6.8.2_1 depends on package: xterm0 - not found
and investigated the Makefile to find why the odd package
name of xterm0.
My portstree from Nov. 12th, has this at this particular place:
RUN_DEPENDS=xterm-static:${PORTSDIR}/x11/xterm
LIB_DEPENDS=png.5:${PORTSDIR}/graphics/png \
Xft.2:${PORTSDIR}/x11-fonts/libXft
Is this xterm0 line a broken download with cvsup, or something?
Rob.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0: during kernel compilation, 'kernel linking' freezes PC
Hi, I have upgraded a Pentium-1 PC from 5 to 6-Stable, which went smoothly. Now I'm running 6 with GENERIC kernel, and I want to compile a new kernel. When I start a new kernel compilation, this process *always* freezes the PC (no crash) when reaching the point of linking kernel; this is 100 percent reproducible!! Then all communication with the PC is frozen; no serial port response, no ssh response etc. However, I can ping the PC. Only power off/on brings the PC back to live. Any idea how I can further investigate. /var/log/messages has no special information while the freezing occurred. The output of 'dmesg' of this PC is here: http://surfion.snu.ac.kr/~lahaye/dmesg Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Swapfile problem in 6? (was: 6.0: during kernel compilation, 'kernel linking' freezes PC)
--- Rob [EMAIL PROTECTED] wrote: Hi, I have upgraded a Pentium-1 PC from 5 to 6-Stable, which went smoothly. Now I'm running 6 with GENERIC kernel, and I want to compile a new kernel. When I start a new kernel compilation, this process *always* freezes the PC (no crash) when reaching the point of linking kernel; this is 100 percent reproducible!! Then all communication with the PC is frozen; no serial port response, no ssh response etc. However, I can ping the PC. Only power off/on brings the PC back to live. Any idea how I can further investigate. /var/log/messages has no special information while the freezing occurred. The output of 'dmesg' of this PC is here: http://surfion.snu.ac.kr/~lahaye/dmesg Problem kind of solved: As this PC has only 32 MB Ram, I add a swapfile. However, when I compile the new kernel without the swapfile, all goes well. Since the freeze is very reproducible with the swapfile (always at the 'kernel linking' stage), and immediately disappears when I do not use the swapfile, I think there's something wrong with using swapfile in 6.0. Is it? I do this: dd if=/dev/zero of=/swapfile bs=1024k count=128 chmod 0600 /swapfile mdconfig -a -t vnode -f /swapfile -u 0 swapon /dev/md0 Is this OK? Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6? (was: 6.0: during kernel compilation, 'kernel linking' freezes PC)
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Nov 14, 2005 at 05:52:42PM -0800, Rob wrote: Problem kind of solved: As this PC has only 32 MB Ram, I add a swapfile. However, when I compile the new kernel without the swapfile, all goes well. Since the freeze is very reproducible with the swapfile (always at the 'kernel linking' stage), and immediately disappears when I do not use the swapfile, I think there's something wrong with using swapfile in 6.0. Is it? I do this: dd if=/dev/zero of=/swapfile bs=1024k count=128 chmod 0600 /swapfile mdconfig -a -t vnode -f /swapfile -u 0 swapon /dev/md0 Is this OK? Looks fine, and I use this myself (on a much larger scale). Are you sure it's freezing and not just taking a really long time? Whenever your system is swapping performance will be terrible, and that goes at least double for swapping onto a file and not a device. What happens if you leave it for an hour or two (or overnight)? I left it overnight twice for performing this 'kernel linking' stage. In both cases the machine remained dead. Without the swapfile, this 'kernel linking' stage completes in just about less than a minute. So I think it's not my impatience, but there is another problem with my swapfile or with 6 :). Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapfile problem in 6? (was: 6.0: during kernel compilation, 'kernel linking' freezes PC)
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Nov 14, 2005 at 06:08:27PM -0800, Rob wrote: I left it overnight twice for performing this 'kernel linking' stage. In both cases the machine remained dead. Without the swapfile, this 'kernel linking' stage completes in just about less than a minute. So I think it's not my impatience, but there is another problem with my swapfile or with 6 :). Since you can compile a kernel without it, add DDB, WITNESS and INVARIANTS support, then trigger the deadlock with the swapfile, break to DDB and examine the state of the machine. See the chapter on kernel debugging in the developers handbook for more instructions. Thanks, but for now, I cannot compile a new kernel, because the kernel compilation terminates with insufficient swap space error. Apparently 32 MB is not enough for a new kernel compilation. So for now I'm stuck with the GENERIC kernel. This is my partitioning: /dev/ad0s1a253678 34446 19893815%/ /dev/ad0s1b 39848 8168 3984820%(swap) /dev/ad0s1d253678 152958 8042666%/var /dev/ad0s1e253678 6016 227368 3%/home /dev/ad0s1f 1624576 727274 76733649%/usr First I used 128 MB swapfile on root partition; then tried again with a 128 MB swapfile on /var. However, exactly the same deadlock occurs: when the kernel compilation reaches 'linking kernel' the PC is dead (no crash). Although I can ping the PC, there's no response to any other service; also serial port console is dead. Without using the swapfile, the compilation easily passes through the 'linking kernel' stage, but somewhat later terminates as swap space is insufficient. With 5-Stable, I used the swapfile extensively for recompiling new kernels and worlds, without any problem. I only can conclude that something is wrong with the swapfile construct in 6. Is 128 MB too big for a swapfile in 6? I'll try again with a smaller swapfile... Any other ideas? dmesg output of this PC is here: http://surfion.snu.ac.kr/~lahaye/dmesg Thanks, Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GENERIC and DEFAULTS
Kris Kennaway wrote: You've clearly never spent much time on the FreeBSD support forums, where every few days someone posts for help 1) with an error caused by removing one of those Do not remove this! lines, and 2) for help on getting X working when they forgot to add /dev/io and /dev/mem to their kernel. Those of us who spend a lot of time answering such questions will surely welcome the change, since it will hopefully reduce our workload. I assume: if a 'novice' innocently removes the io/mem devices, he/she as well will happily add a 'nodevice io' and 'nodevice mem' in their new kernel configand again scream HELP to the mailinglist when X does not start! Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GENERIC and DEFAULTS
Kris Kennaway wrote: You missed the part where I said that the error is commonly reported by people who have chosen not to build modules. The DEFAULTS construction is put in place to help 'novices' not to do stupid things (as removing io/mem). However, does 'building a kernel without modules' qualify as a novice action? I wonder. I think if you know how to do that, you've quite progressed in the world of kernel building! Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GENERIC and DEFAULTS
Kris Kennaway wrote:
You've clearly never spent much time on the FreeBSD
support forums, where every few days someone posts
for help
1) with an error caused by removing one of those
Do not remove this! lines, and
2) for help on getting X working when they forgot
to add /dev/io and /dev/mem to their kernel.
I believe *BSD can offer a better solution for such
issues.
For example, when having firewall_enable=YES,
then /etc/rc.d/ipfw does:
if ! ${SYSCTL} net.inet.ip.fw.enable; then
if ! kldload ipfw; then
warn unable to load firewall module.
return 1
fi
fi
So if ipfw is not supported by the kernel, this
script will automagically load the ipfw module,
or issue a warning what is missing.
(Similarly, but not yet implemented, /etc/rc.d/sshd
should automagically load the random module, if
not in the kernel).
My point is then to follow this strategy also for X:
instead of a DEFAULTS file, have a /etc/rc.d/xdm
script, which starts X and loads the modules io/mem
if needed.
Rob.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Easy way to kill a 5.x/6.x box as a basic user.
Michael A. Koerber wrote: I have found that ImageMagick writes to (and often fills up) /var/tmp...my system becomes sluggish, dies, reboots. The solution I have used is to 1) create a /usr/tmp, 2) remove /var/tmp , 3) make a symbolic link between /usr/tmp and /var/tmp. Perhaps ImageMagick could be patched to use a /usr/tmp directory for scratch. Use: setenv MAGICK_TMPDIR /usr/tmp Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: math/grace port: libXcursor.so.1.0 not found ??
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Oct 25, 2005 at 08:41:33PM -0700, Rob wrote: I'm running FreeBSD 5-Stable. I only seem to encounter this problem with the math/graphical port 'grace', and the dlopen() call inthere. I answered this question the last time you posted it. Yes, indeed. Thank you. You said: Sounds like the application is broken for requesting it, since as you found there is no such library on FreeBSD. Here the application refers to what? Grace? Or dlopen()? If you mean grace, then I have a problem: the grace mailinglist blames FreeBSD, and here grace is blamed. Argh! I am the only FreeBSD user on the Grace mailinglist. Apparently the dlopen() call in grace works fine on Linux and others. But not with FreeBSD. Is there something fishy or tricky about the dlopen() call on FreeBSD, when compared to, for example, Linux? Grace runs fine on FreeBSD, until I use it such that it does the 'dlopen()' call. I am at a total loss here How can I further analyse this problem? Thanks, Rob. __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: math/grace port: libXcursor.so.1.0 not found ??
--- Pete French [EMAIL PROTECTED] wrote: I am the only FreeBSD user on the Grace mailinglist. Apparently the dlopen() call in grace works fine on Linux and others. But not with FreeBSD. This is not a problem with the dlopen call *or* freebsd - the problem is that it is asking for a library 'libXcursor.so.1.0' which does not exist on FreeBSD. There is a 'libXcursor.so.1' though. You need to get the grace people to change the application so it requests the correct library when running on FreeBSD. The reason why the grace developper blames FreeBSD is because of this: The executable 'xmgrace' is linked to /usr/X11R6/lib/libX11.so.6 and 'strings /usr/X11R6/lib/libX11.so.6 | grep libXcursor' gives: libXcursor.so.1.0.2 So according to the grace developper, the reason for my problem is a problem with libX11.so.6. But I know nothing about this stuff By the way: can someone also explain to me why libX11.so.6 has the string libXcursor.so.1.0.2. I will then forward this to the grace mailinglist, and tell them that there's something wrong with Grace. Thank so much! Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: math/grace port: libXcursor.so.1.0 not found ??
--- Peter Jeremy [EMAIL PROTECTED] wrote: On Tue, 2005-Oct-25 20:41:33 -0700, Rob wrote: 2. Create $HOME/.grace/gracerc.user and put one line in this file: USE pow TYPE f_of_dd FROM /usr/lib/libm.so (this is the example from the Grace UsersGuide) Does grace work correctly if you don't include this line? Without that line, grace starts without any problem. With that line, grace cannot perform the action described in that line (USE pow FROM libm.so), because the responsible dlopen() call has the error: Shared object libXcursor.so.1.0 not found, required by xmgrace However, despite this error, grace continues to start up fine (but, as I said, without loading the function from the library). Rob. __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
math/grace port: libXcursor.so.1.0 not found ??
Hi, I'm running FreeBSD 5-Stable. I only seem to encounter this problem with the math/graphical port 'grace', and the dlopen() call inthere. It seems to be a FreeBSD specific problem and I wonder if other people on this list encounter the same problem. This is the problem: 1. Install Grace from ports (math/grace) 2. Create $HOME/.grace/gracerc.user and put one line in this file: USE pow TYPE f_of_dd FROM /usr/lib/libm.so (this is the example from the Grace UsersGuide) 3. Start grace like this: $ xmgrace Shared object libXcursor.so.1.0 not found, required by xmgrace DL module load failed: USE pow TYPE F_OF_DD FROM /usr/lib/libm.so Error at line 1 Because if this library problem, Grace cannot load pow from /usr/lib/libm.so. However, apart from that, grace starts normally. The syntax in file gracerc.user is correct; I have verified this with the Grace mailinglist. The line Shared object...not found is the error message-string set by the dlopen() call in Grace: handle = (void *)dlopen(/usr/lib/libm.so, RTLD_LAZY) When I do a 'locate libXcursor.so.1.0', I get: /usr/compat/linux/usr/X11R6/lib/libXcursor.so.1.0.2 Why is dlopen() failing on libXcursor.so.1.0 ? A possible hint could be that libXcursor.so.1.0.2 appears when 'strings /usr/X11R6/lib/libX11.so.6'. Why is it in libX11.so.6 ?? Thanks for help or clues! Rob. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5-Stable: DMA count reg bogus distorts sound (ESS-Solo)
Hi, I'm running 5-Stable as of Sept. 24th. My sound card is an ESS Solo-1 (integrated in the motherboard). I load the modules sound.ko and snd_solo.ko. When using realplayer or mplayer, sound is very much distorted; also, the console gets an endless stream of these kind of messages: DMA count reg bogus: 4ff4 4ff4 Any idea what this means and what I can do about this to solve the distortion of the sound? The dmesg output of the PC is here: http://surfion.snu.ac.kr/~lahaye/dmesg.boot Thanks, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: any ideas when 5.5 will be out
On Tuesday, September 20, 2005 2:47 AM, Paul Root unleashed the infinite monkeys and produced: I will go to 5.5, I'm sure, on my servers. I update from source fairly regularly. And that was the original question: Why would 5.5 come out after 6.0? For the same reason 4.11 came out after 5.3. Quoting from Kris Kennaway's response to the mail before yours :) Read the handbook for detailed explanation of how FreeBSD releases work. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Crash on Alpha - 4.11-STABLE
Hi there, This is the second time I've seen this crash in the past three weeks. I'm not sure what the root cause either. This box is just a home server with a single NFS exported directory and one NFS client. It is also a caching http proxy server for my home LAN (three machines). The crash is not occurring during busy times for the proxy side of things, as it happened at 2:01am. FreeBSD erwin.number6 4.11-STABLE FreeBSD 4.11-STABLE #9: Mon Jun 13 23:54:13 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ERWIN alpha panic: ffs_write: dir_write panic Stopped at Debugger+02xc: ldq ra,0(sp) 0xfe000bab5988 ra=0xfc557be0, sp=0xfe000ba5988 db trace Debugger() at Debugger+02xc panic() at panic+0x2c ffs_write() at ffs_write+0x120 vnode_pager_generic_putpages() at vnode_pager_generic_putpages+0x21c ffs_putpages() at ffs_putpages+0x30 vnode_pager_putpages() at vnode_pager_putpages+0x9c vm_pageout_flush() at vm_pageout_flush+0x15c cheers, Rob -- A husband is what is left of a man after the nerve is extracted. This is random quote 159 of 1268. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
atapci VIA 82C596B UDMA66 controller: problem for 5.X ?
Hi, I have two PCs, with apparently a somewhat old motherboard, since there's a maximum support for UDMA66 by the harddisk controller. The attached harddisks are newer and allow a higher speed of UDMA100. This combination of older motherboard and newer harddisk causes great problems with 5.X (it never did with 4.X). I have irregular crashes of X and even crashes at initial bootup. All this is solved by using hw.ata.ata_dma=0, which forces the harddisk to use the very low speed of PIO4 :(. Both PCs have a VIA 82C596B UDMA66 controller. I wonder if that is the problem for 5.X ? On these two PCs, the output is of grep -i ata /var/run/dmesg.boot is: -- PC1 --- atapci0: VIA 82C596B UDMA66 controller port 0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63] at ata0-master PIO4 acd0: CDROM CRD-8520B/1.00 at ata1-master PIO4 -- PC2 --- atapci0: VIA 82C596B UDMA66 controller port 0xc000-0xc00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata0-master PIO4 ad1: 16448MB WDC WD172AA/05.05B05 [33420/16/63] at ata0-slave PIO4 acd0: CDRW HL-DT-ST RW/DVD GCC-4320B/1.00 at ata1-master UDMA33 - I consider this a serious drawback of 5.3. Any idea how this can be resolved? Best regards, Rob. __ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fatal trap 12 in pagedaemon on dual-core opteron machine
On Thu, 30 Jun 2005, Kris Kennaway wrote:
On Thu, Jun 30, 2005 at 04:00:47PM -0400, Rob Watt wrote:
#7 0x80400c0b in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:171
#8 0xff007c3b00f0 in ?? ()
#9 0xff007b78c500 in ?? ()
#10 0x0001840f in ?? ()
#11 0x in ?? ()
#12 0x in ?? ()
[..]
All these bogus stack frames can be caused by having compiled the
kernel with -O2 instead of -O. Is this the case?
It seems the default for amd64 is to compile with:
COPTFLAGS=-O2 -frename-registers -pipe
I changed the -O2 to -O, and there are still a large number of bogus stack
frames (although there are more readable frames then before):
#0 doadump () at pcpu.h:167
#1 0x in ?? ()
#2 0x802aca23 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:410
#3 0x802ace8b in panic (fmt=0xff007b78c500 \u\022y{) at
/usr/src/sys/kern/kern_shutdown.c:566
#4 0x804275bc in trap_fatal (frame=0xff007b78c500,
eva=18446742976269456104)
at /usr/src/sys/amd64/amd64/trap.c:639
#5 0x80427220 in trap_pfault (frame=0xb1c129c0,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:562
#6 0x80426e99 in trap (frame=
{tf_rdi = -1097427386128, tf_rsi = -1097440115456, tf_rdx = 100956,
tf_rcx = 0, tf_r8 = 0, tf_r9 = 0, tf_rax = 100956, tf_rbx = 0, tf_rbp =
-1098510893056, tf_r10 = 30, tf_r11 = 29, tf_r12 = -1097364252160, tf_r13
= -2143265920, tf_r14 = 0, tf_r15 = -2141262160, tf_trapno = 12, tf_addr =
136, tf_flags = 0, tf_err = 0, tf_rip = -2144628916, tf_cs = 8, tf_rflags
= 66050, tf_rsp = -1312740736, tf_ss = 16}) at
/usr/src/sys/amd64/amd64/trap.c:341
#7 0x80413c5b in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:171
#8 0xff007c3b00f0 in ?? ()
#9 0xff007b78c500 in ?? ()
#10 0x00018a5c in ?? ()
#11 0x in ?? ()
#12 0x in ?? ()
#13 0x in ?? ()
#14 0x00018a5c in ?? ()
#15 0x in ?? ()
#16 0xff003ba6 in ?? ()
#17 0x001e in ?? ()
#18 0x001d in ?? ()
#19 0xff007ffe5a00 in ?? ()
#20 0x80405b80 in vm_pageout_page_stats () at
/usr/src/sys/vm/vm_pageout.c:1350
#21 0x in ?? ()
#22 0x805eeeb0 in sysctl___kern_sched_runq_fuzz ()
#23 0x000c in ?? ()
#24 0x0088 in ?? ()
#25 0x in ?? ()
#26 0x in ?? ()
#27 0x802b8f4c in thread_fini (mem=0x0, size=0) at
/usr/src/sys/kern/kern_thread.c:271
#28 0x0010 in ?? ()
#29 0xff007ffe4620 in ?? ()
#30 0x in ?? ()
#31 0xff003ba60f98 in ?? ()
#32 0x80407a41 in zone_drain (zone=0x10202) at
/usr/src/sys/vm/uma_core.c:749
#33 0x80408ed6 in zone_foreach (zfunc=0x80407810
zone_drain) at /usr/src/sys/vm/uma_core.c:1494
#34 0x8040acb5 in uma_reclaim () at
/usr/src/sys/vm/uma_core.c:2623
#35 0x80404836 in vm_pageout_scan (pass=0) at
/usr/src/sys/vm/vm_pageout.c:674
#36 0x80405f1e in vm_pageout () at
/usr/src/sys/vm/vm_pageout.c:1476
#37 0x80292e4b in fork_exit (callout=0x80405b80
vm_pageout, arg=0x0, frame=0xb1c12c50)
at /usr/src/sys/kern/kern_fork.c:791
#38 0x80413e5e in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:296
#39 0x in ?? ()
#40 0x in ?? ()
#41 0x0001 in ?? ()
#42 0x in ?? ()
#43 0x in ?? ()
#44 0x in ?? ()
#45 0x in ?? ()
#46 0x in ?? ()
#47 0x in ?? ()
#48 0x in ?? ()
#49 0x in ?? ()
#50 0x in ?? ()
#51 0x in ?? ()
#52 0x in ?? ()
#53 0x in ?? ()
#54 0x in ?? ()
#55 0x in ?? ()
#56 0x in ?? ()
#57 0x in ?? ()
#58 0x in ?? ()
#59 0x in ?? ()
#60 0x in ?? ()
#61 0x in ?? ()
#62 0x in ?? ()
#63 0x in ?? ()
#64 0x in ?? ()
#65 0x in ?? ()
#66 0x in ?? ()
#67 0x in ?? ()
#68 0x in ?? ()
#69 0x in ?? ()
#70 0x in ?? ()
#71 0x0081e000 in ?? ()
#72 0x806457f4 in vm_page_max_wired ()
#73 0x in ?? ()
#74 0x0001 in ?? ()
#75 0xff007b7912e8 in ?? ()
#76 0xff007b7f5000 in ?? ()
#77 0xb1c12ae8 in ?? ()
#78 0xff007b78c500 in ?? ()
#79 0x802c0c84 in sched_switch (td=0x0, newtd=0x0, flags=1) at
/usr/src/sys/kern/sched_4bsd.c:881
...
-
Rob Watt
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL
fatal trap 12 in pagedaemon on dual-core opteron machine
# GUID Partition Tables. options COMPAT_43 # Needed by COMPAT_LINUX32 options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_LINUX32 # Compatible with i386 linux binaries 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 AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug options ADAPTIVE_GIANT # Giant mutex is adaptive. options SMP device atpic # 8259A compatability options LINPROCFS # Cannot be a module yet. device acpi device isa device pci device fdc 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 device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) 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 device sc device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device device em # Intel PRO/1000 adapter Gigabit Ethernet Card device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet 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 device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse any thoughts? thanks. - Rob Watt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
any users of the fla(4) left ?
Has there been any update to the status of fla on 5.x ? We are interested in seeing these drivers become available on 5.x Pity we didn't express that interest at the right time - nearly a year ago Rob Stevens Silverspring Networks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA378 / SATA150 RAID controller supported by 5.4?
--- Doug White [EMAIL PROTECTED] wrote: On Tue, 17 May 2005, Rob wrote: The 'pciconf -lv' tells me: [EMAIL PROTECTED]:4:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20378 FastTrak 378/SATA 378 RAID Controller' class= mass storage subclass = RAID But I get this in my dmesg output: atapci0: Promise PDC20378 SATA150 controller port 0xd880-0xd8ff,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac-0xfead,0xfeafe000-0xfeafefff irq 10 at device 4.0 on pci2 atapci0: failed: rid 0x20 is memory, requested 4 That's the PCI busmaster register, although it seems to be the wrong resource type. It should be I/O space, which maps to PCI config space, and not memory-mapped. I can't seem to find what function emits that message. A full dmesg would be useful. It's at: http://surfion.snu.ac.kr/~lahaye/dmesg.boot Does that help? Thanks, Rob. Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SATA378 / SATA150 RAID controller supported by 5.4?
Hi, The 'pciconf -lv' tells me: [EMAIL PROTECTED]:4:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20378 FastTrak 378/SATA 378 RAID Controller' class= mass storage subclass = RAID But I get this in my dmesg output: atapci0: Promise PDC20378 SATA150 controller port 0xd880-0xd8ff,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac-0xfead,0xfeafe000-0xfeafefff irq 10 at device 4.0 on pci2 atapci0: failed: rid 0x20 is memory, requested 4 rl0: RealTek 8139 10/100BaseTX port 0xd000-0xd0ff mem 0xfeaff400-0xfeaff4ff irq 10 at device 9.0 on pci2 At present I use a single harddisk on the regular IDE connector (atapci1 UDMA100-controller). Is the RAID controllor on atapci0 supported by 5.4? What is the 'failed' message about in dmesg? Also note the seemingly interrupt conflict of both, rl0 and atapci0, claiming irq 10 ?!?! Thanks, Rob. __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installing on headless boxes
Dick Davies wrote: Is it possible to install using only a serial console? I didn't think so, so thought I might roll my own 5.4 cd to enable that. Is there anything else that needs doing about from See: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5.4-RELEASE/floppies/README.TXT And scroll to the section: 1.5.6 Tips for Serial Console Users I think this explains what you're asking for. Rob. __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 5.4 and asus k8n nforce3 250
On Sunday, May 15, 2005 6:44 AM, Zoran Kolic unleashed the infinite monkeys and produced: Dear all! I've installed 5.4 for amd64 on this asus mobo. Went just fine, but few things make me nervous. 1. Cannot see ethernet interface. There is RJ-45 port, but not in dmesg (attached). In manual says ic plus ip101 10/100 lan phy. Default on board is PnP on. How could I make OS to recognize the interface? Also, it has onboard lan boot rom, but doesn't change anything. Try the net/nvnet port (at least, it works for the NForce2 chipset). -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
--- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 8:04, Rob wrote: All computers are running 5-Stable, as of May 10. All, but PC1 with fxp, use polling, with: options DEVICE_POLLING options HZ=1000 1000 IMHO seems a bit too heavy. Try something lower. Same problem. Ssh-tunnel connection is also disrupted with HZ=100. May I conclude that the HZ value is not the culprit? Or should I try once again with HZ=10? kern.ipc.nmbclusters is 4928 for this PC. Is that good or bad? sysctl -a | grep -i polling gives following: kern.polling.burst: 150 kern.polling.each_burst: 5 kern.polling.burst_max: 150 kern.polling.idle_poll: 0 kern.polling.poll_in_trap: 0 kern.polling.user_frac: 50 kern.polling.reg_frac: 20 kern.polling.short_ticks: 0 kern.polling.lost_polls: 6 kern.polling.pending_polls: 0 kern.polling.residual_burst: 0 kern.polling.handlers: 0 kern.polling.enable: 0 kern.polling.phase: 0 kern.polling.suspect: 6 kern.polling.stalled: 0 kern.polling.idlepoll_sleeping: 1 118kern.polling.enable: 118xl0: flags=18843UP,BROADCAST,RUNNING,SIMPLEX, MULTICAST,POLLING mtu 1500 118 options=49RXCSUM,VLAN_MTU,POLLING 118xl1: flags=18843UP,BROADCAST,RUNNING,SIMPLEX, MULTICAST,POLLING mtu 1500 118 options=49RXCSUM,VLAN_MTU,POLLING I actually doubt whether the default values of these sysctl variables would cause the problem. Regards, Rob. __ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
--- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 13:13, Rob wrote: --- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 8:04, Rob wrote: All computers are running 5-Stable, as of May 10. All, but PC1 with fxp, use polling, with: options DEVICE_POLLING options HZ=1000 1000 IMHO seems a bit too heavy. Try something lower. Same problem. Ssh-tunnel connection is also disrupted with HZ=100. May I conclude that the HZ value is not the culprit? Or should I try once again with HZ=10? 100 should be fine. 10 would be a bit too much overkill. kern.ipc.nmbclusters is 4928 for this PC. Is that good or bad? What is the purpose of the box? Give a description of the network traffic. This is a lab in the Chemistry department; the box in question is a dual-homed gateway to eight other PCs in the lab. The box has a tight firewall, and runs an apache server and an SSH server. On the private network, the box also runs as a DHCP server, Samba server and NTP server. OS = 5-Stable. The other PCs in the lab are two FreeBSD PCs and various flavours of Windows. Did you use any strange CFLAGS like -O3 or -f* compile time options when you built the system? No. My /etc/make.conf has: CFLAGS= -O -pipe NOPROFILE=true NO_PF=true kern.polling.enable: 0 Force this to be 1. Damn I should have noted it earlier I took this printout after I changed the value to 0. Of course it is 1 when I test the polling, but when I noticed that the ssh-tunnel connection problem persisted, I changed it to 0; so that my ssh-tunnel connection is not randomly closed :). Thanks for your elaborate help! Rob. __ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
--- Ruslan Ermilov [EMAIL PROTECTED] wrote: On Wed, May 11, 2005 at 12:43:09AM -0700, Rob wrote: I actually doubt whether the default values of these sysctl variables would cause the problem. No. Can you observe the broken IP/TCP/UDP checksums? netstat -ss -f inet |grep -w bad Argh, just found out that it is not the polling. Even without the polling, the ssh-tunnel connection gets disrupted, although not as frequent as with the polling. Possibly, the polling makes the problem more visible, but it not the culprit. My apologies for the noise. I don't know yet exactly what it is. I use a script to test whether the ssh-tunnel is still alive; if not, then the tunnel is renewed. This script has worked like a charm for almost 6 months. Don't know what's has changed in the meantime. Also, four PCs are part of this ssh-tunnel, which makes it rather complex to pin-point the problem :(. Anyway, that's my problem. Most important: the xl polling seems OK. Meanwhile I have learned a lot more about what polling actually is! Thanks, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
Ruslan Ermilov wrote:
Greetings,
Those of you wishing to try your xl(4) card under
polling(4) are welcome to test this patch:
Ruslan,
Yesterday I discovered that polling of the xl
interface randomly disrupts an ssh-tunnel of mine.
I think there's still a subtle, yet critical problem
with xl polling.
I cannot locate the details of the problem, so I
will describe the symptoms that I see in my network,
and why I suspect xl polling.
Here is a sketch of my two private networks:
PC1 - GW1 GW2 - PC2
PC1 = PC on private network, Intel Pro/100 (fxp)
GW1 = Dual-homed Gateway, 2 x 3Com 3c905B-TX (xl)
GW2 = Dual-homed Gateway, 2 x RealTek 8139 (rl)
PC2 = PC on private network, RealTek 8139 (rl)
= Internet
All computers are running 5-Stable, as of May 10.
All, but PC1 with fxp, use polling, with:
options DEVICE_POLLING
options HZ=1000
GW2 redirects (with natd) port 2200 to PC2.
PC1 establishes an ssh-tunnel to PC2:
PC1$ ssh -p 2200 -N -f -R 2000:localhost:22 GW2
Then on PC2, I can use this tunnel to connect
directly to PC1, for example to run xbiff:
PC2$ ssh -Y -p 2000 localhost xbiff
This works beautifully, but every now and then the
ssh-tunnel connection is 'closed' for no reason
(the ssh-tunnel itself remains, but the connection
is closed).
This happens at least once an hour, seemingly at
random.
After some trial and error, I discovered that the
polling of the xl devices (GW1) is the culprit.
As soon as I disable the polling for the xl devices
on GW1, the ssh-tunnel connection is not disrupted
anymore.
-
GW1 is also a production server, so experimenting
is rather limited. However, I can run tests, if that
would help resolve the problem.
Here you can find some relevant info on GW1 with the
xl devices:
dmesg output:
http://surfion.snu.ac.kr/~lahaye/dmesg.boot
kernel configuration:
http://surfion.snu.ac.kr/~lahaye/MYKERNEL
/boot/loader.conf:
http://surfion.snu.ac.kr/~lahaye/loader.conf
Regards,
Rob.
__
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
--- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 8:04, Rob wrote: All computers are running 5-Stable, as of May 10. All, but PC1 with fxp, use polling, with: options DEVICE_POLLING options HZ=1000 1000 IMHO seems a bit too heavy. Try something lower. What is heavy and what is not? Does 100 sound better? How can I develop a feeling for the 'heaviness' of this HZ number? Is it related to the CPU speed? Thanks for clarifying! Rob. Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xl(4) polling
--- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 10:40, Rob wrote: --- Subhro [EMAIL PROTECTED] wrote: On 5/11/2005 8:04, Rob wrote: All computers are running 5-Stable, as of May 10. All, but PC1 with fxp, use polling, with: options DEVICE_POLLING options HZ=1000 1000 IMHO seems a bit too heavy. Try something lower. What is heavy and what is not? Does 100 sound better? How can I develop a feeling for the 'heaviness' of this HZ number? Is it related to the CPU speed? Thanks for clarifying! Rob. Before I answer this question, I would like to clarify a few things. Thanks for the detailed explanation. I now got a much better idea of what polling actually means. Great! When I have to put up a new FreeBSD box, I start from 100 and start beefing up the number until I find a good balance. Hmmm, how do you find a good balance ? Network access speed vs. lost connections.? --- I'm now trying a kernel with HZ=100 and will report the result shortly. Interestingly: HZ=1000 is apparently a problem with the xl devices (3Com 3c905B-TX), but not with the rl devices (RealTek 8139). What could cause that difference? Could a difference in buffer size on the LAN card cause this? Rob. Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Apache + Caching DNS: conflict at bootup? (DNS runs too late)
Hi, I'm running 5-Stable as of today. The PC is a dual-homed gateway to a local network, a caching nameserver, httpd server, firewall etc. In /etc/rc.conf, I have: named_enable=YES apache2_enable=YES The nameserver works fine after bootup, so I suppose that the named.conf is properly configured as a caching nameserver. After bootup, there's no httpd running, so I have to start it manually. During the bootup, following line occurs in httpd-error logs: hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of my.host.name (I faked my.host.name in this email, but it is an officially registered hostname + IP) I solved the problem, by commenting out the line LoadModule unique_id_module libexec/apache2/mod_unique_id.so in httpd.conf. But I think the actual problem is that there's a conflict in bootup order of the caching nameserver and the apache server. Some time ago, there was (or still is) a similar conflict with hostname resolution at bootup when using ntpd. Somehow the caching nameserver seems to get up and working too late in the boot process. Is that possible? Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buggy ATA controller: I can install 4.11, but not 5.3 !?!
Doug White wrote: On Thu, 31 Mar 2005, Rob wrote: --- Doug White [EMAIL PROTECTED] wrote: AFAIK the RZ1000 bug was that it would corrupt data to the slave channel if the primary channel was also active. If you only have one device then you may not be able to reproduce it. I have two harddisks on ata0: ad0: 520MB ST3660A [1057/16/63] at ata0-master BIOSPIO ad1: 2423MB SAMSUNG WINNER-3 WN32543A(2.5GB) [4924/16/63] at ata0-slave BIOSPIO ad0 has the base OS, and ad1 has /usr/src and /usr/obj for recompiling world and kernel. So far no problems. However, if I remember well, the other IDE connector on the motherboard does not seem to work, which now I realize could be caused by the buggy RZ 1000 chip. Entirely possible. With FreeBSD 4-Stable running still fine, I get this: # grep ata /var/run/dmesg.boot atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible at device 1.0 on pci0 atapci0: ATA channel disabled by BIOS ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ad0: 520MB ST3660A [1057/16/63] at ata0-master BIOSPIO ad1: 2423MB SAMSUNG WINNER-3 WN32543A(2.5GB) [4924/16/63] at ata0-slave BIOSPIO # vmstat -i | grep -i ata interrupt total rate rl0 irq11 3187504 1 fdc0 irq6 2 0 ata0 irq14 33429902 17 sio0 irq4 3 0 sio1 irq3 1 0 clk irq0187773091100 rtc irq8240341556127 Total 464732059247 So ata1 (irq 15) is not in the interrupt table !?! What does that mean? As a reminder: I have following in dmesg output: atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible at device 1.0 on pci0 atapci0: ATA channel disabled by BIOS For the harddisk to be recognized by the kernel, I need exactly this in the kernel config: device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 Without these lines in the kernel config, I get a fatal 'no root device found' error at bootup. Apart from these peculiar findings, 4-Stable is running flawlessly on this old Pentium-1 PC. - Another reminder: when I try to install 5.3 on this PC, I get a no disk found error at a very early stage of the installation procedure. I hope to investigate this further in a not-so-near future Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buggy ATA controller: I can install 4.11, but not 5.3 !?!
--- Graham Menhennitt wrote: Rob wrote: Another reminder: when I try to install 5.3 on this PC, I get a no disk found error at a very early stage of the installation procedure. I hope to investigate this further in a not-so-near future Rob, I have a similar problem with 5.3 although I'm not doing a new install - I'm upgrading from an earlier 5.X. Can you please try installing a 5.X from December last year or earlier. Actually, you don't need to install anything - I'd just like to know whether it can see the disk. I've faised PR kern/79332 about it which contains two possible fixes. Thank you. The computer is my brother's old Pentium-1 (60 MHz); he and the computer are at the other end of the world. Only when my brother has spare time, we open a live chat connection and I assist him with certain console tasks (he is not at all a Unix/FreeBSD person). However, most of the time I manage this PC remotely (it's now running 4-Stable flawlessly). At some point, we may try once again to install a 5.X version; it should be a straightforward install procedure, because too much freaky stuff might be too complex to explain to a non-Unix, non-FreeBSD person My plan for next time, is to use a serial console during install, so that I can receive the kernel output to get a clue why 5.X cannot find the disk, which 4-Stable does find easily. I may travel to my brother's home some time this year; then I will do whatever freaky tricks are needed to find out why 5.X is not installing properly. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Tape drive issues
): INQUIRY. CDB: 12 c0 0 0 24 0 (probe0:isp0:0:0:6): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:6): Initiator detected error message received (probe0:isp0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:isp0:0:0:7): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:7): Initiator detected error message received (probe0:isp0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:isp0:0:0:7): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:7): Initiator detected error message received (probe0:isp0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:isp0:0:0:7): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:7): Initiator detected error message received (probe0:isp0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:isp0:0:0:7): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:7): Initiator detected error message received (probe0:isp0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:isp0:0:0:7): ABORTED COMMAND asc:48,0 (probe0:isp0:0:0:7): Initiator detected error message received sa0 at isp0 bus 0 target 0 lun 0 sa0: SONY SDT-1 0101 Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) I've never seen these messages before, but they appear now once the tape drive has been added. I'm also unable to actually do anything with the device - [EMAIL PROTECTED] ~ % sudo camcontrol tur 0:0:0 Unit is not ready [EMAIL PROTECTED] ~ % sudo mt status mt: /dev/nsa0: Input/output err If I turn off tagged queuing at this point, things start to look up ... [EMAIL PROTECTED] ~ % sudo camcontrol negotiate -n sa -u 0 -T disable Current Parameters: (pass0:isp0:0:0:0): bus width: 16 bits (pass0:isp0:0:0:0): disconnection is enabled (pass0:isp0:0:0:0): tagged queueing is disabled [EMAIL PROTECTED] ~ % sudo camcontrol tur 0:0:0 Unit is ready However- [EMAIL PROTECTED] ~ % sudo mt status mt: /dev/nsa0: Input/output error Any advice? cheers, Rob -- Why do the Irish call their pound a punt? It rhymes with 'Bank Manager'. This is random quote 1215 of 1267. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] Re: /etc/rc.d/sshd : kldload random missing?
Daniel O'Connor wrote: On Tue, 19 Apr 2005 17:06, Daniel O'Connor wrote: On Tue, 19 Apr 2005 16:43, Rob wrote: Should I submit a patch here? Following patch works fine for me (be aware some lines are wrapped :[ ) I think a more correct solution would be to make a 'random' rc.d script which sshd depends on (and others if they're found to need it) Heh actually now that I look.. there IS a random script already.. Perhaps.. [inchoate 17:08] /etc/rc.d diff -u sshd.orig sshd --- sshd.orig Tue Apr 19 17:07:52 2005 +++ sshdTue Apr 19 17:07:59 2005 @@ -5,7 +5,7 @@ # # PROVIDE: sshd -# REQUIRE: LOGIN cleanvar +# REQUIRE: LOGIN cleanvar random . /etc/rc.subr Either I don't understand this, or it is not working properly. I am using 5-Stable, not Current, so the 'cleanvar' is not there. So in /etc/rc.d/sshd I have this line: # REQUIRE: LOGIN random I then do: /etc/rc.d/random stop /etc/rc.d/sshd stop /etc/rc.d/sshd start But the random script is not executed. I have added a echo statement in the random_start() function, but nothing is printed out. It seems that random is not started at all when sshd is started. Or do I misunderstand something here? Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] Re: /etc/rc.d/sshd : kldload random missing?
--- Daniel O'Connor [EMAIL PROTECTED] wrote: On Sun, 24 Apr 2005 16:16, Rob wrote: Either I don't understand this, or it is not working properly. I am using 5-Stable, not Current, so the 'cleanvar' is not there. So in /etc/rc.d/sshd I have this line: # REQUIRE: LOGIN random I then do: /etc/rc.d/random stop /etc/rc.d/sshd stop /etc/rc.d/sshd start But the random script is not executed. I have added a echo statement in the random_start() function, but nothing is printed out. It seems that random is not started at all when sshd is started. Or do I misunderstand something here? Try putting random_enable=YES in /etc/rc.conf. That gets it called here (although I already had random.ko loaded so I'm not 100% sure it worked) Oh? There's no such 'random_enable' entry in /etc/defaults/rc.conf on my 5.4-Stable system. Is this a Current only thing? Moreover, on my system, '/etc/rc.d/random rcvar' has no output at all. Adding an entry in /etc/rc.conf doesn't change that. Nevertheless, I have tried your advice, but to no avail. Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] Re: /etc/rc.d/sshd : kldload random missing?
--- Daniel O'Connor [EMAIL PROTECTED] wrote: On Sun, 24 Apr 2005 17:39, Rob wrote: Nevertheless, I have tried your advice, but to no avail. Hmm, try this diff it kldload's random if it's not present. It's not present on 5.4-Stable, so I have patched it. In /etc/rc.d/sshd I also have this: # REQUIRE: LOGIN random However, it still does not work. This is what I observe: 1. If random is not started, it will load the random module, if needed. So this part seems to work OK now. 2. If random module is not loaded and random has not yet started, then I get this: # /etc/rc.d/sshd start Starting sshd. PRNG is not seeded My conclusion is: sshd does simply not call random at all, although I have added it in the # REQUIRE: line. Is this a general bug in 5-Stable? Or am I testing this in the wrong way? Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ftpd PAM
On Thursday, April 21, 2005 5:48 PM, Ivan Voras unleashed the infinite monkeys and produced: in.ftpd: LOCAL: allow in.ftpd: ALL: deny ALL : ALL : allow I constructed the in.ftpd lines by looking at other examples and the man page, but it doesn't seem to work - I can login from another machine on the same network. ALl machines have proper (global) DNS entries so I don't think this should fall under the manual excerpt: LOCAL Matches any host whose name does not contain a dot character. Which will include any host in the same domain (or at least anything where you can do host fred and get an IP back. Try: in.ftpd: 127.0.0.1: allow in.ftpd: ALL: deny Instead -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: load 1, no process using 10% CPU...?
On Wednesday, April 20, 2005 2:20 AM, Damian Gerow unleashed the infinite monkeys and produced: Until the build failed. Now top /still/ isn't showing me much. systat -vm is showing me at just under 100% User, with little to no disk activity. I'm a little fuzzy as to /how/ load is calculated, but why would my system think that it's doing all kinds of work when ps, top, and systat can't really tell me /what/ it's doing? The load is the number of active processes (the number of processes in the run queue). That's all it measures - not CPU load, disk I/O or anything else - purely the number of processes in the run queue. Load and processor usage aren't linked. If the processes are I/O bound (for example) then while the system load may be high, the actual CPU usage may well be low. Google produced http://www.teamquest.com/resources/gunther/ldavg1.shtml, which isn't a bad description of the load average, though heavily based on Linux. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
