Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Jul 2020 08:18:53 -0700
From:      Vincent Milum Jr <freebsd-arm@darkain.com>
To:        Emmanuel Vadot <manu@bidouilliste.com>
Cc:        =?UTF-8?Q?Danilo_Eg=C3=AAa_Gondolfo?= <danilo@freebsd.org>,  freebsd-arm@freebsd.org
Subject:   Re: big.LITTLE status for rk3399/rockpro64?
Message-ID:  <CAOWUMWGjE9ttZmasMEJ9046Gq_FaOogWahsRRhhycp=GAefn0g@mail.gmail.com>
In-Reply-To: <20200714094519.f61b85e267d24c02f6a1c09f@bidouilliste.com>
References:  <878sfnz61y.wl-bsd@zeppelin.net> <CAOWUMWGY%2B=w%2B9jJ8yhb9Lew6MjGorVquvATgok1_fyRMUBS6vg@mail.gmail.com> <CAFU7VyNzbFbOP5rMuVEZiMpHs_pdaD3X0Cp0GJRZTyd2pXTHPQ@mail.gmail.com> <20200714094519.f61b85e267d24c02f6a1c09f@bidouilliste.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I can confirm that USB Mass Storage causes kernel panics ~50% of the time.
This happens during detection/initialization of the device.
Leaving the drive in during boot has the same chance of panic.
It is not 100%, as sometimes I can get the drive to register and use it.
I've yet to see any other USB device have an issue though.
I'm actively using a USB-3 hub with keyboard, mouse, and ethernet without
issue.

On Tue, Jul 14, 2020 at 12:45 AM Emmanuel Vadot <manu@bidouilliste.com>
wrote:

> On Mon, 13 Jul 2020 19:06:22 +0100
> Danilo Eg=C3=AAa Gondolfo <danilo@freebsd.org> wrote:
>
> > On Mon, Jul 13, 2020 at 6:27 PM Vincent Milum Jr <
> freebsd-arm@darkain.com>
> > wrote:
> >
> > > I'm curious about this, too. I recently got the Pinebook Pro up and
> > > running, and would like to start testing all 6 CPU cores for doing
> > > compilation tasks.
> > >
> > > On Mon, Jul 13, 2020 at 10:19 AM Josh Howard <bsd@zeppelin.net> wrote=
:
> > >
> > > > It looks like it's been a couple of months since there's been any
> news
> > > > around it. Anything in particular still needed as far as testing or
> > > > debugging that goes? I have a Rockpro64 and a RockPi4e (though I
> don't
> > > have
> > > > that booting yet.) that I could potentially test on.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > _______________________________________________
> > > > freebsd-arm@freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > > To unsubscribe, send any mail to "
> freebsd-arm-unsubscribe@freebsd.org"
> > > >
> > > _______________________________________________
> > > freebsd-arm@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org=
"
> > >
> >
> > The number of CPUs was limited here
> > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D360321
> >
> > If you remove the hw.ncpu from your loader.conf you'll be able to use a=
ll
> > the 6 cores.
> >
> > Although the commit message mentions a "known issue" with the big.LITTL=
E
> > architecture, I was able to use all the 6 cores to rebuild the entire
> > system and I didn't face any issue.
> >
> > Maybe manu@ could give us some context about that.
>
>  On rockpro64 it was (it's been a while since I've tested) very easy to
> trigger a panic doing anything usb related (sometimes just inserting a
> usb thumb drive would triggers it). This is why I've disabled the big
> cores on the rockpro64 image.
>
> --
> Emmanuel Vadot <manu@bidouilliste.com>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOWUMWGjE9ttZmasMEJ9046Gq_FaOogWahsRRhhycp=GAefn0g>