[Bug 215819] head r311147's clang 3.9.1 for powerpc64: locore.o generation messed up: generates R_PPC64_ADDR16_DS instead of R_PPC64_TOC16_DS with .toc

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215819

Bug ID: 215819
   Summary: head r311147's clang 3.9.1 for powerpc64: locore.o
generation messed up: generates R_PPC64_ADDR16_DS
instead of R_PPC64_TOC16_DS with .toc
   Product: Base System
   Version: CURRENT
  Hardware: powerpc
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: mar...@dsl-only.net

/boot/kernel/kernel for powerpc64 ends up with 0(r2) use and the like
where it should involve more like -32760 . Note that a devel/*binutils
must be used because the bootstrapped binutils has other problems.
(I intend a submittal for that as well at some point.)

[Note: In order to get this far I've got other workarounds for other
issues that allowed exploring for "the next problem".]

[I expect this submittal also applies to stable/11's clang 3.9.1 but
I've not explored that environment yet.]

It turns out that this 0(r2) type of code traces back to the locore.o
that is generated:

Using objdump on locore.o I see variations based on clang vs. xtoolchain,
including the below relative to .toc handling:
(- -> clang , + -> xtoolchain)

RELOCATION RECORDS FOR [.text]:
OFFSET   TYPE  VALUE 
. . .
-0046 R_PPC64_ADDR16_DS  .toc
+0046 R_PPC64_TOC16_DS  .toc
. . .
-0182 R_PPC64_ADDR16_DS  .toc
+0182 R_PPC64_TOC16_DS  .toc
. . .
-0916 R_PPC64_ADDR16_DS  .toc
. . .
+0916 R_PPC64_TOC16_DS  .toc
. . .

In the boot code (/boot/kernel/kernel) these match up with. . .

Disassembly of section .text:
00100160 <.__start> mfmsr   r20 # clang
vs.
Disassembly of section .text:
00100120 <.__start> mfmsr   r20 # xtoolchain

. . .
001001a4 <.__start+0x44> ld  r1,0(r2)   # 100160+46 clang
vs.
00100164 <.__start+0x44> ld  r1,-32760(r2)  # 100120+46 xtoolchain

. . .
001002e0  ld  r1,0(r2)  # 100160+182 clang
vs.
001002a0  ld  r1,-32760(r2) # 100120+182 xtoolchain

. . .
00100a74  ld  r1,0(r1) # 100160+916 clang
vs.
00100a34  ld  r1,-32760(r1)# 100120+916 xtoolchain

clang's code does not boot; xtoolchain's code does.

I do not know if clang's use of R_PPC64_ADDR16_DS here is somehow
specific to FreeBSD's variant or not. It may or may not need fixes
from llvm (based on my ignorance).

The actual failure example is (from a PowerMac G5 so-called
"Quad Core"):

Booting. . .
Kernel entry at 0x100160

Invalid memory access at   %SSR0: .001001b0   %SRR1:9000.3030

>From objdump:

001001a4 <.__start+0x44> ld  r1,0(r2)<<<=== !
booting xtoolchain based kernel has:   r1,-32760(r2) above <<<=== !
001001a8 <.__start+0x48> addir1,r1,16288
001001ac <.__start+0x4c> add r1,r1,r31
001001b0 <.__start+0x50> std r3,48(r1)


(Code from cross builds can be inspected even if one does not
have powerpc64 hardware.)


Showing the SRC_ENV_CONF file for cross-builds (amd64 -> powerpc64)
based on the (failing) clang and on using devel/powerpc64-binutils :
(It references a KERNCONF of mine that includes a standard one.)

# more ~/src.configs/src.conf.powerpc64-clang_altbinutils-bootstrap.amd64-host 
TO_TYPE=powerpc64
TOOLS_TO_TYPE=${TO_TYPE}
VERSION_CONTEXT=12.0
#
KERNCONF=GENERIC64vtsc-NODBG
TARGET=powerpc
.if ${.MAKE.LEVEL} == 0
TARGET_ARCH=${TO_TYPE}
.export TARGET_ARCH
.endif
#
WITH_CROSS_COMPILER=
WITHOUT_SYSTEM_COMPILER=
#
WITH_LIBCPLUSPLUS=
WITHOUT_BINUTILS_BOOTSTRAP=
WITH_CLANG_BOOTSTRAP=
WITH_CLANG=
WITH_CLANG_IS_CC=
WITH_CLANG_FULL=
WITH_CLANG_EXTRAS=
WITH_LLDB=
#
WITH_BOOT=
WITH_LIB32=
#
WITHOUT_ELFTOOLCHAIN_BOOTSTRAP=
WITHOUT_GCC_BOOTSTRAP=
WITHOUT_GCC=
WITHOUT_GCC_IS_CC=
WITHOUT_GNUCXX=
#
NO_WERROR=
WERROR=
MALLOC_PRODUCTION=
#
WITH_DEBUG_FILES=
#
#
# For TO (so-called "cross") stages . . .
# So-called-cross via ${TO_TYPE}-xtoolchain-gcc/${TO_TYPE}-gcc. . .
# TOOLS_TO_TYPE based on ${TO_TYPE}-xtoolchain-gcc related binutils. . .
#
CROSS_BINUTILS_PREFIX=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/
.if ${.MAKE.LEVEL} == 0
XAS=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/as
XAR=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ar
XLD=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ld
XNM=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/nm
XOBJCOPY=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/objcopy
XOBJDUMP=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/objdump
XRANLIB=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/ranlib
XSIZE=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/size
#NO-SUCH: XSTRINGS=/usr/local/${TOOLS_TO_TYPE}-freebsd/bin/strings
XSTRINGS=/usr/local/bin/${TOOLS_TO_TYPE}-freebsd-strings
.export XAS
.export XAR
.export XLD
.export XNM
.export XOBJCOPY
.export XOBJDUMP
.export XRANLIB

[Bug 215781] Calling pgrep "javafrom java process

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215781

--- Comment #4 from Brandon Barker  ---
I'll admit I'm curious as to why this isn't an issue when calling pgrep from
other shells, like tcsh: "pgrep tcsh" from tcsh.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 148675] [ata] [panic] kernel panics - reboots

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148675

--- Comment #2 from Hiren Panchasara  ---
Is this still valid?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 117733] [patch] [request] allow to tee(1) to sockets, descriptors

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=117733

Hiren Panchasara  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org

--- Comment #1 from Hiren Panchasara  ---
Links here are still valid for the patch. :-)
I am not sure if this is still worth pursuing but assigning to -net for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 17540] [nfs] NIS host lookups cause NFS mounts to wedge at boot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=17540

Hiren Panchasara  changed:

   What|Removed |Added

 Status|In Progress |Closed
 CC||hi...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #6 from Hiren Panchasara  ---
Been quite some time. Please reopen if this is still a problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 210466] [panic] Fatal trap 12: page fault while in kernel mode

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210466

Hiren Panchasara  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-virtualization@Free
   ||BSD.org

--- Comment #1 from Hiren Panchasara  ---
Assigning to virtualization list. Please reassign appropriately if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 171700] cannot record a crashdump whan FreeBSD panics, it panics while doing this again

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171700

Hiren Panchasara  changed:

   What|Removed |Added

 Resolution|--- |Unable to Reproduce
 CC||hi...@freebsd.org
 Status|In Progress |Closed

--- Comment #1 from Hiren Panchasara  ---
I am not sure whats special in your setup but this functionality works for me
and many others. Can you try to reprod this with latest FreeBSD version and
reopen the bug if the problem still exists?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 109277] [pppd] [patch] : kernel ppp(4) botches clist reservation in RELENG_6

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=109277

Hiren Panchasara  changed:

   What|Removed |Added

 CC||hi...@freebsd.org

--- Comment #4 from Hiren Panchasara  ---
Is this still a problem? If so, anyone willing to take a stab at it?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 207200] Page Fault - Fatal Trap 12

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207200

Hiren Panchasara  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
   Keywords||IntelNetworking

--- Comment #1 from Hiren Panchasara  ---
Can you reprod the problem? Seems like NFS and igb(4) are involved.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 181529] [panic] sysutils/devcpu-data: Panic after CPU microcode update

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181529

Hiren Panchasara  changed:

   What|Removed |Added

 CC||hi...@freebsd.org

--- Comment #6 from Hiren Panchasara  ---
Is this still valid?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 143324] [panic] vm_fault: fault on nofault entry, addr: c10a5000

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=143324

Hiren Panchasara  changed:

   What|Removed |Added

 CC||hi...@freebsd.org
 Status|In Progress |Closed
 Resolution|--- |Overcome By Events

--- Comment #1 from Hiren Panchasara  ---
Please reopen if this still happens.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 59772] [patch] ftpd(8)/FreeBSD 5: support for tcp_wrappers in daemon mode

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59772

Ngie Cooper  changed:

   What|Removed |Added

 CC||n...@freebsd.org

--- Comment #1 from Ngie Cooper  ---
I question the value of adding more code to ftpd when inetd already handles
wrap(3) properly.

I'm CCing myself on the bug so I keep track of it and I will consider fixing
the patch if I have time to work on this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215810] libbsnmptools: r311152 breaks bsnmpget functionality

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215810

Ngie Cooper  changed:

   What|Removed |Added

 CC||n...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 95559] RELENG_6: write(2) fails with EPERM on TCP socket under certain situations

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=95559

Hiren Panchasara  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |Feedback Timeout

--- Comment #7 from Hiren Panchasara  ---
Please reopen if needed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215727] [iscsi] target sends invalid NOP-out and drops connection if initiator doesn't reply

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215727

Mark Johnston  changed:

   What|Removed |Added

  Component|standards   |kern
   Assignee|freebsd-standards@FreeBSD.o |freebsd-bugs@FreeBSD.org
   |rg  |
 CC||ma...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215810] libbsnmptools: r311152 breaks bsnmpget functionality

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215810

Bug ID: 215810
   Summary: libbsnmptools: r311152 breaks bsnmpget functionality
   Product: Base System
   Version: 11.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: zarych...@plan-b.pwste.edu.pl
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Unfortunately, at least on amd64 bsnmpget is currently broken, but on i386 it
still seems to work fine.

# bsnmpget -M 1 -n -s public@x.x.x.x -v 1 -p get -o quiet
1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1
Segmentation fault

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215781] Calling pgrep "javafrom java process

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215781

Brandon Barker  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Not A Bug

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215781] Calling pgrep "javafrom java process

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215781

--- Comment #3 from Brandon Barker  ---
Aha, thanks, and sorry about that - I really should be more thorough in man
page checking between systems. Adding "-a" does indeed fix the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215798] clang: Include thread sanitizer (and all other available sanitizers)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215798

Bug ID: 215798
   Summary: clang: Include thread sanitizer (and all other
available sanitizers)
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: german...@gmail.com

Thread sanitizers where created to build safer/more secure code; it is my
opinion all available clang thread sanitizers should be readily usable from the
base system.

In particular, I'd ve very interested in having thread sanitizer included as
part of the base system, currently, when I try to compile using it, it gives me
this error (FreeBSD 11):

/usr/bin/ld: /usr/bin/../lib/clang/3.8.0/lib/freebsd/libclang_rt.tsan-x86_64.a:
No such file: No such file or directory

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215797] fs/fuse : allow_other & allow_root not restricted to root

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215797

Bug ID: 215797
   Summary: fs/fuse : allow_other & allow_root not restricted to
root
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ben.rub...@gmail.com

Hello,

>From Linux mount.fuse(8) :
CONFIGURATION
  Some options regarding mount policy can be set in /etc/fuse.conf :
user_allow_other
  Allow non-root users to specify allow_other or allow_root options 

>From FreeBSD mount_fusefs(8) :
allow_other
  Do not apply STRICT ACCESS POLICY. Only root can use this option.

I would like to see the Linux behaviour under FreeBSD, being able to allow
non-root users to use allow_other/allow_root option.

I then also think that it could be interesting to support allow_root :
allow_root
  This option is similar to allow_other but file access is limited to the user
mounting the filesystem and root. This option and allow_other are mutually
exclusive.

I need Fuse FS mounted by non-root users to be available to root (at least the
very first dir).
I then use this dirty quick tweak :

--- sys/fs/fuse/fuse_internal.c.orig
+++ sys/fs/fuse/fuse_internal.c
@@ -142,7 +142,7 @@
int denied = fuse_match_cred(data->daemoncred,
cred);

-   if (denied) {
+   if (denied && (cred->cr_uid)) {
return EPERM;
}
}

Would then be nice to be officially supported.

Many thanks !

Ben

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #39 from Ben RUBSON  ---
Strange, as if mbufs were "consumed" but not released.
And when devices are disconnected, can you reconnect to them properly ?
Or do you need to change their target name or to reboot, as explained in my
first message of this bug report ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 213155] possible kernel regression when running 11.0-RELEASE on KVM on AMD Opterons

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155

Martin Waschbüsch  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2133
   ||33

--- Comment #4 from Martin Waschbüsch  ---
It seems that PRs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214242

are similar or possibly identical to this issue.

However, all three PRs just hang there as 'New'.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 213155] possible kernel regression when running 11.0-RELEASE on KVM on AMD Opterons

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155

Martin Waschbüsch  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2142
   ||42

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215719] Scripts in /usr/share/dtrace/toolkit still use /usr/bin/perl

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215719

--- Comment #2 from verma...@interia.pl ---
Yep, but its better to fix this as its fast and simple or remove these tools
from base system if they they are unmaintained.

Regards,
vermaden

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 210141] Building sshd with WITHOUT_TCP_WRAPPERS=YES fails

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210141

Ngie Cooper  changed:

   What|Removed |Added

 CC||n...@freebsd.org
 Status|New |Open
URL||https://reviews.freebsd.org
   ||/D9049
   Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 215793] mpsutil show adapter gives incomplete output

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215793

Bug ID: 215793
   Summary: mpsutil show adapter gives incomplete output
   Product: Base System
   Version: 10.3-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: longw...@incore.de

The command "mpsutil show adapter" gives
mps0 Adapter:
  Board Name:
  Board Assembly:
   Chip Name: LSISAS2308
   Chip Revision:
   BIOS Revision: 7.39.02.00
   Firmware Revision: 20.00.07.00
 Integrated RAID: no

After applying the patch

--- mps_cmd.c.orig   2016-04-11 11:10:46.0 +0200
+++ mps_cmd.c   2017-01-05 09:59:39.0 +0100
@@ -365,8 +365,7 @@
req.Action = MPI2_CONFIG_ACTION_PAGE_READ_CURRENT;
req.PageAddress = PageAddress;
req.Header = header;
-   req.Header.PageLength = reply.Header.PageLength;
-   if (reply.Header.PageLength == 0)
+   if (req.Header.PageLength == 0)
req.Header.PageLength = 4;

len = req.Header.PageLength * 4;

the output looks better:

mps0 Adapter:
   Board Name: SAS9207-8i
   Board Assembly: H3-25412-00E
Chip Name: LSISAS2308
Chip Revision: ALL
BIOS Revision: 7.39.02.00
Firmware Revision: 20.00.07.00
  Integrated RAID: no

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #38 from Julien Cigar  ---
(In reply to Ben RUBSON from comment #37)

it only delayed the problem, .. but it would be interesting if you could test
on your side..!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #37 from Ben RUBSON  ---
And no improvements ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211990] iscsi fails to reconnect and does not release devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211990

--- Comment #36 from Julien Cigar  ---
(In reply to Ben RUBSON from comment #35)

yes, .. but only slightly as the machine has only 8GB of RAM

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 210141] Building sshd with WITHOUT_TCP_WRAPPERS=YES fails

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210141

--- Comment #2 from Sergey  ---
Please consider editing /usr/src/crypto/openssh/config.h file:

#define LIBWRAP 1

it's enable by default not checking WITHOUT_TCP_WRAPPERS=YES variable

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"