Page fault in udp_usrreq.c:823

2018-06-20 Thread Peter Holm
20180620 10:32:47 all (1/1): udp.sh Kernel page fault with the following non-sleepable locks held: shared rw udpinp (udpinp) r = 0 (0xf80bbc808d78) locked @ netinet/in_pcb.c:2398 stack backtrace: #0 0x80c00733 at witness_debugger+0x73 #1 0x80c01b11 at witness_warn+0x461 #2

Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Ed Maste
Work is in progress to migrate fully to modern and permissively licensed components for the tool chain. This includes moving away from the three obsolete binutils components that are still in the base system (as, ld, objdump). objdump is a tool to report information about binary objects (such as he

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Brooks Davis
On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > Work is in progress to migrate fully to modern and permissively > licensed components for the tool chain. This includes moving away from > the three obsolete binutils components that are still in the base > system (as, ld, objdump). objdum

mount_smbfs stack overflow issue with long hostnames

2018-06-20 Thread Eric Joyner
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228354 Can someone look at fixing this for 12? Non-gracefully handling long names is a pretty bad bug. - Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

[CFT] tinderbox/universe building clang once

2018-06-20 Thread Bryan Drewery
https://people.freebsd.org/~bdrewery/patches/universe-one-clang.diff This will build clang once if any of the targets specified (or defaulted) require bootstrapping clang. It probably has some issues with LLD_BOOTSTRAP in some cases. It could be improved more in the future for reusing more of the

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Shawn Webb
On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > Work is in progress to migrate fully to modern and permissively > licensed components for the tool chain. This includes moving away from > the three obsolete binutils components that are still in the base > system (as, ld, objdump). objdum

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Ed Maste
On 20 June 2018 at 18:25, Shawn Webb wrote: > > Would you like me to quantify the compilation breakages due to the > full llvm toolchain switch? If so, I can do that after July 12th. Thanks Shawn, right now I'm interested specifically in llvm-objdump, with the goal of sorting it out in advance of

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Shawn Webb
On Wed, Jun 20, 2018 at 07:31:21PM -0400, Ed Maste wrote: > On 20 June 2018 at 18:25, Shawn Webb wrote: > > > > Would you like me to quantify the compilation breakages due to the > > full llvm toolchain switch? If so, I can do that after July 12th. > > Thanks Shawn, right now I'm interested speci

Re: [CFT] tinderbox/universe building clang once

2018-06-20 Thread Bryan Drewery
On 6/20/2018 2:08 PM, Bryan Drewery wrote: > https://people.freebsd.org/~bdrewery/patches/universe-one-clang.diff > > This will build clang once if any of the targets specified (or > defaulted) require bootstrapping clang. > The longterm plan does include making 'TARGET=arch1 make buildworld' an

ZFS: I/O error - blocks larger than 16777216 are not supported

2018-06-20 Thread KIRIYAMA Kazuhiko
Hi all, I've been reported ZFS boot disable problem [1], and found that this issue occers form RAID configuration [2]. So I rebuit with RAID5 and re-installed 12.0-CURRENT (r333982). But failed to boot with: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zroot gptzfsboo

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Alexander Richardson
On Wed, 20 Jun 2018 at 16:50 Brooks Davis wrote: > On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > > Work is in progress to migrate fully to modern and permissively > > licensed components for the tool chain. This includes moving away from > > the three obsolete binutils components th

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

2018-06-20 Thread Allan Jude
On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote: > Hi all, > > I've been reported ZFS boot disable problem [1], and found > that this issue occers form RAID configuration [2]. So I > rebuit with RAID5 and re-installed 12.0-CURRENT > (r333982). But failed to boot with: > > ZFS: i/o error - all block

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

2018-06-20 Thread Toomas Soome
> On 21 Jun 2018, at 06:34, Allan Jude wrote: > > On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote: >> Hi all, >> >> I've been reported ZFS boot disable problem [1], and found >> that this issue occers form RAID configuration [2]. So I >> rebuit with RAID5 and re-installed 12.0-CURRENT >> (r33398

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

2018-06-20 Thread KIRIYAMA Kazuhiko
At Wed, 20 Jun 2018 23:34:48 -0400, Allan Jude wrote: > > On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote: > > Hi all, > > > > I've been reported ZFS boot disable problem [1], and found > > that this issue occers form RAID configuration [2]. So I > > rebuit with RAID5 and re-installed 12.0-CURRENT >