Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Marcelo Araujo]

2017-06-27 4:18 GMT+08:00 Guido Falsi :

> On 06/26/17 16:36, Marcelo Araujo wrote:
>
> Hi,
>>
>> Could you guys test this patch: https://reviews.freebsd.org/D11365?
>> Would it solve the issue?
>>
>>
> Hi,
>
> I confirm the patch fixes the problem for me.
>
> Thanks!
>
> --
> Guido Falsi 
>

Thanks all for the test, very appreciated!
I just committed it: r320390 with MFC for 3 days.

Also thanks trasz@ to point me out to this thread that I was not aware of.


Best,
-- 

-- 
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org    \/  \ ^
Power To Server. .\. /_)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/26/17 16:36, Marcelo Araujo wrote:


Hi,

Could you guys test this patch: https://reviews.freebsd.org/D11365?
Would it solve the issue?



Hi,

I confirm the patch fixes the problem for me.

Thanks!

--
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Peter Blok]

Marcelo,

This fix solved the problem for RPI-1B. I’ll do some more testing on other RPI 
and nanobsd variants.

Peter

> On 26 Jun 2017, at 16:36, Marcelo Araujo  wrote:
> 
> 
> 
> 2017-06-23 4:02 GMT+08:00 Guido Falsi  >:
> On 06/22/17 19:06, Guido Falsi wrote:
> On 06/22/17 18:38, Warner Losh wrote:
> 
> I'll followup as soon as I have easier use case to reproduce it. I first need 
> to revert to an image affected by the problem.
> 
> I have made a few more tests.
> 
> I am able to trigger this bug easily by running gpart.
> 
> I'm testing on a PCEngines APU2 board with SD memory card.
> 
> # gpart set -a active -i 1 mmcsd0
> active set on mmcsd0s1
> # fsck_ffs -n /dev/mmcsd0s1a
> ** /dev/mmcsd0s1a (NO WRITE)
> ** Last Mounted on /mnt
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> Segmentation fault
> # shutdown -r now
> /sbin/shutdown: Device not configured
> 
> also, if I open another shell I can't perform many other operations which are 
> not failing in the previous root shell:
> 
> > tail /var/log/messages
> /usr/bin/tail: Device not configured.
> 
> 
> BTW while testing this multiple times I also had the root shell segfault 
> while browsing history, so it should be quite easy to reproduce on your side 
> too. running the gpart set command triggers it every time, with slightly 
> different bu always disruptive symptoms.
> 
> There is a chance it only shows with these embedded systems storage 
> controllers though.
> 
> -- 
> Guido Falsi 
> ___
> freebsd...@freebsd.org  mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs 
> 
> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org 
> "
> 
> 
> Hi,
> 
> Could you guys test this patch: https://reviews.freebsd.org/D11365 
> ?
> Would it solve the issue?
> 
> Best,
> -- 
> 
> -- 
> Marcelo Araujo(__)
> ara...@freebsd.org  \\\'',)
> http://www.FreeBSD.org    \/  \ ^
> Power To Server. .\. /_)

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Marcelo Araujo]

2017-06-23 4:02 GMT+08:00 Guido Falsi :

> On 06/22/17 19:06, Guido Falsi wrote:
>
>> On 06/22/17 18:38, Warner Losh wrote:
>>
>
> I'll followup as soon as I have easier use case to reproduce it. I first
>> need to revert to an image affected by the problem.
>>
>
> I have made a few more tests.
>
> I am able to trigger this bug easily by running gpart.
>
> I'm testing on a PCEngines APU2 board with SD memory card.
>
> # gpart set -a active -i 1 mmcsd0
> active set on mmcsd0s1
> # fsck_ffs -n /dev/mmcsd0s1a
> ** /dev/mmcsd0s1a (NO WRITE)
> ** Last Mounted on /mnt
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> Segmentation fault
> # shutdown -r now
> /sbin/shutdown: Device not configured
>
> also, if I open another shell I can't perform many other operations which
> are not failing in the previous root shell:
>
> > tail /var/log/messages
> /usr/bin/tail: Device not configured.
>
>
> BTW while testing this multiple times I also had the root shell segfault
> while browsing history, so it should be quite easy to reproduce on your
> side too. running the gpart set command triggers it every time, with
> slightly different bu always disruptive symptoms.
>
> There is a chance it only shows with these embedded systems storage
> controllers though.
>
> --
> Guido Falsi 
> ___
> freebsd...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org"
>


Hi,

Could you guys test this patch: https://reviews.freebsd.org/D11365?
Would it solve the issue?

