Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ATF t_mlock() babylon5 kernel panics

To: Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: ATF t_mlock() babylon5 kernel panics
From: Jason Thorpe <thorpej%me.com@localhost>
Date: Thu, 14 Mar 2019 08:06:58 -0700

On Mar 14, 2019, at 5:44 AM, Robert Elz <kre%munnari.OZ.AU@localhost> wrote:
> 
>  am guessing at the UVMHIST_LOG() stuff (copy/paste/edit...)
> 
> Does all of this sound plausible, and reasonable to do ?
> Please do remember, that before this, I have never been
> anywhere near uvm or anything pmap related, so have mercy!

Great sleuthing, you pretty much nailed it.

-- thorpej

References:
- Re: ATF t_mlock() babylon5 kernel panics
  - From: Jason Thorpe
- Re: ATF t_mlock() babylon5 kernel panics
  - From: Robert Elz
- Re: ATF t_mlock() babylon5 kernel panics
  - From: Jason Thorpe
- ATF t_mlock() babylon5 kernel panics
  - From: Robert Elz
- Re: ATF t_mlock() babylon5 kernel panics
  - From: Robert Elz
- Re: ATF t_mlock() babylon5 kernel panics
  - From: Robert Elz

Prev by Date: strange libc symbol renaming issue
Next by Date: Re: ATF t_mlock() babylon5 kernel panics
Previous by Thread: Re: ATF t_mlock() babylon5 kernel panics
Next by Thread: Re: ATF t_mlock() babylon5 kernel panics
Indexes:

Home | Main Index | Thread Index | Old Index