Re: php56

> I have a mission critical app server running an old PHP 5.6 > application which will not work on PHP 7+. wordpress 5.x and nfsen are dying on the php 7.x hill here randy ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/lis

php

the large ports update seems to have broken a lot of things which use php-72 (yes, it serves them right:), e.g. wordpress 5, nfsen, ... randy, waiting patiently for someone to clean this one up ___ freebsd-stable@freebsd.org mailing list https://lists.fr

Re: bad hash in repo

this problem seems to have magically cleared up, he said suspiciously randy ___ 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: bad hash in repo

> Is there any possibility there’s something between these you and these > update hosts? it is the internet; anything is possible :) but the hosts having the problem are on the nekkid global interner. > > This thread has some interesting info i need to tcpdump. i'll try to do so in a day or th

Re: bad hash in repo

someone asked if the failures were limited to update5.freebsd.org today's batch were both 4 and 5 randy ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stabl

Re: bad hash in repo

>>> # pkg update -f >>> Updating FreeBSD repository catalogue... >>> Fetching meta.txz: 100%944 B 0.9kB/s00:01 >>> Fetching packagesite.txz: 100%6 MiB 2.2MB/s00:03 >>> Processing entries: 100% >>> FreeBSD repository update completed. 32029 packages processed. >>> All rep

Re: bad hash in repo

seeing a lot of these Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. >

Re: drm / drm2 removal in 12

> I'll just post this again to try and keep the focus on the issue at hand. plonk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.o

Re: bad hash in repo

>>> seeing a lot of these >>> >>> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >>> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... >>> done. >>> Fetching metadata index... done. >>> Inspecting system... done. >>> Preparing to download files... done. >>> Fetch

Re: bad hash in repo

> seeing a lot of these > > Looking up update.FreeBSD.org mirrors... 2 mirrors found. > Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. > Fetching 2 patches.. done.

Re: bad hash in repo

> Looking up update.FreeBSD.org >> Applying patches... done. >> Fetching 2 files... >> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has >> incorrect hash. > Do you have a transparent proxy in your network or at your ISP raw nekkid global ip space, aka the internet :) randy ___

bad hash in repo

seeing a lot of these Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. Fetching 2 patches.. done. Applying patche

Re: zfs boot size

> We always put swap directly after it so if a resize is needed its easy > without and resilvering . i am an idiot raid0.dfw.rg.net:/root# gpart backup da0 GPT 128 1 freebsd-boot 34128 2 freebsd-swap162 33554432 3freebsd-zfs 33554594 3873308477 so somet

zfs boot size

so the number of blocks one must reserve for zfs boot has gone from 34 to 40. is one supposed to, one at a time, drop each disk out of the pool, repartition, re-add, and resilver? luckily, there are only 16 drives, and resilvering a drive only takes a couple of days. so we might be done with it

Re: freebsd-update: cannot open patchlist

>> # freebsd-update upgrade -r 11.1-RELEASE > > Does it still happen when you run > rm -rf /var/db/freebsd-update/* > freebsd-update -r 11.1-RELEASE upgrade indeed, that fixes it. thank you. randy ___ freebsd-stable@freebsd.org mailing list https://li

Re: freebsd-update: cannot open patchlist

>> # freebsd-update upgrade -r 11.1-RELEASEa > > you probably noticed the moment you hit the send button, but in case > you didn't: Try to update to 11.1-RELEASE instead of 11.1-RELEASEa typo after paste # history | grep upgrade 53 freebsd-update upgrade -r 11.1-RELEASE 58 history | grep

freebsd-update: cannot open patchlist

# uname -a FreeBSD rip.psg.com 10.3-RELEASE-p24 FreeBSD 10.3-RELEASE-p24 #0: Wed Nov 15 04:57:40 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # freebsd-update upgrade -r 11.1-RELEASEa ... .3090030910309203093030940309503096030970

Re: freebsd-update

