Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jan 2018 10:38:04 -0700
From:      John Nielsen <lists@jnielsen.net>
To:        Maurizio Vairani <maurizio1018@gmail.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>, Daisuke Aoyama <aoyama@peach.ne.jp>
Subject:   Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.
Message-ID:  <3E242843-7D43-4A36-A448-E4B0DACB2AB4@jnielsen.net>
In-Reply-To: <CAN0zgYXfKjKo3CjjfbEX7oSrd2NXqU6kmSXy__OVPr0y3R2Log@mail.gmail.com>
References:  <CAN0zgYXfKjKo3CjjfbEX7oSrd2NXqU6kmSXy__OVPr0y3R2Log@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
[ resending from correct email address ]

> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani <maurizio1018@gmail.com> =
wrote:
>=20
> I am running
> # uname
> -a
>=20
> FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 =
04:48:52
> UTC 2018     =
root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64
>=20
> After compiling the kernel module as discussed in this thread :
> =
https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068272.ht=
ml
>=20
> I can boot FreeBSD via iSCSI using iPXE. But when the isboot, the =
iSCSI
> boot driver version 0.2.13, starts I receive a panic:
> https://mega.nz/#!tkVwBBKA!PUj14-Za6KCNaoo9hxuXORRLQoWkb4LMvTdUA1BorD4
>=20
> Any idea?

Bummer!=20

Aoyama-san-

Are you still maintaining isboot? Can you help debug this issue on =
FreeBSD 12-CURRENT?

Once we get it working I will update the port with whatever is needed =
and send you the patches in case you'd like to cut a new release.

Thank you!=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E242843-7D43-4A36-A448-E4B0DACB2AB4>