date:20180928

[Bug 231795] 12-ALPHA8 top SIGSEGV

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231795
   Summary: 12-ALPHA8 top SIGSEGV
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: gldisa...@gmail.com

Created attachment 197585
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197585=edit
tar zcvf top-core.tar.gz /usr/bin/top top.core

FreeBSD constans 12.0-ALPHA8 FreeBSD 12.0-ALPHA8 r338991 GENERIC  amd64

constans# gdb top top.core
GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from top...Reading symbols from
/usr/lib/debug//usr/bin/top.debug...done.
done.
[New LWP 102558]
Core was generated by `top'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  format_next_process (xhandle=0x213590 , get_userid=0x20f6a0
, flags=0)
at /usr/src/usr.bin/top/machine.c:895
895 if ((pp->ki_flag & P_INMEM) == 0) {
(gdb) bt
#0  format_next_process (xhandle=0x213590 , get_userid=0x20f6a0
, flags=0)
at /usr/src/usr.bin/top/machine.c:895
#1  0x0020e398 in main (argc=2147483647, argv=0x8007cd000) at
/usr/src/usr.bin/top/top.c:652
(gdb)

-- 
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 231794] Panic in ZFS due to arc related memory exhaustion

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231794
   Summary: Panic in ZFS due to arc related memory exhaustion
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: davewrobi...@gmail.com

Created attachment 197582
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197582=edit
Photo of backtrace

We are evaluating two servers based on the HP DL360 G10 (16 gigs RAM) and HP
DL380 G10 (32 gigs RAM) motherboards. We can routinely panic these machines by
putting them under load while running ZFS. Running six instances of bonnie++
and six instances of memtester (testing 2g) is enough to panic the DL360 in
around 15 minutes and the DL380 in 10-13 hours.

Reducing ARC dramatically using vfs.zfs.arc_min and vfs.zfs.arc_max seems to
mitigate this problem, at least after a day of testing under 12.0-A7. We are
testing now on 11.2-RELEASE which we will use in production.

Daiichi from Japan was here to help diagnose this problem, and has been in
contact with core team members who requested this bugzilla submission.

More panic photos available on request.

-- 
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 231791] daemon utility doesn't redirect SIGTERM to child process

2018-09-28 Thread bugzilla-noreply

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

--- Comment #3 from kus...@gmail.com ---
Problem is not in SIGTERM redirecton, problem is in not showing child process
output after SIGTERM

-- 
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 231791] daemon utility doesn't redirect SIGTERM to child process

2018-09-28 Thread bugzilla-noreply

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

kus...@gmail.com changed:

   What|Removed |Added

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

-- 
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 231793] panic: [pmc,4965] pm=0xfffff80480ff2400 runcount 0

2018-09-28 Thread bugzilla-noreply

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

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Unable to Reproduce
 Status|New |Closed

--- Comment #1 from Mark Johnston  ---
I realized that my kernel was somewhat newer than the world.  After rebuilding
everything I can't repro the problem anymore.  Will reopen if it resurfaces.

-- 
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 231791] daemon utility doesn't redirect SIGTERM to child process

2018-09-28 Thread bugzilla-noreply

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

--- Comment #2 from kus...@gmail.com ---
Hmmm... it's interesting that I receive SIGTERM in child process with confused
handlers of SIGTERM and SIGCHLD too, but I didn't detect it because I didn't
get child's output on SIGTERM (see Comment 1)

-- 
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 231791] daemon utility doesn't redirect SIGTERM to child process

2018-09-28 Thread bugzilla-noreply

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

--- Comment #1 from kus...@gmail.com ---
Also after resolving this bug there is a problem with child process output
after SIGTERM - "handle_term()" set "terminate = 1" on line 540, so "for (;;)"
loop on line 319 ends due to "if (terminate)" on line 337 and the daemon
process don't dublicate child's output from listen_child()

-- 
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 231793] panic: [pmc,4965] pm=0xfffff80480ff2400 runcount 0

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231793
   Summary: panic: [pmc,4965] pm=0xf80480ff2400 runcount 0
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ma...@freebsd.org

Created attachment 197581
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=197581=edit
core.txt

I can get an INVARIANTS kernel to crash reliably by running

# pmcstat -S inst_retired.any_p -T

and starting a -j32 buildkernel from a different shell.  It takes a minute or
so.   This is on ALPHA7.

-- 
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 231791] daemon utility doesn't redirect SIGTERM to child process

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231791
   Summary: daemon utility doesn't redirect SIGTERM to child
process
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: kus...@gmail.com

daemon utility doesn't redirect SIGTERM to child process. I think, the problem
is in the confused handlers of SIGTERM and SIGCHLD signals, see lines 207-215
of https://github.com/freebsd/freebsd/blob/master/usr.sbin/daemon/daemon.c :

memset(_term, 0, sizeof(act_term));
act_term.sa_handler = handle_term;
sigemptyset(_term.sa_mask);
sigaddset(_term.sa_mask, SIGCHLD);

memset(_chld, 0, sizeof(act_chld));
act_chld.sa_handler = handle_chld;
sigemptyset(_chld.sa_mask);
sigaddset(_chld.sa_mask, SIGTERM);

-- 
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 231746] lua loader does not work on PowerPC

2018-09-28 Thread bugzilla-noreply

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

Andreas Tobler  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|andre...@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 231746] lua loader does not work on PowerPC

2018-09-28 Thread bugzilla-noreply

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

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org

--- Comment #7 from Conrad Meyer  ---
Any idea what that error status decodes to?  Probably unaligned access but if
we can get a faulting address and turn it into a code location that might help.

-- 
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 231080] callout structure corruption and panic

2018-09-28 Thread bugzilla-noreply

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

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org
Summary|callout struture corruption |callout structure
   |and panic   |corruption and panic

-- 
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 231790] mips64: attempting to load a module results in relocation errors and crash

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231790
   Summary: mips64: attempting to load a module results in
relocation errors and crash
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ema...@freebsd.org

On an EdgeRouter Lite

uname -a: FreeBSD  12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338982+19c946c159e5(master) 
ERL  mips

# kldload /boot/kernel/geom_nop.ko
kldload: unexpected relocation type 3
kldload: unexpected relocation type 12
kldload: unexpected relocation type 11

cpu:0-Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
panic: trap
cpuid = 0
time = 1538152731
Uptime: 3h32m5s

Some examples of the relocations:
# for r in R_MIPS_REL32 R_MIPS_GPREL32 R_MIPS_16; do readelf -r
/boot/kernel/geom_nop.ko | grep $r | head -n 5; done
0028 00020003 R_MIPS_REL32 .rodata + 420
0184 00020003 R_MIPS_REL32 .rodata + 3a0
02a8 00020003 R_MIPS_REL32 .rodata + 420
0578 00020003 R_MIPS_REL32 .rodata + 2da4
05c8 00020003 R_MIPS_REL32 .rodata + 2da4
0034 004a000c R_MIPS_GPREL32  
__mtx_unlock_sleep + 0
004c 0063000c R_MIPS_GPREL32    + 0
0098 0004000c R_MIPS_GPREL32   .data + 0
00b0 003c R_MIPS_GPREL32   arc4random + 0
00d0 0009000c R_MIPS_GPREL32  0478 g_nop_orphan + 0
 00020001 R_MIPS_16    .rodata + 0
0020 00020001 R_MIPS_16    .rodata + 440
0040 00020001 R_MIPS_16    .rodata + 478
0060 00020001 R_MIPS_16    .rodata + 4b0
0080 00020001 R_MIPS_16    .rodata + 2dd0

-- 
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 231514] Potential null pointer deference in function ffec_alloc_mbufcl (sys/dev/ffec/if_ffec.c)

2018-09-28 Thread bugzilla-noreply

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

Andrey V. Elsukov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Assignee|b...@freebsd.org|a...@freebsd.org
 Status|New |Closed
 CC||a...@freebsd.org

--- Comment #3 from Andrey V. Elsukov  ---
Fixed in head/ and stable/11. Thanks!

-- 
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 231514] Potential null pointer deference in function ffec_alloc_mbufcl (sys/dev/ffec/if_ffec.c)

2018-09-28 Thread bugzilla-noreply

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

--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:

Author: ae
Date: Fri Sep 28 10:02:47 UTC 2018
New revision: 338992
URL: https://svnweb.freebsd.org/changeset/base/338992

Log:
  MFC r338857:
Fix possible NULL pointer dereference in ffec_alloc_mbufcl().

PR: 231514

Changes:
_U  stable/11/
  stable/11/sys/dev/ffec/if_ffec.c

-- 
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 231773] Nested jails: "IPv4 addresses clash"

2018-09-28 Thread bugzilla-noreply

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

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|j...@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 231773] Nested jails: "IPv4 addresses clash"

2018-09-28 Thread bugzilla-noreply

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

Bug ID: 231773
   Summary: Nested jails: "IPv4 addresses clash"
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: k...@freebsd.org

I recently upgraded one of my stable/11 machines to head (so what will be
stable/12 soon), and ran into an issue with my nested jails setup.

I run standard (i.e. non-vnet) jails, by assigning e.g. 172.16.4.2 to the
parent jail, and starting a jail with that IP address from within that jail
(basically, so I can delegate a jailed setup to other people).

That used to work on stable/11, but now it failed with ‘IPv4 addresses clash’.
To the extent that I understand the relevant code it looks like we try to
verify that no other jail uses the address we’re trying to assign to the new
jail.

I think this block tries to ensure we start at either the host system or the
vnet jail that’s hosting us. I suspect that’s just wrong, because we don’t do
that if VIMAGE is not enabled (and there’s no need either, because this check
will already have been done for the parent jail).

#ifdef VIMAGE
for (; tppr !=  tppr = tppr->pr_parent)
if (tppr->pr_flags & PR_VNET)
break;
#endif

I can work around the problem by resetting 'tppr = ppr;' just before the
FOREACH_PRISON_DESCENDANT() loop.
(The IPv6 code has exactly the same problem.)

Presumably the trigger for this is the enabling of VIMAGE in CURRENT.

-- 
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 175943] [PATCH] Add trim capability to gpart(8)

2018-09-28 Thread bugzilla-noreply

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

Eugene Grosbein  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|g...@freebsd.org
 CC||eu...@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 231457] Out of swap space on ZFS

2018-09-28 Thread bugzilla-noreply

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

Shane  changed:

   What|Removed |Added

 CC||free...@shaneware.biz

--- Comment #4 from Shane  ---
Actually, you don't have to use all your swap to get out of swap errors, they
also happen when too much ram is wired, this prevents any ram being swapped
in/out.

I started getting out of swap errors on 10.1 with 8G ram.

Look at "vm.stats.vm.v_wire_count * hw.page_size" at the time of getting out of
swap errors, this is the wired amount shown in top.

As I mentioned in bug #229764 max_wired is 30% so arc should be less than 70%
ram. Another thing that often wires ram is bhyve, so any guest ram should also
be considered when setting arc_max.

-- 
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 231795] 12-ALPHA8 top SIGSEGV

[Bug 231794] Panic in ZFS due to arc related memory exhaustion

[Bug 231791] daemon utility doesn't redirect SIGTERM to child process

[Bug 231791] daemon utility doesn't redirect SIGTERM to child process

[Bug 231793] panic: [pmc,4965] pm=0xfffff80480ff2400 runcount 0

[Bug 231791] daemon utility doesn't redirect SIGTERM to child process

[Bug 231791] daemon utility doesn't redirect SIGTERM to child process

[Bug 231793] panic: [pmc,4965] pm=0xfffff80480ff2400 runcount 0

[Bug 231791] daemon utility doesn't redirect SIGTERM to child process

[Bug 231746] lua loader does not work on PowerPC

[Bug 231746] lua loader does not work on PowerPC

[Bug 231080] callout structure corruption and panic

[Bug 231790] mips64: attempting to load a module results in relocation errors and crash

[Bug 231514] Potential null pointer deference in function ffec_alloc_mbufcl (sys/dev/ffec/if_ffec.c)

[Bug 231514] Potential null pointer deference in function ffec_alloc_mbufcl (sys/dev/ffec/if_ffec.c)

[Bug 231773] Nested jails: "IPv4 addresses clash"

[Bug 231773] Nested jails: "IPv4 addresses clash"

[Bug 175943] [PATCH] Add trim capability to gpart(8)

[Bug 231457] Out of swap space on ZFS

19 matches

Site Navigation

Mail list logo

Footer information