Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Mar 2024 20:03:53 +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:  <CAFDf7ULh8E_PTVCgUGbSyh70zE0eeArW0NKn%2BWQfoUgZR1mDEg@mail.gmail.com>
In-Reply-To: <CAFDf7UKmW7dwWpfp5Aw3v9fd_G=g8WvnkOZ8EsgB2itPpri4SQ@mail.gmail.com>
References:  <ZghruPv71WIkoLnQ@ilythia.eden.le-fay.org> <CAFDf7UKmW7dwWpfp5Aw3v9fd_G=g8WvnkOZ8EsgB2itPpri4SQ@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
(...)

initial_turbo
https://www.raspberrypi.com/documentation/computers/config_txt.html#overclocking

Nuno Teixeira <eduardo@freebsd.org> escreveu (domingo, 31/03/2024 à(s)
19:59):

> 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ábado, 30/03/2024 à(s) 19: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 = 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=0x2<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=USB_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.
>>
>
>
> --
> Nuno Teixeira
> FreeBSD Committer (ports)
>


-- 
Nuno Teixeira
FreeBSD Committer (ports)

[-- Attachment #2 --]
<div dir="ltr"><div>(...)</div><div><br></div><div>initial_turbo<br><a href="https://www.raspberrypi.com/documentation/computers/config_txt.html#overclocking">https://www.raspberrypi.com/documentation/computers/config_txt.html#overclocking</a><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Nuno Teixeira &lt;<a href="mailto:eduardo@freebsd.org">eduardo@freebsd.org</a>&gt; escreveu (domingo, 31/03/2024 à(s) 19:59):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><br></div><div>If you got a fan in your 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 boot time.<br><br></div><div>I can&#39;t remember the funtion but I&#39;m looking at:<br><a href="https://www.raspberrypi.com/documentation/computers/config_txt.html" target="_blank">https://www.raspberrypi.com/documentation/computers/config_txt.html</a><br><br></div><div>Cheers,<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Lexi Winter &lt;<a href="mailto:lexi@le-fay.org" target="_blank">lexi@le-fay.org</a>&gt; escreveu (sábado, 30/03/2024 à(s) 19:45):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hello,<br>
<br>
i&#39;m using 15.0 (f66a994d59) on an 4GB RPi4 with a USB&lt;&gt;SATA adapter for<br>
the root disk:<br>
<br>
usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa)<br>
ugen0.3: &lt;ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA&gt; at usbus0<br>
umass0 on uhub1<br>
umass0: &lt;ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA, class 0/0, rev 2.10/1.00, addr 2&gt; on usbus0<br>
umass0:  SCSI over Bulk-Only; quirks = 0x0100<br>
umass0:1:0: Attached to scbus1<br>
da0 at umass-sim0 bus 0 scbus1 target 0 lun 0<br>
da0: &lt;ASM1153U ASM1153USB3.0TOS 0&gt; Fixed Direct Access SPC-4 SCSI device<br>
da0: Serial Number 123456789019<br>
da0: 40.000MB/s transfers<br>
da0: 228936MB (468862128 512 byte sectors)<br>
da0: quirks=0x2&lt;NO_6_BYTE&gt;<br>
<br>
when connected via USB 2, this works fine.  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=USB_ERR_TIMEOUT<br>
uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 2<br>
<br>
however, if i boot with &quot;boot -v&quot;, the device is reliably detected<br>
correctly.  since -v shouldn&#39;t cause any functional changes, i suspect<br>
this may be some kind of timing issue.<br>
<br>
i&#39;ve tried increasing some of the USB timings (hw.usb.timings.*) but<br>
this didn&#39;t seem to have any effect.  is there anything else i could try<br>
that might affect this, or is this perhaps a known issue?<br>
<br>
        thanks, lexi.<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committer (ports)</span></div></div>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committer (ports)</span></div></div>
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7ULh8E_PTVCgUGbSyh70zE0eeArW0NKn%2BWQfoUgZR1mDEg>