On Wed, Aug 08, 2018 at 01:42:07AM +0300, Konstantin Belousov wrote:
| On Tue, Aug 07, 2018 at 02:49:10PM -0700, Doug Ambrisko wrote:
| > On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
| > | On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
| > | > On Tue, Aug 7, 201
On Tue, Aug 07, 2018 at 02:49:10PM -0700, Doug Ambrisko wrote:
> On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
> | On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
> | > On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> | > > On Mon, 6 Aug 2018 at 11:27, Kyle
On Tue, Aug 07, 2018 at 08:29:49PM +0300, Konstantin Belousov wrote:
| On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
| > On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
| > > On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
| > >>
| > >> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin
On Tue, Aug 07, 2018 at 11:50:44AM -0500, Kyle Evans wrote:
> On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> > On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
> >>
> >> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov
> >> wrote:
> >> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Ev
On Tue, Aug 7, 2018 at 12:09 AM, Eitan Adler wrote:
> On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
>>
>> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov
>> wrote:
>> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Evans wrote:
>> >>
>> >> He now gets a little further, but ends up with th
On Mon, 6 Aug 2018 at 11:27, Kyle Evans wrote:
>
> On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov
> wrote:
> > On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Evans wrote:
> >>
> >> He now gets a little further, but ends up with the same panic due to
> >> efirtc_probe trying to get time to v
On Sun, Aug 5, 2018 at 5:43 AM, Konstantin Belousov wrote:
> On Sat, Aug 04, 2018 at 09:46:39PM -0500, Kyle Evans wrote:
>>
>> He now gets a little further, but ends up with the same panic due to
>> efirtc_probe trying to get time to verify the rtc's actually
>> implemented. What kind of approach
gt; >> >
> >> > After installing the latest current kernel I get the following panic:
> >> >
> >> > panic: mutex pmap not owned at ... efirt_machdep.c:255
> >> > cpuid =3
> >> > time = 1
> >> > ...
> >>
g panic:
>> >
>> > panic: mutex pmap not owned at ... efirt_machdep.c:255
>> > cpuid =3
>> > time = 1
>> > ...
>> > mtx_assert()
>> > efi_arch_enter()
>> > efirt_modevents()
>> > module_register_init()
>> >
On Sat, Aug 04, 2018 at 08:28:25PM +0100, Warner Losh wrote:
> When I looked at it, I'd assumed there would be VA range we'd assign to the
> PAs in the EFI table that at the loader and kernel would agree on. The DMAP
> does this on x64 and aarch64, but that's not an option for armv7 nor i386.
It i
On Sat, Aug 4, 2018, 8:21 PM Emmanuel Vadot wrote:
> On Sat, 04 Aug 2018 09:47:11 -0600
> Ian Lepore wrote:
>
> > On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote:
> > > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote:
> > > >
> > > > On Sat, 2018-08-04 at 18:22 +0300, Kon
On Sat, 04 Aug 2018 09:47:11 -0600
Ian Lepore wrote:
> On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote:
> > On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote:
> > >
> > > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote:
> > > >
> > > > On Sat, Aug 04, 2018 at
On Sat, 2018-08-04 at 18:43 +0300, Konstantin Belousov wrote:
> On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote:
> >
> > On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote:
> > >
> > > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote:
> > > >
> > > >
> > > > On Sa
On Sat, Aug 04, 2018 at 09:25:47AM -0600, Ian Lepore wrote:
> On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote:
> > On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote:
> > >
> > > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote:
> > > >
> > > > On Sat, 2018-08-04 at 08:56 -0
On Sat, 2018-08-04 at 18:22 +0300, Konstantin Belousov wrote:
> On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote:
> >
> > On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote:
> > >
> > > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote:
> > > >
> > > > On Sat, Aug 4, 2018 at 8:13 AM,
On Sat, Aug 04, 2018 at 09:58:43AM -0500, Kyle Evans wrote:
> On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote:
> > On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote:
> >> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov >> com> wrote:
> >> >
> >> > On Sat, Aug 04, 2018 at 08:05:24AM -0500,
On Sat, Aug 4, 2018 at 9:51 AM, Ian Lepore wrote:
> On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote:
>> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov > com> wrote:
>> >
>> > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote:
>> > >
>> > > On Sat, Aug 4, 2018 at 3:37 AM, Konstant
On Sat, 2018-08-04 at 08:56 -0500, Kyle Evans wrote:
> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov com> wrote:
> >
> > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote:
> > >
> > > On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov > > ail.com> wrote:
> > > >
> > > > On Fri,
On Sat, Aug 04, 2018 at 08:56:58AM -0500, Kyle Evans wrote:
> On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov
> wrote:
> > On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote:
> >> On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov
> >> wrote:
> >> > On Fri, Aug 03, 2018 at 11:27:02
On Sat, Aug 4, 2018 at 8:13 AM, Konstantin Belousov wrote:
> On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote:
>> On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov
>> wrote:
>> > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote:
>> >>
>> >> This seems odd- pmap lock is acqu
On Sat, Aug 04, 2018 at 08:05:24AM -0500, Kyle Evans wrote:
> On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov
> wrote:
> > On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote:
> >>
> >> This seems odd- pmap lock is acquired at [1], then asserted shortly
> >> later at [2]... I avoid som
On Sat, Aug 4, 2018 at 3:37 AM, Konstantin Belousov wrote:
> On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote:
>>
>> This seems odd- pmap lock is acquired at [1], then asserted shortly
>> later at [2]... I avoid some of this stuff as well as I can, but is it
>> actually possible for PCPU
On Fri, Aug 03, 2018 at 11:27:02PM -0500, Kyle Evans wrote:
> On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler wrote:
> > Hi all,
> >
> > After installing the latest current kernel I get the following panic:
> >
> > panic: mutex pmap not owned at ... efirt_machde
On Fri, Aug 3, 2018 at 10:10 PM, Eitan Adler wrote:
> Hi all,
>
> After installing the latest current kernel I get the following panic:
>
> panic: mutex pmap not owned at ... efirt_machdep.c:255
> cpuid =3
> time = 1
> ...
> mtx_assert()
> efi_
Hi all,
After installing the latest current kernel I get the following panic:
panic: mutex pmap not owned at ... efirt_machdep.c:255
cpuid =3
time = 1
...
mtx_assert()
efi_arch_enter()
efirt_modevents()
module_register_init()
mi_startup()
btext()
Unfortunately this appears to be early enough
25 matches
Mail list logo