Best,
-- 

-- 
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org    \/  \ ^
Power To Server. .\. /_)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/22/17 19:06, Guido Falsi wrote:

On 06/22/17 18:38, Warner Losh wrote:


I'll followup as soon as I have easier use case to reproduce it. I first 
need to revert to an image affected by the problem.


I have made a few more tests.

I am able to trigger this bug easily by running gpart.

I'm testing on a PCEngines APU2 board with SD memory card.

# gpart set -a active -i 1 mmcsd0
active set on mmcsd0s1
# fsck_ffs -n /dev/mmcsd0s1a
** /dev/mmcsd0s1a (NO WRITE)
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
Segmentation fault
# shutdown -r now
/sbin/shutdown: Device not configured

also, if I open another shell I can't perform many other operations 
which are not failing in the previous root shell:


> tail /var/log/messages
/usr/bin/tail: Device not configured.


BTW while testing this multiple times I also had the root shell segfault 
while browsing history, so it should be quite easy to reproduce on your 
side too. running the gpart set command triggers it every time, with 
slightly different bu always disruptive symptoms.


There is a chance it only shows with these embedded systems storage 
controllers though.

--
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/22/17 18:38, Warner Losh wrote:



On Thu, Jun 22, 2017 at 2:26 AM, Guido Falsi > wrote:


On 06/21/17 16:59, Guido Falsi wrote:
> On 06/13/17 13:44, Peter Blok wrote:
>> Hi,
>>
>> For a while now, I’m not able to build a RPI1-B image from -stable. I 
have narrowed it dow to fix 318394, which adds a refresh option to geom_label. If I 
undo this fix in today’s stable it works ok. If I don’t I’m getting continuously:
>>
>> vm_fault: pager read error, pid 1 (init)
>> vnode_pager_generic_getpages_done: I/O read error 5
>>
>> I have looked at the fix and I can’t figure out why it breaks the code.
>>
>> And yes I have tried various other SD cards - they all have the same 
issue.
>>
>
> Hi,
>
> I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and
> APU2 boards, using compactflash and SD card storage respectively. The
> problem has appeared as soon as I started testing 11.1-BETA1 from the
> stable branch.
>
> Problem appears when I update the image, using a slightly modified
> version of the standard nanobsd update and updatep[12] scripts. My
> changes are not in the dd/gpart commands though, which are the same.
> gpart seems the most likely candidate though.
>
> I have just discovered this thread and I will test reverting r318394
> soon. Thanks to Peter for narrowing it down!
>
> Maybe this is related to having the disks mounted read-only?
>

I noticed that after the problem appears many commands, including
shutdown, start failing telling "device not configured" for all mounted
FSes. I'm even unable to "ls /dev".

Looks like the geom refresh changes devices from below the system in a
way which triggers this reaction.

I don't know the geom code and have been unable to find an immediate
problem in the commit mentioned above. I'd really like some help to know
where to look, or what kind of debugging information is needed.

This is quite a bad bug for people running NanoBSD and should be fixed
before the release.


So can I recreate this with the embedded-type NanoBSD image? If this 
change breaks NanoBSD, it will need to be reverted...




You should be able to reproduce it with a nanobsd image, then updating 
it using the standard script which dumps the new image in the "other" 
partition and uses gpart to configure the new partition as bootable.


I'm using a slightly modified update script which also mounts the new 
partition in /mnt  and performs some operations there. Then it dismounts 
the partition and launches the "gpart set -a active -i ${_to} 
${NANO_DRIVE}" command (which I suspect is exactly where the actual 
problem is happening).


I also tested reverting the change and can confirm that it makes the 
problem go away.


I'm sure it can be triggered by other gpart operations. I'm trying to 
understand exactly which operations.


I'll followup as soon as I have easier use case to reproduce it. I first 
need to revert to an image affected by the problem.


Thanks for your feedback!

--
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Warner Losh]

On Thu, Jun 22, 2017 at 2:26 AM, Guido Falsi  wrote:

