Date: Sun, 31 Mar 2024 19:59:51 +0100 From: Nuno Teixeira <eduardo@freebsd.org> To: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT Message-ID: <CAFDf7UKmW7dwWpfp5Aw3v9fd_G=g8WvnkOZ8EsgB2itPpri4SQ@mail.gmail.com> In-Reply-To: <ZghruPv71WIkoLnQ@ilythia.eden.le-fay.org> References: <ZghruPv71WIkoLnQ@ilythia.eden.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000ecd0160614f97a11 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, If you got a fan in your rpi4 box, you could try to overclock it. If not, there is a funcionality in config.txt to overclock it just for a few seconds at boot time. I can't remember the funtion but I'm looking at: https://www.raspberrypi.com/documentation/computers/config_txt.html Cheers, Lexi Winter <lexi@le-fay.org> escreveu (s=C3=A1bado, 30/03/2024 =C3=A0(s) 1= 9:45): > hello, > > i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapter for > the root disk: > > usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device > ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa) > ugen0.3: <ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA> at usbus0 > umass0 on uhub1 > umass0: <ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA, class 0/0, rev > 2.10/1.00, addr 2> on usbus0 > umass0: SCSI over Bulk-Only; quirks =3D 0x0100 > umass0:1:0: Attached to scbus1 > da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 > da0: <ASM1153U ASM1153USB3.0TOS 0> Fixed Direct Access SPC-4 SCSI device > da0: Serial Number 123456789019 > da0: 40.000MB/s transfers > da0: 228936MB (468862128 512 byte sectors) > da0: quirks=3D0x2<NO_6_BYTE> > > when connected via USB 2, this works fine. when connected via USB 3.0, > the device sometimes fails to attach on boot, causing mountroot to fail. > i can reproduce this reliably with both GENERIC-NODEBUG and a custom > modular kernel, and sometimes (but not every boot) with GENERIC. > > when the problem happens, with USB_DEBUG enabled, the kernel logs: > > uhub_reattach_port: port 2 reset failed, error=3DUSB_ERR_TIMEOUT > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2 > > however, if i boot with "boot -v", the device is reliably detected > correctly. since -v shouldn't cause any functional changes, i suspect > this may be some kind of timing issue. > > i've tried increasing some of the USB timings (hw.usb.timings.*) but > this didn't seem to have any effect. is there anything else i could try > that might affect this, or is this perhaps a known issue? > > thanks, lexi. > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000ecd0160614f97a11 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hello,</div><div><br></div><div>If you got a fan in y= our rpi4 box, you could try to overclock it.<br></div><div>If not, there is= a funcionality in config.txt to overclock it just for a few seconds at boo= t time.<br><br></div><div>I can't remember the funtion but I'm look= ing at:<br><a href=3D"https://www.raspberrypi.com/documentation/computers/c= onfig_txt.html">https://www.raspberrypi.com/documentation/computers/config_= txt.html</a><br><br></div><div>Cheers,<br></div></div><br><div class=3D"gma= il_quote"><div dir=3D"ltr" class=3D"gmail_attr">Lexi Winter <<a href=3D"= mailto:lexi@le-fay.org">lexi@le-fay.org</a>> escreveu (s=C3=A1bado, 30/0= 3/2024 =C3=A0(s) 19:45):<br></div><blockquote class=3D"gmail_quote" style= =3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding= -left:1ex">hello,<br> <br> i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapt= er for<br> the root disk:<br> <br> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASM= 1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa)<br> ugen0.3: <ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA> at usbus0<br> umass0 on uhub1<br> umass0: <ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA, class 0/0, rev 2.10/1.= 00, addr 2> on usbus0<br> umass0:=C2=A0 SCSI over Bulk-Only; quirks =3D 0x0100<br> umass0:1:0: Attached to scbus1<br> da0 at umass-sim0 bus 0 scbus1 target 0 lun 0<br> da0: <ASM1153U ASM1153USB3.0TOS 0> Fixed Direct Access SPC-4 SCSI dev= ice<br> da0: Serial Number 123456789019<br> da0: 40.000MB/s transfers<br> da0: 228936MB (468862128 512 byte sectors)<br> da0: quirks=3D0x2<NO_6_BYTE><br> <br> when connected via USB 2, this works fine.=C2=A0 when connected via USB 3.0= ,<br> the device sometimes fails to attach on boot, causing mountroot to fail.<br= > i can reproduce this reliably with both GENERIC-NODEBUG and a custom<br> modular kernel, and sometimes (but not every boot) with GENERIC.<br> <br> when the problem happens, with USB_DEBUG enabled, the kernel logs:<br> <br> uhub_reattach_port: port 2 reset failed, error=3DUSB_ERR_TIMEOUT<br> uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2<br> <br> however, if i boot with "boot -v", the device is reliably detecte= d<br> correctly.=C2=A0 since -v shouldn't cause any functional changes, i sus= pect<br> this may be some kind of timing issue.<br> <br> i've tried increasing some of the USB timings (hw.usb.timings.*) but<br= > this didn't seem to have any effect.=C2=A0 is there anything else i cou= ld try<br> that might affect this, or is this perhaps a known issue?<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 thanks, lexi.<br> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l= tr"><span style=3D"color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committ= er (ports)</span></div></div> --000000000000ecd0160614f97a11--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UKmW7dwWpfp5Aw3v9fd_G=g8WvnkOZ8EsgB2itPpri4SQ>