* [Qemu-devel] [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
@ 2018-10-19 11:59 ` Alex Bennée
2018-10-19 12:26 ` Peter Maydell
2019-05-01 17:24 ` Philippe Mathieu-Daudé
` (4 subsequent siblings)
5 siblings, 1 reply; 8+ messages in thread
From: Alex Bennée @ 2018-10-19 11:59 UTC (permalink / raw)
To: qemu-devel
Isn't this likely due to the newer kernel accessing hardware we are not
emulating properly?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
New
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
2018-10-19 11:59 ` [Qemu-devel] [Bug 1797262] " Alex Bennée
@ 2019-05-01 17:24 ` Philippe Mathieu-Daudé
2019-07-08 16:48 ` Philippe Mathieu-Daudé
` (3 subsequent siblings)
5 siblings, 0 replies; 8+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-05-01 17:24 UTC (permalink / raw)
To: qemu-devel
** Tags added: arm
** Changed in: qemu
Status: New => Confirmed
** Changed in: qemu
Assignee: (unassigned) => Philippe Mathieu-Daudé (philmd)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
Confirmed
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
2018-10-19 11:59 ` [Qemu-devel] [Bug 1797262] " Alex Bennée
2019-05-01 17:24 ` Philippe Mathieu-Daudé
@ 2019-07-08 16:48 ` Philippe Mathieu-Daudé
2020-11-04 13:59 ` Philippe Mathieu-Daudé
` (2 subsequent siblings)
5 siblings, 0 replies; 8+ messages in thread
From: Philippe Mathieu-Daudé @ 2019-07-08 16:48 UTC (permalink / raw)
To: qemu-devel
latest series posted:
https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00191.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
Confirmed
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
` (2 preceding siblings ...)
2019-07-08 16:48 ` Philippe Mathieu-Daudé
@ 2020-11-04 13:59 ` Philippe Mathieu-Daudé
2020-11-05 9:00 ` Thomas Huth
2020-12-10 9:21 ` Thomas Huth
5 siblings, 0 replies; 8+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-11-04 13:59 UTC (permalink / raw)
To: qemu-devel
Should be now fixed by commits 74de7145fd6..83ad4695478 (CPRMAN model
added).
** Changed in: qemu
Assignee: Philippe Mathieu-Daudé (philmd) => (unassigned)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
Confirmed
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
` (3 preceding siblings ...)
2020-11-04 13:59 ` Philippe Mathieu-Daudé
@ 2020-11-05 9:00 ` Thomas Huth
2020-12-10 9:21 ` Thomas Huth
5 siblings, 0 replies; 8+ messages in thread
From: Thomas Huth @ 2020-11-05 9:00 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
Fix Committed
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Bug 1797262] Re: qemu arm no longer able to boot RPI Kernels
2018-10-10 23:59 [Qemu-devel] [Bug 1797262] [NEW] qemu arm no longer able to boot RPI Kernels Rob Thomas
` (4 preceding siblings ...)
2020-11-05 9:00 ` Thomas Huth
@ 2020-12-10 9:21 ` Thomas Huth
5 siblings, 0 replies; 8+ messages in thread
From: Thomas Huth @ 2020-12-10 9:21 UTC (permalink / raw)
To: qemu-devel
Released with QEMU v5.2.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
Status in QEMU:
Fix Released
Bug description:
Since RPi Kernel 1.20170427, qemu is no longer able to emulate the
Rasberry Pi, as the linux kernel is complaining about timing issues.
Old kernel output - https://pastebin.com/wvkneNNF
New kernel output - https://pastebin.com/QTwgCkV2
Note that the actual error is caused by the kernel being unable to get
the timing source for the mmc (Line 160), which causes an unable-to-
mount-root panic. There are other issues with the serial port
returning an invalid speed, which displays a divide-by-zero error,
which is PROBABLY a symptom of the same root cause.
This is simple to replicate - The last working kernel is available
here:
https://github.com/raspberrypi/firmware/tree/1.20170405/boot
Download kernel7 and the dtb, and try to boot with (for example)
qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb
bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append
"root=/dev/mmcblk0p2 init=/bin/bash"
This works, and boots successfully.
However, if you replace the kernel7.img and dtb with ones taken from
https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will
NOT boot because of various clock timing issues (as in the second
paste)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1797262/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread