Re: lib not found and found at the same time ?
On Wed, Nov 13, 2019 at 04:48:40PM -0500, mike tancsa wrote: > I was trying to upgrade (failed) and then re-install the > samba410-4.10.10 port on a RELENG12 box. One of the Samba libs shows > some output I dont understand on ldd > > ldd /usr/local/lib/nss_wins.so.1 > /usr/local/lib/nss_wins.so.1: > libwbclient.so.0 => /usr/local/lib/samba4/libwbclient.so.0 > (0x801003000) > libwinbind-client-samba4.so => not found (0) > libreplace-samba4.so => not found (0) > libcrypt.so.5 => /lib/libcrypt.so.5 (0x80066b000) > libc.so.7 => /lib/libc.so.7 (0x80024a000) > libwinbind-client-samba4.so => > /usr/local/lib/samba4/private/libwinbind-client-samba4.so (0x801213000) > libreplace-samba4.so => > /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) > > > There are 2 libs it says it cannot find, but then a few lines below it > says it found them ? First instance (not found) is probably the direct dependency, which is probably not found because nss_wins.so does not have rpath recorded. Then, I guess, some other library also depends on libwinbind-client-samba4.so, but this library has rpath. You can check this with readelf, look for DT_NEEDED and DT_RPATH* dynamic entries. > > ldd -av /usr/local/lib/nss_wins.so.1 > /usr/local/lib/nss_wins.so.1: > libwbclient.so.0 => /usr/local/lib/samba4/libwbclient.so.0 > (0x801003000) > libwinbind-client-samba4.so => not found (0) > libreplace-samba4.so => not found (0) > libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) > libc.so.7 => /lib/libc.so.7 (0x80024a000) > /usr/local/lib/samba4/libwbclient.so.0: > libwinbind-client-samba4.so => > /usr/local/lib/samba4/private/libwinbind-client-samba4.so (0x801213000) > libreplace-samba4.so => > /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) > libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) > libc.so.7 => /lib/libc.so.7 (0x80024a000) > /lib/libcrypt.so.5: > libc.so.7 => /lib/libc.so.7 (0x80024a000) > /usr/local/lib/samba4/private/libwinbind-client-samba4.so: > libreplace-samba4.so => > /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) > libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) > libc.so.7 => /lib/libc.so.7 (0x80024a000) > /usr/local/lib/samba4/private/libreplace-samba4.so: > libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) > libc.so.7 => /lib/libc.so.7 (0x80024a000) > > ---Mike > > > ___ > 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-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: Random system lockups with 12.1-STABLE r354241 amd64
Yesterday evening I fetched the lastest from svn stable (r354662), created a custom kernel configuration with the following options, and rebuilt everything; > include GENERIC ident MACBOOK # For full debugger support use (turn off in stable branch): options BUF_TRACKING # Track buffer history options DDB # Support DDB. options FULL_BUF_TRACKING # Track more buffer history options GDB # Support remote GDB. options DEADLKRES # Enable the deadlock resolver options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones options VERBOSE_SYSINIT=0 # Support debug.verbose_sysinit, off by default < Then this evening, another system hang, no debugger messages or any sort of output whatsoever! :-( The only upside is that I'm experiencing these hangs almost daily now, so going to try a process of elimination. The hangs generally seem to occur when I'm working using Sublime Text 3 (via the linuxulator), with an open xterm window or two with X11 (currently using the Intel video driver). So might try switching to modesetting video driver, or using an editor that is native, or ditch the graphical environment altogether and see if I still get issues working on the console. If anyone has any ideas on how else I may be able to track down the issue, please let me know! :-) Thanks, James On 07/11/2019 21:21, James Wright wrote: On 06/11/2019 23:42, Julian Elischer wrote: On 11/6/19 2:58 PM, James Wright wrote: Hi, [...] Can anyone offer some advice as to how I can track down this issue? The first question which I couldn't see from your dmesg is "do you have ht krnel debugger configured into your kernel?" Nope it isn't, I will build it in, is it just adding options KDB and DDB? Another problem I have is I don't seemt to get any crash dumps even though I have 'dumpdev="AUTO"' in my /etc/rc.conf, could this be due to my system using a swap file (md) rather than a dedicated swap partition? ___ 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"
lib not found and found at the same time ?
I was trying to upgrade (failed) and then re-install the samba410-4.10.10 port on a RELENG12 box. One of the Samba libs shows some output I dont understand on ldd ldd /usr/local/lib/nss_wins.so.1 /usr/local/lib/nss_wins.so.1: libwbclient.so.0 => /usr/local/lib/samba4/libwbclient.so.0 (0x801003000) libwinbind-client-samba4.so => not found (0) libreplace-samba4.so => not found (0) libcrypt.so.5 => /lib/libcrypt.so.5 (0x80066b000) libc.so.7 => /lib/libc.so.7 (0x80024a000) libwinbind-client-samba4.so => /usr/local/lib/samba4/private/libwinbind-client-samba4.so (0x801213000) libreplace-samba4.so => /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) There are 2 libs it says it cannot find, but then a few lines below it says it found them ? ldd -av /usr/local/lib/nss_wins.so.1 /usr/local/lib/nss_wins.so.1: libwbclient.so.0 => /usr/local/lib/samba4/libwbclient.so.0 (0x801003000) libwinbind-client-samba4.so => not found (0) libreplace-samba4.so => not found (0) libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) libc.so.7 => /lib/libc.so.7 (0x80024a000) /usr/local/lib/samba4/libwbclient.so.0: libwinbind-client-samba4.so => /usr/local/lib/samba4/private/libwinbind-client-samba4.so (0x801213000) libreplace-samba4.so => /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) libc.so.7 => /lib/libc.so.7 (0x80024a000) /lib/libcrypt.so.5: libc.so.7 => /lib/libc.so.7 (0x80024a000) /usr/local/lib/samba4/private/libwinbind-client-samba4.so: libreplace-samba4.so => /usr/local/lib/samba4/private/libreplace-samba4.so (0x801417000) libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) libc.so.7 => /lib/libc.so.7 (0x80024a000) /usr/local/lib/samba4/private/libreplace-samba4.so: libcrypt.so.5 => /lib/libcrypt.so.5 (0x800665000) libc.so.7 => /lib/libc.so.7 (0x80024a000) ---Mike ___ 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: NVMe timeout / aborting outstanding i/o (again)
On Wed, Nov 13, 2019 at 11:34 AM Theron wrote: > With latest 12.1-STABLE (r354687), I have file access 30 second hang > problem again when resuming from suspend, with dmesg: > > nvme0: Resetting controller due to a timeout. > nvme0: resetting controller > nvme0: aborting outstanding i/o > nvme0: aborting outstanding i/o > (...) > nvme0: aborting outstanding i/o > nvme0: aborting outstanding i/o > nvme0: nvme0: aborting outstanding i/o > async event occurred (type 0x0, info 0x00, page 0x01) > nvme0: aborting outstanding i/o > nvme0: aborting outstanding i/o > (...) > > I thought this was fixed with r351914 "MFC r351747: Implement nvme > suspend / resume for pci attachment." > There are three causes of timeouts this fixed: First, a prior MFC fixed a missed interrupt due to some difference in how some drives implemented read modify write of the MSI registers. Second, during suspend, we weren't properly shutting down the controller. Finally, there was a restoration of the controller that might have had power removed issue the commit also fixed. > Latest change, r354074 "MFC r352630: Make nvme(4) driver some more NUMA > aware.", looks suspicious, I'll test before vs. after that change when I > can. > > Is anyone else seeing this? > I've had no other reports of this, so it's a good one to test. I don't think it will matter, but I'm not sure of that. Warner ___ 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"
NVMe timeout / aborting outstanding i/o (again)
With latest 12.1-STABLE (r354687), I have file access 30 second hang problem again when resuming from suspend, with dmesg: nvme0: Resetting controller due to a timeout. nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o (...) nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: nvme0: aborting outstanding i/o async event occurred (type 0x0, info 0x00, page 0x01) nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o (...) I thought this was fixed with r351914 "MFC r351747: Implement nvme suspend / resume for pci attachment." Latest change, r354074 "MFC r352630: Make nvme(4) driver some more NUMA aware.", looks suspicious, I'll test before vs. after that change when I can. Is anyone else seeing this? Theron Tarigo ___ 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: syslogd truncating messages on FreeBSD >11.2-R
Thanks all.
Scott
On Wed, Nov 13, 2019 at 05:11:51PM +1100, Kubilay Kocak wrote:
> On 9/11/2019 2:08 pm, Scott wrote:
> > Hi,
> >
> > please let me know if there is a better forum for this.
> >
> > As of 11.3-RELEASE syslogd truncates all forwarded messages to 480 bytes for
> > IPV4 and 1180 for IPv6.
> >
> > The change occurs in the added code:
> >
> > switch (f->f_type) {
> > case F_FORW:
> > /* Truncate messages to RFC 5426 recommended size. */
> > dprintf(" %s", f->fu_forw_hname);
> > switch (f->fu_forw_addr->ai_addr->sa_family) {
> > #ifdef INET
> > case AF_INET:
> > dprintf(":%d\n",
> >
> > ntohs(satosin(f->fu_forw_addr->ai_addr)->sin_port));
> > iovlist_truncate(il, 480);
> > break;
> > #endif
> >
> > There's more code for IPv6 and the function iovlist_truncate itself.
> >
> > This change is not turned on by a switch and happens automatically, however
> > I
> > can't find it documented in UPDATING or the release notes. I would have
> > thought that any change in default behaviour of the system should at least
> > be
> > documented.
> >
> > Ideally this change would have been implemented via a switch given that the
> > RFC mentioned in the code (RFC 5426) does not mandate truncation, but
> > recommends it when the network MTU is not known.
> >
> > What's the best way to reach out to the maintainer to suggest a switch to
> > turn on this code?
> >
> > Thanks,
> > Scott
>
>
> Hi Scott,
>
> Looks like this came in in base r332510 [1] via:
>
> https://reviews.freebsd.org/D15011
>
> The commit log message and review history may provide additional context
> for the behaviour change (I haven't reviewed them)
>
> I have CC'd the committer on this email, but in the meantime, and if you
> wouldn't mind, it is worth reporting the issue via Bugzilla, so that we
> track it, and so others can find it.
>
> [1] https://svnweb.freebsd.org/changeset/base/332510
>
> --
> Regards,
>
> koobs
>
>
>
___
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"
