Re: OpenZFS support merged

[Danilo Egêa Gondolfo]

On Tue, Aug 25, 2020 at 5:43 PM Matthew Macy  wrote:

> On Tue, Aug 25, 2020 at 9:36 AM Danilo Egêa Gondolfo 
> wrote:
> >
> > On Tue, Aug 25, 2020 at 3:39 AM Matthew Macy  wrote:
> >>
> >> r364746 merged OpenZFS support in to HEAD.
> >>
> >> The change should be transparent unless you want to use new features.
> >> I caution against 'zpool upgrade' for the next few weeks.
> >>
> >> https://svnweb.freebsd.org/base?view=revision=364746
> >>
> >> If you encounter problems please report them to me, Ryan Moeller, and
> -current.
> >> ___
> >> freebsd-hack...@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> >> To unsubscribe, send any mail to "
> freebsd-hackers-unsubscr...@freebsd.org"
> >
> >
> > Hi, that is good news.
> >
> > It seems that our boot loader will fail to boot after zpool upgrade. Is
> that a known issue?
>
> No. Unfortunately zstd support was merged in to openzfs very late in
> the CFT. Features needed for read like zstd need to be white listed in
> the loader and added to the support.
>
> -M
>
>
> > I've replicated my setup, root zfs over GELI, in a VM to avoid any
> surprise (phew!), and it booted fine after upgrading the system. Although
> it fails after zpool upgrade (yes, I know you've asked us to be cautious
> with zpool upgrade):
> >
> > ZFS: unsupported feature: org.freebsd:zstd_compress
> > ZFS: pool zroot is not supported
> > ZFS: can't find pool by guid
> >
> > Thank you!
>

Fair enough.

I believe it should be mentioned in the UPDATING file then. It's not clear
that it will happen if one zpool upgrades his/her pools.

Thank you.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: OpenZFS support merged

[Danilo Egêa Gondolfo]

On Tue, Aug 25, 2020 at 3:39 AM Matthew Macy  wrote:

> r364746 merged OpenZFS support in to HEAD.
>
> The change should be transparent unless you want to use new features.
> I caution against 'zpool upgrade' for the next few weeks.
>
> https://svnweb.freebsd.org/base?view=revision=364746
>
> If you encounter problems please report them to me, Ryan Moeller, and
> -current.
> ___
> freebsd-hack...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>

Hi, that is good news.

It seems that our boot loader will fail to boot after zpool upgrade. Is
that a known issue?

I've replicated my setup, root zfs over GELI, in a VM to avoid any surprise
(phew!), and it booted fine after upgrading the system. Although it fails
after zpool upgrade (yes, I know you've asked us to be cautious with zpool
upgrade):

ZFS: unsupported feature: org.freebsd:zstd_compress
ZFS: pool zroot is not supported
ZFS: can't find pool by guid

Thank you!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Vbox causing host crash/reboot on 12-current

[Danilo Egêa Gondolfo]

On Wed, Aug 8, 2018 at 5:25 PM Vladimir Kondratyev 
wrote:

> Hi
>
> I am sure that crashes was caused by SMAP as I am faced with them too.
> I have made following patch to fix panic (attached)
> Apply it to portstree and rebuild emulators/virtualbox-ose-kmod
>
> P.S. It is POC so no arch/SMAP autodetection
>
> On 8/7/18 6:14 PM, AN wrote:
> > Update:
> >
> > I found the revision:
> > https://svnweb.freebsd.org/base?view=revision=336876
> >
> > Use SMAP on amd64.
> >
> > Could this possibly cause VBox to crash and reboot the system?  Is
> > there a sysctl to disable?
> >
> > Thanks
> >
> > On Tue, Aug 7, 2018 at 10:46 AM, AN  wrote:
> >> I recently started having severe instability on a workstation with
> >> VirtualBox.  I'm not sure if it was caused by the recent large ports
> >> update, or a recent commit that affected SMAP.  I can't seem to find
> >> that revision, would someone please post it and also the workaround to
> >> disable it, I would like to try it after work and see if disabling it
> >> allows VBox to work.  Is anyone else seeing this effect with Vbox?
> >>
> >> What I'm seeing is that as soon as a VM is started it reboots the
> >> host, totally reproducible every time.  I tried to rebuild VBox and
> >> kmod, and also some qt5 ports but still not working.  Any help is
> >> appreciated, thanks for reading.
> >>
> >> Regards
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
>
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>


Same problem here, but I'm getting two different panics:

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address   = 0x28
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80c7e806
stack pointer   = 0x28:0xfe009ced64c0
frame pointer   = 0x28:0xfe009ced64f0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 42332 (VBoxNetAdpCtl)

and

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x804209ab8
fault code  = supervisor read data, protection violation
instruction pointer = 0x20:0x835cc164
stack pointer   = 0x28:0xfe00b33031f0
frame pointer   = 0x28:0xfe00b33031f0
code segment= base r
x0, limit 0xf, type
0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0

current process = 21985 (VBoxHeadless)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: buildkernel broken on if_ixl when EVDEV is enabled

[Danilo Egêa Gondolfo]

Hi,

check if you have 'options IXL_IW' in your kernel conf. It's removed from
GENERIC. I had the same problem here with my customized conf.

On Thu, Jun 21, 2018 at 11:43 PM, Pete Wright  wrote:

> howdy - just ran into an issue with building a kernel that has EVDEV
> enabled causing this error:
>
> --- kernel.full ---
> linking kernel.full
> ld: error: undefined symbol: ixl_iw_pf_init
> >>> referenced by if_ixl.c:900 (/usr/home/pete/git/freebsd/sy
> s/dev/ixl/if_ixl.c:900)
> >>>   if_ixl.o:(ixl_if_init)
>
> ld: error: undefined symbol: ixl_iw_pf_stop
> >>> referenced by if_ixl.c:920 (/usr/home/pete/git/freebsd/sy
> s/dev/ixl/if_ixl.c:920)
> >>>   if_ixl.o:(ixl_if_stop)
>
> ld: error: undefined symbol: ixl_iw_pf_attach
> >>> referenced by if_ixl.c:669 (/usr/home/pete/git/freebsd/sy
> s/dev/ixl/if_ixl.c:669)
> >>>   if_ixl.o:(ixl_if_attach_post)
>
> ld: error: undefined symbol: ixl_iw_pf_detach
> >>> referenced by if_ixl.c:711 (/usr/home/pete/git/freebsd/sy
> s/dev/ixl/if_ixl.c:711)
> >>>   if_ixl.o:(ixl_if_detach)
> *** [kernel.full] Error code 1
>
>
> building a standard GENERIC kernel works without issue.  my "EVDEV" kern
> conf has the following two lines added:
>
> options EVDEV_SUPPORT   # D10265 from phabricator
> device  evdev
>
> Not sure if anyone else has seen this?
>
> -pete
>
> --
> Pete Wright
> p...@nomadlogic.org
> @nomadlogicLA
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"