the problems were o op error trying to binary on stable not release o freebsf-update fetch should not be dns case sensitive no matter what o the libipx.so.4/5 lack of update in 10-release.p13 i am sure there are other problems including yours. it's getting sloppy. randy ___

freebsd-update

Basic symptom: # /usr/sbin/freebsd-update fetch Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.3-STABLE from update.FreeBSD.org... failed. No mirrors remaining, giving up. Trace: # sh -x /usr/sbin/freebsd-update fetch ... + e

Re: Jenkins build is still unstable: FreeBSD_stable_10 #358

jenkins-ad...@freebsd.org wrote: > > See > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-s

Re: leapsecond file

> But I see what you do on 10.3-RELEASE. Looks like the update has not > made it into 10 (an I would guess 9). i will be patient. probably wait for 11.1. thanks. randy ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/list

Re: leapsecond file

>> Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file >> ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago >> >> # grep ntp /etc/periodic.conf.local >> # 480.leapfile-ntpd >> daily_ntpd_leapfile_enable="YES" >> daily_ntpd_avoid_congestion="NO" > > For whatever reason, /etc/periodi

leapsecond file

i get these on all fbsd 10.3 hosts Aug 7 04:13:06 cache0 ntpd[576]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired less than 68 days ago i have # grep ntp /etc/periodic.conf.local # 480.leapfile-ntpd daily_ntpd_leapfile_enable="YES" daily_ntpd_avoid_congestion="NO" consulting th

Re: ssh install with freebsd-update

> uname -KU > > I am guessing your kernel is new, and your userland is old, as Xin Li said # uname -KU 1001000 1001000 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to

Re: ssh install with freebsd-update

> My guess is that there was some fetched 'freebsd-update' upgrade data > that was not applied, and the freebsd-update install have somehow > confused by that. any idea on how i can make it fresh? our suspicion is that we caught the frebsd-update repo on a bad day and poisoned all the systems. >

Re: ssh install with freebsd-update

>> # uname -a FreeBSD foux.psg.com 10.1-RELEASE-p10 FreeBSD >> 10.1-RELEASE-p10 #0: Tue May 12 19:33:13 UTC 2015 >> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >> i386 >> >> it's really p11 now >> >> if i run freebsd-update install of p11. all looks well until the >> reboot,

ssh install with freebsd-update

# uname -a FreeBSD foux.psg.com 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Tue May 12 19:33:13 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 it's really p11 now if i run freebsd-update install of p11. all looks well until the reboot, when i get Perf

Re: freebsd-update mergemaster options

> I am getting hundreds of files with "conflicts" like: > <<< current version > # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.4.1 2010/06/14 02:09:06 kensmith Exp > $ > === > # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.8.1 2012/03/03 06:15:13 kensmith Exp > $ > >>> 8.3-RELEASE mergemaster to

Re: buildworld on geode blowing chunks in lib/clang/libllvmcore

WITHOUT_CLANG=yes c++ -O2 -pipe -DIPFIREWALL_NAT -march=pentium -I/usr/src/lib/clang/libllvmcore/ ../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/ llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/ lib/VMCore -I. -I/usr/src/lib/clang/l

Re: buildworld on geode blowing chunks in lib/clang/libllvmcore

>> c++: Internal error: Killed: 9 (program cc1plus) >> Please submit a full bug report. >> See http://gcc.gnu.org/bugs.html> for instructions. >> *** [Function.o] Error code 1 >> >> Stop in /usr/src/lib/clang/libllvmcore. >> *** [all] Error code 1 >> >> clues? is it buildtools? i started one, but

buildworld on geode blowing chunks in lib/clang/libllvmcore

FreeBSD soek0.psg.com 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0: Wed Oct 17 19:07:49 UTC 2012 r...@soek0.psg.com:/usr/obj/usr/src/sys/SOEK0 i386 running a pretty stripped kernel as it is just an 8G flash, http://archive.psg.com/SOEK0 c++ -DIPFIREWALL_NAT -O -march=pentium -I/usr/src/lib/cl

