[Bug 238076] 13.0-CURRENT r341837 : RISC-V panic sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zrlock.c, line: 65

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238076

--- Comment #2 from Dennis Clarke  ---
Merely a follow up comment. 

Here is how I bring up the qemu virtual machine with a few extra disks
in order to test zpool and zfs functions : 

qemu-system-riscv64 -nographic \
-machine virt -smp 8 -m 12G -kernel bbl \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-device,rng=rng0 \
-drive
file=./20190107183100/riscv64_freebsd/disk.img,format=raw,index=0,media=disk,id=hd0
\
-device virtio-blk-device,drive=hd0 \
-drive
file=/usr/local/build/qemu_qcow2_test/d0.img,format=raw,index=1,media=disk,id=hd1
\
-device virtio-blk-device,drive=hd1 \
-drive
file=/usr/local/build/qemu_qcow2_test/d1.img,format=raw,index=2,media=disk,id=hd2
\
-device virtio-blk-device,drive=hd2 \
-drive
file=/usr/local/build/qemu_qcow2_test/d2.img,format=raw,index=3,media=disk,id=hd3
\
-device virtio-blk-device,drive=hd3 \
-device virtio-net-device,netdev=usernet \
-netdev user,id=usernet,hostfwd=tcp::1-:22

-- 
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 238076] 13.0-CURRENT r341837 : RISC-V panic sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zrlock.c, line: 65

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238076

--- Comment #3 from Dennis Clarke  ---
The panic is repeatable.

Seems to need a few tries to hit it on shutdown

ganymede# uname -a 
FreeBSD ganymede 13.0-CURRENT FreeBSD 13.0-CURRENT r341837 QEMU  riscv
ganymede# zpool status
  pool: rv64imafdc
 state: ONLINE
  scan: resilvered 861M in 0 days 00:05:14 with 0 errors on Thu May 23 15:20:49
2019
config:

NAMESTATE READ WRITE CKSUM
rv64imafdc  ONLINE   0 0 0
  mirror-0  ONLINE   0 0 0
vtbd1   ONLINE   0 0 0
vtbd2   ONLINE   0 0 0
spares
  vtbd3 AVAIL   

errors: No known data errors
ganymede# sysctl hw.machine hw.ncpu hw.machine_arch kern.smp.maxcpus
kern.smp.active kern.smp.disabled kern.smp.cpus
hw.machine: riscv
hw.ncpu: 8
hw.machine_arch: riscv64
kern.smp.maxcpus: 16
kern.smp.active: 1
kern.smp.disabled: 0
kern.smp.cpus: 8
ganymede# 
ganymede# uptime
12:07PM  up 1 day, 21:03, 1 user, load averages: 0.41, 0.25, 0.18
ganymede# 
ganymede# 
ganymede# 
ganymede# shutdown -p 'now'
Shutdown NOW!
shutdown: [pid 6028]
ganymede#   
*** FINAL System shutdown message from root@ganymede *** 

System going down IMMEDIATELY  



System shutdown time has arrived
May 25 12:07:57 ganymede shutdown[6028]: power-down by root: 
Stopping cron.
Waiting for PIDS: 561.
Stopping sshd.
Waiting for PIDS: 551.
90 second watchdog timeout expired. Shutdown terminated.
Sat May 25 12:09:34 UTC 2019
May 25 12:09:35 ganymede syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop... 
Syncing disks, vnodes remaining... 0 0 0 done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-2' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-4' to stop... done
All buffers synced.
Uptime: 1d21h5m29s
panic: solaris assert: zrl->zr_refcount == 0 (0x3 == 0x0), file:
/usr/src/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zrlock.c, line: 65
cpuid = 1
time = 1558786186
KDB: stack backtrace:
db_trace_self() at db_read_token+0x5e2
 pc = 0xffc00046539a ra = 0xffcc1d52
 sp = 0xffc06f85c7a0 fp = 0xffc06f85c9c0

db_read_token() at kdb_backtrace+0x2e
 pc = 0xffcc1d52 ra = 0xffc0002156ea
 sp = 0xffc06f85c9c0 fp = 0xffc06f85c9d0

kdb_backtrace() at vpanic+0x15a
 pc = 0xffc0002156ea ra = 0xffc0001d9f8c
 sp = 0xffc06f85c9d0 fp = 0xffc06f85ca10

