Date: Sat, 1 Oct 2022 11:08:05 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, freebsd-uboot@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <D0FDFFBD-0582-4A5D-83C2-F7456944FD60@yahoo.com> In-Reply-To: <20221001163323.GB97581@www.zefox.net> References: <20220929170927.GB80020@www.zefox.net> <6C5019EC-B4A8-448F-9A85-4A98BC46F7DD@yahoo.com> <20220930002742.GA81169@www.zefox.net> <7A431698-1A8C-44BA-AFA2-EF5BAA69574F@googlemail.com> <924ED901-F9EB-4CFE-8376-1C2653FB6EBE@yahoo.com> <97AB11F6-2F4D-4026-8A96-50FC68B6EF8C@googlemail.com> <20220930214234.GA86711@www.zefox.net> <B25A7647-D109-48C9-AFDB-DE3F5AB08C56@yahoo.com> <20221001152242.GA97581@www.zefox.net> <51B729B0-3792-4870-9DEA-3E47F8BCB37F@yahoo.com> <20221001163323.GB97581@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-1, at 09:33, bob prohaska <fbsd@www.zefox.net> wrote: > On Sat, Oct 01, 2022 at 09:12:23AM -0700, Mark Millard wrote: >> On 2022-Oct-1, at 08:22, bob prohaska <fbsd@www.zefox.net> wrote: >>=20 >>> On Fri, Sep 30, 2022 at 05:51:03PM -0700, Mark Millard wrote: >>>>=20 >>>> By the way, it looks like having the line: >>>>=20 >>>> CONFIG_CMD_LOG=3Dy >>>>=20 >>>> in files/rpi_arm64_fragment would try to build the >>>> log command into U-Boot. >>>>=20 >>>=20 >>> Done and working. Now to learn how to use it. >>=20 >> Good. >>=20 >> Have you tried the updated patch-common_usb.c that >> has the 3 mdelay(...) adjustments? Does it lead to >> avoiding the problem? Any change in observed >> behavior? >>=20 >>=20 > Not yet. >=20 > However, with logging enabled (but still not understood) > there are more mountroot failures. Here's a list of tries, > where > S means I issued shutdown -r=20 > P means I had to powercycle > R means I issued a reset to u-boot > L means the Pi got stuck in a loop > U means usb reset was issued > M means the Pi stopped at mountroot (self-reset) > B means I issued a boot at the loader prompt >=20 > The sequence was: > PRSSSSBSSSSULPMSSM >=20 > I've placed the log script at > http://nemesis.zefox.com/~fbsd/ with mountroot in the filename. >=20 > I'll try your patch next. >=20 A failure leading to mount root failure: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device = JMicron USB Mass Storage (0x152d:0x0577) usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage = device JMicron USB Mass Storage (0x152d:0x0577) Root mount waiting for: usbus1 usbd_req_re_enumerate: addr=3D5, set address failed! (USB_ERR_IOERROR, = ignored) Root mount waiting for: usbus1 usbd_setup_device_desc: getting device descriptor at addr 5 failed, = USB_ERR_IOERROR Root mount waiting for: usbus1 ugen1.5: <JMicron USB Mass Storage> at usbus1 umass0 on uhub2 umass0: <JMicron USB Mass Storage, class 0/0, rev 2.10/2.14, addr 5> on = usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0x8100 umass0:0:0: Attached to scbus0 uhub_reattach_port: device problem (USB_ERR_STALLED), disabling port 3 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error (probe0:umass-sim0:0:0:0): Retrying command, 3 more tries remain ugen1.6: <FTDI FT232R USB UART> at usbus1 ugen1.5: <JMicron USB Mass Storage> at usbus1 (disconnected) umass0: at uhub2, port 4, addr 5 (disconnected) (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error (probe0:umass-sim0:0:0:0): Retrying command, 2 more tries remain . . . da0: <SABRENT 0214> Fixed Direct Access SPC-4 SCSI device da0: Serial Number DD564198838F9 Another failure leading to such: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device = JMicron USB Mass Storage (0x152d:0x0577) usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage = device JMicron USB Mass Storage (0x152d:0x0577) usbd_req_re_enumerate: addr=3D5, set address failed! (USB_ERR_IOERROR, = ignored) Root mount waiting for: usbus1 Root mount waiting for: usbus1 usbd_setup_device_desc: getting device descriptor at addr 5 failed, = USB_ERR_IOERROR ugen1.5: <JMicron USB Mass Storage> at usbus1 umass0 on uhub2 umass0: <JMicron USB Mass Storage, class 0/0, rev 2.10/2.14, addr 5> on = usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0x8100 umass0:0:0: Attached to scbus0 Root mount waiting for: usbus1 CAM ugen1.6: <FTDI FT232R USB UART> at usbus1 ugen1.5: <JMicron USB Mass Storage> at usbus1 (disconnected) umass0: at uhub2, port 4, addr 5 (disconnected) (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error (probe0:umass-sim0:0:0:0): Retrying command, 3 more tries remain umass0: detached Yet another failure leading to such: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device = JMicron USB Mass Storage (0x152d:0x0577) usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage = device JMicron USB Mass Storage (0x152d:0x0577) usbd_req_re_enumerate: addr=3D5, set address failed! (USB_ERR_IOERROR, = ignored) Root mount waiting for: usbus1 Root mount waiting for: usbus1 usbd_setup_device_desc: getting device descriptor at addr 5 failed, = USB_ERR_IOERROR Root mount waiting for: usbus1 ugen1.5: <JMicron USB Mass Storage> at usbus1 umass0 on uhub2 umass0: <JMicron USB Mass Storage, class 0/0, rev 2.10/2.14, addr 5> on = usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0x8100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <SABRENT 0214> Fixed Direct Access SPC-4 SCSI device da0: Serial Number DD564198838F9 da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors) da0: quirks=3D0x2<NO_6_BYTE> ugen1.6: <FTDI FT232R USB UART> at usbus1 ugen1.5: <JMicron USB Mass Storage> at usbus1 (disconnected) umass0: at uhub2, port 4, addr 5 (disconnected) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 74 70 6d af 00 00 01 00=20 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <SABRENT 0214> s/n DD564198838F9 detached g_dev_taste: g_dev_taste(da0) failed to g_attach, error=3D6 (da0:umass-sim0:0:0:0): Periph destroyed umass0: detached All 3 got: usbd_req_re_enumerate: addr=3D5, set address failed! (USB_ERR_IOERROR, = ignored) as the first failure of the sequence. This establishes that U-Boot is not the only thing to have problems with your equipment. I'll note that the: da0: <SABRENT 0214> Fixed Direct Access SPC-4 SCSI device da0: Serial Number DD564198838F9 does not match other log files: da0: <SABRENT 1214> Fixed Direct Access SPC-4 SCSI device da0: Serial Number 000000000000A but it may well be an example of garbage-in/garbage-out. The same goes for the usual: umass0: SCSI over Bulk-Only; quirks =3D 0x8100 vs. the 3 odd examples: umass0: SCSI over Bulk-Only; quirks =3D 0xc105 umass0: SCSI over Bulk-Only; quirks =3D 0xc105 umass0: SCSI over Bulk-Only; quirks =3D 0x8101 You also got another "0 Storage Device(s) found". It again has the sequence for portstatus: 311, 311, (sequence of 5 instanced of:) 301 for: Manufacturer=20 Product U-Boot Root Hub SerialNumber=20 bind node usb1@1 So, just like the others. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0FDFFBD-0582-4A5D-83C2-F7456944FD60>