Re: atkbd attach excitement during boot

> on 01/10/2012 17:56 Randy Bush said the following: >>> Humm. It seems this wasn't the actual faulting instruction. Can you do >>> 'l *0x80704740'? >> >> (gdb) l *0x80704740 >> 0x80704740 is in sckbdevent (/usr/src

Re: atkbd attach excitement during boot

> Humm. It seems this wasn't the actual faulting instruction. Can you do > 'l *0x80704740'? (gdb) l *0x80704740 0x80704740 is in sckbdevent (/usr/src/sys/dev/syscons/syscons.c:743). 738 * the Xaccel-2.1 keyboard hang, but it can't hurt. XXX 739 *

Re: atkbd attach excitement during boot

>> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0x38 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0x80704740 >> stack pointer = 0x28:0x815336e0 >> frame point

atkbd attach excitement during boot

booting FreeBSD fbsd64.psg.com 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r241020: Fri Sep 28 07:14:15 UTC 2012 r...@kaos.glenbarber.us:/usr/obj/usr/src/sys/GENERIC amd64 if i do not type a key during boot (after typing to beastie), i get the following Fatal trap 12: page fault while in k

Re: FreeBSD and IPMI how-to (was Re: su problem)

i want two things from ipmi, reset and kva console. freebsd ipmitool gives me the first, and i already had an apc controlled power bar. randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubsc

Re: clang tautology

> Mark Linimon is monitoring the status of ports and clang at > http://blog.vx.sk/archives/25-FreeBSD-Compiler-Benchmark-gcc-base-vs-gcc-ports-vs-clang.html > Which might save you some work. looks like benchmarks, not status of compilability/runability randy _

Re: clang tautology

>> is the clang build for releng_9 for amd64 in good enough shape that i >> can simply >> csup >> hack make.conf >> make buildworld >> make kernel >> boot single >> make installworld >> mergemaster -cviFU >> reboot this did work. i am now doing a portupgrade to see if i can break

Re: clang tautology

and if i try to follow http://wiki.freebsd.org/BuildingFreeBSDWithClang i do not see where the clang world and kernel are actually made the normal bootable. is the clang build for releng_9 for amd64 in good enough shape that i can simply csup hack make.conf make buildworld make kernel bo

Re: clang tautology

and, for a bonus, clang buildworld ... /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:196:14: note: use '=' to turn this equality comparison into an assignment (ix86_tune)) == ( ^~ = randy ___ fre

Re: clang tautology

> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:4249:29: > warning: self-comparison always evaluates to false [-Wtautological-compare] > && (TARGET_64BIT || DImode != DImode)) >^ > 12 warnings generated. apologies. releng

clang tautology

trying a clang buildworld and get a bunch of /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md:4249:29: warning: self-comparison always evaluates to false [-Wtautological-compare] && (TARGET_64BIT || DImode != DImode)) ^ 12 war

Re: 9-stable from i386 to amd64

> These statements are false, esp. worrying is that they are > interwinned with some facts that get tilted to support false presumption. > > Kernel do not care about which interpreter is /libexec/ld-elf.so. > The path to the interpreter is specified in the binary itself. So if you > have 32bit bin

Re: 9-stable from i386 to amd64

> The cleanest upgrade path is to prepare your 32-bit root to be bootable by > both 32- and 64-bit kernels: copy the ld-elf32.so that was built during your > buildworld over to /libexec/ld-elf32.so, and also make copies of > /lib and /usr/lib to /lib32 and /usr/lib32 respectively. That way when yo

Re: 9-stable from i386 to amd64

> heh? An i386 world should run (almost) fine on an amd64 kernel. I > know people who have done that update (but I know of no one done it > headless). i am not sure i want to be the first :) > PS: do you happen to know why the amd64 kernel did hang on boot? nope. dmesg -a did not help on rese

9-stable from i386 to amd64