> On 06/21/17 16:59, Guido Falsi wrote:
> > On 06/13/17 13:44, Peter Blok wrote:
> >> Hi,
> >>
> >> For a while now, I’m not able to build a RPI1-B image from -stable. I
> have narrowed it dow to fix 318394, which adds a refresh option to
> geom_label. If I undo this fix in today’s stable it works ok. If I don’t
> I’m getting continuously:
> >>
> >> vm_fault: pager read error, pid 1 (init)
> >> vnode_pager_generic_getpages_done: I/O read error 5
> >>
> >> I have looked at the fix and I can’t figure out why it breaks the code.
> >>
> >> And yes I have tried various other SD cards - they all have the same
> issue.
> >>
> >
> > Hi,
> >
> > I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and
> > APU2 boards, using compactflash and SD card storage respectively. The
> > problem has appeared as soon as I started testing 11.1-BETA1 from the
> > stable branch.
> >
> > Problem appears when I update the image, using a slightly modified
> > version of the standard nanobsd update and updatep[12] scripts. My
> > changes are not in the dd/gpart commands though, which are the same.
> > gpart seems the most likely candidate though.
> >
> > I have just discovered this thread and I will test reverting r318394
> > soon. Thanks to Peter for narrowing it down!
> >
> > Maybe this is related to having the disks mounted read-only?
> >
>
> I noticed that after the problem appears many commands, including
> shutdown, start failing telling "device not configured" for all mounted
> FSes. I'm even unable to "ls /dev".
>
> Looks like the geom refresh changes devices from below the system in a
> way which triggers this reaction.
>
> I don't know the geom code and have been unable to find an immediate
> problem in the commit mentioned above. I'd really like some help to know
> where to look, or what kind of debugging information is needed.
>
> This is quite a bad bug for people running NanoBSD and should be fixed
> before the release.
>

So can I recreate this with the embedded-type NanoBSD image? If this change
breaks NanoBSD, it will need to be reverted...

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/21/17 16:59, Guido Falsi wrote:
> On 06/13/17 13:44, Peter Blok wrote:
>> Hi,
>>
>> For a while now, I’m not able to build a RPI1-B image from -stable. I have 
>> narrowed it dow to fix 318394, which adds a refresh option to geom_label. If 
>> I undo this fix in today’s stable it works ok. If I don’t I’m getting 
>> continuously:
>>
>> vm_fault: pager read error, pid 1 (init)
>> vnode_pager_generic_getpages_done: I/O read error 5
>>
>> I have looked at the fix and I can’t figure out why it breaks the code.
>>
>> And yes I have tried various other SD cards - they all have the same issue.
>>
> 
> Hi,
> 
> I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and
> APU2 boards, using compactflash and SD card storage respectively. The
> problem has appeared as soon as I started testing 11.1-BETA1 from the
> stable branch.
> 
> Problem appears when I update the image, using a slightly modified
> version of the standard nanobsd update and updatep[12] scripts. My
> changes are not in the dd/gpart commands though, which are the same.
> gpart seems the most likely candidate though.
> 
> I have just discovered this thread and I will test reverting r318394
> soon. Thanks to Peter for narrowing it down!
> 
> Maybe this is related to having the disks mounted read-only?
> 

I noticed that after the problem appears many commands, including
shutdown, start failing telling "device not configured" for all mounted
FSes. I'm even unable to "ls /dev".

Looks like the geom refresh changes devices from below the system in a
way which triggers this reaction.

I don't know the geom code and have been unable to find an immediate
problem in the commit mentioned above. I'd really like some help to know
where to look, or what kind of debugging information is needed.

This is quite a bad bug for people running NanoBSD and should be fixed
before the release.

Thanks in advance!

-- 
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

vnode_pager_generic_getpages_done: I/O read error 5 caused by r318394 (was Re: FreeBSD 11.1-BETA1 Now Available)

[Guido Falsi]

On 06/13/17 13:44, Peter Blok wrote:
> Hi,
> 
> For a while now, I’m not able to build a RPI1-B image from -stable. I have 
> narrowed it dow to fix 318394, which adds a refresh option to geom_label. If 
> I undo this fix in today’s stable it works ok. If I don’t I’m getting 
> continuously:
> 
> vm_fault: pager read error, pid 1 (init)
> vnode_pager_generic_getpages_done: I/O read error 5
> 
> I have looked at the fix and I can’t figure out why it breaks the code.
> 
> And yes I have tried various other SD cards - they all have the same issue.
> 

Hi,

I'm seeing similar symptoms with NanoBSD images on PCEngines ALIX and
APU2 boards, using compactflash and SD card storage respectively. The
problem has appeared as soon as I started testing 11.1-BETA1 from the
stable branch.

Problem appears when I update the image, using a slightly modified
version of the standard nanobsd update and updatep[12] scripts. My
changes are not in the dd/gpart commands though, which are the same.
gpart seems the most likely candidate though.

I have just discovered this thread and I will test reverting r318394
soon. Thanks to Peter for narrowing it down!

Maybe this is related to having the disks mounted read-only?

Should I open a bug report to properly track this down?

P.S.  CCing freebsd-fs@

