11-STABLE build failure in gnu/usr.bin/binutils/ld on recent -CURRENT

I ran into another problem updating my 11-STABLE poudriere jails on my package build machine, which runs a fairly recent version of -CURRENT. If I try to cross build: -O2 -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/tmp/src11/gnu/usr.bin/binutils/l d -I/tmp/src11/gnu/usr.bin/binutils/ld/../libbfd

Re: 11-STABLE and 12-STABLE build failures

On 25 Jul, Yuri Pankov wrote: > Don Lewis wrote: >> On 25 Jul, Don Lewis wrote: >>> On 25 Jul, Don Lewis wrote: >>>> On 25 Jul, Warner Losh wrote: >>>>> Liby.a was retired. Maybe there is some dangling references? >>>>

Re: 11-STABLE and 12-STABLE build failures

On 25 Jul, Don Lewis wrote: > On 25 Jul, Don Lewis wrote: >> On 25 Jul, Warner Losh wrote: >>> Liby.a was retired. Maybe there is some dangling references? >> >> # grep yydebug * >> localedef.c: yydebug = 0; >> localedef.h:extern int yydebug; >

Re: 11-STABLE and 12-STABLE build failures

On 25 Jul, Don Lewis wrote: > On 25 Jul, Warner Losh wrote: >> Liby.a was retired. Maybe there is some dangling references? > > # grep yydebug * > localedef.c: yydebug = 0; > localedef.h:extern int yydebug; > > I see the same in the 13-CURRENT source and it buil

Re: 11-STABLE and 12-STABLE build failures

On 25 Jul, Warner Losh wrote: > Liby.a was retired. Maybe there is some dangling references? # grep yydebug * localedef.c:yydebug = 0; localedef.h:extern int yydebug; I see the same in the 13-CURRENT source and it builds successfully. > On Sat, Jul 25, 2020, 2:05 PM Don Lewis

11-STABLE and 12-STABLE build failures

I'm seeing this failure when building 11-STABLE and 12-STABLE poudriere jails: --- localedef.full --- cc -O2 -pipe -fno-common -I. -I/var/poudriere/jails/12STABLEamd64/usr/src/usr.bin/localedef -I/var/poudriere/jails/12STABLEamd64/usr/src/lib/libc/locale

Re: ZFS...

On 3 May, Michelle Sullivan wrote: > > > Michelle Sullivan > http://www.mhix.org/ > Sent from my iPad > >> On 03 May 2019, at 03:18, N.J. Mann wrote: >> >> Hi, >> >> >> On Friday, May 03, 2019 03:00:05 +1000 Michelle Sullivan >> wrote: > I am sorry to hear about your loss of data, but

Re: Congratulations on the Silver Anniversery Edition of FreeBSD

On 12 Dec, Kevin Oberman wrote: > I worked with 4.2BSD and 4.3BSD back in the 70s and 80s. I moved to other > OSes (Digital RT, RSX and VMS an Varian Vortex) and returned in about 1999 > to FreeBSD 3.0. I've been using FreeBSD ever since. It's been wonderful and > I am so grateful to all of the

Re: early boot netisr_init() panic on older AMD SMP machine with recent 11-STABLE

On 9 Oct, Don Lewis wrote: > My desktop machine has an older AMD SMP CPU and tracks 11-STABLE. For > about six months or so it frequently panics early in boot. If I retry a > sufficient number of times I can get a successful boot, but this is > rather annoying. > > A norm

early boot netisr_init() panic on older AMD SMP machine with recent 11-STABLE

My desktop machine has an older AMD SMP CPU and tracks 11-STABLE. For about six months or so it frequently panics early in boot. If I retry a sufficient number of times I can get a successful boot, but this is rather annoying. A normal boot looks like this: Copyright (c) 1992-2018 The FreeBSD

Re: building 11.2-STABLE on CURRENT is broken

