I tested the patch myself (arm64 and armhf kernels on different Pi
boards), it worked well. With this patch, the usb_owg could work well
even with HIGHMEM and VMSPLIT_3G enabled, so far we still could use a
single armhf kernel for Pi2/3/4 boards.
The testing kernel is at:
Probably I found the root cause of this problem.
After enabling the HIGHMEM and VMSPLIT_3G, the urb sent to the driver of
dwc_otg maybe allocated in the highmem, if it is in the highmem, the usb
core will not set the urb->transfer_buffer and call hcd->urb_enquenue().
With other hcd drivers, they
Dave in comment #10 you said "load on the ARM during transfers (my hunch
is, if anything is affected, it'll be the latter - I vaguely recall
forum posts about improvements on the ARM load during large USB
transactions)." Were the systems checked for load during the transfer
tests?
Additionally,
Tested the new armhf kernel on RPi3B+; copied 40Mb and 600Mb files
successfully with no issues. Compared performance of the 40Mb copy+sync
to the same machine running Disco (which has dwc_otg) and performance on
eoan with the new kernel was marginally quicker (6.8-7.0s on eoan with
dwc2 vs
Tested the new kernels on rpi3B+, rpi3A+ and rpi2Bv1.1, those devices
worked well as rpi4.
And I also compared the usb performance by copying a 700M file to usb
stick, there is no significant difference between dwc_otg and dwc2, all
cost around 2:40s. And I also tested usb performance with
These are the kernels with the dwc2 enabled (replaced dwc_otg with dwc2
for both arm64 and armhf kernels).
https://people.canonical.com/~hwang4/dwc2/
I just tested arm64 and armhf kernels on the rpi4 boards, the
uart/ethernet/sd card/sound/hdmi display/wifi/usb host all worked well.
I will test
On Fri, 15 Nov 2019 at 09:30, Hui Wang wrote:
>
> I did test with VMSPLIT_2G today, the mmc/sd controller will not work
> anymore on rpi4 boards, so enable VMSPLIT_2G is not a solution so far.
Oh well, was worth a try.
> And today I also tested dwc2, it worked well, maybe we could enable dwc2
>
I did test with VMSPLIT_2G today, the mmc/sd controller will not work
anymore on rpi4 boards, so enable VMSPLIT_2G is not a solution so far.
And today I also tested dwc2, it worked well, maybe we could enable dwc2
instead of dwc_otg, then we could use a single kernel to support
rpi2/3/4. dwc2
Thank you Hui! Please continue to communicate with upstream about
possible solutions. In the meantime, were you able to re-test the
VMSPLIT_2G setting with the current updated patches?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
submitted a upstream bug:
https://github.com/raspberrypi/linux/issues/3332
** Bug watch added: github.com/raspberrypi/linux/issues #3332
https://github.com/raspberrypi/linux/issues/3332
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In theory, we could enable HIGHMEM and VMSPLIT_2G (not VMSPLIT_3G) for
arm32 kernel to workaround this issue, with the 2G user space and 2G
kernel space, those boards (rpi2/3 boards) with only 1G physical ram
will not map ram to highmem region.
But I remember setting VMSPLIT_2G will break the SD
Some additional notes from testing last night (more or less blindly
after a load of googling for dwc_otg errors and mitigations):
* Adding dwc_otg.speed=1 (limiting the driver speed to Full Speed
USB1.1), fixes the mass-storage issue, but breaks compatibility with
most keyboards. So, not terribly
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852510
Title:
IO errors when writing large amounts of data to USB storage
> The upstream kernel of https://github.com/raspberrypi/linux.git also
has this issue.
This be one reason why Raspbian uses three different kernels (one for
0/B+, one for 2B/3B/3B+, one for 4B).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I reproduced this problem on the rpi3B+ and rpi2Bv1.1 with armhf kernel.
This problem is introduced by enabling two kernel configs for arm32
kernel, they are HIGHMEM and VMSPLIT_3G.
We need to use a single arm32 kernel to support rpi2/3/4, while rpi4 has
1G/2G/4G ram, to support 2G and 4G ram,
** Changed in: linux-raspi2 (Ubuntu Eoan)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852510
Title:
IO errors when writing large amounts of
Note that according to Dave this issue doesn't appear using the Disco
kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852510
Title:
IO errors when writing large amounts of data to USB storage
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => Critical
** Also affects: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided => Critical
--
You received this bug notification because you are
18 matches
Mail list logo