vpanic() at panic+0x22
 pc = 0xffc0001d9f8c ra = 0xffc0001d9fc4
 sp = 0xffc06f85ca10 fp = 0xffc06f85ca30

panic() at assfail3+0x18
 pc = 0xffc0001d9fc4 ra = 0xffc0013ec590
 sp = 0xffc06f85ca30 fp = 0xffd005bb10a8

KDB: enter: panic
[ thread pid 0 tid 100108 ]
Stopped at  kdb_enter+0x3a: c.ebreak
db> bt
Tracing pid 0 tid 100108 td 0xffd0058d
db_trace_self() at db_trace_thread+0x3c
 pc = 0xffc00046539a ra = 0xffc00046542c
 sp = 0xffc06f85c448 fp = 0xffc06f85c478

db_trace_thread() at db_skip_to_eol+0x300
 pc = 0xffc00046542c ra = 0xffcbf8e4
 sp = 0xffc06f85c478 fp = 0xffc06f85c4a8

db_skip_to_eol() at db_skip_to_eol+0x414
 pc = 0xffcbf8e4 ra = 0xffcbf9f8
 sp = 0xffc06f85c4a8 fp = 0xffc06f85c598

db_skip_to_eol() at db_command_loop+0x74
 pc = 0xffcbf9f8 ra = 0xffcbff28
 sp = 0xffc06f85c598 fp = 0xffc06f85c5d8

db_command_loop() at db_read_token+0x4ba
 pc = 0xffcbff28 ra = 0xffcc1c2a
 sp = 0xffc06f85c5d8 fp = 0xffc06f85c818

db_read_token() at kdb_trap+0x122
 pc = 0xffcc1c2a ra = 0xffc000215e1c
 sp = 0xffc06f85c818 fp = 0xffc06f85c878

kdb_trap() at do_trap_supervisor+0x96
 pc = 0xffc000215e1c ra = 0xffc00046f064
 sp = 0xffc06f85c878 fp = 0xffc06f85c898

do_trap_supervisor() at cpu_exception_handler_supervisor+0x68
 pc = 0xffc00046f064 ra = 0xffc000465a28
 sp = 0xffc06f85c898 fp = 0xffc06f85c9d0

cpu_exception_handler_supervisor() at vpanic+0x16a
 pc = 0xffc000465a28 ra = 0xffc0001d9f9c
 sp = 0xffc06f85c9d0 fp = 0xffc06f85ca10

vpanic() at panic+0x22
 pc = 0xffc0001d9f9c ra = 0xffc0001d9fc4
 sp = 0xffc06f85ca

[Bug 233094] [meta] Base system tool chain modernization tracking

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233094
Bug 233094 depends on bug 233056, which changed state.

Bug 233056 Summary: [exp-run] Enable the new crtbegin/crtend in head
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233056

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |FIXED

-- 
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 238120] cron(8) doesn't set the HOME environment variable to users's home directory when command runs under regular user

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238120

Bug ID: 238120
   Summary: cron(8) doesn't set the HOME environment variable to
users's home directory when command runs under regular
user
   Product: Base System
   Version: 12.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: y...@freebsd.org

When crontab contains
> 10 *   *   *   * yuri env DISPLAY=:0.0 
> /usr/local/bin/bash /path/to/some/script

this script is run by cron(8) with HOME=/var/log

Once the field "who" in crontab is set to some user, cron(8) should also set
the "HOME" environment variable properly.

HOME=/var/log looks wrong in any case.

(Not sure if "root" also suffers from this problem.)


FreeBSD nohost 12.0-STABLE FreeBSD 12.0-STABLE r347548 GENERIC  amd64

-- 
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 238123] Swap usage in top(1) broken

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238123

Bug ID: 238123
   Summary: Swap usage in top(1) broken
   Product: Base System
   Version: 11.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: eu...@freebsd.org
CC: k...@freebsd.org

"top -w -o space" is supposed to show approximate swap usage per process
sorting list of processes by swap usage. This is what it shows for stable/11
r345946 (11.2-STABLE/amd64) with GENERIC kernel after swapoff(8) invocation:

