Hi,
I just got this error when fetching from remote; related?
[elars@laurel: ~/src] git fetch --all
Fetching origin
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
Fetching upstream
remote: Counting objects: 557, done.
remote: Compress
amd64
--
Sent from a mobile device; please excuse typos.
+49 151 120 55791
> On Oct 22, 2015, at 21:08, Ian Lepore wrote:
>
>> On Wed, 2015-10-21 at 08:09 +0000, Eggert, Lars wrote:
>> Hi,
>>
>> I'm trying to include some loader tunables in the ker
Hi,
I'm trying to include some loader tunables in the kernel, via the "env"
functionality described in config(5).
When I look at the compiled kernel binary with strings(1), I see that the
tunables are compiled in.
However, they don't seem to take any effect when booting the kernel, and they
a
Hi,
I'm netbooting with a read-only rootfs. Up until version 1.5.2 of pkg, that
sometimes caused some errors when installing various packages, but the install
continued even if some files couldn't be written.
That seems to have changed with 1.5.4. Specifically, upgrading ca_root_nss from
3.19
On 2015-5-20, at 17:42, Ryan Stone wrote:
> Oh, I bet that you have a bunch of CPUs and ixl is consuming all of your
> interrupt vectors. Does setting this tunable fix the issue?
>
> hw.ixl.max_queues=1
Yeah, this box has 40 cores, but unfortunately that tunable doesn't change
things in terms
On 2015-5-18, at 19:22, Ryan Stone wrote:
> Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My
> hardware is a little different from yours -- my CPU is a Haswell Xeon, and I
> have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I
> didn't have Xen or anyth
On 2015-5-18, at 16:08, Ryan Stone wrote:
> This is very strange. I have successfully netbooted -CURRENT in a very
> similar environment (ixl compiled into kernel and booting over igb). I
> can't remember when the last time I did this but it was probably within the
> last couple of weeks. I rou
Hi,
when I have the ixl driver compiled into my -CURRENT kernel (or loaded as a
module via loader.conf), the boot seems to hang (or silently crash) when BOOTP
starts bringing up interfaces to send out probes. (I'm not netbooting over an
ixl, the boot interface is an igb.)
What works is buildin
Hi,
this came up when trying to port tup (https://github.com/gittup/tup) to FreeBSD.
Even though we are opening the file read-only with cat, FUSE calls truncate()
on it, which modifies its mtime and this screws up tup. See
https://github.com/gittup/tup/issues/198
Anyone know why FreeBSD's FUSE
On 2015-1-7, at 16:28, Garrett Cooper wrote:
> Please open a bug and cc hselasky@ on it.
Done: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196597
Lars
signature.asc
Description: Message signed with OpenPGP using GPGMail
Hi,
On 2014-12-31, at 21:41, Dimitry Andric wrote:
> I just committed an upgrade of clang, llvm and lldb to 3.5.0 to head, in
> r276479.
there seem to be issues when building with -DWITH_OFED:
--- contrib/ofed.all__D ---
/usr/home/elars/src/contrib/ofed/usr.bin/opensm/../../management/opensm/op
Hi,
I've been seeing the same issues with nscd not caching, but unfortunately your
patch doesn't seem to change things, for better or worse.
My nsswitch.conf looks as follows:
group: cache files nis
hosts: cache files dns
networks: cache files
passwd: cache files nis
shells: files
services: cac
On 2014-8-19, at 13:54, Daniel Braniss wrote:
>
> I know that this a bit late but have you ever considered Hesiod? it uses
> DNS/txt.
> we have been using it since the days when BSDi had no NIS support and haven’t
> seen a ypserver not responding since :-)
I don't control the master NIS infrast
On 2014-8-18, at 20:23, John-Mark Gurney wrote:
> Why not run a local slave on your server?
I am trying to get one set up. It requires a change request to our
organization's IT, which is, ahem, not always lightning fast.
Lars
signature.asc
Description: Message signed with OpenPGP using GPGMai
Hi,
On 2014-8-17, at 18:10, Adam McDougall wrote:
> We were using +: type entries in the local password and group
> tables and I believe we used an unmodified /etc/nsswitch.conf (excluding
> cache lines while testing nscd):
I tried that setup too, and it doesn't seem to be caching any NI
Nobody using nscd? Really?
On 2014-8-14, at 13:26, Eggert, Lars wrote:
> [Resending to current@, since I can't get it to work on -CURRENT either.]
>
> Hi,
>
> anyone have an idea why nscd would not be caching NIS lookups?
>
> My nsswitch.conf looks as follows:
&
[Resending to current@, since I can't get it to work on -CURRENT either.]
Hi,
anyone have an idea why nscd would not be caching NIS lookups?
My nsswitch.conf looks as follows:
group: cache files nis
hosts: cache files dns
networks: cache files
passwd: cache files nis
shells: files
services: cac
Disregard - pilot error. (It's not Feb 4...)
Lars
On 2014-2-18, at 9:50, Eggert, Lars wrote:
> Hi,
>
> On 2014-2-16, at 21:06, Dimitry Andric wrote:
>> I have just upgraded our copy of llvm/clang to 3.4 release, in r261991.
>
> I just done a "git pull" f
Hi,
On 2014-2-16, at 21:06, Dimitry Andric wrote:
> I have just upgraded our copy of llvm/clang to 3.4 release, in r261991.
I just done a "git pull" followed by a buildworld. Shouldn't I be having
version 3.4?
root@six:~ # dmesg | grep clang
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183
Last follow-up: I just saw that there are some additional messages (errors?) on
the serial console when changing the device from IB to Ethernet, maybe they
mean something to someone:
root@one:~ # sysctl sys.device.mlx4_core0.mlx4_port1=eth
sys.device.mlx4_core0.mlx4_port1: auto (ib)<7>ib0: stopp
On 2014-1-21, at 10:04, Lars Eggert wrote:
> See the attached dmesg
which I of course forget to attach (sigh). See below.
Lars
GDB: no debug ports present970
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986,
Hi,
On 2014-1-20, at 21:59, John Baldwin wrote:
> I believe this should work, yes. Getting a crashdump or the panic messages
> would be really helpful in figuring out why it isn't. Thanks.
I rebuilt the kernel, and see no crashes anymore. So that's good.
But there are a bunch of other issues
Hi,
if I leave the mlx4ib device out of the kernel (i.e., only compile in mlxen),
doing the sysctl switch to Ethernet mode works fine.
Lars
On 2014-1-20, at 13:08, Eggert, Lars wrote:
> Hi,
>
> On 2013-7-9, at 22:08, John Nielsen wrote:
> On Jul 9, 2013, at 9:58 AM, John Ba
Hi,
On 2013-7-9, at 22:08, John Nielsen wrote:
On Jul 9, 2013, at 9:58 AM, John Baldwin wrote:
>> So this was just fixed (finally) in HEAD in r253048. You can how use the
>> sysctls to change this.
>
> I saw the commit. Thanks! I'll give it a try at some point (whenever my
> schedule and hard
Hi,
every few days or so, my -STABLE NFS server (v3 and v4) gets wedged with a ton
of messages about "nfsd server cache flooded, try to increase nfsrc_floodlevel"
in the log, and nfsstat shows TCPPeak at 16385. It requires a reboot to
unwedge, restarting the server does not help.
The clients a
Hi,
On Jun 29, 2013, at 2:45, Rick Macklem wrote:
> Btw, a NFSv4 mounted root fs will not work correctly, because the client
> name is generated from the host uuid, which isn't set when the root fs
> is mounted. I'm not sure what the client would use as its client name,
> but this will definitely
Thanks Rick! I will check these Monday.
Lars
On Jun 29, 2013, at 2:45, Rick Macklem wrote:
> Lars Eggert wrote:
>> Hi,
>>
>> On Jun 28, 2013, at 16:37, "Eggert, Lars" wrote:
>>> On Jun 28, 2013, at 16:14, "Eggert, Lars" wrote:
>>
Hi,
I should have mentioned that the server is FreeBSD -STABLE running newnfs, and
the network isn't partitioned (because I access the box over SSH at the same
time I see these messages.)
They only appear under heavy NFS load (portmaster build of math/R in this case.)
Lars
On Jun 29, 2013, at
Hi,
On Jun 28, 2013, at 16:37, "Eggert, Lars" wrote:
> On Jun 28, 2013, at 16:14, "Eggert, Lars" wrote:
>> on a -CURRENT client, I get quite a number of console messages under heavy
>> NFSv4 load, such as:
>>
>> nfsv4 expired locks lost
>>
Hi,
On Jun 28, 2013, at 16:14, "Eggert, Lars" wrote:
> on a -CURRENT client, I get quite a number of console messages under heavy
> NFSv4 load, such as:
>
> nfsv4 expired locks lost
> nfscl: never fnd open
actually, not sure if the "nfscl" message is from an
Hi,
on a -CURRENT client, I get quite a number of console messages under heavy
NFSv4 load, such as:
nfsv4 expired locks lost
nfscl: never fnd open
nfscl: never fnd open
nfscl: never fnd open
nfsv4 expired locks lost
nfscl: never fnd open
nfscl: never fnd open
nfsv4 expired locks lost
nfsv4 expir
Hi,
On Jun 17, 2013, at 14:51, Bryan Drewery wrote:
> ccache is known to be broken with clang [1]. I would recommend not using it.
Pity! We do buildworld often enough that that's an inconvenience.
> Sometimes CCACHE_CPP2=1 in make.conf can help. CCACHE_CPP2=1 is
> hardcoded in version 3.1.9_2 o
On Jun 17, 2013, at 15:18, Luiz Otavio O Souza
wrote:
> It was a change on alq. The fix was committed in r251838.
Awesome! I can confirm it's fixed.
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
Hi,
any further ideas? This issue still exist when building -CURRENT on -STABLE as
of today.
Thanks,
Lars
On May 23, 2013, at 12:33, "Eggert, Lars" wrote:
> Hi,
>
> On May 22, 2013, at 13:37, Dimitry Andric wrote:
>> Can you try to figure out which copy of cl
Hi,
something changed in the last 2-3 weeks on -CURRENT that causes reboots to hang
after this line:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
I need to manually cycle the power to reboot.
Any clues?
Thanks,
Lars
___
freebsd
Hi,
On Jun 3, 2013, at 1:57, Rick Macklem wrote:
> Cool. Thanks. Would you like to review and/or test the above?
it'd be great if folks would test this a bit. It certainly works for me, but I
can't say that I have done a very thorough testing.
> I'll be happy to commit it if Lars doesn't have
Hi,
to conclude this thread, the patch below allows one to specify an nfs rootfs
via the ROOTDEVNAME kernel option, which will be mounted when BOOTP does not
return a root-path option.
Lars
diff --git a/sys/nfs/bootp_subr.c b/sys/nfs/bootp_subr.c
index 2c57a91..972fb12 100644
--- a/sys/nfs/bo
Hi,
when I try to build ports on -CURRENT, I've been seeing tons of these messages
since the past week or so:
make: "/usr/ports/Mk/bsd.port.mk" line 1633: warning: Couldn't read shell's
output for "if /sbin/sysctl -n compat.ia32.maxvmem >/dev/null 2>&1; then echo
YES; fi"
The amd64 kernel I'm
Hi,
On May 22, 2013, at 13:37, Dimitry Andric wrote:
> Can you try to figure out which copy of clang ccache finds and runs?
I enabled CCACHE_LOGFILE, and it seems that it runs /usr/bin/clang:
[2013-05-23T12:25:36.810346 48913] Command line:
/usr/local/libexec/ccache/clang
--sysroot=/home/elar
Hi,
my buildworlds using ccache have recently begun failing with the message below.
Buildworld without ccache works fine. Any ideas?
CC='/usr/local/libexec/ccache/world/clang
--sysroot=/home/elars/obj/usr/home/elars/src/tmp
-B/home/elars/obj/usr/home/elars/src/tmp/usr/bin' mkdep -f .depend -a
Hi,
On Apr 22, 2013, at 2:56, Baptiste Daroussin wrote:
> As anyone been able to test this patch?
I've been running with it for a few days. I've done a reinstall of all ports
plus a few "portmaster -a" runs without pkgng database corruption. I've not
tested it for very long, but so far, things
Hi,
On Apr 12, 2013, at 1:10, Rick Macklem wrote:
> Well, I have no idea why an NFS server would reply errno 70 if the file
> still exists, unless the client has somehow sent a bogus file handle
> to the server. (I am not aware of any client bug that might do that. I
> am almost suspicious that t
Hi,
On Apr 11, 2013, at 10:30, Baptiste Daroussin wrote:
> First, I think you can recover your database.
that would be great.
> Can you try the following command:
>
> # mv /var/db/pkg/local.sqlite /var/db/pkg/backup.sqlite
> # echo '.dump' | pkg shell /var/db/pkg/backup.sqlite | pkg shell
Tha
Hi,
On Apr 11, 2013, at 0:16, Baptiste Daroussin wrote:
> Will you be able to test it?
yes. (But I will be traveling for the next two weeks and so the turnaround may
be a bit longer than normal.)
Lars
___
freebsd-current@freebsd.org mailing list
http
Hi,
On Apr 11, 2013, at 1:28, Rick Macklem wrote:
> Error code 70 is ESTALE (or NFSERR_STALE, if you prefer). The server
> replies with that when the file no longer exists.
>
> File locking doesn't stop a file from being removed, as far as I know.
but the file is still there.
Lars
Hi,
On Apr 10, 2013, at 10:02, Baptiste Daroussin wrote:
> This can usually happen when a user do not have the nfs lock system started.
> Are you sure that nfs lock is correctly started?
with NFSv4, the locking system is integrated with the main protocol, it's no
longer separate.
> If that is
Hi,
on a diskless server, I keep the ports tree and pkgng databases on a newnfs
NFSv4 mount. After a bunch of "portmaster -a" runs, the pkgng sqlite database
appears to get corrupted. For example, when I try to update an existing port,
this happens:
root@five:~ # portmaster ports-mgmt/pkg
...
Hi,
this reminds me that I ran into an issue lately with the new NFS and locking
for NFSv3 mounts on a client that ran -CURRENT and a server that ran -STABLE.
When I ran "portmaster -a" on the client, which mounted /usr/ports and
/usr/local, as well as the location of the respective sqlite data
On Mar 4, 2013, at 20:59, Doug Ambrisko wrote:
> Try to do a {Ctrl}D to see if works. We've seen that the TX on reset
> hangs but input works fine. I'm not sure if we ran into this with
> uart(4) but had a problem with sio(4).
No change.
Lars
___
fre
Hi,
On Feb 19, 2013, at 16:03, Andriy Gapon wrote:
> Couple of thoughts:
> - is your kernel installed in the typical location?
yup.
> - what does the following produce?
> readelf -a -W /boot/kernel/kernel | fgrep shstrtab
> readelf -a -W /boot/kernel/kernel | fgrep SUNW_ctf
# readelf -
Hi,
On Feb 19, 2013, at 17:58, Adrian Chadd wrote:
> Try top -HS .. to try and break down the kernel threads.
ACPI is eating the cycles, according to top:
0 root 80 0K 496K - 2 1:13 27.88%
kernel{acpi_task_2}
0 root 80 0K 496K - 0 1:1
Hi,
did you ever figure this out? I'm seeing the same thing.
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Hi,
On Feb 19, 2013, at 13:37, "Eggert, Lars" wrote:
> On Feb 19, 2013, at 13:15, Lars Engels wrote:
>> You need to recompile your Kernel to use DTrace:
>> https://wiki.freebsd.org/DTrace
>
> I did. But I still get that error, even with the sample from the
Hi,
On Feb 19, 2013, at 13:15, Lars Engels wrote:
> You need to recompile your Kernel to use DTrace:
> https://wiki.freebsd.org/DTrace
I did. But I still get that error, even with the sample from the wiki:
# dtrace -n 'syscall:::entry { @num[execname] = count(); }'
dtrace: invalid probe specifi
Hi,
thanks for looking into this!
On Feb 19, 2013, at 12:14, Andriy Gapon wrote:
> Please try to run the following DTrace script (dtrace -s script-file) and
> capture its output.
I get this error:
# dtrace -s x
dtrace: failed to compile script x: "/usr/lib/dtrace/psinfo.d", line 90: failed
to
Hi,
On Feb 19, 2013, at 11:21, Fleuriot Damien wrote:
> What about a newly build kernel without the line "device acpi" and without
> the options ACPI_DEBUG ?
> Hoping that this kernel:
> 1/ won't crash on boot
> 2/ will make the 20% cpu load and high interrupt rates disappear
I added "device at
Hi,
On Feb 19, 2013, at 10:54, Fleuriot Damien
wrote:
> And indeed we find your answer here, acpi0 firing up a lot of interrupts.
>
> Don't you get any message about that in dmesg -a or /var/log/messages ?
>
> I'd expect something like "interrupt storm blabla… source throttled blabla.."
nope.
Hi,
On Feb 19, 2013, at 10:40, Fleuriot Damien
wrote:
> What about reviewing top(1) ?
top shows the ~20% I mentioned:
last pid: 3176; load averages: 0.79, 0.80, 0.84
up 0+14:49:49 09:43:51
17 processes:
Hi,
I have a system running -CURRENT that in top(1) is showing ~20% CPU usage for
the system at all times. Any ideas what could be causing this, or how I would
go about diagnosing this further? Nothing in the logs.
Thanks,
Lars
PS: dmesg attached, in case it helps:
Copyright (c) 1992-2013 The
On Jan 31, 2013, at 15:54, Daniel Braniss wrote:
> a shot in the dark, but is /usr/home/elars/dst properly exported?
Yep, the NFS mount works fine when I use BOOTP with a root-path option
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.f
On Jan 31, 2013, at 12:53, Andre Oppermann
wrote:
> The interface doesn't have a name during loader stage. The kernel
> finds the interface to use based on the MAC address. You should
> set boot.netif.hwaddr as well in the kernel environment.
Done, no change. Here is what's in my loader enviro
On Jan 31, 2013, at 12:45, Andreas Nilsson
wrote:
> Just a shot in the dark, did you actually tell it to do the root mount ro,
> or try with the nfs share as rw?
ro
Lars
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
Hi,
On Jan 30, 2013, at 22:43, Craig Rodrigues wrote:
> What you need to do is, before the FreeBSD kernel boots, your
> loader needs to export some environment variables. This will trigger
> the various behaviors in the FreeBSD mount code.
the loader can export some environment variables (this
Hi,
On Jan 30, 2013, at 10:32, "Eggert, Lars" wrote:
> On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
>> In src/sys/boot/common/boot.c which is part of the loader (not the kernel),
>> if you look in the getrootmount() function,
>> you will see that the loader w
Hi,
On Jan 29, 2013, at 20:22, Craig Rodrigues wrote:
> What kind of architecture are you trying to do this on? Is this
> i386/amd64 or something else?
amd64
> I am not familiar with netboot compared to
> PXE. Is TFTP involved at all with netboot?
TFTP is not involved. The kernel gets boote
On Jan 29, 2013, at 10:13, Lars Eggert
wrote:
> On Jan 29, 2013, at 9:34, Craig Rodrigues wrote:
>> I recommend that you do not use ROOTDEVNAME, and instead
>> you should follow the instructions which I wrote and contributed to the
>> FreeBSD handbook:
>>
>> "PXE Booting with an NFS Root File S
Hi,
On Jan 29, 2013, at 9:34, Craig Rodrigues wrote:
> I recommend that you do not use ROOTDEVNAME, and instead
> you should follow the instructions which I wrote and contributed to the
> FreeBSD handbook:
>
> "PXE Booting with an NFS Root File System"
>
> http://www.freebsd.org/doc/en_US.ISO88
Hi,
On Jan 28, 2013, at 16:23, Ian Lepore wrote:
> Remove the BOOTP_NFSROOT option, it tells the bootp/dhcp code to keep
> querying the server until a root path is delivered. Without it, the
> ROOTDEVNAME option should get used (and I think even override a path
> from the server, if it delivers
Hi,
I'm trying to netboot a system where the root device is specified in the kernel
via ROOTDEVNAME:
options BOOTP
options BOOTP_NFSROOT
options BOOTP_NFSV3
options BOOTP_COMPAT
options BOOTP_WIRED_TO=em4
options ROOTDEVNAME=\"nfs:10.11.12.13:/usr/
Hi,
On Jan 23, 2013, at 17:04, Dimitry Andric wrote:
> CTS/RTS hardware flow control, maybe? E.g. add ":hw" to the default
> settings in /etc/gettytab, or make a specific entry with an added ":hw"
> setting.
nope, I don't even get a login prompt if I do that.
> If it is a physical serial conso
Hi,
I'm embarrassed to ask this newbie question, but I'm at my wit's end: I've
configured a serial console according to the handbook. I see the boot messages
and get the login prompt. But at no point during the boot process does the
console seem to accept any input, incl. when at the boot promp
Hi,
anyone see something similar before:
> ===> usr.sbin/zic/zdump (depend)
> rm -f .depend
> mkdep -f .depend -a-DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED
> -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\"/usr/share/zoneinfo\" -Demkdir=mkdir
> -I/usr/src/usr.sbin/zic/zdump/..
> -I/usr/src
72 matches
Mail list logo