Theo de Raadt (2015-04-26 16:53 +0200):
> > Eivind Eide (2015-04-26 13:02 +0200):
> > > I've been trying to update this -current machine with the bsd.rd from the
> > > last 4 snapshots,
> > > the last being from "Sun Apr 26 02:22:08 MDT 2015".
> > > However this kernel immediately after reporting h
On Sun, Apr 26, 2015 at 01:02:49PM +0200, Eivind Eide wrote:
> I've been trying to update this -current machine with the bsd.rd
> from the last 4 snapshots,
> the last being from "Sun Apr 26 02:22:08 MDT 2015".
> However this kernel immediately after reporting how much ram I have
> panics with this
> Eivind Eide (2015-04-26 13:02 +0200):
> > I've been trying to update this -current machine with the bsd.rd from the
> > last 4 snapshots,
> > the last being from "Sun Apr 26 02:22:08 MDT 2015".
> > However this kernel immediately after reporting how much ram I have panics
> > with this message:
>
Eivind Eide (2015-04-26 13:02 +0200):
> I've been trying to update this -current machine with the bsd.rd from the
> last 4 snapshots,
> the last being from "Sun Apr 26 02:22:08 MDT 2015".
> However this kernel immediately after reporting how much ram I have panics
> with this message:
>
> fatal pr
I've been trying to update this -current machine with the bsd.rd from
the last 4 snapshots,
the last being from "Sun Apr 26 02:22:08 MDT 2015".
However this kernel immediately after reporting how much ram I have
panics with this message:
fatal protection fault (4) in supervisor mode
trap type
5 matches
Mail list logo