last pid:  9909;  load averages:  0.35,  0.29,  0.27up 50+00:09:28 
22:31:18
59 processes:  1 running, 58 sleeping
CPU:  0.0% user,  0.0% nice,  2.0% system,  0.0% interrupt, 98.0% idle
Mem: 108M Active, 330M Inact, 317M Laundry, 1096M Wired, 60M Free
ARC: 118M Total, 17M MFU, 64M MRU, 32K Anon, 3162K Header, 34M Other
 53M Compressed, 192M Uncompressed, 3.65:1 Ratio
Swap:

  PID USERNAMETHR PRI NICE   SIZERES   SWAP STATETIMEWCPU
COMMAND
40557 squid 1  520 20752K 0K  9376K wait 0:00   0.00%

94177 eugen 1  200  7860K 0K  3080K wait 0:00   0.00%

58019 eugen 1  230  7860K 0K  3068K wait 0:00   0.00%

  992 eugen 1  230  7860K 0K  3064K wait 0:00   0.00%

26511 eugen 1  230  7860K 0K  2576K wait 0:00   0.00%

83131 eugen 1  210  7860K 0K  2576K wait 0:00   0.00%


top was restarted but numbers are same as before swapoff: it shows some
processes as swapped out but there is no swap 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 238123] per process swap usage in top(1) broken

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238123

Eugene Grosbein  changed:

   What|Removed |Added

Summary|Swap usage in top(1) broken |per process swap usage in
   ||top(1) broken

-- 
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 238123] per process swap usage in top(1) broken

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238123

--- Comment #1 from Eugene Grosbein  ---
The command should be "top -w -o swap" (s/space/swap).

-- 
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 238129] [toolchain] Please enable the type __float128 that is already supported by clang

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238129

Bug ID: 238129
   Summary: [toolchain] Please enable the type __float128 that is
already supported by clang
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: y...@freebsd.org

Since clang supports it and there is no equivalent 128-bit type currently
supported by clang, please enable it.

In the current ML conversation it has been revealed: "But from clang's
OSTargets.h file, it looks like 128 bit float support is never set to enabled
for FreeBSD." [1]


--References--

[1] hackers@ thread:
https://lists.freebsd.org/pipermail/freebsd-hackers/2019-May/054660.html

-- 
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 233281] IP forwarding clarification in rc.conf man-page

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233281

Allan Jude  changed:

   What|Removed |Added

 CC||allanj...@freebsd.org
 Resolution|--- |Works As Intended
 Status|New |Closed

--- Comment #2 from Allan Jude  ---
They are not equivalent, gateway_enable="YES" is a superset of
net.inet.ip.forwarding=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 212258] bootpool is not imported after reboot on a MBR partitioned drive

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212258

--- Comment #17 from Allan Jude  ---
(In reply to James B. Byrne from comment #16)
James, Your issue seems totally unrelated to the rest of this PR.

I am guessing your issue is that you do not have the 'GELI Boot' flag set on
your encrypted partitions, so you are not being prompted to decrypt them in the
loader.

Try: geli configure -g /dev/disk-partition-here

-- 
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 238131] strip(1) fails to strip the library: elf_update() failed: Invalid data buffer descriptor

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238131

Bug ID: 238131
   Summary: strip(1) fails to strip the library: elf_update()
failed: Invalid data buffer descriptor
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: y...@freebsd.org

The problem only occurs on i386.

Testcase: the port comms/quisk

Failure log:
http://beefy5.nyi.freebsd.org/data/120i386-default/502498/logs/quisk-4.1.39.log

-- 
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 238131] strip(1) fails to strip the library: elf_update() failed: Invalid data buffer descriptor

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238131

Mark Linimon  changed:

   What|Removed |Added

   Hardware|Any |i386

-- 
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 238129] [toolchain] Please enable the type __float128 that is already supported by clang

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238129

--- Comment #1 from Conrad Meyer  ---
Is there some reason the compiler should emulate a floating point mode that
doesn't exist on any hardware, rather than using a separate library like MPFR?

-- 
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 238129] [toolchain] Please enable the type __float128 that is already supported by clang

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238129

--- Comment #2 from Yuri Victorovich  ---
(In reply to Conrad Meyer from comment #1)

IMO, this question should be directed to the clang team. Once they have some
feature we shouldn't be second guessing their judgement.

-- 
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 237270] pam_opieaccess does not support IPv6, or documentation is lacking

2019-05-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237270

--- Comment #2 from Victor Sudakov  ---
How can I up this one? It's really annoying not to be able to skip one-time
passwords when logging in from a trusted IPv6-only host.

-- 
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"