Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Mar 2021 12:44:07 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>, Robert Crowston <crowston@protonmail.com>, Mike Karels <mike@karels.net>, bob prohaska <fbsd@www.zefox.net>
Subject:   Re: RPi4 Status and xorg behavior
Message-ID:  <A5A6AC0F-DE97-4EBC-84F8-FEEE5B2CF895@yahoo.com>
In-Reply-To: <3B29C885-7156-488A-99AD-DB43911470B9@yahoo.com>
References:  <BDF8C846-1CB3-421E-A8D5-25E0075C7106@yahoo.com> <20210307021628.GA99890@www.zefox.net> <AAA4E495-4E9E-4C55-A07E-74D9737EC15B@yahoo.com> <20210307155515.GA4591@www.zefox.net> <67BF2EAC-04AD-4822-99B2-48A99563331F@yahoo.com> <G5ZAfvg49jl5dj40HAnjmwoEKpVSuGp8KmiBrSY_EBLXou6UGBIjU3tVxUuPGKeCvXEovg2d3tqhIGOmQCyb7c3wKsUHJ8xrSasvwXfbqwk=@protonmail.com> <4B963C56-D7E9-42FE-8B8B-B8A425ACE78F@yahoo.com> <20210308011035.GA6603@www.zefox.net> <DB3CD5BA-337E-476F-9F0C-C70401F7D800@yahoo.com> <C500EE5B-B483-4580-8C7C-9B9B013D726B@googlemail.com> <20210308173045.GB13739@www.zefox.net> <258E57DD-2276-43FC-A531-A54E073F6D3E@googlemail.com> <27EAA28B-9F49-4496-897F-3A7C128441C9@yahoo.com> <9F5BC32D-C26E-40E0-8BAA-C4FCDE98685B@googlemail.com> <3B29C885-7156-488A-99AD-DB43911470B9@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> On 2021-Mar-8, at 12:24, Mark Millard <marklmi at yahoo.com> wrote:
>=20
> On 2021-Mar-8, at 12:02, Klaus K=C3=BCchemann <maciphone2 at =
googlemail.com> wrote:
>=20
>>=20
>>> Am 08.03.2021 um 20:47 schrieb Mark Millard <marklmi@yahoo.com>:
>>>=20
>>>=20
>>> FYI the 2021-Mar-04 snapshot:
>>>=20
>>> =
FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210304-483c6da3a20-257149.img=E2=80=
=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6
>>> =E2=80=A6..=20
>>>=20
>>> and so is not yet based on the 1.20210303 tagged
>>> firmware:
>>>=20
>>=20
>> Yes, thank you ,I know(=C2=B4ve tested both with & without 1.20210303 =
with 483c6da3a20-257149.img=20
>> on the 8GB-model )
>> e.g. unplugging the keyboard leads.. to the  crash reported here at =
boot time  :
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253981#c16
>> ( xhci-ring.c:498 ) if  1.20210303 is used=E2=80=A6
>=20
> I get no such crashes from my non-debug build based
> on main 14 bad9fa56620e (CommitDate: 2021-03-06
> 21:46:28 +0000) on a Rpi4B 8 GiByte:
>=20
> ugen0.3: <vendor 0x05e3 USB2.0 Hub> at usbus0 (disconnected)
> uhub2: at uhub1, port 3, addr 2 (disconnected)
> ugen0.4: <vendor 0x04d9 RPI Wired Keyboard 4> at usbus0 (disconnected)
> ukbd0: at uhub2, port 1, addr 3 (disconnected)
> ukbd0: detached
> uhid0: at uhub2, port 1, addr 3 (disconnected)
> uhid0: detached
> uhub2: detached
> ugen0.3: <vendor 0x05e3 USB2.0 Hub> at usbus0
> uhub2 on uhub1
> uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/32.98, addr 2> =
on usbus0
> uhub2: MTT enabled
> uhub2: 4 ports with 4 removable, self powered
> ugen0.4: <vendor 0x04d9 RPI Wired Keyboard 4> at usbus0
> ukbd0 on uhub2
> ukbd0: <vendor 0x04d9 RPI Wired Keyboard 4, class 0/0, rev 2.00/1.40, =
addr 3> on usbus0
> kbd1 at ukbd0
> uhid0 on uhub2
> uhid0: <vendor 0x04d9 RPI Wired Keyboard 4, class 0/0, rev 2.00/1.40, =
addr 3> on usbus0
>=20
> the USB keyboard works fine when plugged in. Things
> work no matter if it is plugged in or not, booting
> and normal operation.
>=20
> Is the crash only present for debug builds?
> If so, then non-debug may be doing some
> bad things internally, despite not crashing.
>=20
> At this point I've no clue what the context
> difference that matters is.
>=20
>>=20
>> .. (other issues came up)=E2=80=A6.
>> If you want, you could test that=E2=80=A6=20
>> I fixed that by replacing known working fw-file-combinations=20
>=20
>> while 1 thing is still unclear:
>> The time-counter delay from kernel-bootup reported by Bob,
>> maybe that=E2=80=99s a change in 14-current=E2=80=A6
>=20
> That timescale difference in the loader prompt
> timeout sequence I do see in my build.
>=20
>> ...no fun testing all that on different hw and OS-versions ;-)
>=20
>=20

I tried 13.0-RC1 with the rpi-firmware updated:

# uname -apKU
FreeBSD generic 13.0-RC1 FreeBSD 13.0-RC1 #0 =
releng/13.0-n244639-60e8939aa85: Fri Mar  5 06:52:59 UTC 2021     =
root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC  =
arm64 aarch64 1300139 1300139

root@generic:~ # strings /boot/msdos/start4.elf | grep VC_BUILD_ID_
VC_BUILD_ID_USER: dom
VC_BUILD_ID_TIME: 12:10:40
VC_BUILD_ID_VARIANT: start
VC_BUILD_ID_TIME: Feb 25 2021
VC_BUILD_ID_BRANCH: bcm2711_2
VC_BUILD_ID_HOSTNAME: buildbot
VC_BUILD_ID_PLATFORM: raspberrypi_linux
VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean)

Again: boots fine, no crashes, keyboard works fine,
including unplugging and plugging back in.

Note: It does get the large font display.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A5A6AC0F-DE97-4EBC-84F8-FEEE5B2CF895>