-- 
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-BETA1 Now Available

[Peter Blok]

Hi,

For a while now, I’m not able to build a RPI1-B image from -stable. I have 
narrowed it dow to fix 318394, which adds a refresh option to geom_label. If I 
undo this fix in today’s stable it works ok. If I don’t I’m getting 
continuously:

vm_fault: pager read error, pid 1 (init)
vnode_pager_generic_getpages_done: I/O read error 5

I have looked at the fix and I can’t figure out why it breaks the code.

And yes I have tried various other SD cards - they all have the same issue.

Peter


> On 12 Jun 2017, at 23:02, Ed Maste  wrote:
> 
> On 12 June 2017 at 00:43, Warner Losh  wrote:
>> 
>> aarch64 support isn't completely integrated into FreeBSD 11 yet.
> 
> A clarification: arm64/aarch64 support has been available as of
> FreeBSD 11.0 for Cavium ThunderX, and the SoftIron arm64 hardware is
> also supported now.
> 
> What we don't have yet is a project-produced SD card image for
> Raspberry Pi 3; until that happens you can use an image from
> raspbsd.org.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-BETA1 Now Available

[peter . blok]

Hi,

For a while now, I’m not able to build a RPI1-B image from -stable. I have 
narrowed it dow to fix 318394, which adds a refresh option to geom_label. If I 
undo this fix in today’s stable it works ok. If I don’t I’m getting 
continuously:

vm_fault: pager read error, pid 1 (init)
vnode_pager_generic_getpages_done: I/O read error 5

I have looked at the fix and I can’t figure out why it breaks the code.

And yes I have tried various other SD cards - they all have the same issue.

Peter


> On 12 Jun 2017, at 23:02, Ed Maste  wrote:
> 
> On 12 June 2017 at 00:43, Warner Losh  wrote:
>> 
>> aarch64 support isn't completely integrated into FreeBSD 11 yet.
> 
> A clarification: arm64/aarch64 support has been available as of
> FreeBSD 11.0 for Cavium ThunderX, and the SoftIron arm64 hardware is
> also supported now.
> 
> What we don't have yet is a project-produced SD card image for
> Raspberry Pi 3; until that happens you can use an image from
> raspbsd.org.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-BETA1 Now Available

[Ed Maste]

On 12 June 2017 at 00:43, Warner Losh  wrote:
>
> aarch64 support isn't completely integrated into FreeBSD 11 yet.

A clarification: arm64/aarch64 support has been available as of
FreeBSD 11.0 for Cavium ThunderX, and the SoftIron arm64 hardware is
also supported now.

What we don't have yet is a project-produced SD card image for
Raspberry Pi 3; until that happens you can use an image from
raspbsd.org.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-BETA1 Now Available

[Warner Losh]

On Sun, Jun 11, 2017 at 5:04 PM, Jonathan Chen  wrote:

> On 11 June 2017 at 00:34, Glen Barber  wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > The first BETA build of the 11.1-RELEASE release cycle is now available.
> >
> > Installation images are available for:
> >
> > o 11.1-BETA1 amd64 GENERIC
> > o 11.1-BETA1 i386 GENERIC
> > o 11.1-BETA1 powerpc GENERIC
> > o 11.1-BETA1 powerpc64 GENERIC64
> > o 11.1-BETA1 sparc64 GENERIC
> > o 11.1-BETA1 armv6 BANANAPI
> > o 11.1-BETA1 armv6 BEAGLEBONE
> > o 11.1-BETA1 armv6 CUBIEBOARD
> > o 11.1-BETA1 armv6 CUBIEBOARD2
> > o 11.1-BETA1 armv6 CUBOX-HUMMINGBOARD
> > o 11.1-BETA1 armv6 GUMSTIX
> > o 11.1-BETA1 armv6 RPI-B
> > o 11.1-BETA1 armv6 RPI2
> > o 11.1-BETA1 armv6 PANDABOARD
> > o 11.1-BETA1 armv6 WANDBOARD
> > o 11.1-BETA1 aarch64 GENERIC
> >
> > Note regarding arm/armv6 images: For convenience for those without
> > console access to the system, a freebsd user with a password of
> > freebsd is available by default for ssh(1) access.  Additionally,
> > the root user password is set to root.  It is strongly recommended
> > to change the password for both users after gaining access to the
> > system.
> [...]
>
> I was hoping for an aarch64 RPI3 image for SD cards to try out FreeBSD
> 11.1. There's a memstick image, but I don't think that will work for
> the RPI3?
>

aarch64 support isn't completely integrated into FreeBSD 11 yet.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 11.1-BETA1 Now Available

