[Bug 219957] FreeBSD Install freeze using UEFI

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957

--- Comment #5 from zheilb...@gmail.com ---
Minor update with some more evidence:

I managed to get the system to boot with the other HDD attached. Apparently
there was a GPT partition table on this HDD. Removing this table allowed the
system to boot normally.

Unfortunately, I didn't inspect the details of the table before removing it. I
still don't know the root cause of 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 220923] [boot] [panic] 11.1-RC3 Kernel panic during boot

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220923

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

-- 
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 220909] device_probe() isn't called for the midi device emu10kx

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220909

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-multimedia@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 219476] [i386] 11.1-PRERELEASE double faults due to low kern.kstack_pages default

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219476

Kubilay Kocak  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|a...@freebsd.org
 Status|New |In Progress
  Flags||mfc-stable11+

-- 
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 220947] sys/cam/cam_iosched.c: Fix a couple of typos in comments

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220947

Bug ID: 220947
   Summary: sys/cam/cam_iosched.c: Fix a couple of typos in
comments
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: f...@fabiankeil.de
CC: i...@freebsd.org

Created attachment 184637
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184637&action=edit
sys/cam/cam_iosched.c: Fix a couple of typos in comments

The attached patch fixes a couple of comment typos in sys/cam/cam_iosched.c.

The following unclear sentence from cam_iosched_get_write()
should probably be fixed as well but the intended meaning
wasn't obvious to me:
|  Limiting the queue depth like this will also limit
| the write throughput and give and reads that want to compete to
| compete unfairly."

In cam_iosched_next_bio() a comment still refers to
"the netflix scheduler" while it probably should refer
to "the dynamic I/O scheduler" to match the name change
done in r302163 and r302396.

Obtained from: ElectroBSD

-- 
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 220948] adaasync() should set ADA_STATE_WCACHE based on ADA_FLAG_CAN_WCACHE

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220948

Bug ID: 220948
   Summary: adaasync() should set ADA_STATE_WCACHE based on
ADA_FLAG_CAN_WCACHE
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch, regression
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: f...@fabiankeil.de
CC: k...@freebsd.org

Created attachment 184638
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184638&action=edit
adaasync(): Set ADA_STATE_WCACHE based on ADA_FLAG_CAN_WCACHE

The attached patch lets adaasync() set ADA_STATE_WCACHE based on
ADA_FLAG_CAN_WCACHE instead of ADA_FLAG_CAN_RAHEAD.

This fixes a regression introduced in r300207 which changed
the flag names.

Obtained from: ElectroBSD

-- 
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #89 from Don Lewis  ---
Created attachment 184641
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184641&action=edit
patch to move amd64 shared page to a lower address to avoid Ryzen problem with
executing code near user address upper limit

I've been doing a number of experiments with openjdk7 builds to try to better
characterize the Ryzen problem.

First I did a number of openjdk7 builds using cpuset to pin the build to
individual cores.  Using cpuset -l 0 to pin the build to the first thread on
core 0 would consistently cause a silent reboot on the first or second try. 
Pinning  the build to any of the other cores allowed me to successfully build
openjdk7.  I ran four builds on each of the other cores to make sure that I
wasn't just getting a successful build by chance.  Surprisingly, pinning the
build to the second thread on core 0 was also successful.  In any case, the
results were consistent with my earlier tests where I disabled SMT and also all
but two cores in the BIOS, since those tests always used the first thread on
core 0.

I tried building openjdk7 on all cores except the first thread of core 0 by
using cpuset -l 1-15 and was also successful.

Based on that positive result, I tried building my default set of ~1600 ports
with cpuset -l 1-15.  A little over two hours into the build, the llvm40 build
failed with the:
  _arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0")
causing the ports that depend on it to be skipped, but everything else built
successfully.  When I restarted poudriere, the llvm40 build succeeded, but the
system hung after about an hour while running java as part of the openjdk7
build.

Next I tried building with cpuset -l 2-15.  The only problem that I ran into is
that the gcc build failed with SIGBUS, causing its dependencies to be skipped. 
When I restarted poudriere, gcc5 and the remaining ports build successfully.

I wanted to try to eliminate the possibility of a subtle defect in core 0 as a
potential cause of the problem, so I tried adding
 hint.lapic.0.disabled=1
 hint.lapic.1.disabled=1
