Re: AWS M5 ena issues [IGNORE]

2018-07-06 Thread Pete Wright
sorry - this was sent to incorrect list - please ignore.  sorry for the noise! -pete On 07/06/2018 16:22, Pete Wright wrote: hi there - this is in relation to this ticket: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 "ena driver causing kernel panics on AWS EC2" reading through

AWS M5 ena issues

2018-07-06 Thread Pete Wright
hi there - this is in relation to this ticket: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 "ena driver causing kernel panics on AWS EC2" reading through the thread, and Colin's blog post on the new M5 instance types, it looks like the issues people are running into are related to

Re: bhyve and freebsd memstick installer

2018-07-06 Thread tech-lists
On 06/07/2018 18:32, Rodney W. Grimes wrote: Untested, but since memstick is actually a "disk" image and not a "cdrom" image you should be able to do something like vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname Your memstick should show up as ada0, and your guest.img

Re: bhyve and freebsd memstick installer

2018-07-06 Thread Rodney W. Grimes
> Hello, > > context: freebsd-12-current server, amd64 > > I usually install a freebsd guest like this: > > sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img > -i -I FreeBSD-installation-dvd1.iso guestname > > I only have memstick.img - how do I either: > > 1. convert

bhyve and freebsd memstick installer

2018-07-06 Thread tech-lists
Hello, context: freebsd-12-current server, amd64 I usually install a freebsd guest like this: sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img -i -I FreeBSD-installation-dvd1.iso guestname I only have memstick.img - how do I either: 1. convert the memstick to

Re: em0 link fail

2018-07-06 Thread tech-lists
On 03/07/2018 18:47, Michael Butler wrote: On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I can't without the em0 interface stalling :-( On a guess, I tried reverting SVN r335303 but that didn't help.

Re: atomic changes break drm-next-kmod?

2018-07-06 Thread Hans Petter Selasky
On 07/06/18 11:14, Johannes Lundberg wrote: On Fri, Jul 6, 2018 at 9:49 AM Konstantin Belousov wrote: On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin mailto:j...@freebsd.org>> wrote:

Re: atomic changes break drm-next-kmod?

2018-07-06 Thread Johannes Lundberg
On Fri, Jul 6, 2018 at 9:49 AM Konstantin Belousov wrote: > On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: > > On 07/06/18 00:02, Warner Losh wrote: > > > > > > > > > On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > > > wrote: > > > > > > On 7/5/18

Re: atomic changes break drm-next-kmod?

2018-07-06 Thread Konstantin Belousov
On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: > On 07/06/18 00:02, Warner Losh wrote: > > > > > > On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > > wrote: > > > > On 7/5/18 12:36 PM, Konstantin Belousov wrote: > > > On Thu, Jul 05, 2018 at

Re: EFI booting from external USB pen drive

2018-07-06 Thread Rodney W. Grimes
> On 2018-07-06 04:17, Warner Losh wrote: > > On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes < > > freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > > >> > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: > >> > > >> > > [ Charset UTF-8 unsupported, converting... ] > >> > >> On 5 Jul 2018, at

CURRENT: building PkgBase for 11.2-RELENG on CURRENT fails

2018-07-06 Thread O. Hartmann
I fail to buildworld/buildkernel and package FreeBSD 11.2-RELENG on a CURRENT host (FreeBSD 12.0-CURRENT #165 r336013: Thu Jul 5 21:00:36 CEST 2018 amd64) with the error shown below. My aim is to have CURRENT building 11.1 and 11.2 packages for "base" and for the poudriere jails. This seems to

Re: EFI booting from external USB pen drive

2018-07-06 Thread Emmanuel Vadot
On 2018-07-06 09:34, Bjoern A. Zeeb wrote: On 6 Jul 2018, at 6:34, Emmanuel Vadot wrote: FAT12 can work with all EFI implementation, the problem is the size of the FAT12 part that sometimes causes problems. Ok, now that we are all on the same page, changing it to newfs_msdos -F 32 did not

Re: atomic changes break drm-next-kmod?

2018-07-06 Thread Niclas Zeising
On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > wrote: On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky

Re: EFI booting from external USB pen drive

2018-07-06 Thread Bjoern A. Zeeb
On 6 Jul 2018, at 6:34, Emmanuel Vadot wrote: FAT12 can work with all EFI implementation, the problem is the size of the FAT12 part that sometimes causes problems. Ok, now that we are all on the same page, changing it to newfs_msdos -F 32 did not make a change to my problem of the boot

Re: EFI booting from external USB pen drive

2018-07-06 Thread Emmanuel Vadot
On 2018-07-06 04:17, Warner Losh wrote: On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: > > > [ Charset UTF-8 unsupported, converting... ] > >> On 5 Jul 2018, at 17:19, Warner Losh wrote: > >> >