is there a recipe for moving from i386 to amd64? on a very remote system, i made the migration from 7.4 to 8.2 to 9.0, all 32-bit. it was done with repeated make buildworld make kernel.new [0] nextboot -k kernel.new reboot make installworld etc [0] - well, there were

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

> What happens if you set hw.bge.allow_asf to 0 and use auto-negotiation > on both sides? it works! the switch was already auto-neg, and i forced auto-neg on the server side. thanks. this was not pleasant. did i remember to whine that i am in tokyo and the server is on the beast coast of the s

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

>> Have you tried to set the loader-tunable hw.bge.allow_asf to 0? >> The default for that option still is different between 8 and 9+. > it no longer panics when booting, but the interface comes up not > seeing carrier an additional datum. o with hw.bge.allow_asf untouched, i.e. default o with

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

> Hrm, the problem apparently is that while when probing, the PHY > still knows about the media it supports, it just has forgotten > about it after the reset during attach. There was a change prior > to 8.2 which would turn this from silently being ignored (which > generally might or might not work

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

>> ok, i >> o used device.hints to disable both bge interfaces >> o booted successfully >> o used serial console >> o ifconfiged bge0 to the normal addresses >> o and it is working >> >> i suspect that something sucks in bge initialization at startup. >> insightful, i know. sorry. > >

Re: Make Buildworld Fails (Broken Servers)

> The root cause was a bad cvsup server. Randy posted to freebsd-hubs > about the problem (I haven't looked to find the mail though). found four bad servers while upgrading various systems. entropy seems to have struck the hub system. randy ___ freebs

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

ok, i o used device.hints to disable both bge interfaces o booted successfully o used serial console o ifconfiged bge0 to the normal addresses o and it is working i suspect that something sucks in bge initialization at startup. insightful, i know. sorry. randy

Re: 9-stable - ifmedia_set: no match for 0x0/0xfffffff

way cool. a /boot/device.hints entry of hint.acpi.bge.1.disable=1 did disable bge1. but now it's bge0, and i need that interface. and media are present! so i tried /etc/rc.conf ifconfig_bge0="198.180.150.1/25 media 1000baseTX" ifconfig_bge0_ipv6="inet6 2001:418:8006::1/64" ifco

9-stable - ifmedia_set: no match for 0x0/0xfffffff

day old i386 current bge1: mem 0xd020-0xd020 irq 10 at device 0.0 on pci5 bge1: CHIP ID 0x4101; ASIC REV 0x04; CHIP REV 0x41; PCI-E miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: OUI 0x001018, model 0x0018, rev. 0 brgphy1: no media present ifmedia_set: no match for 0x0/0x

Re: buildworld: don't know how to make iterator.cc

> I have this problem on two of my systems. Yesterday I was trying my > weekly update on a i386 9.0 stable and had this failure. This morning > on my i386 8.2 stable I had the same failure. > > I csup'd the sources again and it found no changes. I the changed my > supfile from mirro 10 to mirror 5

Re: buildworld: don't know how to make iterator.cc

> Randy, when moving from one to another, are you deleting the contents of > /usr/src before doing the csup? More explicitly, this is what you > should do when going from one release to another: > > rm -fr /usr/src > rm -fr /var/db/sup/src-all > rm -fr /usr/obj/* > csup ... first one in is one o

Re: buildworld: don't know how to make iterator.cc

> Randy, when moving from one to another, are you deleting the contents > of /usr/src before doing the csup? More explicitly, this is what you > should do when going from one release to another: > > rm -fr /usr/src > rm -fr /var/db/sup/src-all > rm -fr /usr/obj/* > csup ... in a decade or more,

Re: buildworld: don't know how to make iterator.cc

fresh csup, multiple am64 machines trying to go from 8.2 to 9.0 it is also on an one i386 running 9.0 FreeBSD psg.com 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #2: Sat Dec 24 13:35:25 GMT 2011 r...@psg.com:/usr/obj/usr/src/sys/PSG i386 sh /usr/src/tools/install.sh -s -o root -g wheel -m 555

Re: buildworld: don't know how to make iterator.cc

> fresh csup, multiple amd64 machines > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 clang-tblgen > /usr/obj/usr/src/tmp/legacy/usr/bin > ===> gnu/usr.bin/gperf (obj,depend,all,install) > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf created for > /usr/src/gnu/usr.bin/gperf > ===

Re: buildworld: don't know how to make iterator.cc

> fresh csup, multiple amd64 machines > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 clang-tblgen > /usr/obj/usr/src/tmp/legacy/usr/bin > ===> gnu/usr.bin/gperf (obj,depend,all,install) > /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf created for > /usr/src/gnu/usr.bin/gperf > ===

buildworld: don't know how to make iterator.cc

fresh csup, multiple amd64 machines sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 clang-tblgen /usr/obj/usr/src/tmp/legacy/usr/bin ===> gnu/usr.bin/gperf (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/usr.bin/gperf ===> gnu/usr.bin/gp

Re: 8.2->9.prerel: gmirror failed with error 19

> I think you should add "device da" or "device ada" option to have some > disks available. indeed. confirmed. randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "

Re: 8.2->9.prerel: gmirror failed with error 19

> I would like to see better documentation on labeling file systems and > disks, though. It can be rather confusing between gpart labels, > glabels, and such. been making me crazy on some systems. and i have one hpt where i used labels but the controller is s smart it moves dev nums under me.

Re: 8.2->9.prerel: gmirror failed with error 19

> With the introduction of FreeBSD 9.x, all ATA devices now use a > translation layer (ATA->CAM), and this is especially so with anything > SATA. I imagine this needs to be documented (in red, bold, etc.) in the > official 9.0-RELEASE documentation, because it's probably going to trip > up others.

Re: 8.2->9.prerel: gmirror failed with error 19

>> # ATA/SCSI peripherals >> device scbus # SCSI bus (required for ATA/SCSI) >> #device ch # SCSI media changers >> #device da # Direct Access (disks) >> #device sa # Sequential Access (tape etc) >

Re: 8.2->9.prerel: gmirror failed with error 19

>> FreeBSD 9.0-PRERELEASE #18: Tue Dec 13 12:20:57 GMT 2011 >> r...@work0.psg.com:/usr/obj/usr/src/sys/WORK0 amd64 > Could you also show your kernel config? cpu HAMMER ident WORK0 makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options

Re: 8.2->9.prerel: gmirror failed with error 19

>> neither 9 nor 8 would boot without ending up here >> the only way out was via loader >> >> OK unload >> OK load boot/kernel.old/kernel >> OK load boot/kernel.old/geom_mirror.ko >> OK set kern.geom.part.check_integrity=0 >> OK set vfs.root.mountfrom.options=rw >> OK boot

8.2->9.prerel: gmirror failed with error 19

8.2 system fully updated as of 2011.12.14 it can reboot quite happily csup to RELENG_9 make buildworld make kernel boot single root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Trying to mount root from ufs:/dev/mirror/boota [rw]... mountroot: waiting fo

Re: recommendations for laptop and desktop

>> I might be able to admin such a wiki, but I have no place to put it. > want a vm guest all for yourself in the westin? apologies, this was supposed to be private ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fre

Re: recommendations for laptop and desktop

> I might be able to admin such a wiki, but I have no place to put it. want a vm guest all for yourself in the westin? randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any ma

Re: genassym.c:1: error: CPU you selected does not support x86-64 instruction set

> Where does the -march=i686 come from ? What's your /etc/make.conf ? doh! thanks. was left from old i386 machine from which i am migrating randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To

genassym.c:1: error: CPU you selected does not support x86-64 instruction set

FreeBSD rip0.psg.com 8.2-RC3 FreeBSD 8.2-RC3 #0: Sun Jan 30 06:28:31 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (1999.78-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Steppin

Re: 7.2 to RELENG_8 boot lockup

> I would advise you build a *generic* 8.x kernel, as opposed to the > custom one you seem to be using, first thing. true. lemme try one thing mt recommended first. > I would also recommend you see and try if you can sell domain name > psg.com to the french Paris Saint Germain football club for

7.2 to RELENG_8 boot lockup

18 month old 7.2 FreeBSD dfw1.psg.com 7.2-STABLE FreeBSD 7.2-STABLE #1: Sat Aug 22 08:37:36 UTC 2009 r...@dfw1.psg.com:/usr/obj/usr/src/sys/DFW1 amd64 csup and o make buildworld o make kernel o boot single user o locks up right after beastie, one twirly and locked boot verbose is r

Re: ZFS - moving from a zraid1 to zraid2 pool with 1.5tb disks

given i have raid or raidz1, can i move to raidz2? # zpool status pool: tank state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz1ONLINE 0 0 0 ad4s2 ONLINE

Re: repeating crashes with 8.1

> Just a shot in the dark, as I got another private report just now on > this one; is any of you by chance running VLANs on the systems you see > this happening? no vlans on the two affected systems here randy ___ freebsd-stable@freebsd.org mailing list

Re: beastiality

> This is often caused by a combination of two things being enabled > simultaneously: BIOS-level serial console redirection after POST, and > FreeBSD's serial console support. bingo! thanks randy ___ freebsd-stable@freebsd.org mailing list http://lists

beastiality

on the serial console, i am seeing twirlies doubled, as in // and the beastie is very tortured +-++¿Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä-Ä|Ä-Ä ||³ ||³ ||³ ,,

Re: repeating crashes with 8.1

> Do you know how this panic is triggered ? Are you able to > create it on demand ? no i do not. bring server up and it'll happen in half an hour. and the server was happy for two months. so i am thinking hardware. >>> >>> Perhaps. The reason I ask is that I had a box go do

Re: repeating crashes with 8.1

>>> Do you know how this panic is triggered ? Are you able to >>> create it on demand ? >> >> no i do not. bring server up and it'll happen in half an hour. >> and the server was happy for two months. so i am thinking hardware. > > Perhaps. The reason I ask is that I had a box go down last night

Re: repeating crashes with 8.1

> Do you know how this panic is triggered ? Are you able to > create it on demand ? no i do not. bring server up and it'll happen in half an hour. and the server was happy for two months. so i am thinking hardware. randy ___ freebsd-stable@freebsd.o

Re: repeating crashes with 8.1

> I need to know which hardware it is and that doesnt show me. how do i find out. >> em0: port 0x2000-0x201f mem >> 0xe800-0xe801 irq 16 at device 0.0 on pci13 joel, do you know? randy ___ freebsd-stable@freebsd.org mailing list http://lists.

Re: repeating crashes with 8.1

em0: port 0x2000-0x201f mem 0xe800-0xe801 irq 16 at device 0.0 on pci13 randy Jeremy Chadwick wrote: > > On Thu, Oct 21, 2010 at 12:08:23PM -0700, Randy Bush wrote: > > FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 > > r...@rip.psg.com:/usr/obj/usr

repeating crashes with 8.1

FreeBSD 8.1-STABLE #2: Thu Oct 21 15:30:45 UTC 2010 r...@rip.psg.com:/usr/obj/usr/src/sys/RIP amd64 console recording em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o packet header em0: discard frame w/o pack

Re: network deamons starting before network!

# grep REQUIRE /etc/rc.d/ppp # REQUIRE: netif ldconfig ^ i had to add this ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubs

Re: Results of BIND RFC

> While it certainly might make sense to drop BIND out of the base, I'm not > sure dropping bind tools as well from it is the best decision. How hard > it will be to continue maintaining bind tools inside the base (so the > critical ones like dig and nslookup still will be available), while movin

Re: Results of BIND RFC

> May I only hope this is legit and not a April Fool's joke :) actually, as an unbound user, i would be quite happy to have bind removed. bloated, ever-buggy, config religion, ... randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.o

Re: recommended miniPCI 802.11a/b/g card for Soekris net5501 running FreeBSD 8-STABLE?

for about two years, i have been using the Metrix CM9 miniPCI () on freebsd 8 on a 5501 and have been happy with it randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: 8.0-RELEASE completed...

yep. have upgraded to 8.0-RELEASE on a number of servers and it is very boring. this is a feature. thanks all. randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to

Re: 5.5-STABLE to 88.0-RELEASE

> I'd suggest either removing all ports, then going through the 5.5 -> > 6.0 -> 7.0 -> 8.0 and be sure to run the mergemaster, make delete-old, > make delete-old-libs at each stage and finally install the ports you > need or back up your data (not the config files) no thanks. too much of a mess,

5.5-STABLE to 88.0-RELEASE

can one go from 5.5 to 8.0 using the normal hammer, or is it multi-stage, and i should just blow it away and go from install? randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send

Re: 7.2 dies in zfs

> Everyone's workloads are different, but the panic is the same every > time: kmem exhaustion. i386 with KVA_PAGES or amd64 -- happens on both. > It's highly dependent upon workload and what the filesystem consists of > (many files vs. fewer files but larger in size, etc.) these are measurable.

Re: 7.2 dies in zfs

> My understanding is that the problem is more that the FreeBSD VM > system doesn't gracefully handle running low or out of memory. to me, that's just life in the big city. the problem i think can be solved before this is let loose on the unsuspecting public is that there are really no good tools

Re: 7.2 dies in zfs

>> imiho, zfs can not be called production ready if it crashes if you >> do not stand on your left leg, put your right hand in the air, and >> burn some eye of newt. > This is not a rant, but where do you read that on FreeBSD 7.2 ZFS has > been marked as production ready. > As far as i know, on Fre

Re: 7.2 dies in zfs

>> imiho, zfs can not be called production ready if it crashes if you >> do not stand on your left leg, put your right hand in the air, and >> burn some eye of newt. > ROFL! > As with any open-source project, I suppose it will be ready > when it is ready. At least it hasn't been made the default.

Re: 7.2 dies in zfs

> vm.kmem_size=1500M > vm.kmem_size_max=2G i am trying this with some success. let's see how the day goes. > BTW: I use auto-tuning of the ARC cache size: > vfs.zfs.arc_min: 12288 > vfs.zfs.arc_max: 98304 how the hell is a sysadmin supposed to guess all this ? if the freebsd sysadmin n

7.2 dies in midnight run again

i think the issue is how to tune for zfs i386 with 4G of RAM RELENG_7 cvsupped Nov 18 02:42 GMT panic: kmem_malloc(65536): kmem_map too small: 535019520 total allocated cpuid = 0 Uptime: 13h15m1s Physical memory: 3958 MB Dumping 637 MB: 622 606 590 574 558 542 526 510 494 478

Re: boot issues

>> i386, 7.2-stable from last summer >> >> cvsupped releng_7 >> made and installed kernel >> buildworld >> boot -s >> installworld >> mergemaster >> reboot >> >> hung after beastie, just as it did the other month >> >> booted -s >> mount -2 / >> /etc/rc.d/hostid start >> /etc/rc.d/zfs start >> l

boot issues

[ this happened a month ago and i backed off ] i386, 7.2-stable from last summer cvsupped releng_7 made and installed kernel buildworld boot -s installworld mergemaster reboot hung after beastie, just as it did the other month booted -s mount -2 / /etc/rc.d/hostid start /etc/rc.d/zfs start look

Re: bootless!

>> i386 running 7.2 as of aug 29 >> twe, gmirrored boot partition, zfs universe >> cvsupped 24 hours ago >> new kernel world >> will not boot. get beastie but stops at first twirly >> >> can boot old kernel -s, but not new kernel >> >> can not use old kernel with new world, hangs if i try to /et

  1   2   >