On 9 Aug, Kyle Evans wrote: > On Thu, Aug 9, 2018 at 12:48 PM, Kyle Evans wrote: >> On Thu, Aug 9, 2018 at 12:32 PM, Don Lewis wrote: >>> My poudriere machine is running fairly recent 12.0-CURRENT, r336859. >>> >>> I just tried upgrading my 11.2-STABLE poudri

building 11.2-STABLE on CURRENT is broken

My poudriere machine is running fairly recent 12.0-CURRENT, r336859. I just tried upgrading my 11.2-STABLE poudriere jail from r336040 to r337508 and got the errors below. Universe builds are also affected. I just started a universe build of r336040 and it looks likely to work, so the problem

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 2 Jun, Pete French wrote: > So,I notice that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 was > closes as fixed. I cant remember if there was another bug report for ongoing > Ryzen issues at all - I have been experimenting and have re-enabled most of > the BIOS setting and tweaks

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 24 Apr, Mike Tancsa wrote: > On 4/24/2018 10:01 AM, Pete French wrote: >> >> Well, I ranh the iperf tests between real machine for 24 hours and that >> worked fine. I also then spun up a Virtualbox with Win10 in it, and ran >> iuperf to there at the same time as doing it betwene real machines,

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 23 Apr, Mike Tancsa wrote: > On 4/22/2018 5:29 PM, Don Lewis wrote: >> Pretty much all of my BIOS settings are the defaults. >> >> I suspect that the idle hang issues are motherboard and/or BIOS >> specific. For the record my motherboard is a Gigabyte >

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 20 Apr, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by

Re: package building performance (was: Re: FreeBSD on AMD Epyc boards)

On 14 Feb, Mark Linimon wrote: > On Wed, Feb 14, 2018 at 09:15:53AM +0100, Kurt Jaeger wrote: >> On the plus side: 16+16 cores, on the minus: A low CPU tact of 2.2 GHz. >> Would a box like this be better for a package build host instead of 4+4 cores >> with 3.x GHz ? > > In my experience, "it

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 31 Jan, Eugene Grosbein wrote: > 31.01.2018 4:36, Mike Tancsa пишет: >> On 1/30/2018 2:51 PM, Mike Tancsa wrote: >>> >>> And sadly, I am still able to hang the compile in about the same place. >>> However, if I set >> >> >> OK, here is a sort of work around. If I have the box a little more

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 Jan, Mike Tancsa wrote: > On 1/30/2018 5:23 PM, Nimrod Levy wrote: >> That's really strange. I never saw those kinds of deadlocks, but I did >> notice that if I kept the cpu busy using distributed.net >> I could keep the full system lockups away for >> at least a

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 Jan, Mike Tancsa wrote: > On 1/30/2018 2:51 PM, Mike Tancsa wrote: >> >> And sadly, I am still able to hang the compile in about the same place. >> However, if I set > > > OK, here is a sort of work around. If I have the box a little more busy, > I can avoid whatever deadlock is going on.

Re: Ryzen issues on FreeBSD ?

On 27 Jan, Mike Tancsa wrote: > On 1/27/2018 3:23 AM, Don Lewis wrote: >> >> I just ran into this for this first time with samba46. I kicked of a >> ports build this evening before leaving for several hours. When I >> returned, samba46 had failed with a build r

Re: Ryzen issues on FreeBSD ?

On 27 Jan, Peter Moody wrote: > Whelp, I replaced the r5 1600x with an r7 1700 (au 1734) and I'm now > getting minutes of uptime before I hard crash. With smt, without, with c > states, without, with opcache, without. No difference. Check the temperatures. Maybe the heat sink isn't making good

Re: Ryzen issues on FreeBSD ?

On 28 Jan, Pete French wrote: > > > On 28/01/2018 20:28, Don Lewis wrote: >> I'd be wary of the B350 boards with the higher TDP eight core Ryzen CPUs >> since the VRMs on the cheaper boards tend to have less robust VRM >> designs. > > Gah! Yes, I forgo

