Re: upgrading from 10.0 to 10.3 problem
> Hello. I tried to upgrade from 10.0-RELEASE: # freebsd-update -r 10.3-RELEASE > upgrade > ... > # freebsd-update install > ... > # reboot > ... > # freebsd-update install > Installing updates...Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) > Segmentation fault (core dumped) Now I have: > # freebsd-version -ku > 10.3-RELEASE-p4 > 10.0-RELEASE It's not looking good. How to fix? PS. In /var/log/messages I > see "(gunzip), uid 0: exited on signal 11" > And yes: > # gunzip > Segmentation fault (core dumped) Hi Sergey: I ran into this problem the week before you did: https://lists.freebsd.org/pipermail/freebsd-stable/2016-July/085115.html Because just about all of the binaries were trashed (including /lib, /[s]bin, /usr/lib, /usr/[s]bin files were truncated to 0), I had to /rescue/nc > base.txz (where I fetched base.txz from the ftp site in the 10.3-RELEASE distribution), then /rescue/tar -zxvf base.txz into a directory, then tar | tar each of /lib and so on to get my binaries back (apparently /rescue does not have a statically compiled cpio). After sending the above to the mailing list I went ahead and replaced the kernel that the broken freebsd-update install installed with the one from 10.3-RELEASE (from the distribution base.txz:boot/kernel), which made the system entirely binary 10.3-RELEASE then I was able to freebsd-update to FreeBSD-10.3-RELEASE-p6 with no problems. Note that the initial freebsd-update from 10.0 also severely trashed my /etc, I had to restore master.passwd and friends! (many of /etc files were also truncated to 0), even though the merge process seemed to complete ok before the broken freebsd-update install. ___ 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"
freebsd-update 10.0 -> 10.3 segmentation fault
I wanted to updating an old 10.0-R-? system to 10.3 and tried to see if I could go from 10.0 to 10.3 using freebsd-update. I got segfaults during the freebsd-update install portion and the base binaries got trashed. Is going up multiple minor versions unsupported with freebsd-update or something? (I haven't played with freebsd-update in a long long time but a 9.x -> 10.0 worked fine the last time I did it several years ago.) I also tried this foolishly on a remote machine, fortunately my ssh session stayed intact, so I was able to use /rescue/nc to retrieve a copy of 10.3/base.txz and a backup of /etc (which freebsd-update also destroyed, even though the merge looked fine to me). I restored the ability to ssh back into the machine. Based on sha256 I think by now, after restoring /bin, /lib, /libexec, /sbin, /usr from base.txz I have Percival's 10.3-R-p4 kernel running with a 10.3-R userland (I retrieved base.txz from ftp.freebsd.org/pub/FreeBSD/releases/amd64/10.3-RELEASE), so I'm not sure if I want to pull down sources and track -RELEASE using svn/buildworld or if I should try to backup this kernel (which is working) and reinstall the 10.3-R kernel from base.txz and see if I freebsd-update will work in the future 10.3 -> 11. ___ 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"
upgrade to 8.3 from 7.2 static root mountpoint disappeared
I just did an upgrade from an old 7.2 installation to 8.3-RC2 last night, and the kernel was only able to mount root from a ufsid label and could not detect any bsdlabels. The 7.2 installation used static bsdlabeled disks (/dev/ad0s1a etc). This seemed to be an unexpected change (I had to get the remote datacenter to connect an ipkvm to fix the problem), particularly because the 7.2 kernel never loaded geom_label but somehow the partitions ended up with labels quite mysteriously; the box was originally installed from 6.x-R from 2006. ___ 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
t_delta too short while trying to enable C3/TurboBoost
Hello I'm trying to enable C3 states to allow TurboBoost on RELENG_8_2 and dmesg is throwing a lot of t_delta too short messages while using boot -v. This platform is 2x Xeon E5620 Gulftown quad core 2.4ghz CPUs on whatever boards Dell ships them on these days (probably Intel X58 derivative.) Kernel is GENERIC for the most part (with network drivers stripped out). Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2394012372 Hz TSC: P-state invariant ACPI timer: 1/2 1/2 1/1 1/2 1/2 1/1 1/2 1/2 1/2 1/1 - 10 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 Here are my loader.conf: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 kern.hz=100 hint.apic.0.clock=0 hint.atrtc.0.clock=0 rc.conf: performance_cpu_freq=NONE # Online CPU frequency economy_cpu_freq=NONE # Offline CPU frequency performance_cx_lowest=C3 # Online CPU idle state economy_cx_lowest=C3 # Offline CPU idle state and here is sysctl dev.cpu: dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU1 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/1 C2/64 C3/96 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 0.90% 0.45% 98.64% last 4096us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU2 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/1 C2/64 C3/96 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.68% 0.34% 98.96% last 2965us dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU3 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.cx_supported: C1/1 C2/64 C3/96 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 0.94% 0.66% 98.38% last 2081us dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU4 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.cx_supported: C1/1 C2/64 C3/96 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 0.81% 0.58% 98.59% last 4124us dev.cpu.4.%desc: ACPI CPU dev.cpu.4.%driver: cpu dev.cpu.4.%location: handle=\_PR_.CPU5 dev.cpu.4.%pnpinfo: _HID=none _UID=0 dev.cpu.4.%parent: acpi0 dev.cpu.4.cx_supported: C1/1 C2/64 C3/96 dev.cpu.4.cx_lowest: C3 dev.cpu.4.cx_usage: 1.07% 0.68% 98.23% last 5046us dev.cpu.5.%desc: ACPI CPU dev.cpu.5.%driver: cpu dev.cpu.5.%location: handle=\_PR_.CPU6 dev.cpu.5.%pnpinfo: _HID=none _UID=0 dev.cpu.5.%parent: acpi0 dev.cpu.5.cx_supported: C1/1 C2/64 C3/96 dev.cpu.5.cx_lowest: C3 dev.cpu.5.cx_usage: 3.01% 1.74% 95.24% last 4504us dev.cpu.6.%desc: ACPI CPU dev.cpu.6.%driver: cpu dev.cpu.6.%location: handle=\_PR_.CPU7 dev.cpu.6.%pnpinfo: _HID=none _UID=0 dev.cpu.6.%parent: acpi0 dev.cpu.6.cx_supported: C1/1 C2/64 C3/96 dev.cpu.6.cx_lowest: C3 dev.cpu.6.cx_usage: 2.45% 1.89% 95.65% last 3506us dev.cpu.7.%desc: ACPI CPU dev.cpu.7.%driver: cpu dev.cpu.7.%location: handle=\_PR_.CPU8 dev.cpu.7.%pnpinfo: _HID=none _UID=0 dev.cpu.7.%parent: acpi0 dev.cpu.7.cx_supported: C1/1 C2/64 C3/96 dev.cpu.7.cx_lowest: C3 dev.cpu.7.cx_usage: 1.21% 0.77% 98.00% last 4180us Should I increment kern.hz until the t_delta too short goes away (I hear that at kern.hz=1000, each core is woken so much by the interrupt counter that it can never enter C3 state) or is there another knob I am supposed to tune? My goal is to see if I can get the box into turboboost as much as possible during idle. ___ 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