[Jonathan Chen]

On 11 June 2017 at 00:34, Glen Barber  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The first BETA build of the 11.1-RELEASE release cycle is now available.
>
> Installation images are available for:
>
> o 11.1-BETA1 amd64 GENERIC
> o 11.1-BETA1 i386 GENERIC
> o 11.1-BETA1 powerpc GENERIC
> o 11.1-BETA1 powerpc64 GENERIC64
> o 11.1-BETA1 sparc64 GENERIC
> o 11.1-BETA1 armv6 BANANAPI
> o 11.1-BETA1 armv6 BEAGLEBONE
> o 11.1-BETA1 armv6 CUBIEBOARD
> o 11.1-BETA1 armv6 CUBIEBOARD2
> o 11.1-BETA1 armv6 CUBOX-HUMMINGBOARD
> o 11.1-BETA1 armv6 GUMSTIX
> o 11.1-BETA1 armv6 RPI-B
> o 11.1-BETA1 armv6 RPI2
> o 11.1-BETA1 armv6 PANDABOARD
> o 11.1-BETA1 armv6 WANDBOARD
> o 11.1-BETA1 aarch64 GENERIC
>
> Note regarding arm/armv6 images: For convenience for those without
> console access to the system, a freebsd user with a password of
> freebsd is available by default for ssh(1) access.  Additionally,
> the root user password is set to root.  It is strongly recommended
> to change the password for both users after gaining access to the
> system.
[...]

I was hoping for an aarch64 RPI3 image for SD cards to try out FreeBSD
11.1. There's a memstick image, but I don't think that will work for
the RPI3?

Cheers.
-- 
Jonathan Chen 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

FreeBSD 11.1-BETA1 Now Available

[Glen Barber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The first BETA build of the 11.1-RELEASE release cycle is now available.

Installation images are available for:

o 11.1-BETA1 amd64 GENERIC
o 11.1-BETA1 i386 GENERIC
o 11.1-BETA1 powerpc GENERIC
o 11.1-BETA1 powerpc64 GENERIC64
o 11.1-BETA1 sparc64 GENERIC
o 11.1-BETA1 armv6 BANANAPI
o 11.1-BETA1 armv6 BEAGLEBONE
o 11.1-BETA1 armv6 CUBIEBOARD
o 11.1-BETA1 armv6 CUBIEBOARD2
o 11.1-BETA1 armv6 CUBOX-HUMMINGBOARD
o 11.1-BETA1 armv6 GUMSTIX
o 11.1-BETA1 armv6 RPI-B
o 11.1-BETA1 armv6 RPI2
o 11.1-BETA1 armv6 PANDABOARD
o 11.1-BETA1 armv6 WANDBOARD
o 11.1-BETA1 aarch64 GENERIC

Note regarding arm/armv6 images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

https://download.freebsd.org/ftp/releases/ISO-IMAGES/11.1/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "stable/11" branch.

A list of changes since 11.0-RELEASE are available on the stable/11
release notes:

https://www.freebsd.org/relnotes/11-STABLE/relnotes/article.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 11.1-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386 and aarch64
architectures.  Disk images may be downloaded from the following URL (or
any of the FreeBSD FTP mirrors):

https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-BETA1/

The partition layout is:

~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
-bios QEMU_EFI.fd -serial telnet::,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

 ap-south-1 region: ami-35136c5a
 eu-west-2 region: ami-b8b6a1dc
 eu-west-1 region: ami-7ec1dc18
 ap-northeast-2 region: ami-d04a96be
 ap-northeast-1 region: ami-fb9e929c
 sa-east-1 region: ami-b3543cdf
 ca-central-1 region: ami-befd42da
 ap-southeast-1 region: ami-4eb6352d
 ap-southeast-2 region: ami-14e7f177
 eu-central-1 region: ami-57389d38
 us-east-1 region: ami-b4035aa2
 us-east-2 region: ami-0cc0e669
 us-west-1 region: ami-c30022a3
 us-west-2 region: ami-267b725f

=== Vagrant Images ===

FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:

% vagrant init freebsd/FreeBSD-11.1-BETA1
% vagrant up

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases.  Systems running earlier
FreeBSD releases can upgrade as follows:

# freebsd-update upgrade -r 11.1-BETA1

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

# freebsd-update install

It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 10.x.  Alternatively, the user can install misc/compat10x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:

# shutdown -r now

Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:

# freebsd-update install

== ISO CHECKSUMS ==

o 11.1-BETA1 amd64 GENERIC:
  SHA512