> 21.01.2020, 20:10, "Nick Hibma" :
>> That (with the return added, thanks Cy) worked like a charm.
> Got committed in r357038.
> Thank you for the report!
Hi.
My machine was panicked on r357061 with in_epoch in netisr.c.
I can not capture screen.
--
Masachika ISHIZUKA
Let's try this again, this time with a subject line. It's late, almost bed
time and I'm forgetting subject lines.
Hi,
Has anyone seen this before? It started happening on two of my machines
this evening. Both machines are AMD (not intel). In both cases powerd was
caught with its hand in the c
Hi,
Has anyone seen this before? It started happening on two of my machines
this evening. Both machines are AMD (not intel). In both cases powerd was
caught with its hand in the cookie jar.
Fatal trap 12: page fault while in kernel mode^M
cpuid = 3; apic id = 03^M
fault virtual address = 0x90
21.01.2020, 20:10, "Nick Hibma" :
> That (with the return added, thanks Cy) worked like a charm.
Got committed in r357038.
Thank you for the report!
>
> Thanks for the fast response.
>
> Nick Hibma
> n...@van-laarhoven.org
>
> -- Open Source: We stand on the shoulders of giants.
>
>> On 21 Jan 202
On Thu, Jan 23, 2020 at 12:25 AM Rares Aioanei wrote:
>
> My bad, here's the link : https://imgur.com/45He1iy
>
> On Wed, Jan 22, 2020 at 8:04 PM Johan Hendriks wrote:
> >
> > These is no file attached. I think the mailing list stripped it off.
> > But i had an kernel panic also with Freebsd curr
My bad, here's the link : https://imgur.com/45He1iy
On Wed, Jan 22, 2020 at 8:04 PM Johan Hendriks wrote:
>
> These is no file attached. I think the mailing list stripped it off.
> But i had an kernel panic also with Freebsd currrent on virtualbox on a mac.
>
> My latetst build is 356985
>
>
>
>