Re: Ryzen issues on FreeBSD ?

On 28 Jan, Pete French wrote: >>> I'm about ready to have a party. My Ryzen 5 1600 has been up for over 8 >>> days so far after changing the memory to a slower speed. System load >>> hovers around .3 >> >> I couldn't find an easy way to down-speed my memory in the bios :( > > Out of interest,

Re: Ryzen issues on FreeBSD ?

On 23 Jan, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >> On 22 Jan, Mike Tancsa wrote: >>> On 1/22/2018 1:41 PM, Peter Moody wrote: >>>> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >>>> hw.lower_amd64_sharedpage

Re: Ryzen issues on FreeBSD ?

On 23 Jan, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >>> >>> I am trying an RMA with AMD. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STA

Re: Ryzen issues on FreeBSD ?

On 23 Jan, Pete French wrote: > On 22/01/2018 18:25, Don Lewis wrote: >> On 22 Jan, Pete French wrote: >>> >>> >>> On 21/01/2018 19:05, Peter Moody wrote: >>>> hm, so i've got nearly 3 days of uptime with smt disabled. >>>> unfortunat

Re: Ryzen issues on FreeBSD ?

On 22 Jan, Mike Tancsa wrote: > On 1/22/2018 1:41 PM, Peter Moody wrote: >> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash >> last night following the familiar high load -> idle. this was with SMT >>

Re: Ryzen issues on FreeBSD ?

On 22 Jan, Mike Tancsa wrote: > On 1/21/2018 3:24 PM, Don Lewis wrote: >>> >>> I have supplied a customer with a Ryzen5 and a 350MB motherboard. >>> But he runs Windows 10, but I haven't heard him complain about anything >>> like this. >>> But

Re: Ryzen issues on FreeBSD ?

On 22 Jan, Pete French wrote: > > > On 21/01/2018 19:05, Peter Moody wrote: >> hm, so i've got nearly 3 days of uptime with smt disabled. >> unfortunately this means that my otherwise '12' cores is actually only >> '6'. I'm also getting occasional segfaults compiling go programs. > > Isn't go

Re: Ryzen issues on FreeBSD ?

On 21 Jan, Willem Jan Withagen wrote: > On 21/01/2018 21:24, Don Lewis wrote: >> On 21 Jan, Willem Jan Withagen wrote: >>> On 19/01/2018 23:29, Don Lewis wrote: >>>> On 19 Jan, Pete French wrote: >>>>> Out of interest, is there anyone out there runni

Re: Ryzen issues on FreeBSD ?

On 21 Jan, Peter Moody wrote: > hm, so i've got nearly 3 days of uptime with smt disabled. > unfortunately this means that my otherwise '12' cores is actually only > '6'. I'm also getting occasional segfaults compiling go programs. Both my original and replacement CPUs croak on go, so I don't

Re: Ryzen issues on FreeBSD ?

On 21 Jan, Willem Jan Withagen wrote: > On 19/01/2018 23:29, Don Lewis wrote: >> On 19 Jan, Pete French wrote: >>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine

Re: Ryzen issues on FreeBSD ?

On 20 Jan, Mark Millard wrote: > Don Lewis truckman at FreeBSD.org wrote on > Sat Jan 20 02:35:40 UTC 2018 : > >> The only real problem with the old CPUs is the random segfault problem >> and some other random strangeness, like the lang/ghc build almost always >> faili

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 5:29 PM, Don Lewis wrote: >> On 19 Jan, Pete French wrote: >>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >>&

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 6:16 PM, Don Lewis wrote: >>> >>> 0(ms-v1)# kldload amdtemp >>> 0(ms-v1)# dmesg | tail -2 >>> ums0: at uhub0, port 3, addr 1 (disconnected) >>> ums0: detached >>> 0(ms-v1)# >> >> Wha

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 5:45 PM, Don Lewis wrote: >>> >>> And it just hangs there. No segfaults, but it just hangs. >>> >>> A ctrl+t shows just shows >>> >>> load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63

Re: Ancient FreeBSD update path

On 19 Jan, Mathieu Arnold wrote: > On Fri, Jan 19, 2018 at 01:28:41PM +0100, Andrea Brancatelli wrote: >> Hello guys. >> >> I have a couple of ancient FreeBSD install that I have to bring into >> this century (read either 10.4 or 11.1) :-) >> >> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:22 PM, Lucas Holt wrote: >> I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late > > Thanks! Thats the board I have, but no luck with amdtemp. Did you have > to change the source code for it to work ? > > dmidecode shows > >

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:48 PM, Peter Moody wrote: >> >> weirdly enough though, with SMT enabled, building net/samba47 would >> always hang (like compilation segfaults). with SMT disabled, no such >> problems. > > wow, thats so strange! I just tried,and the same thing and

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:48 PM, Peter Moody wrote: >> >> weirdly enough though, with SMT enabled, building net/samba47 would >> always hang (like compilation segfaults). with SMT disabled, no such >> problems. > > wow, thats so strange! I just tried,and the same thing and

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:32 PM, Peter Moody wrote: >> >> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about >> everything in all of these threads; disabling C state (no effect), >> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking >> voltage

