Re: FreeBSD 7.0 + Xen 3.1 + HVM: Success!
Kip, Does the problem with Xen 3.1 in HVM/Intel manifest as those BTX halted errors (e.g. http://lists.xensource.com/archives/html/xen-users/2006-10/msg00014.html) ? If so, do you happen to know whether this problem has been solved in Xen 3.2 or 3.2.1? This message of yours was written this March, so I'm assuming that 3.2.1 will contain this fix? Can anybody confirm this? I'm having a hard time finding an RPM for CentOS 5.2/Xen 3.2.1 right now... I know this isn't a CentOS list, but I'm just wondering if anybody has been able to boot FBSD 7.0/HVM/Intel 64 bit? I'd just like to observe that due to bugs in their real-mode emulation (only required on intel) FreeBSD won't run on Xen 3.1 in HVM on Intel processors. This longstanding issue was finally fixed very recently in the 3.2 branch. -Kip On Fri, Feb 29, 2008 at 3:34 PM, Freddie Cash [EMAIL PROTECTED] wrote: Just thought I'd pass along that I have successfully installed FreeBSD 7.0 into a Xen 3.1 HVM. This one went as smooth as I expected, considering my experience with 6.3. Haven't done any benchmarking or stress testing or port installs or anything. But so far it's working nicely. Here's all the info. If you'd like to see anything else, let me know. Host hardware: Tyan h2000M motherboard 2x AMD Opteron 2200-series CPUs (dual-core) 8 GB ECC DDR2-800 SDRAM 3Ware Escalade 9650SX-12ML PCIe RAID controller 12x 400 GB SATA harddrives in RAID6 with 1 hot spare (4 TB) Host software: Ubuntu Server 7.10 64-bit version Linux kernel 2.6.22 Xen 3.1 LVM partitions for all the virtual machines Xen config file: # Enable hardware virtualisation using HVM kernel = '/usr/lib/xen-ioemu-3.1/boot/hvmloader' device_model = '/usr/lib/xen-ioemu-3.1/bin/qemu-dm' builder = 'hvm' # VM/domain name name = 'freebsd70' # Memory and CPU settings vcpus = '1' memory = '1024' # Disk settings disk = [ 'phy:/dev/xenvol0/freebsd70,ioemu:hda,w', 'file:/home/fcash/freebsd-7.0-i386-cd1.iso,hdc:cdrom,r' ] boot = 'c' # Network settings hostname = 'fbsdvm2.sd73.bc.ca' vif = [ 'type=ioemu, bridge=xenbr3, mac=00:16:3e:00:00:03' ] dhcp = '1' # Graphics settings sdl = '0' vnc = '1' vncviewer = '1' # Other settings pae = '0' # Whether to enable PAE for 32-bit VMs acpi = '0' # Whether to enable ACPI for guests localtime = '1' # Whether system clock is set to local time or UTC # Start/stop settings on_poweroff = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' FreeBSD 7.0 dmesg: Copyright (c) 1992-2008 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 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2220 (2793.13-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x40f13 Stepping = 3 Features=0x789fbbfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x2001SSE3,CX16 AMD Features=0x28400800SYSCALL,MMX+,RDTSCP,LM AMD Features2=0x19LAHF,ExtAPIC,CR8 real memory = 1073717248 (1023 MB) avail memory = 1037139968 (989 MB) MPTable: _HVMCPU_ XEN ioapic0: Changing APIC ID to 1 ioapic0: Assuming intbase of 0 ioapic0 Version 1.1 irqs 0-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 6 Entries on motherboard pci0: PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 WDMA2 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] vgapci0: VGA-compatible display mem 0xf000-0xf1ff,0xf200-0xf2000fff at device 2.0 on pci0 pci0: unknown at device 3.0 (no driver attached) re0: RealTek 8139C+ 10/100BaseTX port 0xc200-0xc2ff mem 0xf400-0xf4ff irq 5 at device 4.0 on pci0 miibus0: MII bus on re0 rlphy0: RealTek internal media interface PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:16:3e:00:00:03 re0: [FILTER] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xc-0xc7fff pnpid ORM on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1
Syncing or maybe update issue
Hello, I have a box which can't sync using cvsup, therefore, I thought of using cvs by invoking the following command in the directory /usr/src/cvs/ # cvs -d [EMAIL PROTECTED]:/home/ncvs co src I do get all the updates and it seems to be checking out successfully, however, when I try to # make -j4 buildword I get the following error about elf.h not being found! -- stage 1.2: bootstrap tools -- cd /usr/cvs/src; MAKEOBJDIRPREFIX=/usr/obj/usr/cvs/src/tmp INSTALL=sh /usr/cvs/src/tools/install.sh PATH=/usr/obj/usr/cvs/src/tmp/legacy/usr/sbin:/usr/obj/usr/cvs/src/tmp/legacy/usr/bin:/usr/obj/usr/cvs/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/cvs/src/tmp VERSION=FreeBSD 6.2-RELEASE i386 602000 MAKEFLAGS=-m /usr/cvs/src/tools/build/mk -j 4 -m /usr/cvs/src/share/mk make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=602000 -DWITHOUT_SSP -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_NLS -DNO_PIC -DWITHOUT_PROFILE -DNO_SHARED -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF bootstrap-tools === cddl/usr.bin/sgsmsg (obj,depend,all,install) /usr/obj/usr/cvs/src/tmp/usr/cvs/src/cddl/usr.bin/sgsmsg created for /usr/cvs/src/cddl/usr.bin/sgsmsg rm -f .depend mkdep -f .depend -a -I/usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/compat/opensolaris -I/usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/compat/opensolaris/include -I/usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include -I/usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/obj/usr/cvs/src/tmp/legacy/usr/include /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/contrib/opensolaris/common/avl/avl.c /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/sgsmsg.c /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/findprime.c In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/sgsmsg.c:81: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:57:20: libelf.h: No such file or directory In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/alist.h:45, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:59, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/sgsmsg.c:81: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/compat/opensolaris/sys/elf.h:30:26: sys/elf.h: No such file or directory In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:31: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:57:20: libelf.h: No such file or directory In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/alist.h:45, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:59, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:31: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/compat/opensolaris/sys/elf.h:30:26: sys/elf.h: No such file or directory In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/findprime.c:30: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:57:20: libelf.h: No such file or directory In file included from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/alist.h:45, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/include/sgs.h:59, from /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/findprime.c:30: /usr/cvs/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/compat/opensolaris/sys/elf.h:30:26: sys/elf.h: No such file or directory mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tracking -stable in the enterprise
Andy Kosela wrote: On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: I think we still have FreeBSD-3.x machines in production. I know we have FreeBSD-4.3. 99.9% of security issues don't affect us. We have our own package system built on top of FreeBSD's pkg_add format and have the ability to push packages to machines. If circumstances warrant it, we can push a fix for something. It'll either push a new binary or be a source patch that is compiled directly on the machines in question. The machines run a custom software stack. More often we push fixes for driver or performance fixes or things like timezone updates. Ports infrastructure do not support such old FreeBSD versions, so how do you deal with that? Do you maintain your own CVS branches of selected packages and backports necessary security patches? I guess it demands considerable effort to compile the latest apache on FreeBSD 3.x or 4.x. It would be easy to maintain 4.x compatibility in Yahoo's package system. They probably only need a relatively small number of ports, and there is no need to stay in sync with changes to the ports infrastructure. Those changes are almost all completely gratuitous from the point of view of deploying packages within a site since they are changes to the *ports* infrastructure. The FreeBSD *package* infrastructure has changed almost not at all over time (but yahoo have their own package system anyway). To the extent that the vendor applications still support old versions, the model would be the same: vendor source + patches -- binary. You can do that with a system based on the ports collection from last century if you like :) I would guess that Yahoo actually forked the ports system long ago (in the 2.x days?) or never used it directly, and either port their changes directly or by taking patches from freebsd ports. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Syncing or maybe update issue
On Mon, Jun 30, 2008 at 01:09:25PM +0300, Yousef Raffah wrote: Hello, I have a box which can't sync using cvsup, therefore, ... Let's start here. Why not? What happens? Have you used -L2? Also, if you're using 6.2 or later, you should be able to use csup (comes with the base system) and not cvsup. I thought of using cvs by invoking the following command in the directory /usr/src/cvs/ # cvs -d [EMAIL PROTECTED]:/home/ncvs co src I do get all the updates and it seems to be checking out successfully, however, when I try to # make -j4 buildword I get the following error about elf.h not being found! This looks like you're checking out HEAD/-CURRENT. Is this really what you want to be doing? Probably not, based on the fact you mailed freebsd-stable and not freebsd-current. Please take the time to read this in full. http://www.freebsd.org/doc/en/books/handbook/anoncvs.html -- | 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: tracking -stable in the enterprise
On Mon, Jun 30, 2008 at 12:26:05PM +0200, Kris Kennaway wrote:
It would be easy to maintain 4.x compatibility in Yahoo's package
system. They probably only need a relatively small number of ports, and
there is no need to stay in sync with changes to the ports
infrastructure. Those changes are almost all completely gratuitous from
the point of view of deploying packages within a site since they are
changes to the *ports* infrastructure. The FreeBSD *package*
infrastructure has changed almost not at all over time (but yahoo have
their own package system anyway).
To the extent that the vendor applications still support old versions,
the model would be the same: vendor source + patches -- binary. You
can do that with a system based on the ports collection from last
century if you like :)
I would guess that Yahoo actually forked the ports system long ago (in
the 2.x days?) or never used it directly, and either port their changes
directly or by taking patches from freebsd ports.
It's pretty easy to use current ports system with RELENG_4,
I do this sometimes. Just have following lines in /etc/make.conf:
# 4.x stuff
PTHREAD_CFLAGS= -D_THREAD_SAFE
PTHREAD_LIBS= -pthread
# may be, ln -s /usr/local/etc/rc.d/rc.subr /etc/rc.subr too
RC_SUBR=${LOCALBASE}/etc/rc.subr
# only if we force port to use base system's port 5.005
PERL_VERSION= 5.00503
PERL_VER= 5.005
PERL_ARCH= ${ARCH}-freebsd
PERL5= ${DESTDIR}/usr/bin/perl${PERL_VERSION}
PERL= ${DESTDIR}/usr/bin/perl
Then, for perl, one needs small patch to bsd.ports.mk:
--- bsd.port.mk.origWed Oct 17 18:12:24 2007
+++ bsd.port.mk Sun Feb 24 00:33:48 2008
@@ -1420,8 +1420,8 @@
SITE_PERL_REL?=lib/perl5/site_perl/${PERL_VER}
SITE_PERL?=${LOCALBASE}/${SITE_PERL_REL}
-PERL5= ${LOCALBASE}/bin/perl${PERL_VERSION}
-PERL= ${LOCALBASE}/bin/perl
+PERL5?=${LOCALBASE}/bin/perl${PERL_VERSION}
+PERL?= ${LOCALBASE}/bin/perl
.endif # !defined(_PERL_REFACTORING_COMPLETE)
This way, I continue to update small standalone mail servers
with new versions of security/clamav (those consoleless 4.11 boxes
have no hope to be upgraded to something newer).
Sometimes there is a need to patch port's Makefile a little,
f.e. when if redefines PTHREAD_LIBS unconditionally (bad, bad habit).
Eugene Grosbein
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Marvell Yukon 88E8062 - media selection problem
Hi, I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected: ifconfig msk0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=11aTXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4 ether 00:10:f3:0d:d6:45 media: Ethernet autoselect (none) status: no carrier msk1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=11aTXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4 ether 00:10:f3:0d:d6:46 media: Ethernet autoselect (none) status: no carrier I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting). # ifconfig msk0 media 1000baseSX ifconfig: SIOCSIFMEDIA (media): Device not configured I'm puzzled here: are there known limitations in the driver wrt support of certain media types? Here is pciconf -lv information if it helps... [EMAIL PROTECTED]:3:0:0: class=0x02 card=0x628211ab chip=0x434711ab rev=0x14 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'Yukon 88E8062 PCI-E IPMI Gigabit Ethernet Controller' class = network subclass = ethernet This is on 7.0-RELEASE on amd64. I also tried kernel from 7-STABLE from few days ago, but the problem was still present. -- Best regards, Krzysztof Jedruczyk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb)
Niki Denev wrote: On Fri, Jun 27, 2008 at 11:37 PM, Stephen Clark [EMAIL PROTECTED] wrote: Hi, I am trying to compile it on 6.2 and get make: don't know how to make cryptodev_if.h. Stop ??? where is this file? Thanks, Steve Have you applied the 6.2 patch included in the latest tgz that Patrick posted? Regards, Niki Uh.. no -wasn't sure what to apply it to - now that I look at it a bit closer I SEE! Thanks, and sorry for the noise. Steve -- They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety. (Ben Franklin) The course of history shows that as a government grows, liberty decreases. (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Syncing or maybe update issue
On Mon, Jun 30, 2008 at 2:03 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Mon, Jun 30, 2008 at 01:09:25PM +0300, Yousef Raffah wrote: Hello, I have a box which can't sync using cvsup, therefore, ... Let's start here. Why not? What happens? Have you used -L2? Also, if you're using 6.2 or later, you should be able to use csup (comes with the base system) and not cvsup. I thought of using cvs by invoking the following command in the directory /usr/src/cvs/ # cvs -d [EMAIL PROTECTED]:/home/ncvs co src I do get all the updates and it seems to be checking out successfully, however, when I try to # make -j4 buildword I get the following error about elf.h not being found! This looks like you're checking out HEAD/-CURRENT. Is this really what you want to be doing? Probably not, based on the fact you mailed freebsd-stable and not freebsd-current. I guess you nailed it, I couldn't understand how to specify that using the command I used earlier. Anyhow, I'm checking it with the -r RELENG_7_0_0_RELEASE and will report back how things go. Thanks for your guidance. Please take the time to read this in full. http://www.freebsd.org/doc/en/books/handbook/anoncvs.html I did, but I didn't go through it in detail, I just skimmed it (bad behaviour) :) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-stable Digest, Vol 258, Issue 5
On Fri, Jun 27, 2008 at 8:00 AM, [EMAIL PROTECTED] wrote: Message: 5 Date: Thu, 26 Jun 2008 12:54:41 -0700 From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: Problem with /boot/loader To: Kelly Black [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org, [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii On Thu, Jun 26, 2008 at 02:34:44PM -0400, Kelly Black wrote: On Wed, Jun 25, 2008 at 7:38 AM, Kelly Black [EMAIL PROTECTED] wrote: I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: [snip] Now when I reboot there is a problem. I get an error that the system cannot boot. Part of it looks like this: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: If I boot from a live disk and replace /boot/loader with /boot/loader.old it boots up fine and everything looks good. A new world and a new kernel. I would be grateful for any help or any pointers. What do you have in /etc/make.conf? I recall there being a point in time where incorrect CFLAGS options could build a broken loader. Try renaming /etc/make.conf (or just commenting out all CFLAGS/CXXFLAGS options) and rebuilding either just the loader or the whole world, and see if that makes a difference. Hello, Thank you for the reply. I put my make.conf file back to its default when I first did the upgrade to avoid other kinds of problems: make.conf # added by use.perl 2008-04-07 11:54:35 PERL_VER=5.8.8 PERL_VERSION=5.8.8 And it still produced the loader that does not load. Kelly, A couple things: I'm wondering if you're getting bit by changes made to loader(8) by John Baldwin last year. Those changes were positive and increased compatibility with systems greatly, but there were a couple reports of users whose systems preferred the old method used. Those changes are documented here; and yes, I realise you don't get a screen full of continual register dumps, but different people saw different behaviour: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Also see these mailing list threads: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078755.html http://lists.freebsd.org/pipermail/freebsd-stable/2007-November/038214.html Secondly, you said you migrated from 6_rel to 7_rel. Do you mean 7.0-RELEASE, or are you referring to the RELENG_7 tag? What tag are you following when doing csup/cvsup? CC'ing John as well. -- | 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 | Hello, Sorry for the delay in reporting back. I have the following line in my cvsup,.conf file: *default release=cvs tag=RELENG_7 I have a copy of my cvsup conf file at http://blackk.union.edu/~black/freebsd/raging/cvsup.conf I had a /boot.conf file that contained -D I deleted the file and tried to boot with the new /boot/loader with no luck. When I copied the old /boot/loader it came up fine. The system is i386. I have a copy of my kernel config file at http://blackk.union.edu/~black/freebsd/raging/BLACK I tried to do dmesg and make it available, but it gives me this message: calcru: runtime went backwards from 331 usec to 327 usec for pid 0 (swapper) Sincerely, Kel -- ___ Kelly Black Phone: (518) 388-8727 Department of Mathematics FAX: (603) 388-6005 Union College e-mail: [EMAIL PROTECTED] Schenectady NY 12308 (USA) WWW: http://blackk.union.edu/~black ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tracking -stable in the enterprise
On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: No. Why on earth would we do that? if we wanted to cause ourselves that much pain for no good reason, we'd go get a pencil and stab ourselves in the eye. We don't upgrade machines that have been deployed unless there is a good reason to. This makes sense. But for personal curiosity sake, what if Yahoo needed to stick with supported FreeBSD releases? How would you deal with updating that many machines every 12 months? Would that be possible in your business? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.3 deadlock (vm_map?) with DDB output
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers running this hardware deadlock about once per week.
Try this change:
snip
We use it at work on 6.x. W/o this fix, round-robin stops working on 4BSD
when softclock() (swi4: clock) blocks on a lock like Giant.
Just wanted to confirm: That patch did the trick. All the SMP machines
that had this problem have been stable for 11 days now, longer than any
of them were up previously.
I changed the patch slightly to work with FreeBSD 6.3-RELEASE. That's
attached, in case anyone needs this later.
Cheers,
Stef
--- sys/kern/sched_4bsd.c.orig 2006-06-16 22:11:55.0 +
+++ sys/kern/sched_4bsd.c 2008-06-18 17:04:34.0 +
@@ -157,13 +157,10 @@
static int sched_quantum; /* Roundrobin scheduling quantum in ticks. */
#define SCHED_QUANTUM (hz / 10) /* Default sched quantum */
-static struct callout roundrobin_callout;
-
static void slot_fill(struct ksegrp *kg);
static struct kse *sched_choose(void); /* XXX Should be thread * */
static void setup_runqs(void);
-static void roundrobin(void *arg);
static void schedcpu(void);
static void schedcpu_thread(void);
static void sched_priority(struct thread *td, u_char prio);
@@ -316,27 +313,6 @@
}
/*
- * Force switch among equal priority processes every 100ms.
- * We don't actually need to force a context switch of the current process.
- * The act of firing the event triggers a context switch to softclock() and
- * then switching back out again which is equivalent to a preemption, thus
- * no further work is needed on the local CPU.
- */
-/* ARGSUSED */
-static void
-roundrobin(void *arg)
-{
-
-#ifdef SMP
- mtx_lock_spin(sched_lock);
- forward_roundrobin();
- mtx_unlock_spin(sched_lock);
-#endif
-
- callout_reset(roundrobin_callout, sched_quantum, roundrobin, NULL);
-}
-
-/*
* Constants for digital decay and forget:
* 90% of (kg_estcpu) usage in 5 * loadav time
* 95% of (ke_pctcpu) usage in 60 seconds (load insensitive)
@@ -618,11 +594,6 @@
sched_quantum = SCHED_QUANTUM;
hogticks = 2 * sched_quantum;
- callout_init(roundrobin_callout, CALLOUT_MPSAFE);
-
- /* Kick off timeout driven events by calling first time. */
- roundrobin(NULL);
-
/* Account for thread0. */
sched_load_add();
}
@@ -697,6 +668,14 @@
resetpriority(kg);
resetpriority_thread(td, kg);
}
+
+ /*
+ * Force a context switch if the current thread has used up a full
+ * quantum (default quantum is 100ms).
+ */
+ if (!((td)-td_flags TDF_IDLETD)
+ ticks - PCPU_GET(switchticks) = sched_quantum)
+ td-td_flags |= TDF_NEEDRESCHED;
}
/*
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
new wiki page to collect information about the ATA subsystem
Jeremy Chadwick (koitsu@) has been gathering together information on the wiki about commonly seen problems with FreeBSD: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting Based on a discussion on #freebsd-bugbusters, I've gone ahead and added a signup page for people that are interested in volunteering to do ATA regression testing (either for patches that are included in the various PRs, or for isolating regressions that have already happened): http://wiki.freebsd.org/ATA/ATA_Volunteers Please feel free to sign up if you're interested in helping on this. Perhaps it will lead to something. There is also a new meta-page to cross-reference the above: http://wiki.freebsd.org/ATA mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell Yukon 88E8062 - media selection problem
On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote: Hi, I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected: ifconfig msk0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=11aTXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4 ether 00:10:f3:0d:d6:45 media: Ethernet autoselect (none) status: no carrier msk1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=11aTXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4 ether 00:10:f3:0d:d6:46 media: Ethernet autoselect (none) status: no carrier I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting). # ifconfig msk0 media 1000baseSX ifconfig: SIOCSIFMEDIA (media): Device not configured I'm puzzled here: are there known limitations in the driver wrt support of certain media types? Here is pciconf -lv information if it helps... [EMAIL PROTECTED]:3:0:0: class=0x02 card=0x628211ab chip=0x434711ab rev=0x14 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'Yukon 88E8062 PCI-E IPMI Gigabit Ethernet Controller' class = network subclass = ethernet This is on 7.0-RELEASE on amd64. I also tried kernel from 7-STABLE from few days ago, but the problem was still present. The 88E8062 support wasn't tested due to lack of hardware and I just copied the device id from myk driver. Would you show me the output of devinfo -rv| grep oui ? Also it would be better if I can see verbosed boot message. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
