INIT:
Paulinha
gnathita at gmail.com
Mon Mar 6 18:55:28 EST 2006
... and TLB support!!
Paula
On 3/3/06, Patil, Pankaj P. <Pankaj.Patil at hp.com> wrote:
> >
> > I do have /dev/console in my file system. In fact , i used ethereal on
> > the host to see how far the INIT goes.
> > I saw all the usual NFS Lookup calls like /lib, /ld-2.3.1.so .....
> > /libc- 2.31.so
> > The last NFS lookup call looks like DH:0xbea72a4a/tty0
> > There are bunch of read replys after that but no more NFS lookups. Is it
> > normal to see a NFS Lookup that looks like 0xbea72a4a/tty0 ??
> > What should be the next NFS Lookup call?
> > I did some searching from previous posts but haven't found exactly what
> > i am looking for. I am attaching a link to something that looks similar to
> > my problem. Just in case, someone's having trouble understanding my issue.
> > http://ozlabs.org/pipermail/linuxppc-embedded/2004-August/015250.html
> >
> > Thanks
> > pankaj
> >
> > -----Original Message-----
> > From: atul.sabharwal at exgate.tek.com
> > [mailto:atul.sabharwal at exgate.tek.com]
> > Sent: Tuesday, February 28, 2006 6:03 PM
> > To: Patil, Pankaj P.
> > Cc: linuxppc-embedded at ozlabs.org
> > Subject: RE: INIT:
> >
> >
> > Easy answer is do you have /dev/console in your file system. Glibc
> > opens
> > /dev/console and the kernel uses /dev/ttyS0 as specified on the command
> > line. There should not be any app calling uart_close as the console
> > deriver
> > should be opening it.
> >
> > --
> > Atul
> >
> > Hi,
> > I am running u-boot & linux2.6.12 on a custom ppc board(functional HW).
> > I can get to the point where u-boot loads the kernel, kernel does all
> > the initialization, loads the Root File System over NFS & calls the
> > Init process.
> > Next, i am expecting to see a shell prompt. I am not sure where in the
> > Init process i am failing. I have written my own serial driver(Philips
> > SC28L194 Quad UART--under development-possible culprit). The printks
> > work just fine.
> > All i see is the kernel calling the Init process & after a minute or so
> > i see uart_close call.
> > The kernel runs just fine & responds to ping.
> > What can trigger a uart_close??(tty_release calls release_dev calls
> > uart_close) I have a JTAG debugger. What's the best way to debug once
> > Init process is running??
> >
> >
> >
> > I am attaching a dump of my console:
> > U-Boot 1.1.3 (Dec 16 2005 - 16:00:23), Build: 0.4.1
> >
> > SysClock = 120Mhz , TClock = 120Mhz
> > CPU: MPC7447A v1.1 @ 960 MHz
> > CPU bus mode : 60x
> >
> > DRAM: SPD Checksum ok!
> > -- DIMM1 has 2 banks
> > -- DIMM2 has 0 banks
> > ECC Initialization of Bank 0: Done
> > CAS Latency = 2 tRP = 3 tRAS = 6 tRCD=3
> > Total SDRAM memory is 1024 MB
> > Now running in RAM - U-Boot at: 00fc0000
> > Remapped Internal SRAM to 0xf2000000
> > Remapped Flash Card to 0xffc00000
> > FLASH: 4 MB
> > Addresses 32M - 0M are saved for the U-Boot usage.
> > Mem malloc Initialization (32M - 16M): Done
> >
> > Internal SRAM ECC Initialization: Done
> > ***Phy Reset***
> > Phy Auto-Negotiation Bit ReEnabled in SW
> > Net: , mv_enet1 [PRIME]
> > Hit any key to stop autoboot: 0
> > Ethernet status port 1: Link up, Full Duplex, Speed 100 Mbps
> > Using mv_enet1 device
> > TFTP from server 192.168.1.1; our IP address is 192.168.1.2
> > Filename 'uImage'.
> > Load address: 0x400000
> > Loading:
> > #################################################################
> >
> > #################################################################
> >
> > #################################################################
> > ########################
> > done
> > Bytes transferred = 1119847 (111667 hex)
> >
> > ### Network statistics: ###
> > --------------------------
> > Packets received: 2192
> > Packets send: 2191
> > Received bytes: 2347583
> > Send bytes: 100803
> > ## Booting image at 00400000 ...
> > Image Name: Linux-2.6.12
> > Created: 2006-02-14 0:37:17 UTC
> > Image Type: PowerPC Linux Kernel Image (gzip compressed)
> > Data Size: 1119783 Bytes = 1.1 MB
> > Load Address: 00000000
> > Entry Point: 00000000
> > Verifying Checksum ... OK
> > Uncompressing Kernel Image ... OK
> > ## cmdline at 0x007FFF00 ... 0x007FFF98
> > memstart = 0x00000000
> > memsize = 0x40000000
> > flashstart = 0xFFC00000
> > flashsize = 0x00400000
> > flashoffset = 0x00000000
> > sramstart = 0xF8000000
> > sramsize = 0x00400000
> > bootflags = 0x00000001
> > intfreq = 960 MHz
> > busfreq = 120 MHz
> > ethaddr = 64:00:00:00:00:00
> > IP addr = 192.168.1.2
> > baudrate = 115200 bps
> > tclk = 0 MHz
> > uboot_ver = 0.4.1a
> > L3 was init = 0
> > Total memory = 768MB; using 2048kB for hash table (at c0400000)
> > Linux version 2.6.12 (root at RHEL40) (gcc version 3.3.3 (DENX ELDK 3.1.1
> > 3.3.3-10)) #154 Mon Feb 13 17:36:35 MST 2006
> > System Identification:
> > Freescale 74XX port
> > Built 1 zonelists
> > Kernel command line: console=ttyS0,115200 root=/dev/nfs rw
> > nfsroot=192.168.1.1:/target/chestnut/rootfs
> > ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:DB64xxx:eth0:non
> > e
> > PID hash table entries: 4096 (order: 12, 65536 bytes)
> > time_init: decrementer frequency = 30.000000 MHz
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> > Memory: 774400k available (1596k kernel code, 556k data, 344k init, 0k
> > highmem)
> > Mount-cache hash table entries: 512
> >
> > NET: Registered protocol family 16
> > PCI: Probing PCI hardware
> > JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
> > Generic RTC Driver v1.07
> > Serial: SC28L194 driver 4 ports
> > ttyS0 at MMIO 0x0 (irq = 17) is a PHILIPS SC28L194
> > ttyS1 at MMIO 0x0 (irq = 17) is a PHILIPS SC28L194
> > ttyS2 at MMIO 0x0 (irq = 17) is a PHILIPS SC28L194
> > ttyS3 at MMIO 0x0 (irq = 17) is a PHILIPS SC28L194
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered
> > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> > loop: loaded (max 8 devices)
> > MV-643xx 10/100/1000 Ethernet Driver
> > eth0: port 1 with MAC address 00:11:85:da:0b:02
> > eth0: RX NAPI Enabled
> > physmap flash device: 400000 at ffc00000
> > mice: PS/2 mouse device common for all mice
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 8192 buckets, 64Kbytes
> > TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
> > TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
> > TCP: Hash tables configured (established 131072 bind 65536)
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > IP-Config: Complete:
> > device=eth0, addr=192.168.1.2 , mask=255.255.255.0, gw=192.168.1.1
> > ,
> > host=DB64xxx, domain=, nis-domain=(none),
> > bootserver=192.168.1.1 , rootserver=192.168.1.1, rootpath=
> > Looking up port of RPC 100003/2 on 192.168.1.1
> > Looking up port of RPC 100005/1 on 192.168.1.1
> > VFS: Mounted root (nfs filesystem).
> > Freeing unused kernel memory: 344k init
> >
> >
> > Any help appreceated.
> > Thanks
> > pankaj
> >
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded at ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded at ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060306/5ac2a903/attachment.htm
More information about the Linuxppc-embedded
mailing list