Re: Ryzen issues on FreeBSD ?

On 19 Jan, Pete French wrote: > Out of interest, is there anyone out there running Ryzen who *hasnt* > seen lockups ? I'd be curious if there a lot of lurkers thinking "mine > works fine" No hangs or silent reboots here with either my original CPU or warranty replacement once the shared page

Re: Ryzen issues on FreeBSD ?

On 17 Jan, Nimrod Levy wrote: > I'm running 11-STABLE from 12/9. amdtemp works for me. It also has the > systl indicating that it it has the shared page fix. I'm pretty sure I've > seen the lockups since then. I'll update to the latest STABLE and see > what happens. > > One weird thing about

Re: Ryzen issues on FreeBSD ?

On 17 Jan, Mike Tancsa wrote: > On 1/17/2018 3:39 PM, Don Lewis wrote: >> On 17 Jan, Mike Tancsa wrote: >>> On 1/17/2018 8:43 AM, Pete French wrote: >>>> >>>> Are you running the latest STABLE ? There were some patches for Ryzen >>>>

Re: Ryzen issues on FreeBSD ?

On 17 Jan, Mike Tancsa wrote: > On 1/17/2018 8:43 AM, Pete French wrote: >> >> Are you running the latest STABLE ? There were some patches for Ryzen >> which went in I belive, and might affect te stability. Specificly the >> chnages to stop it locking up when executing code in the top page ? > >

Re: stable/11 r321349 crashing immediately

On 22 Jul, To: pz-freebsd-sta...@ziemba.us wrote: > On 22 Jul, G. Paul Ziemba wrote: >> My previous table had an error in the cumulative size column >> (keyboard made "220" into "20" when I was plugging into the hex >> calculator), so thet stack is 0x200 bigger than I originally thought: >> >>

Re: stable/11 r321349 crashing immediately

On 22 Jul, G. Paul Ziemba wrote: > My previous table had an error in the cumulative size column > (keyboard made "220" into "20" when I was plugging into the hex > calculator), so thet stack is 0x200 bigger than I originally thought: > > Frame Stack Pointer sz cumu function > -

Re: stable/11 r321349 crashing immediately

On 22 Jul, David Wolfskill wrote: > On Fri, Jul 21, 2017 at 04:53:18AM +, G. Paul Ziemba wrote: >> ... >> >It looks like you are trying to execute a program from an NFS file >> >system that is exported by the same host. This isn't exactly optimal >> >... >> >> Perhaps not optimal for the

Re: stable/11 r321349 crashing immediately

On 21 Jul, G. Paul Ziemba wrote: > truck...@freebsd.org (Don Lewis) writes: > >>On 21 Jul, G. Paul Ziemba wrote: >>> GENERIC kernel r321349 results in the following about a minute after >>> multiuser boot completes. >>> >>> What additional inf

