Re: which way to update export_args structure?

Brooks Davis wrote: > Yes, I think that's the right way foward. Thanks for following up. >Rick Macklem wrote: >> Just in case you missed it in the email thread, in your general question >> below... >> Did you mean/suggest that the fields of "struct export_args" be passed in as >> separate

DRM: radeonkms … can not be unloaded (kernel panic)) …

On 20/10/2018 00:01, Graham Perrin wrote: > kldunload radeonkms > > – results in a kernel panic. Found, at under 'drm-devel-kmod g20180822 screen freeze': >> … normally you never unload the graphics driver so we

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Matthew D. Fuller wrote: > On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of > Don Lewis, and lo! it spake thus: >> >> The first is that when I attempt to start a Virtualbox VM, the >> system panics. > > Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of Don Lewis, and lo! it spake thus: > > The first is that when I attempt to start a Virtualbox VM, the > system panics. Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460 -- Matthew Fuller (MF4839) |

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Don Lewis wrote: > On 20 Oct, Graham Perrin wrote: >> On 19/10/2018 23:47, Don Lewis wrote: >> >>> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >>> Windows 7 with >> networking configured as > NAT and the underlying adapter being Intel >> PRO/1000 >> MT

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 20 Oct, Graham Perrin wrote: > On 19/10/2018 23:47, Don Lewis wrote: > >> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >> Windows 7 with > networking configured as > NAT and the underlying adapter being Intel PRO/1000 > MT Desktop (82540EM). … > > No panic here.

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19/10/2018 23:47, Don Lewis wrote: > … when I attempt to start a Virtualbox VM, the system panics. … (guest) > Windows 7 with networking configured as > NAT and the underlying adapter being Intel PRO/1000 MT Desktop (82540EM). … No panic here. 32-bit Windows 7 guest with the same virtual

DRM: radeonkms no longer usable (and can not be unloaded (kernel panic)) following a switch to stable, FreeBSD 12.0-BETA1 r339438

$ uname -v FreeBSD 12.0-BETA1 r339438 GENERIC $ which xauth /usr/local/bin/xauth $ Radeon HD 7570M, HP EliteBook 8570p. Following the switch to STABLE I could no longer use a desktop environment. For example: service sddm onestart – results in endless repetition of two lines, comparable to

virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

It looks like there are a couple of problems here. The first is that when I attempt to start a Virtualbox VM, the system panics. The DDB backtrace seems to indicate that the panic is occuring inside the ng_ether module, which was being called due to a virtualbox doing an ioctl call. The VM

Re: OpenSSL 1.1.1 Update report (ongoing)

On 14/10/2018 19:31, Eric McCorkle wrote: More: * ImageMagick (unrelated to OpenSSL 1.1.1): This fails with the OpenMP option ticked, due to trying to link with the base ld. Can be fixed by setting CC, CXX, LD to a port-installed clang, clang++, lld. The port should probably do this

boot message: sendmsg on igb0: No buffer space available

Since starting to test HEAD, I noticed at bootup time I get the message in dmesg sendmsg on igb0: No buffer space available It seems innocuous enough in that I dont see any obvious issues.  Is it a symptom of some misconfiguration ? This originally was a releng11 box that I upgraded via source