qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] Freescale qemu kvm and virtio


From: Florian Chazal
Subject: Re: [Qemu-ppc] Freescale qemu kvm and virtio
Date: Tue, 17 Dec 2013 09:09:58 -0800

Hi scott,

Sorry for this late answer but I was trying to gather more relevant information linked to my issue.
Thanks for the answer.

I am working with the 1.4 SDK fom freescale which bring the kernel 3.8.r14-3 (for host and guest) and the fsl-core-image yocto recipe provided by the SDK

Following your though, I tried hosting my VM image on a SD card and with ext4 fs but I still have error coming. Then analysing my guest processes, I realised that the error happen only during a specific cp command ...
So I though it is maybe link to the VM image size (more than 7G qcow2 image). Therefore I tried directly on host to create a 10G file with dd andI killed the system with a simple dd if=/dev/zero of=a.log bs=1M count=10000 
Then I tried to figure out what is the critical sizeand it seems to be around 1096M.
Coming back to my VM issue, using directly a usb key or sdcard as main partition (no more big qcow2 image but -drive file=/dev/sda,if=virtio) it works perfectly.

I don't currently don't know enough on ppc and low kernel/u-boot layer to debug but I will work on it. Here Are all the info I got :

Host boot log under u-boot:

Boot

U-Boot 2011.09sdk1.1-626584-01_00 (Build on : Jul 29 2013 - 09:41:15)

CPU0:  P4080E, Version: 2.0, (0x82080020)
Core:  E500MC, Version: 2.0, (0x80230020)
Clock Configuration:
       CPU0:1500 MHz, CPU1:1500 MHz, CPU2:1500 MHz, CPU3:1500 MHz,
       CPU4:1500 MHz, CPU5:1500 MHz, CPU6:1500 MHz, CPU7:1500 MHz,
       CCB:800  MHz,
       DDR:650  MHz (1300 MT/s data rate) (Asynchronous), LBC:25   MHz
       FMAN1: 600 MHz
       FMAN2: 600 MHz
       PME:   400 MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: COMX-P4040, 36-bit Addressing
Reset Configuration Word (RCW):
       00000000: 105a0000 00000000 1e1e181e 0000cccc
       00000010: 3c464400 003c2000 fe800000 61000000
       00000020: 00000000 00000000 00000000 0013e1a0
       00000030: a0000000 00000000 00000000 00000000
I2C:   ready
SPI:   ready
DRAM:  Initializing....using SPD
Detected UDIMM
Detected UDIMM
2 GiB left unmapped
    DDR: 4 GiB (DDR3, 64-bit, CL=9, ECC on)
       DDR Controller Interleaving Mode: cache line
Testing 0x00000000 - 0x7fffffff
Testing 0x80000000 - 0xffffffff
Remap DDR 2 GiB left unmapped


### Using TLB entry 15 for DSU-D4 Xilinx
### Using TLB entry 16 for DSU-D4 Actel U93
### Using TLB entry 17 for DSU-D4 Holt U86 @ 0000000f f5000000
Flash: 128 MiB
L2:    128 KB enabled
Corenet Platform Cache: 2048 KB enabled
Warning: SERDES8 requires banks two and three to be disabled in the RCW
NAND:  1024 MiB
MMC:  FSL_ESDHC: 0
*** Warning - bad CRC, using default environment

EEPROM: NXID v1
EEPROM: Invalid ID (a0 31 33 33)
PCIe1: Root Complex, no link, regs @ 0xfe200000
PCIe1: Bus 00 - 00
PCIe2: disabled
PCIe3: disabled
In:    serial
Out:   serial
Err:   serial
RTC:  N/address@hidden
WDT:  address@hidden(disabled)
Net:   Fman1: Uploading microcode version 101.6.0
Fman2: Uploading microcode version 101.6.0
address@hidden, address@hidden: failed to set MAC address
, address@hidden: failed to set MAC address
, address@hidden: failed to set MAC address
, address@hidden: failed to set MAC address
, address@hidden: failed to set MAC address


