Error while copiling the kernel

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Error while copiling the kernel

1,303件の閲覧回数
Nico
Contributor II

Hi...

i'm compiling the kernel using LTIB enviroment for iMX28 platform.

 

When the kernel is loading, it stops after the following serial print:

...

...

Starting kernel ...
Uncompressing Linux... done, booting the kernel.Linux version 2.6.35.3-571-gcca29a0 (root@ubuntu) (gcc version 4.4.4 
(4.4.4_09.06.2010) ) #3 PREEMPT Tue Sep 13 15:48:51 CEST 2011CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177CPU: VIVT data cache, VIVT instruction cacheMachine: Freescale MX28EVK boardMemory policy: ECC disabled, Data cache writebackBuilt 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512Kernel command line: console=ttyAM0,115200n8 root=/dev/nfs 
nfsroot=10.3.3.3:/home/nico/ltib/rootfs,nolock,rsize=4096,wsize=4096 ip=10.3.3.4PID hash table entries: 512 (order: -1, 2048 bytes)Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)Memory: 128MB = 128MB totalMemory: 124316k/124316k available, 6756k reserved, 0K highmemVirtual kernel memory layout:    vector  : 0xffff0000 - 0xffff1000   (   4 kB)    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)    vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)    modules : 0xbf000000 - 0xc0000000   (  16 MB)      .init : 0xc0008000 - 0xc0030000   ( 160 kB)      .text : 0xc0030000 - 0xc04f7000   (4892 kB)      .data : 0xc04f8000 - 0xc0535960   ( 247 kB)SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1Hierarchical RCU implementation.        RCU-based detection of stalled CPUs is disabled.        Verbose stalled-CPUs detection is disabled.NR_IRQS:288Console: colour dummy device 80x30console [ttyAM0] enabledCalibrating delay loop... 226.09 BogoMIPS (lpj=1130496)pid_max: default: 32768 minimum: 301Security Framework initializedSELinux:  Initializing.Mount-cache hash table entries: 512CPU: Testing write buffer coherency: okregulator: core version 0.5NET: Registered protocol family 16regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normalregulator: vdddbo: 800 <--> 1575 mV fast normalregulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normalvddio = 3380000, val=10regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normalregulator: overall_current: fast normalregulator: vbus5v:regulator: mxs-duart-1: fast normalregulator: mxs-bl-1: fast normalregulator: mxs-i2c-1: fast normalregulator: mmc_ssp-1: fast normalregulator: mmc_ssp-2: fast normalregulator: charger-1: fast normalregulator: power-test-1: fast normalregulator: cpufreq-1: fast normali.MX IRAM pool: 124 KB@0xc8820000usb DR wakeup device is registeredIMX usb wakeup probeaudit: cannot initialize inotify handlebio: create slab <bio-0> at 0SCSI subsystem initializedFreescale USB OTG Driver loaded, $Revision: 1.55 $usbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbAdvanced Linux Sound Architecture Driver Version 1.0.23.Switching to clocksource mxs clock sourceNET: Registered protocol family 2IP route cache hash table entries: 1024 (order: 0, 4096 bytes)TCP established hash table entries: 4096 (order: 3, 32768 bytes)TCP bind hash table entries: 4096 (order: 2, 16384 bytes)TCP: Hash tables configured (established 4096 bind 4096)TCP reno registeredUDP hash table entries: 256 (order: 0, 4096 bytes)UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Bus freq driver module loadedIMX

usb wakeup probeusb h1 wakeup device is registered

mxs_cpu_init: cpufreq init finished

 

Looking other demo kernel, the following line should be:

audit: initializing netlink socket (disabled)

type=2000 audit(0.600:1): initialized

 

...any idea  on wich packets include on the kernel configuration provided by LTIB?

ラベル(1)
4 返答(返信)

1,187件の閲覧回数
Nico
Contributor II
Solve!!! Erase all. install ltib again and set FSL gnome release package
0 件の賞賛
返信

1,187件の閲覧回数
AhmetYUCE
Contributor II

I had a similar lockup, the problem was the DDR frequency selected during CPU Freq. module init. Performance governor uses 200MHz which works always.

 

Anyway regarding your second question, if i understand correctly your asking for kernel source and config. If you selected "leave sources..."   option in LTIB, kernel sources should be in /ltib/rpm/BUILD directory. Configs are in usual location in the kernel three.

 

Regards

0 件の賞賛
返信

1,187件の閲覧回数
Nico
Contributor II

The configuration was already in that mode.

 

Others ideas??

Ahmet YUCE said:

Take a look at default governor in kernel settings :

 

CPU Power Management > Default CPUFreq Governor

 

use "performance" governor only.

 

Regards

Ahmet

0 件の賞賛
返信

1,187件の閲覧回数
AhmetYUCE
Contributor II

Take a look at default governor in kernel settings :

 

CPU Power Management > Default CPUFreq Governor

 

use "performance" governor only.

 

Regards

Ahmet