[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Boot Process Hangs

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] Boot Process Hangs
From: Michal Simek <monstr@xxxxxxxxx>
Date: Mon, 29 Sep 2008 20:53:05 +0200
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=seznam.cz; h=Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Smtpd:X-Seznam-User:X-QM-Mark; b=XMZAhz2TJFeDcfXV74AYXmDgalSwYLas4xOG8ANZ6B8AsBNy4KJTS2SOLUwTilhr9 0jffR3Q66juPoQp6MNRIXWXkbAGlIzXEHpmnoYdnWuTmKjOGXLsPFVMOENjj++3dFLB HcumbfrGxqxxnpQgWiHE17DCRBoOwzA412+2Q18=
In-reply-to: <380D9721A8E2114485644D71E87C6AB2070D67A5@xxxxxxxxxxxxxxxxxxxxxxx>
References: <380D9721A8E2114485644D71E87C6AB20702A06B@xxxxxxxxxxxxxxxxxxxxxxx> <48D93D57.7020000@xxxxxxxxx> <380D9721A8E2114485644D71E87C6AB2070D67A5@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (X11/20080724)
Hi Makarand,

problem with scheduling while atomic was solved in past

http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2007/07/msg00042.html

I think that conclusion is there.

Regards,
Michal


makarand.vispute@xxxxxxxxx wrote:
> Hi Michal,
> 
> I am sorry for the delayed response.
> 
> I am using microblaze 7.1  with noMMU and EDK 10.1 with SP2.
> I am using Petalinux 2.6.20 and trying on my Spartan3E-500 board.
> I am also searching for some mail archives but till now I found none who
> has faced the problem while booting.
> I have one more doubt as I have enabled the interrupt for the
> Timer/Counter.
> It is causing some interrupt problem while booting?
> 
> Now I have enabled some traces.
> The complete log is as follows: 
> ************************************************************************
> **************************
> =================================================
> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
> =================================================
> FS-BOOT: System initialisation completed.
> FS-BOOT: Booting from FLASH. Press 's' for image download.
> FS-BOOT: Booting image...
> SDRAM :
>         Enabling caches :
>                 Icache:OK
>                 Dcache:OK
>         U-Boot Start:0x87fc0000
>         Malloc Start:0x87f60000
>         Board Info Start:0x87f5ffd0
>         Boot Parameters Start:0x87f4ffd0
> FLASH: 16 MB
> ETHERNET: MAC:00:0a:35:00:22:01
> 
> Hit any key to stop autoboot:  0
> ## Booting image at 850c0000 ...
>    Image Name:   PetaLinux Kernel 2.6
>    Image Type:   Microblaze Linux Kernel Image (uncompressed)
>    Data Size:    4755491 Bytes =  4.5 MB
>    Load Address: 86000000
>    Entry Point:  86000000
>    Verifying Checksum ... OK
> OK
> Found romfs @ 0x86257000 (0x00232000)
> #### klimit 8626e000 ####
> Moving 0x00232000 bytes from 0x86257000 to 0x8626d974
> New klimit: 0x864a0000
> Linux version 2.6.20-uc0 (makarvi@xxxxxxxxxxxxxxxxxxxxx) (gcc version
> 3.4.1 ( Pe
> taLinux 0.20 Build -rc1 050607 )) #11 Mon Sep 29 18:19:24 IST 2008
> setup_cpuinfo: initialising
> setup_cpuinfo: No PVR support in CPU.  Using static compile-time info
> set_cpuinfo_static: Using static CPU info.
> setup_memory: max_mapnr: 0x87fff
> setup_memory: min_low_pfn: 0x86000
> setup_memory: max_low_pfn: 0x2000
> On node 0 totalpages: 8192
>   DMA zone: 64 pages used for memmap
>   DMA zone: 0 pages reserved
>   DMA zone: 8128 pages, LIFO batch:0
>   Normal zone: 0 pages used for memmap
> Built 1 zonelists.  Total pages: 8128
> Kernel command line:
> mtdparts=physmap-flash.0:256K(boot),256K(bootenv),256K(conf
> ig),5M(image),10M(spare) macaddr=00:0a:35:00:22:01
> OPB INTC #0 at 0x81800000
> PID hash table entries: 128 (order: 7, 512 bytes)
> ------------------------
> | Locking API testsuite:
> ------------------------------------------------------------------------
> ----
>                                  | spin |wlock |rlock |mutex | wsem |
> rsem |
>  
> ------------------------------------------------------------------------
> --
>                      A-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>                  A-B-B-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>              A-B-B-C-C-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>              A-B-C-A-B-C deadlock:failed|failed|  ok
> |failed|failed|failed|
>          A-B-B-C-C-D-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>          A-B-C-D-B-D-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>          A-B-C-D-B-C-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
>                     double
> unlock:failed|failed|failed|failed|failed|failed|
>                   initialize
> held:failed|failed|failed|failed|failed|failed|
>                  bad unlock order:  ok  |  ok  |  ok  |  ok  |  ok  |
> ok  |
>  
> ------------------------------------------------------------------------
> --
>               recursive read-lock:             |  ok  |
> |failed|
>            recursive read-lock #2:             |  ok  |
> |failed|
>             mixed read-write-lock:             |failed|
> |failed|
>             mixed write-read-lock:             |failed|
> |failed|
>  
> ------------------------------------------------------------------------
> --
>      hard-irqs-on + irq-safe-A/12:failed|failed|  ok  |
>      soft-irqs-on + irq-safe-A/12:failed|failed|  ok  |
>      hard-irqs-on + irq-safe-A/21:failed|failed|  ok  |
>      soft-irqs-on + irq-safe-A/21:failed|failed|  ok  |
>        sirq-safe-A => hirqs-on/12:failed|failed|  ok  |
>        sirq-safe-A => hirqs-on/21:failed|failed|  ok  |
>          hard-safe-A + irqs-on/12:failed|failed|  ok  |
>          soft-safe-A + irqs-on/12:failed|failed|  ok  |
>          hard-safe-A + irqs-on/21:failed|failed|  ok  |
>          soft-safe-A + irqs-on/21:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/123:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/123:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/132:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/132:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/213:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/213:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/231:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/231:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/312:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/312:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #1/321:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #1/321:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/123:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/123:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/132:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/132:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/213:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/213:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/231:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/231:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/312:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/312:failed|failed|  ok  |
>     hard-safe-A + unsafe-B #2/321:failed|failed|  ok  |
>     soft-safe-A + unsafe-B #2/321:failed|failed|  ok  |
>       hard-irq lock-inversion/123:failed|failed|  ok  |
>       soft-irq lock-inversion/123:failed|failed|  ok  |
>       hard-irq lock-inversion/132:failed|failed|  ok  |
>       soft-irq lock-inversion/132:failed|failed|  ok  |
>       hard-irq lock-inversion/213:failed|failed|  ok  |
>       soft-irq lock-inversion/213:failed|failed|  ok  |
>       hard-irq lock-inversion/231:failed|failed|  ok  |
>       soft-irq lock-inversion/231:failed|failed|  ok  |
>       hard-irq lock-inversion/312:failed|failed|  ok  |
>       soft-irq lock-inversion/312:failed|failed|  ok  |
>       hard-irq lock-inversion/321:failed|failed|  ok  |
>       soft-irq lock-inversion/321:failed|failed|  ok  |
>       hard-irq read-recursion/123:  ok  |
>       soft-irq read-recursion/123:  ok  |
>       hard-irq read-recursion/132:  ok  |
>       soft-irq read-recursion/132:  ok  |
>       hard-irq read-recursion/213:  ok  |
>       soft-irq read-recursion/213:  ok  |
>       hard-irq read-recursion/231:  ok  |
>       soft-irq read-recursion/231:  ok  |
>       hard-irq read-recursion/312:  ok  |
>       soft-irq read-recursion/312:  ok  |
>       hard-irq read-recursion/321:  ok  |
>       soft-irq read-recursion/321:  ok  |
> --------------------------------------------------------
> 145 out of 218 testcases failed, as expected. |
> ----------------------------------------------------
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 27744k/32768k available
> Calibrating delay loop... 24.52 BogoMIPS (lpj=122624)
> Mount-cache hash table entries: 512
> NET: Registered protocol family 16
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 0, 4096 bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> xgpio0 #0 at 0x81400000 mapped to 0x81400000 device: 10,185 not using
> IRQ
> uartlite.0: ttyS0 at MMIO 0x84000000 (irq = 2) is a uartlite
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> eth0: using fifo mode.
> eth0: No PHY detected.  Assuming a PHY at address 0.
> eth0: Xilinx EMACLite #0 at 0x81000000 mapped to 0x81000000, irq=1
> physmap platform flash device: 01000000 at 85000000
> physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
>  Intel/Sharp Extended Query Table at 0x0031
> Using buffer write method
> cfi_cmdset_0001: Erase suspend on write enabled
> erase region 0: offset=0x0,size=0x20000,blocks=128
> 5 cmdlinepart partitions found on MTD device physmap-flash.0
> Creating 5 MTD partitions on "physmap-flash.0":
> 0x00000000-0x00040000 : "boot"
> 0x00040000-0x00080000 : "bootenv"
> 0x00080000-0x000c0000 : "config"
> 0x000c0000-0x005c0000 : "image"
> 0x005c0000-0x00fc0000 : "spare"
> kobject_add failed for physmap-flash.0 with -EEXIST, don't try to
> register thing
> s with the same name in the same directory.
> 
> Stack:
>   87fe1ea4 00000000 86234950 864fbb38 86234950 8612cd58 861fff60
> 86234954
>   8610c14c 86234963 000041ed ffffffff 862348e8 862348e0 8623498c
> ffffffea
>   86131d74 862348e0 862036cc 8623498c 85fffffe 87e2fd1c ffffffff
> 00000001
> Call Trace:
> [<8612cd58>] device_add+0xdc/0x55c
> [<8610c14c>] kobject_release+0x0/0x1c
> [<86131d74>] platform_device_add+0x160/0x1a4
> [<86131dd4>] platform_device_register+0x1c/0x34
> [<86131dcc>] platform_device_register+0x14/0x34
> [<8624fef8>] physmap_init+0x48/0x58
> [<8624fec8>] physmap_init+0x18/0x58
> [<8624fe98>] map_ram_init+0x14/0x2c
> [<860001dc>] init+0x110/0x354
> [<860001dc>] init+0x110/0x354
> [<86001454>] kernel_thread_helper+0xc/0x20
> [<86001448>] kernel_thread_helper+0x0/0x20
> 
> uclinux[mtd]: RAM probe address=0x8626d974 size=0x232000
> Creating 1 MTD partitions on "RAM":
> 0x00000000-0x00232000 : "ROMfs"
> uclinux[mtd]: set ROMfs to be root filesystem index=5
> i8042.c: i8042 controller self test timeout.
> TCP cubic registered
> NET: Registered protocol family 1
> VFS: Mounted root (cramfs filesystem) readonly.
> Freeing unused kernel memory: 100k freed
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> 
> BUG: scheduling while atomic: init/0x00000005/1
> 
> Stack:
>   87fe1f0c 86011568 00000001 00000000 00000000 860020d4 861eeed4
> 864efe58
>   00000005 00000001 8622d2f0 00000000 87fe0000 00000008 00000013
> 00000010
>   87e9ff21 00000001 00000000 00000000 00000000 00000000 00000000
> 16000000
> Call Trace:
> [<86011568>] irq_exit+0x40/0x54
> [<860020d4>] ret_from_intr+0x1c/0x40
> ************************************************************************
> **************************
> 
> Please ignore the disclimer, as it got appended automatically. Sorry for
> the inconvenience caused.
> 
> Regards,
> Makarand
> 
> 
> 
> -----Original Message-----
> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Michal
> Simek
> Sent: Wednesday, September 24, 2008 12:33 AM
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Subject: Re: [microblaze-uclinux] Boot Process Hangs
> 
> Hi Makarand,
> 
> 
> Please send full kernel log.
> Which kernel version do you use? MMU or noMMU version.
> 
>>From part of log which you send me seems you use noMMU version. There is
> interesting that you need 100k of memory for noMMU kernel.
> 
> Please look at pre-built folder in hardware directory and use this
> design and of course in vendor folder are prepared config files for this
> platform. Please test  it first.
> 
> Thanks,
> Michal
> 
>> Hello,
>>  
>> I am trying to bring up the Petalinux on my Spartan3E500RevC board.
>> I managed to build the Hardware, FS-Boot, U-Boot and Kernel Image.
>> But when I tried to boot the kernel image, after a while, the boot 
>> process hangs.
>> The booting process just stops after the "Freeing unused kernel
> memory:
>> 100k freed" message
>>  
>> I have double checked the memory address, those seems to be OK.
>>  
>> One more thing I have tried, that is downloaded the kernel image 
>> directly into SDRAM. But my processor got resetted.
>> Is the U-Boot executes from Flash or SDRAM after copied from Flash?
>>  
>> Any pointer to the solution is highly appreciated.
>>  
>> Thanks
>> Makarand
>>  
>> I got the following message:
>> ========================================================
>> ..
>> ..
>> Creating 5 MTD partitions on "physmap-flash.0":
>> 0x00000000-0x00040000 : "boot"
>> 0x00040000-0x00080000 : "bootenv"
>> 0x00080000-0x000c0000 : "config"
>> 0x000c0000-0x005c0000 : "image"
>> 0x005c0000-0x00fc0000 : "spare"
>> kobject_add failed for physmap-flash.0 with -EEXIST, don't try to 
>> register thing s with the same name in the same directory.
>>  
>> Stack:
>>   8650dea4 00000000 8613efd8 87fc34f8 862523b8 8613efe4 86220790
> 862523bc
>>   86122320 862523cb 000041ed ffffffff 86252350 86252348 862523f4
> ffffffea
>>   86144090 86252348 86223188 862523f4 85fffffe 87f2aad8 ffffffff 
>> 00000001 Call Trace:
>> [<8613efd8>] device_add+0xd0/0x560
>> [<8613efe4>] device_add+0xdc/0x560
>> [<86122320>] kobject_release+0x0/0x1c
>> [<86144090>] platform_device_add+0x160/0x1a4 [<861440f0>] 
>> platform_device_register+0x1c/0x34
>> [<861440e8>] platform_device_register+0x14/0x34
>> [<8626bfbc>] physmap_init+0x48/0x58
>> [<8626bf8c>] physmap_init+0x18/0x58
>> [<8626bf5c>] map_ram_init+0x14/0x2c
>> [<8600020c>] init+0x110/0x360
>> [<8600020c>] init+0x110/0x360
>> [<860014ac>] kernel_thread_helper+0xc/0x20 [<860014a0>] 
>> kernel_thread_helper+0x0/0x20
>>  
>> uclinux[mtd]: RAM probe address=0x86289988 size=0x231000 Creating 1 
>> MTD partitions on "RAM":
>> 0x00000000-0x00231000 : "ROMfs"
>> uclinux[mtd]: set ROMfs to be root filesystem index=5
>> i8042.c: i8042 controller self test timeout.
>> TCP cubic registered
>> NET: Registered protocol family 1
>> VFS: Mounted root (cramfs filesystem) readonly.
>> Freeing unused kernel memory: 100k freed 
>> =========================================================
>>
>> * Please do not print this email unless it is absolutely necessary. *
>>
>> The information contained in this electronic message and any 
>> attachments to this message are intended for the exclusive use of the 
>> addressee(s) and may contain proprietary, confidential or privileged 
>> information. If you are not the intended recipient, you should not 
>> disseminate, distribute or copy this e-mail. Please notify the sender 
>> immediately and destroy all copies of this message and any
> attachments.
>> WARNING: Computer viruses can be transmitted via email. The recipient 
>> should check this email and any attachments for the presence of
> viruses.
>> The company accepts no liability for any damage caused by any virus 
>> transmitted by this email.
>>
>> www.wipro.com
>>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> 
> 
> Please do not print this email unless it is absolutely necessary. 
> 
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 
> 
> www.wipro.com
> 
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
> 
> 
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
Follow-Ups:
- RE: [microblaze-uclinux] Boot Process Hangs
  - From: makarand.vispute
References:
- [microblaze-uclinux] Boot Process Hangs
  - From: makarand.vispute
- Re: [microblaze-uclinux] Boot Process Hangs
  - From: Michal Simek
- RE: [microblaze-uclinux] Boot Process Hangs
  - From: makarand.vispute
Prev by Date: RE: [microblaze-uclinux] Boot Process Hangs
Next by Date: Re: [microblaze-uclinux] Bad page state in process
Previous by thread: RE: [microblaze-uclinux] Boot Process Hangs
Next by thread: RE: [microblaze-uclinux] Boot Process Hangs
Index(es):
- Date
- Thread