############################### Performing DSUD4 U-Boot POST ##############################


         Start POST:[DDR3 memory]

         DDR3-Ram Data Lines...OK
         DDR3-Ram Address Lines...OK
         DDR3-Ram Zero Pattern Test...OK
         DDR3-Ram Negative Pattern Test...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[I2C bus]

         I2C bus...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[Watchdog timer]

         I2C Probe...OK
         WDT Chip Detection...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[EEPROM communication]

         I2C Probe...OK
         EEPROM Chip Detection...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[RTC communication]

         RTC Time Uniformity...Error !!!

         Result:[FAIL]

        ---------------------------------------------------------------------

         Start POST:[NOR flash]

         Erasing NOR Sector...OK
         Writing Test Pattern To NOR Memory...OK
         Read Test Pattern From NOR Memory and Compare...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[NAND flash]

         Probing NAND Device...OKnand_read_bbt: Bad block at 0x00000a6e0000
nand_read_bbt: Bad block at 0x00000a720000
nand_read_bbt: Bad block at 0x0000205e0000
nand_read_bbt: Bad block at 0x000026780000
nand_read_bbt: Bad block at 0x000030680000
nand_read_bbt: Bad block at 0x000036aa0000
nand_read_bbt: Bad block at 0x0000377c0000
nand_read_bbt: Bad block at 0x0000379e0000
nand_read_bbt: Bad block at 0x000038aa0000
nand_read_bbt: Bad block at 0x00003afe0000
nand_read_bbt: Bad block at 0x00003b2a0000
nand_read_bbt: Bad block at 0x00003b540000
nand_read_bbt: Bad block at 0x00003ce60000
nand_read_bbt: Bad block at 0x00003dc20000
nand_read_bbt: Bad block at 0x00003f860000

         Reading NAND Memory...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[Ethernet (RGMII 1G Port) test]

         Ethernet(RGMII 1G Port) Loop_Back_Mode Config...OK
         Ethernet(RGMII 1G Port) Tx Rx...OK

         Result:[PASS]

        ---------------------------------------------------------------------

         Start POST:[Xilinx FPGA Communication]

         Xilinx FPGA Magic Number Read...Error !!!
         Xilinx FPGA MAJOR Revision Code Read...Error !!!
         Xilinx FPGA MINOR Revision Code Read...Error !!!

         Result:[FAIL]

        ---------------------------------------------------------------------

         LED blinking...done

################################ DSUD4 U-Boot POST SUMMARY ###############################

        -------------------------------------------------------------------------------
         POST TEST NAME                             POST RESULT         FAILURE COST
        -------------------------------------------------------------------------------
         [1].DDR3 memory                    ........   PASSED  ........  BLOCKING
         [2].I2C bus                        ........   PASSED  ........  BLOCKING
         [3].Watchdog timer                 ........   PASSED  ........  BLOCKING
         [4].EEPROM communication           ........   PASSED  ........  BLOCKING
         [5].RTC communication              ........   FAILED  ........  BLOCKING
         [6].NOR flash                      ........   PASSED  ........  BLOCKING
         [7].NAND flash                     ........   PASSED  ........  BLOCKING
         [8].Ethernet (RGMII 1G Port) test  ........   PASSED  ........  BLOCKING
         [9].Xilinx FPGA Communication      ........   FAILED  ........  BLOCKING
         [10].Keyline FPGA Communication    ........   SKIPPED ........  BLOCKING
         [11].Power OK Status               ........   SKIPPED ........  BLOCKING
         [12].GPIO Communication            ........   SKIPPED ........  BLOCKING
         [13].EEPROM Checksum Status        ........   SKIPPED ........  BLOCKING
         [14].Ethernet Switch Chip Detection........   SKIPPED ........  BLOCKING
         [15].SPI test                      ........   SKIPPED ........  NON-BLOCKING
         [16].SAS Controller Chip Detection ........   SKIPPED ........  NON-BLOCKING
         [17].AR429 SPI BUS                 ........   SKIPPED ........  NON-BLOCKING
         [18].10G Port (XAUI 10GbE) test    ........   SKIPPED ........  NON-BLOCKING
        -------------------------------------------------------------------------------

