[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] "Found romfs @... klimit" message during kernel boot
Victor G. wrote:
>>> petalinux-dist/u-boot/System.map
>>> linux-2.6-x-petalogix/System.map <- "__log_buf" is at address 0x901b3df8
>>>
>>> When I md this address right after u-boot upload (without kernel
>>> start), I see Linux version 2.6.20, PetaLinux build, CPU info, etc.
>> this is correct - you should see there what you should see on console. Is there any problem with
>> kernel? (Kernel panic or whatever non standard?)
>
> I did not see any panic messages. Since this is the first time booting
> it up, I might be looking in the wrong place for them (i.e. I am just
> referring to kermit and u-boot's messages).
>
> Nothing is displayed on screen except :
> Console 1:
> xmd> dow -data /tftpboot/image.bin 0x90000000
> xmd> rst
>
> Console 2:
> # Uploaded u-boot via serial cat /tftpboot/u-boot.srec > /dev/ttyUSB1
> # Then stopped it and
> U-boot> go 0x90000000
> ## Starting application at 0x90000000 ...
> Found romfs @ 0x901b108c (0x000f7000)
> #### klimit 901c9000 ####
> Moving 0x000f7000 bytes from 0x901b108c to 0x901c8868
> New klimit: 0x902c0000
> L
>
> Note that the last line displays "L", which is the first letter of the
> bootup sequence!
>
> So, what I've done now is via console 1's xmd, I reset the processor
> and it printed "i" to console 2!
> So, every "xmd> rst" in console 1 prints another letter of __log_buf
> to console 2!
>
> Could it be uart flushing problem? When I am running "xmd> rst", it is
> probably re-starting FS-boot at 0x0, but what I see on console 2 is
> the old buffered message sitting in uart. Maybe it has to do something
> with uart interrupts?
>
> It could be that the "klimit" message is normal. I've checked
> 0x901b108c and it has "Compressed ROMFS" text. It is also found at the
> "moved" location as per the message (i.e. 0x901c8868). Looks like it's
> copied there. (it does not lie, there is romfs there).
>
> Does __log_buf address (0x901b3df8) store the messages written by
> kernel? And uart just reads from there and send it over the serial
> link? Then it is booting!
Yes, kernel store all printk messages there and when console driver is ready
then is this ring-buffer written to your console.
>
>>> If I upload kernel, however, using xmd as described in my previous
>>> post, the "klimit" message is displayed and u-boot becomes
>>> inaccessible. Did you want me to check this address after kernel
>>> loading attempt by any chance?
>> Workflow - load kernel via xmd, wait some time - xmd - load U-BOOT (dow u-boot),
>> md 0x901b3df8 to see what kernel did.
>
> After the above debugging, I re-uploaded the system bitstream via
> impact because I could not get back to normal u-boot prompt. Checking
> 0x901b3df8 showed the expected bootup sequence "Linux version
> 2.6.20"etc. I scrolled down the memory and saw that the last messages
> displayed were (followed by empty lines):
> "io scheduler deadline registered
> io scheduler cfq registered (default)
> uartlite.0: ttyUL0 at MMIO 0x84000000 (irq = 2) is uartlite"
>
> Another thing I've seen above in __log_buf was:
> OPB INTC #0 at 0x81800000
> which calls for another question. I enabled OPB interrupt controller
> in menuconfig. However, I am using PLB bus. Does it make sense? I
> didn't see any warnings.
>
> Maybe something is screwed with Uartlite's interrupts because of that.
For MMU kernel which I have up
grep "__log_buf" System.map
c0519bf0 b __log_buf
My main memory starts at 0x90000000 -> changed log buffer 0x90519bf0 (you get for noMMU kernel this
address)
Reset board and read this addr by md. You get the similar output.
What do you have there? Please send full log not only part of it!
Michal
SDRAM :
Icache:OK
Dcache:OK
U-Boot Start:0x9ffc0000
FLASH: 32 MB
MAC:00:E0:0C:00:00:FD
eth0: Xilinx XPS LocalLink Tri-Mode Ether MAC #0 at 0x81C00000.
Unsupported mode
U-Boot-mONStR> md 0x90519bf0
90519bf0: 3c353e4c 696e7578 20766572 73696f6e <5>Linux version
90519c00: 20322e36 2e33302d 30303030 332d6766 2.6.30-00003-gf
90519c10: 63303331 34322d64 69727479 20286d6f c03142-dirty (mo
90519c20: 6e737472 406d6f6e 7374722e 65752920 nstr@xxxxxxxxx)
90519c30: 28676363 20766572 73696f6e 20342e31 (gcc version 4.1
90519c40: 2e322920 23313134 20547565 204a756c .2) #114 Tue Jul
90519c50: 20313420 31303a35 313a3437 20434553 14 10:51:47 CES
90519c60: 54203230 30390a3c 363e7365 7475705f T 2009.<6>setup_
90519c70: 63707569 6e666f3a 20696e69 7469616c cpuinfo: initial
90519c80: 6973696e 670a3c36 3e736574 75705f63 ising.<6>setup_c
90519c90: 7075696e 666f3a20 5573696e 67206675 puinfo: Using fu
90519ca0: 6c6c2043 50552050 56522073 7570706f ll CPU PVR suppo
90519cb0: 72740a3c 363e7365 7475705f 6d656d6f rt.<6>setup_memo
90519cc0: 72793a20 6d61785f 6d61706e 723a2030 ry: max_mapnr: 0
90519cd0: 78313030 30300a3c 363e7365 7475705f x10000.<6>setup_
90519ce0: 6d656d6f 72793a20 6d696e5f 6c6f775f memory: min_low_
U-Boot-mONStR>
90519cf0: 70666e3a 20307839 30303030 0a3c363e pfn: 0x90000.<6>
90519d00: 73657475 705f6d65 6d6f7279 3a206d61 setup_memory: ma
90519d10: 785f6c6f 775f7066 6e3a2030 78613030 x_low_pfn: 0xa00
90519d20: 30300a3c 373e4f6e 206e6f64 65203020 00.<7>On node 0
90519d30: 746f7461 6c706167 65733a20 36353533 totalpages: 6553
90519d40: 360a3c37 3e667265 655f6172 65615f69 6.<7>free_area_i
90519d50: 6e69745f 6e6f6465 3a206e6f 64652030 nit_node: node 0
90519d60: 2c207067 64617420 63303264 64333030 , pgdat c02dd300
90519d70: 2c206e6f 64655f6d 656d5f6d 61702063 , node_mem_map c
90519d80: 30353439 3030300a 3c373e20 204e6f72 0549000.<7> Nor
90519d90: 6d616c20 7a6f6e65 3a203531 32207061 mal zone: 512 pa
90519da0: 67657320 75736564 20666f72 206d656d ges used for mem
90519db0: 6d61700a 3c373e20 204e6f72 6d616c20 map.<7> Normal
90519dc0: 7a6f6e65 3a203020 70616765 73207265 zone: 0 pages re
90519dd0: 73657276 65640a3c 373e2020 4e6f726d served.<7> Norm
90519de0: 616c207a 6f6e653a 20363530 32342070 al zone: 65024 p
U-Boot-mONStR>
90519df0: 61676573 2c204c49 464f2062 61746368 ages, LIFO batch
90519e00: 3a31350a 3c343e42 75696c74 2031207a :15.<4>Built 1 z
90519e10: 6f6e656c 69737473 20696e20 5a6f6e65 onelists in Zone
90519e20: 206f7264 65722c20 6d6f6269 6c697479 order, mobility
90519e30: 2067726f 7570696e 67206f6e 2e202054 grouping on. T
90519e40: 6f74616c 20706167 65733a20 36353032 otal pages: 6502
90519e50: 340a3c35 3e4b6572 6e656c20 636f6d6d 4.<5>Kernel comm
90519e60: 616e6420 6c696e65 3a20636f 6e736f6c and line: consol
90519e70: 653d7474 79554c30 2c313135 3230300a e=ttyUL0,115200.
90519e80: 3c363e4e 525f4952 51533a33 320a3c36 <6>NR_IRQS:32.<6
90519e90: 3e786c6e 782c7870 732d696e 74632d31 >xlnx,xps-intc-1
90519ea0: 2e30302e 61202330 20617420 30786664 .00.a #0 at 0xfd
90519eb0: 66666630 30302c20 6e756d5f 6972713d fff000, num_irq=
90519ec0: 392c2065 6467653d 30783130 300a3c34 9, edge=0x100.<4
90519ed0: 3e504944 20686173 68207461 626c6520 >PID hash table
90519ee0: 656e7472 6965733a 20313032 3420286f entries: 1024 (o
U-Boot-mONStR>
90519ef0: 72646572 3a203130 2c203430 39362062 rder: 10, 4096 b
90519f00: 79746573 290a3c36 3e786c6e 782c7870 ytes).<6>xlnx,xp
90519f10: 732d7469 6d65722d 312e3030 2e612023 s-timer-1.00.a #
90519f20: 30206174 20307866 64666665 3030302c 0 at 0xfdffe000,
90519f30: 20697271 3d330a3c 353e4865 61727462 irq=3.<5>Heartb
90519f40: 65617420 4750494f 20617420 30786664 eat GPIO at 0xfd
90519f50: 66666430 30300a3c 363e6d69 63726f62 ffd000.<6>microb
90519f60: 6c617a65 5f74696d 65725f73 65745f6d laze_timer_set_m
90519f70: 6f64653a 20736875 74646f77 6e0a3c36 ode: shutdown.<6
90519f80: 3e6d6963 726f626c 617a655f 74696d65 >microblaze_time
90519f90: 725f7365 745f6d6f 64653a20 70657269 r_set_mode: peri
90519fa0: 6f646963 0a3c363e 44656e74 72792063 odic.<6>Dentry c
90519fb0: 61636865 20686173 68207461 626c6520 ache hash table
90519fc0: 656e7472 6965733a 20333237 36382028 entries: 32768 (
90519fd0: 6f726465 723a2035 2c203133 31303732 order: 5, 131072
90519fe0: 20627974 6573290a 3c363e49 6e6f6465 bytes).<6>Inode
U-Boot-mONStR>
90519ff0: 2d636163 68652068 61736820 7461626c -cache hash tabl
9051a000: 6520656e 74726965 733a2031 36333834 e entries: 16384
9051a010: 20286f72 6465723a 20342c20 36353533 (order: 4, 6553
9051a020: 36206279 74657329 0a3c363e 4d656d6f 6 bytes).<6>Memo
9051a030: 72793a20 32353430 38306b2f 32363231 ry: 254080k/2621
9051a040: 34346b20 61766169 6c61626c 650a3c36 44k available.<6
9051a050: 3e43616c 69627261 74696e67 2064656c >Calibrating del
9051a060: 6179206c 6f6f702e 2e2e2036 312e3233 ay loop... 61.23
9051a070: 20426f67 6f4d4950 5320286c 706a3d33 BogoMIPS (lpj=3
9051a080: 30363137 36290a3c 343e4d6f 756e742d 06176).<4>Mount-
9051a090: 63616368 65206861 73682074 61626c65 cache hash table
9051a0a0: 20656e74 72696573 3a203531 320a3c36 entries: 512.<6
9051a0b0: 3e6e6574 5f6e616d 65737061 63653a20 >net_namespace:
9051a0c0: 35363420 62797465 730a3c36 3e4e4554 564 bytes.<6>NET
9051a0d0: 3a205265 67697374 65726564 2070726f : Registered pro
9051a0e0: 746f636f 6c206661 6d696c79 2031360a tocol family 16.
U-Boot-mONStR>
9051a0f0: 3c343e62 696f3a20 63726561 74652073 <4>bio: create s
9051a100: 6c616220 3c62696f 2d303e20 61742030 lab <bio-0> at 0
9051a110: 0a3c363e 4e45543a 20526567 69737465 .<6>NET: Registe
9051a120: 72656420 70726f74 6f636f6c 2066616d red protocol fam
9051a130: 696c7920 320a3c36 3e495020 726f7574 ily 2.<6>IP rout
9051a140: 65206361 63686520 68617368 20746162 e cache hash tab
9051a150: 6c652065 6e747269 65733a20 32303438 le entries: 2048
9051a160: 20286f72 6465723a 20312c20 38313932 (order: 1, 8192
9051a170: 20627974 6573290a 3c363e54 43502065 bytes).<6>TCP e
9051a180: 73746162 6c697368 65642068 61736820 stablished hash
9051a190: 7461626c 6520656e 74726965 733a2038 table entries: 8
9051a1a0: 31393220 286f7264 65723a20 342c2036 192 (order: 4, 6
9051a1b0: 35353336 20627974 6573290a 3c363e54 5536 bytes).<6>T
9051a1c0: 43502062 696e6420 68617368 20746162 CP bind hash tab
9051a1d0: 6c652065 6e747269 65733a20 38313932 le entries: 8192
9051a1e0: 20286f72 6465723a 20352c20 31363338 (order: 5, 1638
>
> Thanks,
> Victor
> ___________________________
> 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/
>
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
___________________________
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/