summary refs log tree commit diff stats
path: root/results/classifier/accel-gemma3:12b/kvm/1579327
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/accel-gemma3:12b/kvm/1579327')
-rw-r--r--results/classifier/accel-gemma3:12b/kvm/1579327120
1 files changed, 120 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1579327 b/results/classifier/accel-gemma3:12b/kvm/1579327
new file mode 100644
index 00000000..f4487998
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/kvm/1579327
@@ -0,0 +1,120 @@
+
+emulation of vexpress-a9 vexpress-a15 in multicore mode seems to be broken
+
+Report based on:
+https://stackoverflow.com/questions/37068688/have-you-got-issues-with-running-u-boot-for-versatile-express-a9-platform-under
+
+I don't see any bug reports about vexpress boards emulation here, so I decided to let you know:
+
+version tested: qemu 2.0.0 on 32 bit Debian GNU/Linux
+
+There are issues with running u-boot on qemu vexpress-a9 ( it was reported to work ok at physical multicore board )  and vexpress-a15 with parameters -smp cores=2 r 3 or 4.
+So far those are two tested. I dont know ATM if any other board emulation works in multiprocessor mode
+
+Original post at stackoverflow:
+---------------------------------------------------------------------------------------------------
+I have tried numerous releases of u-boot since vexpress-a9 was introduced in u-bot stable release. Under qemu with multicore emulation its behaving unstable - mostly crashes instantly after loading. Sometimes it loads without issues but its rare. My version of qemu is 2.0.0 on x86 32bit Debian. I would be interested to hear if you succeeded in runing it under qemu with multicore emulation ( if yes which version of qemu and u-boot ) or physical versatile express board with multiple cores.
+
+Example outputs are
+
+$ qemu-system-arm -M vexpress-a9 -nographic -kernel u-boot -smp cores=2
+U-Boot 2013.01.01-dirty (May 05 2016 - 08:27:19)
+
+DRAM:  128 MiB
+WARNING: Caches not enabled
+undefined instruction
+pc : [<00000000>]      lr : [<00000000>]
+sp : 60000ef0  ip : 67eedfd8     fp : 00000000
+r10: 00000000  r9 : 00000000     r8 : 60000f00
+r7 : 00000000  r6 : 608146ac     r5 : 60828365  r4 : 0000004d
+r3 : 00000000  r2 : 00000000     r1 : 60000f80  r0 : 47cc9e10
+Flags: nzcv  IRQs on  FIQs on  Mode USER_26
+Resetting CPU ...
+resetting ...
+Flash: 256 MiB
+MMC:   MMC: 0
+*** Warning - bad CRC, using default environment
+
+In:    serial
+Out:   serial
+Err:   serial
+Net:   smc911x-0
+Warning: smc911x-0 using MAC address from net device
+
+Hit any key to stop autoboot:  0 
+Wrong Image Format for bootm command
+ERROR: can't get kernel image!
+VExpress# 
+
+This time it was loaded
+
+Other time it was not...
+
+$ qemu-system-arm -M vexpress-a9 -nographic -kernel u-boot -smp cores=2
+
+
+U-Boot 2013.01.01-dirty (May 05 2016 - 08:27:19)
+
+DRAM:  128 MiB
+WARNING: Caches not enabled
+
+
+U-Boot 2013.01.01-dirty (May 05 2016 - 08:27:19)
+
+DRAM:  128 MiB
+WARNING: Caches not enabled
+Flash: 256 MiB
+MMC:   MMC: 0
+*** Warning - bad CRC, using default environment
+
+In:    serial
+Out:   serial
+Err:   serial
+Net:   smc911x-0
+Warning: smc911x-0 using MAC address from net device
+
+Hit any key to stop autoboot:  2 qemu: fatal: Trying to execute code outside RAM or ROM at 0x6f71c004
+
+R00=00418937 R01=000003e8 R02=00418937 R03=00000000
+R04=00000000 R05=67eedf58 R06=67f8e000 R07=00000002
+R08=00418937 R09=0778e000 R10=6082f688 R11=00000000
+R12=67eedfd8 R13=00000000 R14=67fb82c0 R15=6f71c004
+PSR=200001db --C- A und32
+s00=00000000 s01=00000000 d00=0000000000000000
+s02=00000000 s03=00000000 d01=0000000000000000
+s04=00000000 s05=00000000 d02=0000000000000000
+s06=00000000 s07=00000000 d03=0000000000000000
+s08=00000000 s09=00000000 d04=0000000000000000
+s10=00000000 s11=00000000 d05=0000000000000000
+vs12=00000000 s13=00000000 d06=0000000000000000
+s14=00000000 s15=00000000 d07=0000000000000000
+s16=00000000 s17=00000000 d08=0000000000000000
+s18=00000000 s19=00000000 d09=0000000000000000
+s20=00000000 s21=00000000 d10=0000000000000000
+s22=00000000 s23=00000000 d11=0000000000000000
+s24=00000000 s25=00000000 d12=0000000000000000
+s26=00000000 s27=00000000 d13=0000000000000000
+s28=00000000 s29=00000000 d14=0000000000000000
+s30=00000000 s31=00000000 d15=0000000000000000
+s32=00000000 s33=00000000 d16=0000000000000000
+s34=00000000 s35=00000000 d17=0000000000000000
+s36=00000000 s37=00000000 d18=0000000000000000
+s38=00000000 s39=00000000 d19=0000000000000000
+s40=00000000 s41=00000000 d20=0000000000000000
+s42=00000000 s43=00000000 d21=0000000000000000
+s44=00000000 s45=00000000 d22=0000000000000000
+s46=00000000 s47=00000000 d23=0000000000000000
+s48=00000000 s49=00000000 d24=0000000000000000
+s50=00000000 s51=00000000 d25=0000000000000000
+s52=00000000 s53=00000000 d26=0000000000000000
+s54=00000000 s55=00000000 d27=0000000000000000
+s56=00000000 s57=00000000 d28=0000000000000000
+s58=00000000 s59=00000000 d29=0000000000000000
+s60=00000000 s61=00000000 d30=0000000000000000
+s62=00000000 s63=00000000 d31=0000000000000000
+FPSCR: 00000000
+-------------------------------------------------------------------------------------------------
+end of post
+
+Original discussion at ( includes comments of head custodian of Das U-boot about u-boot working on physical board versatile express a9 and him having issues with runing Linux distro at qemu vexpress-a9 board emulation ):
+https://stackoverflow.com/questions/37068688/have-you-got-issues-with-running-u-boot-for-versatile-express-a9-platform-under
\ No newline at end of file