ltib
[Top][All Lists]
Advanced

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

RE: [Ltib] Build success for LPC32xx target, kernel issues :-(


From: Kevin Wells
Subject: RE: [Ltib] Build success for LPC32xx target, kernel issues :-(
Date: Sat, 31 Jul 2010 00:00:35 +0200

Hi Peter & Tim,

 

One more item to look at…

 

>ÿLinux version 2.6.27.8 (address@hidden) (gcc version 4.3.2 (crosstool -NG-1.3.1) ) #3 PREEMPT Fri May 15 17:31:02 CST 2009

This is suspect. The default configurations in LTIB use GCC-4.1.2 for kernel and rootfs build. GCC 4.3.2 is no longer available in the options list for the Phytec board.

The date and time on this kernel image suggest this was an older archived kernel image. (?)

 

Is your root file system also built with GCC 4.3.2? The latest updates use GCC 4.12. to built the rootfs. Images built with GCC 4.1.2 (and EABI) won’t run on a kernel built with 4.3.2.

 

thanks,

Kevin

 

 

From: address@hidden [mailto:address@hidden On Behalf Of Peter Barada
Sent: Friday, July 30, 2010 1:48 PM
To: Tim Nelson
Cc: address@hidden
Subject: Re: [Ltib] Build success for LPC32xx target, kernel issues :-(

 

On Fri, 2010-07-30 at 15:33 -0500, Tim Nelson wrote:

----- "Peter Barada" <address@hidden> wrote: 

> Can you verify your NFS setup by mounting 172.16.23.170:/usr/src/ltib_clean_postcrcerrors/ltib/rootfs from another machine?  If it works there, then somethings not quite

> right with your kernel - can you post the relevant portion of the kernel log?

Yes, the export is mountable from other machines as well. Here is the full output of the boot including where it fails:

 

***BEGIN***

Phytec LPC3250 board

Build date: Dec  4 2008 11:44:18

Autoboot in progress, press any key to stop

 

U-Boot 1.3.3 (May 15 2009 - 12:30:25)

 

DRAM:  64 MB

NAND:  32 MiB

In:    serial

Out:   serial

Err:   serial

Hit any key to stop autoboot:  0

 

Loading from NAND 32MiB 3,3V 8-bit, offset 0x190000

   Image Name:   Linux-2.6.27.8

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1697180 Bytes =  1.6 MB

   Load Address: 80008000

   Entry Point:  80008000

## Booting kernel from Legacy Image at 80100000 ...

   Image Name:   Linux-2.6.27.8

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1697180 Bytes =  1.6 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

 

Starting kernel ...

 

Uncompressing Linux.............................................................

..................... done, booting the kernel.

ÿLinux version 2.6.27.8 (address@hidden) (gcc version 4.3.2 (crosstool

-NG-1.3.1) ) #3 PREEMPT Fri May 15 17:31:02 CST 2009

CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177

Machine: Phytec 3250 board with the LPC3250 Microcontroller

Memory policy: ECC disabled, Data cache writeback

CPU0: D VIVT write-back cache

CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256

Kernel command line: console=ttyS0,115200n81 root=/dev/nfs rw nfsroot=172.16.23.

170:/usr/src/ltib_clean_postcrcerrors/ltib/rootfs ip=dhcp init=/sbin/init

PID hash table entries: 256 (order: 8, 1024 bytes)

Console: colour dummy device 80x30

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory: 64MB = 64MB total

Memory: 61304KB available (3216K code, 233K data, 104K init)

Calibrating delay loop... 103.42 BogoMIPS (lpj=206848)

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

net_namespace: 288 bytes

NET: Registered protocol family 16

Hardware descriptor info:

 DRAM config word: 0x00000008

 syscfg word:      0x00000001

 fieldval word:    0x000a3250

 MAC address:      <6>00:01:90:00:c0:81

LPC32XX DMA driver

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

NET: Registered protocol family 1

NetWinder Floating Point Emulator V0.97 (double precision)

JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

msgmni has been set to 119

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

CLCD: Phytec LCD hardware, QVGA portrait display

Console: switching to colour frame buffer device 40x30

Serial: 8250/16550 driver4 ports, IRQ sharing disabled

serial8250.0: ttyS0 at MMIO 0x40090000 (irq = 9) is a 16550A

console [ttyS0] enabled

serial8250.0: ttyS1 at MMIO 0x40080000 (irq = 7) is a 16550A

loop: module loaded

LPC32XX_mii_bus: probed

eth0: LPC32XX mac at 0x31060000 irq 29

eth0: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=0:00, irq=-1)

Driver 'sd' needs updating - please use bus_type methods

NAND device: Manufacturer ID: 0x20, Chip ID: 0x75 (ST Micro NAND 32MiB 3,3V 8-bi

t)

Scanning device for bad blocks

Creating 4 MTD partitions on "lpc32xx_nand":

0x00000000-0x00168000 : "phy3250-boot"

0x00168000-0x00190000 : "phy3250-ubt-prms"

0x00190000-0x00590000 : "phy3250-kernel"

0x00590000-0x02000000 : "phy3250-rootfs"

at25 spi0.0: 32 KByte at25256a eeprom, pagesize 64

usbmon: debugfs is not available

I2C device at address 0x2d<6>ISP1301 Vendor ID  : 0x04cc

ISP1301 Product ID : 0x1301

ISP1301 Version ID : 0x0210

usb-ohci usb-ohci: at 0xf3120000, irq 0

usb-ohci usb-ohci: pnx4008 OHCI

usb-ohci usb-ohci: new USB bus registered, assigned bus number 1

usb-ohci usb-ohci: irq 59, io mem 0xf3120000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 2 ports detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver libusual

mice: PS/2 mouse device common for all mice

input: LPC32xx Touchscreen as /class/input/input0

rtc-lpc32xx rtc-lpc32xx: rtc core: registered rtc-lpc32xx as rtc0

i2c /dev entries driver

PNX4008-WDT: PNX4008 Watchdog Timer: heartbeat 19 sec

mmci-pl18x: DMA buffer(10000 bytes), P:0x83950000, V:0xffc40000

mmc0: MMCI rev 0 cfg 00 at 0x0000000020098000 irq 15,13

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.17.

ASoC version 0.13.2

UDA1380 Audio Codec 0.6<6>asoc: UDA1380 <-> lpc3xxx-i2s1 mapping ok

ALSA device list:

  #0: LPC3XXX_I2S_UDA1380 (UDA1380)

TCP cubic registered

NET: Registered protocol family 17

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

ieee80211: 802.11 data/management/control stack, git-1.1.13

ieee80211: Copyright (C) 2004-2005 Intel Corporation <address@hidden>

VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1

rtc-lpc32xx rtc-lpc32xx: setting system clock to 1970-02-02 13:56:56 UTC (281501

6)

Sending DHCP requests .., OK

IP-Config: Got DHCP answer from 172.16.23.45, my address is 172.16.23.131

IP-Config: Complete:

     device=eth0, addr=172.16.23.131, mask=255.255.255.0, gw=172.16.23.1,

     host=172.16.23.131, domain=rockbochs.com, nis-domain=(none),

     bootserver=172.16.23.45, rootserver=172.16.23.170, rootpath=

Looking up port of RPC 100003/2 on 172.16.23.170

Looking up port of RPC 100005/1 on 172.16.23.170

VFS: Mounted root (nfs filesystem).

Freeing init memory: 104K

Kernel panic - not syncing: Attempted to kill init!

***END***


That's quite strange.  Usually when it panic's with that message the kernel tells you why.  You could try adding printk's into the end of init_post (init/main.c) before/after each line that tries to run init program:

 
    printk("%s:%d\n", __FUNCTION__, __LINE__);
    run_init_process("/sbin/init");
    printk("%s:%d\n", __FUNCTION__, __LINE__);
    run_init_process("/etc/init");
    printk("%s:%d\n", __FUNCTION__, __LINE__);
    run_init_process("/bin/init");
    printk("%s:%d\n", __FUNCTION__, __LINE__);
    run_init_process("/bin/sh");
    printk("%s:%d\n", __FUNCTION__, __LINE__);
 

boot with "ignore_loglevel" to see if a "printk(KERN_DEIBUG" message was suppressed.  With the output you should be able to figure out if the kernel fired up init (and its init that's dying).  Also check that the init program and libraries are all installed on your rootfs correctly (and are for the right machine)...


 

So, it appears I can mount the filesystem (or rather the kernel can...) but something is amiss after this.

 

--Tim

 
_______________________________________________
LTIB home page: http://ltib.org
 
Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib

 


reply via email to

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