Re: stable/11 r321349 crashing immediately

On 21 Jul, G. Paul Ziemba wrote: > GENERIC kernel r321349 results in the following about a minute after > multiuser boot completes. > > What additional information should I provide to assist in debugging? > > Many thanks! > > [Extracted from /var/crash/core.txt.NNN] > > KDB: stack backtrace: >

Re: Where is 10.2-STABLE?

On 30 Mar, Ronald F. Guilmette wrote: > > > I was looking to download an ISO for 10.2-STABLE for a new build I'm > doing, however I can't see to locate any such ISO. It isn't where > it seems it should be, according to the info on this page: > > https://www.freebsd.org/snapshots/ > > Where

Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)?

On 24 Jul, Matthieu Volat wrote: On Mon, 20 Jul 2015 14:03:01 -0700 (PDT) Don Lewis truck...@freebsd.org wrote: Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, which use clang as their base compiler and don't have gcc in base by default, the math/scilab port uses

MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)?

Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, which use clang as their base compiler and don't have gcc in base by default, the math/scilab port uses clang for cc and c++ compilation, but finds /usr/include/omp.h (and links to libgomp from lang/gcc). The build succeeds,

Re: There has to be a better way of merging /etc during a major freebsd-update

On 10 Mar, Miroslav Lachman wrote: This and some other problems with freebsd-update (hanging on the reboot after update) turns me back to using source compiled upgrades. I am compiling 10.1 right now to do the upgrades from 8.4 to 10.1 on 15 machines. I only do source upgrades, but I've

Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade?

On 26 Jun, Bob Willcox wrote: On Wed, Jun 26, 2013 at 01:23:32PM -0700, Jeremy Chadwick wrote: On Wed, Jun 26, 2013 at 09:42:43AM -0700, Chris H wrote: Greetings, I haven't upgraded my tree(s) for awhile. My last attempt to rebuild after an updating src ports, resulted in nearly

Re: What is the Right Way(™) to run X?

On 17 Mar, Andreas Nilsson wrote: On Sun, Mar 17, 2013 at 1:58 PM, Daniel O'Connor dar...@dons.net.au wrote: On 17/03/2013, at 23:08, Matthew D. Fuller fulle...@over-yonder.net wrote: However, some time back, X _did_ start being all stupid about finding the mouse for me. Un/re-plugging

Re: amdtemp does not find my CPU.

On 16 Mar, Jim Ohlstein wrote: On 3/16/13 2:20 AM, Jeremy Chadwick wrote: On Fri, Mar 15, 2013 at 03:16:19PM -0400, Jim Ohlstein wrote: On 3/15/13 12:15 PM, Zoran Kolic wrote: After I installed 9.1 amd64 on node with amd 8120, I was not able to read temperatures out of the box. I fetched

Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?

On 20 Feb, Jeremy Chadwick wrote: On Wed, Feb 20, 2013 at 10:29:05PM -0800, Don Lewis wrote: On 17 Feb, Torfinn Ingolfsen wrote: Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo@kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2

Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?

On 17 Feb, Torfinn Ingolfsen wrote: Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo@kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64

Re: LSI 9240-4i 4K alignment

On 8 Aug, George Kontostanos wrote: The problem: When trying to create a RaidZ pool using gpart and perform a 4K alignment using gnop, we get the follwoing error immediately after exporting the pool and destroying the .nop devices: id: 8043746387654554958 state: FAULTED status:

Re: LSI 9240-4i 4K alignment

On 19 Aug, Josh Paetzel wrote: On 08/19/2012 14:04, Steven Hartland wrote: HBA's are the way to go if your using ZFS to manage the disks, you only need RAID if your using a FS which doesn't manage the disk side well such as UFS. Its often quite common for RAID controllers to actually be

Re: LSI 9240-4i 4K alignment