################################ DSUD4 POST BITE DATA SUMMARY ###############################

         Previous POST BITE Data ............[3133336c]
         Current  POST BITE Data ............[00010008]
         Save POST BITE Data in EEPROM ......[NO]

############################### FPGA Auto-Recovery Routine ################################

        -------------------------------------------------------------------------------

                 XILINX FPGA AUTO RECOVERY RETRY OVER !!!
                 NO MORE AUTO RECOVERY WILL BE PERFORMED !!!
                 DSUD4 UNIT : MAJOR CRITICAL FAULT DETECTED !!!
        -------------------------------------------------------------------------------

         XILINX/KEYLINE FPGA AUTO RECOVERY INFORMATION
        -------------------------------------------------------------------------------

         Xilinx  FPGA Recovery .............. = 4
         Keyline FPGA Recovery .............. = ▒
         Current Xilinx  FPGA Retry Count ... = ▒
         Current Keyline FPGA Retry Count ... = ▒
         Xilinx  FPGA Total Recovery Count .. = ▒
         Keyline FPGA Total Recovery Count .. = ▒

        -------------------------------------------------------------------------------

##########################################################################################


         !!! Aborting auto-boot after 10 sec due to blocking POST FAILURE !!!

##########################################################################################
Hit 's' or 'S' key to stop autoboot:  0

U-boot

[DSU-D4 U-boot]=> version

U-Boot 2011.09sdk1.1-626584-01_00 (Build on : Jul 29 2013 - 09:41:15)
powerpc-linux-gnu-gcc (Sourcery G++ Lite 2010.09-55) 4.5.1
GNU ld (Sourcery G++ Lite 2010.09-55) 2.20.51.20100809

OS information

address@hidden:~# uname -ra
Linux p4080ds 3.8.13-rt9-QorIQ-SDK-V1.4 #9 SMP Wed Dec 11 16:59:05 PST 2013 ppc GNU/Linux
address@hidden:~# free
             total       used       free     shared    buffers     cached
Mem:       4003476     234620    3768856          0       6444      29000
-/+ buffers/cache:     199176    3804300
Swap:            0          0          0
address@hidden:~# cat /proc/cpuinfo
processor       : 0
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 1
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 2
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 3
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 4
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 5
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 6
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

processor       : 7
cpu             : e500mc
clock           : 1500.000000MHz
revision        : 2.0 (pvr 8023 0020)
bogomips        : 100.00

total bogomips  : 800.00
timebase        : 50000000
platform        : P4080 DS
model           : fsl,P4080DS
Memory          : 4096 MB

dd command result

address@hidden:/media/mmcblk0p1# dd if=/dev/zero  of=a.log bs=1M count=1096
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc0128e70
Unable to handle kernel paging request for data at address 0x00000004
Faulting instruction address: 0xc00f3d0c
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=8 P4080 DS
Modules linked in:
NIP: c00f3d0c LR: c00f3ac8 CTR: 000003f9
REGS: dd92bcf0 TRAP: 0300   Not tainted  (3.8.13-rt9-QorIQ-SDK-V1.4)
MSR: 00021002 <CE,ME>  CR: 24002488  XER: 00000000
DEAR: 00000004, ESR: 00800000
TASK = e330fab0[2269] 'klogd' THREAD: dd92a000 CPU: 1
GPR00: c00f3a0c dd92bda0 e330fab0 00000000 000080d0 00000000 ffffffff ffffffff
GPR08: 00000000 00000000 00000000 00000100 44002422 1001d4a4 00000075 10010000
GPR16: c0a10000 00000001 e7022f50 e7022f48 c0a10000 00100100 00200200 e7022f40
GPR24: c0a0f51c 00000000 000080d0 dd92a000 e7021ec0 e70bea00 ffffffff eeb3b040
NIP [c00f3d0c] cache_alloc_refill+0x2cc/0x730
LR [c00f3ac8] cache_alloc_refill+0x88/0x730
Call Trace:
[dd92bda0] [c0a0bf30] dirty_balance_reserve+0x0/0x4 (unreliable)
[dd92bdf0] [c00f3a0c] kmem_cache_alloc+0xcc/0x100
[dd92be10] [c00fbc14] get_empty_filp+0x74/0x1e0
[dd92be30] [c0109d7c] path_openat.isra.42+0x3c/0x4c0
[dd92be90] [c010a5b0] do_filp_open+0x30/0x90
[dd92bf10] [c00f95f4] do_sys_open+0x104/0x1e0
[dd92bf40] [c000ec90] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xfeec6e4
    LR = 0xfe90294