to /boot/loader.conf, but FreeBSD does not allow the BSP to be disabled B-(

The other thing that is unique about core 0 on my machine is that it looks like
all of the external interrupts (but not interprocessor interrupts) go there. 
The biggest source of those seemed to be hpet, but I couldn't figure out how to
disable that (other than maybe disabling ACPI totally).  When I tried
hint.hpet.0.clock=0, all of the CPUs got assigned interrupts from another
timer.

The next thing I tried was inspired by the Dragonfly patch.  At least some
thread implementations use signals to communicate between threads.  I'm not
familiar with OpenJDK, but it is possible that it is such an implementation, so
it might be a heavy signal user and spend a lot of cycles in the signal
trampoline code.  Our signal trampoline code is in a different location than
Dragonfly uses, but it is still close to (in the top page of) the top of user
memory.  Even though I got the impression that the Dragonfly patch addresses an
issue with SMT, it does involve an interaction between interrupts and execution
of code near the top of user memory.

As an experiment, I patched the kernel to move the location of the shared page
lower by PAGE_SIZE.  I'm not sure if it is necessary, but the page at the old
location has the same rwx permissions and is zero filled.  I don't know if the
bug is triggered by executing code close to the upper address boundary or close
to a permission boundary.  The preliminary results so far are very promising. 
With the patch applied, I am able to successfully build openjdk7 either
unpinned or pinned to the first thread of core 0.

I just kicked off an unpinned ~1600 port poudriere run.  I should have results
of that late today.

The patch is attached.

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


Problem reports for freebsd-bugs@FreeBSD.org that need special attention

2017-07-23 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
In Progress |192528 | pwd_mkdb fails if /etc/shells contains duplicates 
In Progress |196973 | sh(1) broken UTF-8 input  
In Progress |207109 | makefs includes a timestamp that prevents reprodu 
In Progress |212562 | stucking kyua test (/usr/tests/lib/libutil) on 10 
New |197876 | [devfs] an error in devfs leads to data loss and  
New |198797 | [PATCH] Added an option to install BSDstats to bs 
New |202290 | /usr/bin/vi conversion error on valid character   
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |204115 | freebsd-update: Add support for better user messa 
New |204545 | Adding quirk entry for some (Acer C720P Chromeboo 
New |205598 | [patch] sbin/md5.c param -c, convert to lowercase 
New |206386 | vendor/libarchive: directory traversal vulnerabil 
New |207940 | [patch] sys/boot/efi/boot1 select boot partition  
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210245 | [PATCH] Update etc/ntp.conf to eliminate failure  
New |210804 | installerconfig - using ZFS create in custom scri 
New |212561 | stucking kyua test (/usr/tests/sys/acl/01) with e 
New |214705 | Kernel panic trying to playback encrypted DVD, "F 
Open|183817 | [patch] [mac] [panic] kernel compiled with option 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|204121 | numa(4) is broken: "vm_page_alloc: missing page"  
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206585 | hpt_set_info possible buffer overflow 
Open|206754 | Out of bounds negative array index in iicrdwr 
Open|207248 | [patch] daemon(8): Add option to redirect stdout  
Open|212418 | kernel panic in _taskqgroup_adjust - uninitialize 
Open|217505 | [asmc] [patch] Add Support for Macbook Pro 8,1
In Progress |191348 | [mps] LSI2308 with WD3000FYYZ drives disappears a 
New |202316 | Add IANA vxlan port to /etc/services  
New |206386 | vendor/libarchive: directory traversal vulnerabil 
Open|206754 | Out of bounds negative array index in iicrdwr 

34 problems total for which you should take action.
___
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
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 220953] rwho/ruptime incorrectly included in rcmds package set

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220953

Bug ID: 220953
   Summary: rwho/ruptime incorrectly included in rcmds package set
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: pe...@freebsd.org

rwho, rwhod and ruptime are not part of the remote login suite (rsh, rlogin
etc).  

They should *not* be in the rcmds package which is disabled by default.  We
rely on rwho/rwhod/ruptime in the freebsd.org cluster.

-- 
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 220953] rwho/ruptime incorrectly included in rcmds package set

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220953

Peter Wemm  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|allanj...@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 210537] [patch] [feature request] set MIME type in cron-generated e-mails

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537

Mikhail Teterin  changed:

   What|Removed |Added

 Attachment #172959|0   |1
is obsolete||

--- Comment #4 from Mikhail Teterin  ---
Created attachment 184654
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184654&action=edit
cron-mime patch updated for the latest 10.3

This version merges in the recent addition of the ``-m mailfrom'' to 10.3.

-- 
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-07-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #90 from Don Lewis  ---
With my patch to relocate the shared page, I was finally able to get a
successful poudriere run.  It built 1596 ports in about 8 1/2 hours with no
errors.

I'm still not able to build lang/ghc, which I think is due to another problem
of some sort.  The SIGBUS error generated by the bootstrap compiler seems to be
totally repeatable.

I think my patch did introduce a new problem.  Whenever a process core dumps,
this new message gets logged:
  Failed to fully fault in a core file segment at VA 0x7fffe000 with size
0x2000 to be written at offset 0x7fef000 for process ghc

I'll try reverting the shared page size part of the change.

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