Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

On Tue, Oct 23, 2018 at 08:54:24AM -0600, Warner Losh wrote: > On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > > > >> It would help to get output from loader lsdev -v comma

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > > https://bugs.freebsd.or

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

> On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > On 22.10.2018 12:27, Toomas Soome wrote: > >> It would help to get output from loader lsdev -v command. > current loader crashes on "lsdev" for me: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232483 (it is not > threadripper-related

loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

On 22.10.2018 12:27, Toomas Soome wrote: > It would help to get output from loader lsdev -v command. current loader crashes on "lsdev" for me: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232483 (it is not threadripper-related, my hardware is Intel Atom). -- // Lev Serebryakov signature

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

[I' unable to reproduce the under-Hyper-V early kernel crash for WITH_ZFS= (implicit) build that includes the for-loaders patch I was given to try.] On 2018-Oct-22, at 10:01 AM, Mark Millard wrote: > [I will note the the loader problem has been shown to > not be involved in the kernel problem th

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

[I will note the the loader problem has been shown to not be involved in the kernel problem that this "Subject:" was originally for.] On 2018-Oct-22, at 9:26 AM, Warner Losh wrote: > On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote: >> On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: >> >> >

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On Mon, Oct 22, 2018 at 6:39 AM Mark Millard wrote: > On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > > > On 22 Oct 2018, at 13:58, Mark Millard wrote: > >> > >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: > >>> > On 22 Oct 2018, at 06:30, Warner Losh wrote: > > On Sun, O

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: > On 22 Oct 2018, at 13:58, Mark Millard wrote: >> >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >>> On 22 Oct 2018, at 06:30, Warner Losh wrote: On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > >

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

> On 22 Oct 2018, at 13:58, Mark Millard wrote: > > On 2018-Oct-22, at 2:27 AM, Toomas Soome http://me.com/>> > wrote: >> >>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>> >>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >>> On Sun, Oct 21, 2018 at 8:57 PM Mark M

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: > >> On 22 Oct 2018, at 06:30, Warner Losh wrote: >> >> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >> >>> >>> >>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >>> freebsd-sta...@freebsd.org> wrote: >>> [I bui

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

> On 22 Oct 2018, at 06:30, Warner Losh wrote: > > On Sun, Oct 21, 2018 at 9:28 PM Warner Losh > wrote: > >> >> >> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >> freebsd-sta...@freebsd.org> wrote: >> >>> [I built based on WITHOUT_ZFS= for other

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On 2018-Oct-21, at 8:30 PM, Warner Losh wrote: > On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable > wrote: >> [I built based on WITHOUT_ZFS= for other reasons. But, >> after installing the build, Hyper-V based boots are

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: > > > On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < > freebsd-sta...@freebsd.org> wrote: > >> [I built based on WITHOUT_ZFS= for other reasons. But, >> after installing the build, Hyper-V based boots are >> working.] >> >> On

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < freebsd-sta...@freebsd.org> wrote: > [I built based on WITHOUT_ZFS= for other reasons. But, > after installing the build, Hyper-V based boots are > working.] > > On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > > > On 2018-Oct-20,

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

[I built based on WITHOUT_ZFS= for other reasons. But, after installing the build, Hyper-V based boots are working.] On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: > On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: > >> I attempted to jump from head -r334014 to -r339076 >> on a threadripper 19

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: > I attempted to jump from head -r334014 to -r339076 > on a threadripper 1950X board and the boot fails. > This is both native booting and under Hyper-V, > same machine and root file system in both cases. I did my investigation under Hyper-V aft

head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

I attempted to jump from head -r334014 to -r339076 on a threadripper 1950X board and the boot fails. This is both native booting and under Hyper-V, same machine and root file system in both cases. It fails just after the FreeBSD/SMP lines, reporting "kernel trap 9 with interrupts disabled". It fa