Fixed in commit 69958d8a3d9
("usb: hcd-dwc2: change assert()s to qemu_log_mask(LOG_GUEST_ERROR...)")
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
So I dug into this a little more, and it looks like this issue has
nothing to do with hcd-dwc2, other than it served as a canary because of
the assert that fired. With hcd-dwc2 removed from the build, the
2016-05-27 Raspbian image still doesn't work, it hangs shortly after the
login prompt appears
I also tried
http://downloads.raspberrypi.org/raspbian/images/raspbian-2016-09-28/2016-09-23
-raspbian-jessie.zip, which is the next Raspbian release after the
cursed one, and it works OK too. So I assume any release after that will
also work OK. Just in case anyone wants to use the older releases
For my use case the newer image is fine too. I'm mildly curious what the
dwc_otg driver is doing in the older image though.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-
The URL to the image I used is
http://downloads.raspberrypi.org/raspbian/images/raspbian-2019-09-30/2019-09-26
-raspbian-buster.zip
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu
Something very strange is going on with the dwc_otg driver in
2016-05-27-raspbian-jessie.img. Something is reading and writing incrementally
throughout the register space of the hcd-dwc2 host.
And adding the "dwc_otg.fiq_fsm_enable=0" kernel option does not fix it.
Brendan, Petunia, is there a r
Hmm, that's odd. I will try to reproduce this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read: Assertion
`addr <= GINTSTS
Nope:
qemu-system-arm -M raspi2 -m 1G -dtb bcm2709-rpi-2-b.dtb -kernel
kernel7.img -append "rw earlyprintk loglevel=8 console=ttyAMA0,115200
dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 dwc_otg.fiq_fsm_enable=0" -sd
2016-05-27-raspbian-jessie.img -smp 4 -serial stdio -display none
raspberrypi login:
Are you able to modify the -append string to add
"dwc_otg.fiq_fsm_enable=0", and if so does it fix the problem?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/u
ah, well then its the same error:
qemu-system-arm: /build/qemu/src/qemu-5.1.0/hw/usb/hcd-dwc2.c:666:
dwc2_glbreg_read: Assertion `addr <= GINTSTS2' failed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bu
That part is easily fixed by running
qemu-img resize 2016-05-27-raspbian-jessie.img 4G
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_
for me the output is:
% qemu-system-arm -M raspi2 -m 1G -dtb bcm2709-rpi-2-b.dtb -kernel kernel7.img
-append "rw earlyprintk loglevel=8 console=ttyAMA0,115200 dwc_otg.lpm_enable=0
root=/dev/mmcblk0p2" -sd 2016-05-27-raspbian-jessie.img -smp 4 -serial stdio
-display none
WARNING: Image format wa
Hmm, yes agreed. I started a 2-week holiday on Monday, I can work on
this after I get back on Sept. 7
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc
It is still a bug in QEMU -- we shouldn't allow guest behaviour to make
QEMU assert(). If there's unimplemented functionality in the USB
controller model that can be logged with qemu_log_mask(LOG_UNIMP, ...)
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Yep, it looks like that works! Sorry for the bogus report, I didn't
think to check the Changelog.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:
What happens if you add "dwc_otg.fiq_fsm_enable=0" to the kernel command
line? This is noted as a requirement in the changelog at
https://wiki.qemu.org/ChangeLog/5.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchp
Note for bisection: it looks like it works fine as of tag stable-4.2 .
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1892604
Title:
qemu-system-arm: ../hw/usb/hcd-dwc2.c:666: dwc2_glbreg_read: Asse
18 matches
Mail list logo