On 16 Aug, Steven Hartland wrote: - Original Message - From: George Kontostanos gkontos.m...@gmail.com You are right, the chip specs say: LSISAS2108 RAID-on-Chip The drives are identified as mfisyspd0, mfisyspd1, etc. The following might be interesting to you:-

Re: LSI 9240-4i 4K alignment

On 8 Aug, George Kontostanos wrote: Hi all, We have a server with a LSI 9240-4i controller configured in JBOD with 4 SATA disks. Running FreeBSD 9.1-Beta1: Relevant dmesg: FreeBSD 9.1-BETA1 #0: Thu Jul 12 09:38:51 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Don Lewis wrote: The silent reboots that I was seeing with WITNESS go away if I add WITNESS_SKIPSPIN. Witness doesn't complain about anything. I've tracked down the the silent reboot problem. It happens when a userland sysctl call gets down into calcru1(), which tries to print

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: on 30/09/2010 02:27 Don Lewis said the following: vmstat -i ? I didn't see anything odd in the vmstat -i output that I posted to the list earlier. It looked more or less normal as the ntp offset suddenly went insane. I did manage to catch the problem

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: on 30/09/2010 02:27 Don Lewis said the following: I tried enabling apic and got worse results. I saw ping RTTs as high as 67 seconds. Here's the timer info with apic enabled: [snip] Here's the verbose boot info with apic: http://people.freebsd.org/~truckman

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Jeremy Chadwick wrote: Given all the information here, in addition to the other portion of the thread (indicating ntpd reports extreme offset between the system clock and its stratum 1 source), I would say the motherboard is faulty or there is a system device which is behaving

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Jeremy Chadwick wrote: On Wed, Sep 29, 2010 at 12:39:49AM -0700, Don Lewis wrote: On 29 Sep, Jeremy Chadwick wrote: Given all the information here, in addition to the other portion of the thread (indicating ntpd reports extreme offset between the system clock and its stratum 1

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Andriy Gapon wrote: on 29/09/2010 00:11 Don Lewis said the following: On 28 Sep, Don Lewis wrote: % vmstat -i interrupt total rate irq0: clk 60683442 1000 irq1: atkbd0 6 0 irq8: rtc

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Andriy Gapon wrote: on 29/09/2010 11:56 Don Lewis said the following: I'm using the same kernel config as the one on a slower !SMP box which I'm trying to squeeze as much performance out of as possible. My kernel config file contains these statements: nooptions SMP

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Chip Camden wrote: Quoth Don Lewis on Monday, 27 September 2010: CPU time accounting is broken on one of my machines running 8-STABLE. I ran a test with a simple program that just loops and consumes CPU time: % time ./a.out 94.544u 0.000s 19:14.10 8.1% 62+2054k 0+0io 0pf+0w

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Jeremy Chadwick wrote: On Tue, Sep 28, 2010 at 10:15:34AM -0700, Don Lewis wrote: My time source is another FreeBSD box with a GPS receiver on my LAN. My other client machine isn't seeing these time jumps. The only messages from ntp in its log from this period are these: Sep 23

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Don Lewis wrote: % vmstat -i interrupt total rate irq0: clk 60683442 1000 irq1: atkbd0 6 0 irq8: rtc7765537127 irq9: acpi0 13

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Jeremy Chadwick wrote: Still speaking purely about ntpd: The above doesn't indicate a single problem. The deltas shown in both delay, offset, and jitter are all 100% legitimate. A dd (to induce more interrupt use) isn't going to exacerbate the problem (depending on your system

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Don Lewis wrote: Looking at the timestamps of things and comparing to my logs, I discovered that the last instance of ntp instability happened when I was running make index in /usr/ports. I tried it again with entertaining results. After a while, the machine became unresponsive

CPU time accounting broken on 8-STABLE machine after a few hours of uptime

CPU time accounting is broken on one of my machines running 8-STABLE. I ran a test with a simple program that just loops and consumes CPU time: % time ./a.out 94.544u 0.000s 19:14.10 8.1%62+2054k 0+0io 0pf+0w The display in top shows the process with WCPU at 100%, but TIME increments very

Re: Extending your zfs pool with multiple devices

On 2 Sep, Jeremy Chadwick wrote: On Thu, Sep 02, 2010 at 04:56:04PM -0400, Zaphod Beeblebrox wrote: [regarding getting more disks in a machine] An inexpensive option are SATA port replicators. Think SATA switch or hub. 1:4 is common and cheap. I have a motherboard with intel ICH10

Re: cname replace in mail address? [off-topic] (Re: Attn Ronald Klop)

On 27 Aug, Ronald Klop wrote: Mandatory? I'm googling, but can't find a document that declares it mandatory and only sendmail seems to do it. I think it is lame to use DNS info to rewrite e-mail addresses, but the person who made it 'mandatory' will have good reasons for it. Does

Re: any hope for nfe/msk?

On 21 Nov, Chris wrote: On 07/11/2007, Pyun YongHyeon [EMAIL PROTECTED] wrote: On Wed, Nov 07, 2007 at 02:28:00PM +0200, Oleg Lomaka wrote: Hello, Pyun YongHyeon wrote: On Thu, Nov 01, 2007 at 10:59:48AM +0200, Oleg Lomaka wrote: Hello, Pyun YongHyeon wrote: On

Re: Call for testing: patch that helps Wine on 6.x

On 6 Aug, John Baldwin wrote: On Friday 03 August 2007 10:56:48 pm Marc G. Fournier wrote: John, I've been running both the signal and pfault patches on my 6.x desktops since Tijl posted them, and haven't noticed any issues resulting from them ... Does cvsup work? A similar patch

Re: removing external usb hdd without unmounting causes reboot?

On 18 Jul, Momchil Ivanov wrote: If the problem is in general with a file system, regardless of the provider, then what does one do when a mounted smbfs becomes unavailable due to remote host down, no route to host or some other network related problems? Same question for NFS mounted

Re: [5.4] mode bits changed by close(2)

On 28 Jan, David Malone wrote: On Fri, Jan 27, 2006 at 02:01:19PM -0700, [EMAIL PROTECTED] wrote: Sticking an fsync() in between the fchmod() and the close() causes the bits to be cleared as a side-effect of the fsync(). Doing another fchmod() after the fsync() produces the final expected

Re: Recurring problem: processes block accessing UFS file system

On 11 Jan, Denis Shaposhnikov wrote: Hi! Don == Don Lewis [EMAIL PROTECTED] writes: Don Are you using any unusual file systems, such as nullfs or Don unionfs? Yes, I'm use a lots of nullfs. This is a host system for about 20 jails with nullfs mounted ro system: Don That would

Re: Recurring problem: processes block accessing UFS file system

On 12 Jan, Don Lewis wrote: On 11 Jan, Denis Shaposhnikov wrote: Hi! Don == Don Lewis [EMAIL PROTECTED] writes: Don Are you using any unusual file systems, such as nullfs or Don unionfs? Yes, I'm use a lots of nullfs. This is a host system for about 20 jails with nullfs mounted

Re: Swapfile problem in 6?

On 2 Jan, Lars Kristiansen wrote: Attempting to catch up with my backlog of unread email, only 12K unread messages to go ... On 24 Nov, Rob wrote: 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

Re: Recurring problem: processes block accessing UFS file system

On 5 Jan, Denis Shaposhnikov wrote: Hi! Greg == Greg Rivers [EMAIL PROTECTED] writes: Greg It's taken more than a month, but the problem has recurred Greg without snapshots ever having been run. I've got a good trace I think that I have the same problem on a fresh CURRENT. For some

WITNESS speedup patch for RELENG_5

If you are running RELENG_5 and using WITNESS, you might want to try the patch below. It speeds up WITNESS rather dramatically. This patch was committed to HEAD in late August (subr_witness.c 1.198) and early September (subr_witness.c 1.200). It was MFC'ed to RELENG_6 in the last few days. I'd

Re: Recurring problem: processes block accessing UFS file system

On 5 Jan, Denis Shaposhnikov wrote: Don == Don Lewis [EMAIL PROTECTED] writes: Don pid 519 wants to lock this vnode but some other thread is Don holding the vnode lock. Unfortunately we don't know who the Don lock holder is because the message is truncated. Is it possible to find out

Re: Recurring problem: processes block accessing UFS file system

On 5 Jan, Denis Shaposhnikov wrote: Don == Don Lewis [EMAIL PROTECTED] writes: Don Are you using any unusual file systems, such as nullfs or Don unionfs? Yes, I'm use a lots of nullfs. This is a host system for about 20 jails with nullfs mounted ro system: That would be my guess

Re: Recurring problem: processes block accessing UFS file system

On 3 Jan, Greg Rivers wrote: On Tue, 3 Jan 2006, Don Lewis wrote: Pid 87117 is playing with buf 0xdc76fe30 which is not locked, and is sleeping on the buf's b_xflags member. It looks like 87117 is waiting for an in-progress write to complete. There are a large number of other sendmail

Re: Recurring problem: processes block accessing UFS file system

On 3 Jan, Greg Rivers wrote: On Tue, 22 Nov 2005, I wrote: On Mon, 21 Nov 2005, Kris Kennaway wrote: It may not be the same problem. You should also try to obtain a trace when snapshots are not implicated. Agreed. I'll do so at the first opportunity. First, my thanks to all of

Re: Recurring problem: processes block accessing UFS file system

On 3 Jan, Greg Rivers wrote: On Tue, 3 Jan 2006, Don Lewis wrote: There are large number of sendmail processes waiting on vnode locks which are held by other sendmail processes that are waiting on other vnode locks, etc. until we get to sendmail pid 87150 which is holding a vnode lock

Re: Swapfile problem in 6?

Attempting to catch up with my backlog of unread email, only 12K unread messages to go ... On 24 Nov, Rob wrote: 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:

Re: Swapfile problem in 6?

On 17 Nov, Kris Kennaway wrote: On Thu, Nov 17, 2005 at 04:33:50PM -0800, Rob wrote: --- 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

Re: Recurring problem: processes block accessing UFS file system

On 26 Nov, Tor Egge wrote: Thanks Kris, these are exactly the clues I needed. Since the deadlock during a snapshot is fairly easy to reproduce, I did so and collected this information below. alltrace didn't work as I expected (didn't produce a trace), so I traced each pid associated

Re: Recurring problem: processes block accessing UFS file system

On 26 Nov, Tor Egge wrote: Thanks Kris, these are exactly the clues I needed. Since the deadlock during a snapshot is fairly easy to reproduce, I did so and collected this information below. alltrace didn't work as I expected (didn't produce a trace), so I traced each pid associated

Re: Recurring problem: processes block accessing UFS file system

On 22 Nov, Greg Rivers wrote: On Mon, 21 Nov 2005, Kris Kennaway wrote: It may not be the same problem. You should also try to obtain a trace when snapshots are not implicated. Agreed. I'll do so at the first opportunity. 'show lockedvnods' is very important for diagnosing

Re: FreeBSD unstable on Dell 1750 using SMP?

.. Thanks for your help! Dan Try this patch, which I posted to stable@ on October 15. I had hoped to commit it to RELENG_5 in November, but my day job intervened. -- Forwarded message -- From: Don Lewis [EMAIL PROTECTED] Subject: testers wanted for 5.4-STABLE sysctl kern.proc patch

testers wanted for 5.4-STABLE sysctl kern.proc patch

The patch below is the 5.4-STABLE version of a patch that was recently committed to HEAD and 6.0-BETA5 to fix locking problems in the kern.proc sysctl handler that could cause panics or deadlocks. It has already been tested by myself and one other person in 5.4-STABLE, but I think it deserves

  1   2   >