Date: Sat, 13 Jun 2020 03:35:34 -0700 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Unrelenting testplan D25219 Message-ID: <1650FF75-2B95-4CF6-B6B1-BDD2240CA09D@yahoo.com> In-Reply-To: <AC4D94CE-8AB0-4660-8BB9-BFB2874DC31A@googlemail.com> References: <876E685B-B3AC-4821-A88F-702ABA3D9812@yahoo.com> <5FE76178-4255-46B0-9A0D-F7640EFCBBE4@googlemail.com> <F1DC2AFB-0CC7-407D-A6C0-4E109590612E@unrelenting.technology> <C7D9957A-5C58-48FF-9601-7DD13DE9D89B@googlemail.com> <8414e0163e5cb2e9c4a4c7b02aa01666@unrelenting.technology> <5B8A58D0-9662-49DD-9CC3-226A3A92EFD6@googlemail.com> <abc05bea-ea4a-9189-611c-a1a0000182d8@selasky.org> <FE0813DD-29CA-4ADA-BD6B-963E3DC635B2@googlemail.com> <eHCAzXv-Rr39w3F-euypm4DrLx9jd88297x9hyHaNi_-VXR-ZiLdgFg6HvpI87aFLHGM_YcbOLADi0BLIR0jy557fbWDxKs4yIqf5ZfsDZ4=@protonmail.com> <26B03CE9-E91F-466B-9912-56CCB4E28817@unrelenting.technology> <19BAFE1A-8E07-47AB-81C9-C8BA21086AD1@googlemail.com> <460696d7-55b3-fcf9-74a8-910ffa89621a@selasky.org> <AC4D94CE-8AB0-4660-8BB9-BFB2874DC31A@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Jun-13, at 01:54, Klaus K=C3=BCchemann via freebsd-arm = <freebsd-arm at freebsd.org> wrote: > Am 13.06.2020 um 10:46 schrieb Hans Petter Selasky <hps@selasky.org>: >>=20 >> On 2020-06-13 10:42, Klaus K=C3=BCchemann wrote: >>> ------ mouse removed from the hub, then panic: ------ >>=20 >> Is the HUB you are using self-powered? >>=20 >> =E2=80=94HPS >=20 > I tried both : 1. :direct-connection of SSD-drive(without external = Hub) > and 2.: external Hub with Power > I=E2=80=99m using the Original Pi- power adapter=20 > and an UninterruptedPowerSupply. >=20 > the filesystem on the SSD is dd`d from the u-boot-uSD where I compiled = the kernel=20 > directly on the RPI(I removed every visible file from the dd`d uSD`s = msdos-partition except the efi). > `tried different efi-loaders..=20 Odd suggestion, try having /boot/loader.conf contain something like: kern.cam.boot_delay=3D10000 vfs.mountroot.timeout=3D10 vfs.root_mount_always_wait=3D1 If you are lucky enough that such makes it behave better, you could then try commenting out subsets of the 3 to isolate a minimal set of them that helps the most. =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?1650FF75-2B95-4CF6-B6B1-BDD2240CA09D>