Instruction dump:
80010054 8181000c 38210050 7c0803a6 7d810120 7d808120 4e800020 60000000
60000000 813f0004 815f0000 2f9e0000 <912a0004> 91490000 92bf0000 92df0004
---[ end trace 7a098f28607e8711 ]---

Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc00e2920
Oops: Kernel access of bad area, sig: 11 [#2]
SMP NR_CPUS=8 P4080 DS
Modules linked in:
NIP: c00e2920 LR: c00d5fb0 CTR: c00c0db0
REGS: dd92bac0 TRAP: 0300   Tainted: G      D       (3.8.13-rt9-QorIQ-SDK-V1.4)
MSR: 00029002 <CE,EE,ME>  CR: 24004428  XER: 00000000
DEAR: 00000000, ESR: 00000000
TASK = e330fab0[2269] 'klogd' THREAD: dd92a000 CPU: 1
GPR00: c00d5fb0 dd92bb70 e330fab0 eeb1aac8 e3318a70 00103000 00000000 00000000
GPR08: 00000000 00000000 00000000 02104000 24004424 1001d4a4 00000075 10010000
GPR16: c0a10000 00000001 e7022f50 e7022f48 c0a10000 00100100 00200200 eeb1aac8
GPR24: c0a0f51c 00021002 eeb1ab04 dd92bbd8 00000000 00100000 00000000 00000000
NIP [c00e2920] unlink_anon_vmas+0x20/0x1e0
LR [c00d5fb0] free_pgtables+0xb0/0x140
Call Trace:
[dd92bb70] [00000001] 0x1 (unreliable)
[dd92bbb0] [c00d5fb0] free_pgtables+0xb0/0x140
[dd92bbd0] [c00df460] exit_mmap+0xe0/0x170
[dd92bc40] [c003a81c] mmput+0x5c/0x110
[dd92bc60] [c0042fdc] do_exit+0x23c/0x8c0
[dd92bcb0] [c000a614] die+0x214/0x300
[dd92bce0] [c000f1ac] handle_page_fault+0x7c/0x80
--- Exception: 300 at cache_alloc_refill+0x2cc/0x730
    LR = cache_alloc_refill+0x88/0x730
[dd92bda0] [c0a0bf30] dirty_balance_reserve+0x0/0x4 (unreliable)
[dd92bdf0] [c00f3a0c] kmem_cache_alloc+0xcc/0x100
[dd92be10] [c00fbc14] get_empty_filp+0x74/0x1e0
[dd92be30] [c0109d7c] path_openat.isra.42+0x3c/0x4c0
[dd92be90] [c010a5b0] do_filp_open+0x30/0x90
[dd92bf10] [c00f95f4] do_sys_open+0x104/0x1e0
[dd92bf40] [c000ec90] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xfeec6e4
    LR = 0xfe90294
Instruction dump:
4bffe8b1 3860fff4 4bfffed4 60000000 9421ffc0 7c0802a6 bea10014 90010044
7c7a1b78 7c771b78 87fa003c 7f9af800 <837f0000> 3bfffff8 3b7bfff8 419e0170
---[ end trace 7a098f28607e8712 ]---

Fixing recursive fault but reboot is needed!
Oops: Kernel access of bad area, sig: 11 [#3]
SMP NR_CPUS=8 P4080 DS
Modules linked in:
NIP: c0128e70 LR: c00b6e5c CTR: c00bfe80
REGS: dd84fd60 TRAP: 0300   Tainted: G      D       (3.8.13-rt9-QorIQ-SDK-V1.4)
MSR: 00029002 <CE,EE,ME>  CR: 24004024  XER: 00000000
DEAR: 00000000, ESR: 00000000
TASK = eed2b0f0[2354] 'dd' THREAD: dd84e000 CPU: 0
GPR00: c00b6e30 dd84fe10 eed2b0f0 eeb3b9c0 00000000 00000000 44400000 00000000
GPR08: 00100000 00010001 00000000 44500000 24004022 10027558 00000000 00000000
GPR16: 00000000 00100000 1001f990 1000e5b0 10020000 00000000 00000000 00000444
GPR24: dd84fec8 00000001 44400000 00000000 eeb3b9c0 e4fab120 e4fab0b0 00100000
NIP [c0128e70] generic_write_sync+0x10/0x90
LR [c00b6e5c] generic_file_aio_write+0xac/0x140
Call Trace:
[dd84fe10] [c00b6e30] generic_file_aio_write+0x80/0x140 (unreliable)
--- Exception: 0 at   (null)
    LR =   (null)
[dd84fe40] [c00f9948] do_sync_write+0x98/0x120 (unreliable)
[dd84fef0] [c00fa3d0] vfs_write+0xb0/0x1a0
[dd84ff10] [c00fa75c] sys_write+0x4c/0xb0
[dd84ff40] [c000ec90] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xfeecfac
    LR = 0x10004fc4
Instruction dump:
7c892378 4e800420 60000000 60000000 3860ffea 4e800020 60000000 60000000
81230020 71241000 4082001c 8143008c <814a0000> 808a001c 80840034 708b0010
---[ end trace 7a098f28607e8713 ]---

Unable to handle kernel paging request for data at address 0x00000024
Faulting instruction address: 0xc07851b4
Oops: Kernel access of bad area, sig: 11 [#4]
SMP NR_CPUS=8 P4080 DS
Modules linked in:
NIP: c07851b4 LR: c00dc880 CTR: c00c0db0
REGS: dd84fb40 TRAP: 0300   Tainted: G      D       (3.8.13-rt9-QorIQ-SDK-V1.4)
MSR: 00029002 <CE,EE,ME>  CR: 24004088  XER: 00000000
DEAR: 00000024, ESR: 00000000
TASK = eed2b0f0[2354] 'dd' THREAD: dd84e000 CPU: 0
GPR00: c00dc880 dd84fbf0 eed2b0f0 00000024 00000003 00000002 0010a6a5 020fa000
GPR08: c2ab8c64 ffffffa0 00000005 00000722 24004084 10027558 00000000 00000000
GPR16: 00000000 00100000 1001f990 1000e5b0 10020000 00000000 00000000 dd84e000
GPR24: dd84fec8 00029002 00000000 dd84fc48 00000000 00000024 e4e01650 00000024
NIP [c07851b4] mutex_lock+0x14/0x50
LR [c00dc880] unlink_file_vma+0x30/0x80
Call Trace:
[dd84fc00] [c00dc880] unlink_file_vma+0x30/0x80
[dd84fc20] [c00d5f48] free_pgtables+0x48/0x140
[dd84fc40] [c00df460] exit_mmap+0xe0/0x170
[dd84fcb0] [c003a81c] mmput+0x5c/0x110
[dd84fcd0] [c0042fdc] do_exit+0x23c/0x8c0
[dd84fd20] [c000a614] die+0x214/0x300
[dd84fd50] [c000f1ac] handle_page_fault+0x7c/0x80
--- Exception: 300 at generic_write_sync+0x10/0x90
    LR = generic_file_aio_write+0xac/0x140
[dd84fe10] [c00b6e30] generic_file_aio_write+0x80/0x140 (unreliable)
--- Exception: 0 at   (null)
    LR =   (null)
[dd84fe40] [c00f9948] do_sync_write+0x98/0x120 (unreliable)
[dd84fef0] [c00fa3d0] vfs_write+0xb0/0x1a0
[dd84ff10] [c00fa75c] sys_write+0x4c/0xb0
[dd84ff40] [c000ec90] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xfeecfac
    LR = 0x10004fc4
Instruction dump:
bb210024 80010044 81810020 38210040 7c0803a6 7d808120 4e800020 9421fff0
7c0802a6 93e1000c 90010014 7c7f1b78 <7d201828> 3129ffff 7d20192d 40a2fff4
---[ end trace 7a098f28607e8714 ]---

Fixing recursive fault but reboot is needed!
------------[ cut here ]------------
kernel BUG at mm/slab.c:3227!
Oops: Exception in kernel mode, sig: 5 [#5]
SMP NR_CPUS=8 P4080 DS
Modules linked in:
NIP: c00f3bb0 LR: c00f3ac8 CTR: 00000000
REGS: ed547c40 TRAP: 0700   Tainted: G      D       (3.8.13-rt9-QorIQ-SDK-V1.4)
MSR: 00021002 <CE,ME>  CR: 22022084  XER: 00000000
TASK = c09c1300[0] 'swapper/0' THREAD: c0a00000 CPU: 0
GPR00: c00f3a0c ed547cf0 c09c1300 eec50d40 00000020 00000000 ffffffff 00000011
GPR08: 00000001 0000001e 0000001e 00000000 42024042 a5433417 00000000 0000000c
GPR16: c0a10000 00000001 e73bfd10 e73bfd08 c0a10000 00100100 00200200 e73bfd00
GPR24: c0a0f51c 00000000 00000020 ed546000 e719f940 e7321600 0000000b eec50000
NIP [c00f3bb0] cache_alloc_refill+0x170/0x730
LR [c00f3ac8] cache_alloc_refill+0x88/0x730
Call Trace:
[ed547cf0] [e719f940] 0xe719f940 (unreliable)
[ed547d40] [c00f3a0c] kmem_cache_alloc+0xcc/0x100
[ed547d60] [c0665bb8] dst_alloc+0x58/0x1a0
[ed547d80] [c06821e0] ip_route_input_noref+0x2c0/0xab0
[ed547e10] [c0685194] ip_rcv+0x374/0x580
[ed547e30] [c0657f84] __netif_receive_skb+0x454/0x6b0
[ed547ea0] [c06599ac] netif_receive_skb+0x3c/0xd0
[ed547ed0] [c053a618] _dpa_rx+0x188/0x340
[ed547f00] [c053a848] ingress_rx_default_dqrr+0x78/0x100
[ed547f20] [c061dd68] qman_poll_dqrr+0x218/0x260
[ed547f50] [c0538e80] dpaa_eth_poll+0x20/0x60
[ed547f70] [c0659db4] net_rx_action+0x134/0x1f0
[ed547fa0] [c0046010] __do_softirq+0x100/0x1a0
[ed547ff0] [c000d1cc] call_do_softirq+0x14/0x24
[c0a01e70] [c0004910] do_softirq+0xa0/0xd0
[c0a01e90] [c0046804] irq_exit+0xa4/0xf0
[c0a01ea0] [c00045c0] do_IRQ+0x80/0x190
[c0a01ed0] [c000f340] ret_from_except+0x0/0x18
--- Exception: 501 at cpu_idle+0xb8/0x180
    LR = cpu_idle+0xb8/0x180
[c0a01f90] [c0007ca8] cpu_idle+0x58/0x180 (unreliable)
[c0a01fc0] [c09767a4] start_kernel+0x2d0/0x2e4
[c0a01ff0] [c00003c8] skpinv+0x2b4/0x2f0
Instruction dump:
3a770008 60000000 60000000 60000000 83f70000 7f17f800 419a01b8 813f0010
815c0018 7d0a4810 39000000 7d084114 <0f080000> 7f0a4840 40990088 3bdeffff
---[ end trace 7a098f28607e8715 ]---

Kernel panic - not syncing: Fatal exception in interrupt

EXT4-fs error (device mmcblk0p1) in ext4_reserve_inode_write:4688: IO failure
EXT4-fs error (device mmcblk0p1): ext4_mb_mark_diskspace_used:2781: comm flush-179:0: Allocating blocks 1040384-1042432 which overlap fs metadata
EXT4-fs error (device mmcblk0p1): ext4_mb_mark_diskspace_used:2781: comm flush-179:0: Allocating blocks 1042432-1044480 which overlap fs metadata
EXT4-fs error (device mmcblk0p1): ext4_mb_mark_diskspace_used:2781: comm flush-179:0: Allocating blocks 1044480-1046528 which overlap fs metadata
EXT4-fs error (device mmcblk0p1): ext4_mb_mark_diskspace_used:2781: comm flush-179:0: Allocating blocks 1046528-1048576 which overlap fs metadata


Regards,

Florian CHAZAL


On 12 December 2013 14:39, Scott Wood <address@hidden> wrote:
On Thu, 2013-12-12 at 14:12 -0800, Florian Chazal wrote:
> Hi guys,
>
>
> I try to virtualize my system running on freescale p4040 (baremetal)
> on top of a p4080 + kvm :
> Every thing seems to work fine till I do intesive I/O in my VM :
> qemu-system-ppc -enable-kvm -name kvm1 -serial tcp::4444,server,telnet -m 1024 -M ppce500 -nographic -netdev tap,id=tap0,script=no,vhost=on -device  e1000,netdev=tap0 -kernel /home/root/uImage--3.8-r14.3-p4080ds-20131211202743.bin -initrd /home/root/rootfs-goodArch.cpio.gz -append "root=dev/vda1 init=sbin/init console=ttyS0,115200 3" -drive file=/media/sda1/d4-fromscratch-v0.8.4.img,if=virtio
> QEMU waiting for connection on: telnet::0.0.0.04444,server
> QEMU 1.4.0 monitor - type 'help' for more information
> (qemu) status
> unknown command: 'status'
> (qemu) info status
> VM status: running
> (qemu) EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> EXT3-fs error (device sda1): ext3_new_block: block(1542) >= blocks count(0) - block_group = 0, es == eff1a400
> EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> EXT3-fs (sda1): error in ext3_orphan_add: IO failure
> EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> EXT3-fs (sda1): error in ext3_orphan_add: IO failure
> EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> EXT3-fs error (device sda1): ext3_new_block: block(1545) >= blocks count(0) - block_group = 0, es == eff1a400
> EXT3-fs (sda1): error in ext3_reserve_inode_write: IO failure
> EXT3-fs (sda1): error in ext3_orphan_add: IO failure
>
>
> My qcow2 image is on a usb key and after this happens, the usb key
> file system is remounted by the host in readonly mode due to ext3
> journal corruption.
>
>
> I tried the following thingto use io throttle with virtio bps/iops
> option => limiting  bps to 500000 everything was slow as expected but
> then I got a different qemu error
>
> (qemu) Unable to handle kernel paging request for data at address 0xffbc8be4
> Faulting instruction address: 0xc048e774

Bare addresses are not useful without the vmlinux they came from -- do
you have a full crash dump with symbol names?  Though if the crash is in
the filesystem code, you'll need to report it to the appropriate
filesystem list.

As for the above ext3 errors, given the message "IO failure" it may be a
hardware problem.

What kernel are you using?  What U-Boot?

Do you have all relevant errata worked around, especially USB errata?
There's a USB erratum that basically says high speed mode can't be used
except on specially screened chips.
>
> I found people saying that it can be linked to the virtio driver
> (https://bugzilla.redhat.com/show_bug.cgi?id=531827)

That bug is about corruption in guest's RFS.  You seem to have
corruption in your host filesystem.  I don't see how that is related to
virtio or KVM -- as far as the host filesystem is concerned, QEMU is
just an ordinary userspace process doing I/O.

> and who advice to go for IDE but unfortunately I can't make ide
> working ("qemu-system-ppc -hda" or -drive ...if=ide), the disk is not
> seen my the kernel.

Right, this is not supported on ppce500.

> The freescale documentation only mentions virtio block disk
> (http://www.freescale.com/infocenter/topic/QORIQSDK/2412421.html#id_2412421).
> Is it because freescale implementation for e500mc does not support
> classic ide ?

Yes.  The closest real-hardware analogue would be either a non-legacy
PCI device, or the CCSR SATA device that can be found on some similar
chips such as p3041.  The latter is not supported in QEMU, and I don't
know what would be involved in the former.

-Scott






--
Florian Chazal

reply via email to

[Prev in Thread] Current Thread [Next in Thread]