Re: unable to boot 11.2-BETA1 on BeagleBone

Hello Glen, On Wed, 16 May 2018 02:07:43 +, Glen Barber wrote: > Hi Christopher, > > On Wed, May 16, 2018 at 10:02:30AM +0800, Christopher Hall wrote: > > Hello Glen, > > > > On Tue, 15 May 2018 13:46:49 +, Glen Barber > > wrote: > > > On Sat, May

Re: unable to boot 11.2-BETA1 on BeagleBone

On Tue, May 15, 2018 at 09:26:01PM -0500, Mike Karels wrote: > > Hi Christopher, > > > On Wed, May 16, 2018 at 10:02:30AM +0800, Christopher Hall wrote: > > > Hello Glen, > > > > > > On Tue, 15 May 2018 13:46:49 +, Glen Barber wrote: > > > > > > > On Sat, May 12, 2018 at

Re: unable to boot 11.2-BETA1 on BeagleBone

> Hi Christopher, > On Wed, May 16, 2018 at 10:02:30AM +0800, Christopher Hall wrote: > > Hello Glen, > > > > On Tue, 15 May 2018 13:46:49 +, Glen Barber wrote: > > > > > On Sat, May 12, 2018 at 04:33:26PM -0500, Mike Karels wrote: > > > > I tried to boot 11.2-BETA1 on a

Re: unable to boot 11.2-BETA1 on BeagleBone

Hi Christopher, On Wed, May 16, 2018 at 10:02:30AM +0800, Christopher Hall wrote: > Hello Glen, > > On Tue, 15 May 2018 13:46:49 +, Glen Barber wrote: > > > On Sat, May 12, 2018 at 04:33:26PM -0500, Mike Karels wrote: > > > I tried to boot 11.2-BETA1 on a BeagleBone Black

Re: unable to boot 11.2-BETA1 on BeagleBone

Hello Glen, On Tue, 15 May 2018 13:46:49 +, Glen Barber wrote: > On Sat, May 12, 2018 at 04:33:26PM -0500, Mike Karels wrote: > > I tried to boot 11.2-BETA1 on a BeagleBone Black that had been > > running 11.1-RELEASE. It didn't boot, falling back to the EMMC > > (which

Re: unable to boot 11.2-BETA1 on BeagleBone

Hello Glen, On Tue, 15 May 2018 13:46:49 +, Glen Barber wrote: > On Sat, May 12, 2018 at 04:33:26PM -0500, Mike Karels wrote: > > I tried to boot 11.2-BETA1 on a BeagleBone Black that had been > > running 11.1-RELEASE. It didn't boot, falling back to the EMMC > > (which

Re: uptime / w coredumping on RELENG11 (i386 only)

On 15 May 2018, at 20:22, Mike Tancsa wrote: > > On 5/15/2018 2:10 PM, Mike Tancsa wrote: >> Wasnt sure if it was my VM, so i took a stock 11.1R installed it on a >> new VM and updated the sources to today. Stock GENERIC kernel >> >> ** this is i386 ** >> >> >> via truss

Re: uptime / w coredumping on RELENG11 (i386 only)

On 5/15/2018 2:10 PM, Mike Tancsa wrote: > Wasnt sure if it was my VM, so i took a stock 11.1R installed it on a > new VM and updated the sources to today. Stock GENERIC kernel > > ** this is i386 ** > > > via truss (w) > > access("/etc/localtime",R_OK)= 0 (0x0) >

uptime / w coredumping on RELENG11 (i386 only)

Wasnt sure if it was my VM, so i took a stock 11.1R installed it on a new VM and updated the sources to today. Stock GENERIC kernel ** this is i386 ** via truss (w) access("/etc/localtime",R_OK)= 0 (0x0) open("/etc/localtime",O_RDONLY,06605223677) = 5 (0x5) fstat(5,{

Re: Cores from 11.2 Beta1 w(1)

On Tue, May 15, 2018 at 10:17:25AM -0700, Rodney W. Grimes wrote: > > Just did my first install of 11.2 Beta1/i386 in a VM and right off the > get go w(1) cores, this also occurs when running from the i386 ISO > if you drop to a shell and type w so very easy to reproduce. > > What about adding

Cores from 11.2 Beta1 w(1)

Just did my first install of 11.2 Beta1/i386 in a VM and right off the get go w(1) cores, this also occurs when running from the i386 ISO if you drop to a shell and type w so very easy to reproduce. What about adding "debugging" as an option dist set to the releases, we ship this by default in

Re: unable to boot 11.2-BETA1 on BeagleBone

On Sat, May 12, 2018 at 04:33:26PM -0500, Mike Karels wrote: > I tried to boot 11.2-BETA1 on a BeagleBone Black that had been running > 11.1-RELEASE. It didn't boot, falling back to the EMMC (which isn't bootable, > a different problem). I was also unable to boot the snapshot from 12/20. > I see

Re: Upgrade to 11.2-BETA1: vboxdrv kernel modulo load leads to panic unless vbox ports be rebuilt

On Monday, May 14 at 05:39:33 CEST, Kevin Oberman wrote: > > Kernel modules are NOT guaranteed to work between kernels. It is > recommended that all kernel modules from ports and lsof be added to > PORTS_MODULES so they are re-built after each kernel update. Rebuild > virtualbox-ose-kmod, unload