Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server
15.12.2011 17:36, Michael Larabel пишет: On 12/15/2011 07:25 AM, Stefan Esser wrote: Am 15.12.2011 11:10, schrieb Michael Larabel: No, the same hardware was used for each OS. In terms of the software, the stock software stack for each OS was used. Just curious: Why did you choose ZFS on FreeBSD, while UFS2 (with journaling enabled) should be an obvious choice since it is more similar in concept to ext4 and since that is what most FreeBSD users will use with FreeBSD? I was running some ZFS vs. UFS tests as well and this happened to have ZFS on when I was running some other tests. Can we look at the tests? My opinion is ZFS without tuning is much slower than UFS2. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Panic after upgrade 7.2 - 7.3
02.06.2010 01:56, Bjoern A. Zeeb пишет: On Tue, 1 Jun 2010, Sergey Matveychuk wrote: Hi. Just after upgrade from 7.2-p5 to 7.3-p1 I've got periodic panics on my router (after about a hour uptime). ... Any ideas? Are you using IPsec? No. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Panic after upgrade 7.2 - 7.3
Hi. Just after upgrade from 7.2-p5 to 7.3-p1 I've got periodic panics on my router (after about a hour uptime). Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 06 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x20:0xc05994ca stack pointer = 0x28:0xc4e49a00 frame pointer = 0x28:0xc4e49a2c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 27 (irq25: bge0) trap number = 12 panic: page fault cpuid = 2 Uptime: 1h5m37s Physical memory: 2039 MB Dumping 180 MB: 165 149bge0: watchdog timeout -- resetting Backtrace: #0 doadump () at pcpu.h:196 #1 0xc054829f in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0548564 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc070be40 in trap_fatal (frame=0xc4e499c0, eva=12) at /usr/src/sys/i386/i386/trap.c:950 #4 0xc070c090 in trap_pfault (frame=0xc4e499c0, usermode=0, eva=12) at /usr/src/sys/i386/i386/trap.c:863 #5 0xc070ca1a in trap (frame=0xc4e499c0) at /usr/src/sys/i386/i386/trap.c:541 #6 0xc06f153b in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #7 0xc05994ca in m_copym (m=0x0, off0=1500, len=1480, wait=1) at /usr/src/sys/kern/uipc_mbuf.c:539 #8 0xc0609430 in ip_fragment (ip=0xc57dc010, m_frag=0xc4e49afc, mtu=1500, if_hwassist_flags=7, sw_csum=3840) at /usr/src/sys/netinet/ip_output.c:731 #9 0xc060a0ec in ip_output (m=0xc57ab300, opt=0x0, ro=0xc4e49b34, flags=1, imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:570 #10 0xc0606fba in ip_forward (m=0xc57ab300, srcrt=0) at /usr/src/sys/netinet/ip_input.c:1366 #11 0xc0608533 in ip_input (m=0xc57ab300) at /usr/src/sys/netinet/ip_input.c:609 #12 0xc05e8fe9 in netisr_dispatch (num=2, m=0xc57ab300) at /usr/src/sys/net/netisr.c:185 #13 0xc05e34c9 in ether_demux (ifp=0xc517c000, m=0xc57ab300) at /usr/src/sys/net/if_ethersubr.c:834 #14 0xc05e389d in ether_input (ifp=0xc517c000, m=0xc57ab300) at /usr/src/sys/net/if_ethersubr.c:692 #15 0xc05e3428 in ether_demux (ifp=0xc5194c00, m=0xc57ab300) at /usr/src/sys/net/if_ethersubr.c:743 #16 0xc05e389d in ether_input (ifp=0xc5194c00, m=0xc57ab300) at /usr/src/sys/net/if_ethersubr.c:692 #17 0xc0478357 in bge_rxeof (sc=0xc5197000, rx_prod=295, holdlck=1) at /usr/src/sys/dev/bge/if_bge.c:3392 #18 0xc047a2db in bge_intr (xsc=0xc5197000) at /usr/src/sys/dev/bge/if_bge.c:3653 #19 0xc05265d8 in ithread_loop (arg=0xc518cbf0) at /usr/src/sys/kern/kern_intr.c:1181 #20 0xc0522eb1 in fork_exit (callout=0xc052643b ithread_loop, arg=0xc518cbf0, frame=0xc4e49d38) at /usr/src/sys/kern/kern_fork.c:811 FreeBSD xxx.xxx.xx 7.3-RELEASE-p1 FreeBSD 7.3-RELEASE-p1 #11: Thu May 27 18:10:35 MSD 2010 r...@xxx.xxx.xx:/usr/obj/usr/src/sys/ROUTER i386 Any ideas? -- Sem. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
pthread_mutex_lock crashed
Hello! I've tested MICO port (CORBA implementation) both on -stable and -current. I use lang/gcc33 port for -stable. On -stable all goes right, but on -current one example crashed in pthread_mutex_lock(). Here is gdb back tracing: #0 0x280830c9 in _atomic_lock () from /usr/lib/libc_r.so.5 #1 0x28083094 in _spinlock_debug () from /usr/lib/libc_r.so.5 #2 0x28088962 in _pthread_mutex_trylock () from /usr/lib/libc_r.so.5 #3 0x28088d12 in pthread_mutex_lock () from /usr/lib/libc_r.so.5 #4 0x282d5fcb in CORBA::ServerlessObject::_deref() () from /usr/local/lib/libmico2.3.11.so #5 0x282ceac6 in ObjVarCORBA::ContextList::release(CORBA::ContextList*) () from /usr/local/lib/libmico2.3.11.so ... etc. The port has been built with -lc_r on -current. Can you comment it? --- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with sysinstall
Richard Nyberg wrote: Doug White wrote: yes, this is a change to -current. It is for your own safety. I think this change in current is for the worse. I don't see why I can't manage slices and partitions from my regular OS, but have to boot up a CD to do the job. It's not even safer; I am perfectly capable of destroying my disk layout from the CD too. Agree. Why I can't change active slice? Or add a partition? Or repair my master boot record? It's absolutely safe. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with sysinstall
Doug White wrote: Missing operating system comes out of the DOS default bootblock, not the BIOS. Yes, I know. But I don't feel better then. Don't use chainloader with FreeBSD. Use 'kernel /boot/loader' instead. This is documented in the GRUB info doc. Again, I have set this exact system up with redhat on the first disk and it works perfectly. Grub do not supporting UFS2. So only way to boot -current is chainloader. This is normal and for your protection. you can't edit the disk you're running off of. If you are running off of ad1, make sure 1) you're root when you run sysinstall and b) you aren't mounting any filesystems from ad0. Well, I understand it for slices. But why I can't create new partition in exist slice and newfs it? It was OK in -stable. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with sysinstall
The first one: when I install -current on disk where WinXP on first slice, sysinstall brakes WinXP boot complete. I got 'Missing operation system' everytime. Even I've tried 'fixboot' and reinstall WinXP. Helps only 'dd if=/dev/zero of=/dev/ad0 count=100' and reinstall WinXP on clean disk. When I've installed first -current on first slice and second -current on second slice I got booting only first one. I use grub and either I set root(hd1,0) or root(hd1,1) (yes, it's a second disk) and 'chainloader +1' and 'boot' I've got always first -current boot. Looks like problem with boot sector where hardcoded booting from first slice (?). The second: when I've tried to save results from Fdisk or Label menu I've got the message: 'ERROR: Unable to write data to disk ad0!' Why? I can change slices and partitions only when I boot from CD-ROM. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Initial list of ports that fail due to -pthread
Kris Kennaway wrote: Here is a partial list of the ports that need to be taught to respect PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I [skipped] omniORB-4.0.2 PR/56862 is waiting for ports unfreezing. -- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: -current brake ufs for -stable
Bruce Evans wrote: -current doesn't write extended attributes unless you enabled them. OK. I'm wrong. Really I don't understand a problem. Superblock was corrupted. I've fix it with fsck (from other sector). But I decided remake the FS and run newfs from -stable again. Now I write on it buth -stable and -current and no problems have now. May be it was an accident. Most likely the problem is some breakage of compatibility of superblocks. When I tried sharing a filesystem between RELENG_3 and -current a few months ago, IIRC the obvious bugs were that RELENG_3 crashed on filesystems written to be -current, and running RELENG_3's fdisk fixed the problem but was not run automatically and it reported an alarming number of errors. Just the same happened. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
-current brake ufs for -stable
Hello! I've installed both -current and -stable on my box. One of partition I plan to share betwen them (place ports/distfiles there). I newfs'ed it from -stable and wrote on it from -current. When I booted with -stable I've found the partition FS was broken. I think it's because of extended atributes -current wrote on it. I don't like to turn off extended attributes on -current at all. I'd like to have some option for mount to disable it (I've not found it on manpage). How can I use the partition this way now? Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc 3.3.1
Alexander Kabaev wrote: On Sat, 12 Jul 2003 06:08:57 +0400 Sergey Matveychuk [EMAIL PROTECTED] wrote: Don't forget bump __FreeBSD_version. :) What for? Bumped __FreeBSD_cc_version is enough. The ports system use it. How can we check is gcc changed? !defined(OSVERSION) .if exists(/sbin/sysctl) OSVERSION!= /sbin/sysctl -n kern.osreldate ... May be I'm wrong? Correct me. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
gcc 3.3.1
Don't forget bump __FreeBSD_version. :) Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1 and nawk
Tonight I'v installed a devel/newfile. When it's build it run nawk. In that time my computer was a very slow reaction without disk operation. When I'v runned top command I'v seen: -- last pid: 38039; load averages: 1.58, 1.80, 1.73up 0+01:21:08 05:22:28 53 processes: 3 running, 50 sleeping CPU states: 98.2% user, 0.0% nice, 1.3% system, 0.5% interrupt, 0.0% idle Mem: 27M Active, 52M Inact, 25M Wired, 6820K Cache, 22M Buf, 13M Free Swap: 237M Total, 160M Used, 77M Free, 67% Inuse PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 38037 root 1240 1456K 788K RUN 4:17 1874.03% 1185.45% nawk -- 1874% CPU load? What's that? --- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Flushing CD-ROM?
Why 5.1 flush acd0 on shutdown? - syncing disk, buffers remaining... done Uptime ... acd0: timeout waiting for cmd=e7 s=01 e=04 acd0: flushing device failed The operating system has halted. - Well, it's cd-writer really, but there is no disk there any way. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
slow console input
Hello! When I'v upgraded from 4.x to 5.x and I'v noticed more slow console input. Will it be so? Or can I faster it? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI
That's saying the acpi.ko module was not built and installed. When you install your new kernel, use the Makefile target, instead of using cp, or it won't install the modules it builds. If you did this, then check your make.conf to see if you are specifically telling it to not build modules, or only telling it to build specific modules, etc.. I build modules with buildworld and install it with installworld. No cp. All modules installed well. I'll check acpi.ko. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI
MODULES_WITH_WORLD causes modules to be installed during installworld. But when you later do installkernel, it renames /boot/kernel to /boot/kernel.old, so all your modules end up there. Don't use MODULES_WITH_WORLD, or use ``make reinstallkernel'' which is safe for MODULES_WITH_WORLD environment. I see it now. Thanks. I'v fixed it just going into /sys/modules/acpi and making install. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI
I'v cvsup'ed from 5.0-RELEASE to RELENG_5_0_0 last night and ACPI doesn't work now. When booting I'v got a message: ACPI autoload failed - no such file or directory. How to fix? Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
