help with inittab

help with inittab

[Chris Dumoulin]

I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
4.0. Currently, I seem to be able to boot without errors, but after the 
root filesystem is mounted, things just stop.

I'm guessing that my problems are related to the setup of the RFS, and 
more specifically, my inittab file. Here is the output I get at boot time:
Linux version 2.6.15 (cdumoulin@localhost.localdomain) (gcc version 
4.0.0 (DENX ELDK 4.0 4.0.0)) #167 PREEMPT Thu Jun 8 6Built 1 zonelists
Kernel command line: console=ttyS0,57600 ip=off
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 62120k available (968k kernel code, 272k data, 76k init, 0k highmem)
Mount-cache hash table entries: 512
checking if image is initramfs...it isn't (no cpio magic); looks like an 
initrd
Freeing initrd memory: 1404k freed
Linux NoNET1.0 for Linux 2.6
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 
sec (nowayout= 0)
ipmi message handler version 38.0
ipmi device interface
IPMI Watchdog: driver initialized
i8042.c: No controller found.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 24) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
mice: PS/2 mouse device common for all mice
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).

And here is my initttab file:
::sysinit:/etc/rc.sh
::askfirst:/bin/sh
::ctrlaltdel:/sbin/reboot
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r
::restart:/sbin/init

Any ideas would be appreciated.

Cheers,
Chris Dumoulin
-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/8/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> 4.0. Currently, I seem to be able to boot without errors, but after the
> root filesystem is mounted, things just stop.
>
> I'm guessing that my problems are related to the setup of the RFS, and
> more specifically, my inittab file. Here is the output I get at boot time:
> Linux version 2.6.15 (cdumoulin@localhost.localdomain) (gcc version
> 4.0.0 (DENX ELDK 4.0 4.0.0)) #167 PREEMPT Thu Jun 8 6Built 1 zonelists
> Kernel command line: console=ttyS0,57600 ip=off
> PID hash table entries: 512 (order: 9, 8192 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 62120k available (968k kernel code, 272k data, 76k init, 0k highmem)
> Mount-cache hash table entries: 512
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
> Freeing initrd memory: 1404k freed
> Linux NoNET1.0 for Linux 2.6
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60
> sec (nowayout= 0)
> ipmi message handler version 38.0
> ipmi device interface
> IPMI Watchdog: driver initialized
> i8042.c: No controller found.
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250: ttyS0 at MMIO 0x0 (irq = 24) is a 16550A
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> mice: PS/2 mouse device common for all mice
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
>
> And here is my initttab file:
> ::sysinit:/etc/rc.sh
> ::askfirst:/bin/sh
> ::ctrlaltdel:/sbin/reboot
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
> ::restart:/sbin/init
>

Doesn't seem like you are respawning any login stuff?  Where are your
tty's?  Change the askfirst to /bin/sh and you should get a shell at
the start assuming you have /bin/sh.


> Any ideas would be appreciated.
>
> Cheers,
> Chris Dumoulin
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

Re: help with inittab

[Wolfgang Denk]

In message <44888B92.40409@ics-ltd.com> you wrote:
> I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
> 4.0. Currently, I seem to be able to boot without errors, but after the 
> root filesystem is mounted, things just stop.

And  what's  your  console  device?  Are  you  passing  any  console=
arguments  on  the  command  line?  Is the corresponding device entry
present in the /dev/directory?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Sometimes a feeling is all we humans have to go on.
	-- Kirk, "A Taste of Armageddon", stardate 3193.9

Help -- failed to boot up kernel on PPC40 5

[Denny]

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

Dear Denk,
 
      I use the linux 2.6.14 of your website, and compile it with the ELDK4.0 succesfully, but when I download it to my PPC405 board, it stopped after initialized the MMU, and encounter an exception in "_start_here".
 
Logs:
u-boot => tftpboot 0x6000000 uImage
miiphy_register: non unique device name 'ppc_4xx_eth0'
ENET Speed is 100 Mbps - FULL duplex connection
TFTP from server 192.168.65.235; our IP address is 192.168.65.239
Filename 'uImage'.
Load address: 0x6000000
Loading: #################################################################
         #####################################
done
Bytes transferred = 521637 (7f5a5 hex)
u-boot => bootm 0x6000000
## Booting image at 0x06000000 ...
   Image Name:   Linux-2.6.14
   Created:      2006-06-09   1:00:37 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    521573 Bytes = 509.3 kB
   Load Address: 0x00100000
   Entry Point:  0x00100000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Now starting to boot the kernel...
## Current stack ends at 0x07F81A90 => set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF00
memstart    = 0x00000000
memsize     = 0x08000000
flashstart  = 0xFFFA0000
flashsize   = 0x01080000
flashoffset = 0x00029300
sramstart   = 0x00000000
sramsize    = 0x00000000
bootflags   = 0x0000A000
procfreq    =    200 MHz
plb_busfreq =    100 MHz
pci_busfreq = 33.333 MHz
ethaddr     = 00:01:02:54:12:47
IP addr     = 192.168.65.239
baudrate    =   9600 bps
Ramdisk image not found, no initrd!
## Transferring control to Linux (at address 0x00100000) ...
booting kernel with FLAT_TREE...
NIP: C000221C XER: 20000000 LR: 00100018 REGS: 07f819a0 TRAP: 0700 DAR: 07FC31D0
MSR: 00021030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
GPR00: C0002218 07F81A90 00000000 C00003C0 C0000000 00000000 007FFF00 007FFF00 
GPR08: 07FAB560 0BEBC200 00000000 00000000 20BDE736 00000000 07FD0D00 007FFF00 
GPR16: 00100000 07FCF70C FFFFFFFF 00000000 00800000 007FFF00 07FCAE20 00000002 
GPR24: 07F81B50 007FFE70 00780000 007FFF00 007FFF00 00000000 00000000 007FFE70 
** Illegal Instruction **
Call backtrace: 
Program Check Exception

U-Boot 1.1.4 (Jun  9 2006 - 09:36:28)
...
...
My objdump file is as the following:
...
c0002208: 7c 00 04 ac  sync    
c000220c: 4c 00 00 64  rfi
c0002210: 48 00 00 00  b       c0002210 <finish_tlb_load+0x48>
c0002214 <giveup_fpu>:
c0002214: 4e 80 00 20  blr
c0002218 <start_here>:
c0002218: 3c 40 c0 0f  lis     r2,-16369
c000221c: 60 42 17 60  ori     r2,r2,5984
c0002220: 3c 82 40 00  addis   r4,r2,16384
c0002224: 38 84 01 c8  addi    r4,r4,456
...
 
Best Regards!
- Denny
 

[-- Attachment #2: Type: text/html, Size: 4128 bytes --]

Re: Help -- failed to boot up kernel on PPC40 5

[Wolfgang Denk]

In message <4488D8D1.00003F.15159@bj163app14.163.com> you wrote:
> 
>       I use the linux 2.6.14 of your website, and compile it with the ELDK4.0 succesfully, but when I download it to my PPC405 board, it stopped after initialized the MMU, and encounter an exception in "_start_here".

Is this a standard AMCC eval board, or a custom board? Which one?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Those who hate and fight must stop themselves -- otherwise it is  not
stopped.
	-- Spock, "Day of the Dove", stardate unknown

Re: help with inittab

[Chris Dumoulin]

I've now determined that my kernel seems to stop in the following line 
of code, in the function init(void * unused), in init/main.c:
run_init_process("/sbin/init");
I've determined that it stops at this call by stepping through the code 
with a BDI2000.

My boot arguments are:
console=ttyS0,57600n8 ip=off root=/dev/ram0 rw

My current inittab is:
::sysinit:/etc/rc.sh
::ctrlaltdel:/sbin/reboot
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r
::restart:/sbin/init
::respawn:/bin/sh

I've tried adding an "echo" command to the /etc/rc.sh script that is 
called, but I don't see any output. I've also trying changing the 
::sysinit line in inittab to point to some non-existent script, to see 
if I'll get some error message, but I still see nothing. Is it possible 
that /sbin/init is dying before it gets to the point of reading inittab?
Any ideas?

Regards,
Chris Dumoulin


Wolfgang Denk wrote:

>In message <44888B92.40409@ics-ltd.com> you wrote:
>  
>
>>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK 
>>4.0. Currently, I seem to be able to boot without errors, but after the 
>>root filesystem is mounted, things just stop.
>>    
>>
>
>And  what's  your  console  device?  Are  you  passing  any  console=
>arguments  on  the  command  line?  Is the corresponding device entry
>present in the /dev/directory?
>
>Best regards,
>
>Wolfgang Denk
>
>  
>

-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> I've now determined that my kernel seems to stop in the following line
> of code, in the function init(void * unused), in init/main.c:
> run_init_process("/sbin/init");

Who's init are  you using??

Are you using Busyboxes or sysinit from GNU?


> I've determined that it stops at this call by stepping through the code
> with a BDI2000.
>
> My boot arguments are:
> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>
> My current inittab is:
> ::sysinit:/etc/rc.sh
> ::ctrlaltdel:/sbin/reboot
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
> ::restart:/sbin/init
> ::respawn:/bin/sh
>
> I've tried adding an "echo" command to the /etc/rc.sh script that is
> called, but I don't see any output. I've also trying changing the
> ::sysinit line in inittab to point to some non-existent script, to see
> if I'll get some error message, but I still see nothing. Is it possible
> that /sbin/init is dying before it gets to the point of reading inittab?
> Any ideas?
>
> Regards,
> Chris Dumoulin
>
>
> Wolfgang Denk wrote:
>
> >In message <44888B92.40409@ics-ltd.com> you wrote:
> >
> >
> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> >>4.0. Currently, I seem to be able to boot without errors, but after the
> >>root filesystem is mounted, things just stop.
> >>
> >>
> >
> >And  what's  your  console  device?  Are  you  passing  any  console=
> >arguments  on  the  command  line?  Is the corresponding device entry
> >present in the /dev/directory?
> >
> >Best regards,
> >
> >Wolfgang Denk
> >
> >
> >
>
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

Re: help with inittab

[Chris Dumoulin]

The init is from Busybox. Since I'm getting output from my serial port 
during the kernel boot process, I think it's safe to say that my 
/dev/ttyS0 is properly configured. Besides passing the kernel argument 
console=ttyS0,57600, is there anything else I need to do to properly 
configure the console? I've looked through my kernel configuration to 
make sure that any serial device or console related stuff was enabled 
and configured.

I'm feeling pretty stumped.

- Chris

Steve Iribarne (GMail) wrote:

> On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>
>> I've now determined that my kernel seems to stop in the following line
>> of code, in the function init(void * unused), in init/main.c:
>> run_init_process("/sbin/init");
>
>
> Who's init are  you using??
>
> Are you using Busyboxes or sysinit from GNU?
>
>
>> I've determined that it stops at this call by stepping through the code
>> with a BDI2000.
>>
>> My boot arguments are:
>> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>>
>> My current inittab is:
>> ::sysinit:/etc/rc.sh
>> ::ctrlaltdel:/sbin/reboot
>> ::shutdown:/sbin/swapoff -a
>> ::shutdown:/bin/umount -a -r
>> ::restart:/sbin/init
>> ::respawn:/bin/sh
>>
>> I've tried adding an "echo" command to the /etc/rc.sh script that is
>> called, but I don't see any output. I've also trying changing the
>> ::sysinit line in inittab to point to some non-existent script, to see
>> if I'll get some error message, but I still see nothing. Is it possible
>> that /sbin/init is dying before it gets to the point of reading inittab?
>> Any ideas?
>>
>> Regards,
>> Chris Dumoulin
>>
>>
>> Wolfgang Denk wrote:
>>
>> >In message <44888B92.40409@ics-ltd.com> you wrote:
>> >
>> >
>> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
>> >>4.0. Currently, I seem to be able to boot without errors, but after 
>> the
>> >>root filesystem is mounted, things just stop.
>> >>
>> >>
>> >
>> >And  what's  your  console  device?  Are  you  passing  any  console=
>> >arguments  on  the  command  line?  Is the corresponding device entry
>> >present in the /dev/directory?
>> >
>> >Best regards,
>> >
>> >Wolfgang Denk
>> >
>> >
>> >
>>
>> -- 
>> *--Christopher Dumoulin--*
>> Software Team Leader
>>
>> <http://ics-ltd.com/>
>> <http://ics-ltd.com/>
>>
>> Interactive Circuits and Systems Ltd.
>> 5430 Canotek Road
>> Ottawa, ON
>> K1J 9G2
>> (613)749-9241
>> 1-800-267-9794 (USA only)
>>
>> ------------------------------------------------------------------------
>> This e-mail is private and confidential and is for the addressee only.
>> If misdirected, please notify us by telephone and confirm that it has
>> been deleted from your system and any hard copies destroyed. You are
>> strictly prohibited from using, printing, distributing or disseminating
>> it or any information contained in it save to the intended recipient.
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>


-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

Re: help with inittab

[Steve Iribarne (GMail)]

On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> The init is from Busybox. Since I'm getting output from my serial port
> during the kernel boot process, I think it's safe to say that my
> /dev/ttyS0 is properly configured. Besides passing the kernel argument
> console=ttyS0,57600, is there anything else I need to do to properly
> configure the console? I've looked through my kernel configuration to
> make sure that any serial device or console related stuff was enabled
> and configured.
>
> I'm feeling pretty stumped.
>

Ok.. so if you are using the init from Busybox, there should be a
softlink and I can't remember where they put it.  I think it is the
root file system.  I think they call in linuxrc or something like
that.  I'd make sure you have that.

**OR** what I did..

Get sysinit from GNU and tell Busybox not to use the init.  I've had
this exact same problem and it was my init.

-stv
> - Chris
>
> Steve Iribarne (GMail) wrote:
>
> > On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
> >
> >> I've now determined that my kernel seems to stop in the following line
> >> of code, in the function init(void * unused), in init/main.c:
> >> run_init_process("/sbin/init");
> >
> >
> > Who's init are  you using??
> >
> > Are you using Busyboxes or sysinit from GNU?
> >
> >
> >> I've determined that it stops at this call by stepping through the code
> >> with a BDI2000.
> >>
> >> My boot arguments are:
> >> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
> >>
> >> My current inittab is:
> >> ::sysinit:/etc/rc.sh
> >> ::ctrlaltdel:/sbin/reboot
> >> ::shutdown:/sbin/swapoff -a
> >> ::shutdown:/bin/umount -a -r
> >> ::restart:/sbin/init
> >> ::respawn:/bin/sh
> >>
> >> I've tried adding an "echo" command to the /etc/rc.sh script that is
> >> called, but I don't see any output. I've also trying changing the
> >> ::sysinit line in inittab to point to some non-existent script, to see
> >> if I'll get some error message, but I still see nothing. Is it possible
> >> that /sbin/init is dying before it gets to the point of reading inittab?
> >> Any ideas?
> >>
> >> Regards,
> >> Chris Dumoulin
> >>
> >>
> >> Wolfgang Denk wrote:
> >>
> >> >In message <44888B92.40409@ics-ltd.com> you wrote:
> >> >
> >> >
> >> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
> >> >>4.0. Currently, I seem to be able to boot without errors, but after
> >> the
> >> >>root filesystem is mounted, things just stop.
> >> >>
> >> >>
> >> >
> >> >And  what's  your  console  device?  Are  you  passing  any  console=
> >> >arguments  on  the  command  line?  Is the corresponding device entry
> >> >present in the /dev/directory?
> >> >
> >> >Best regards,
> >> >
> >> >Wolfgang Denk
> >> >
> >> >
> >> >
> >>
> >> --
> >> *--Christopher Dumoulin--*
> >> Software Team Leader
> >>
> >> <http://ics-ltd.com/>
> >> <http://ics-ltd.com/>
> >>
> >> Interactive Circuits and Systems Ltd.
> >> 5430 Canotek Road
> >> Ottawa, ON
> >> K1J 9G2
> >> (613)749-9241
> >> 1-800-267-9794 (USA only)
> >>
> >> ------------------------------------------------------------------------
> >> This e-mail is private and confidential and is for the addressee only.
> >> If misdirected, please notify us by telephone and confirm that it has
> >> been deleted from your system and any hard copies destroyed. You are
> >> strictly prohibited from using, printing, distributing or disseminating
> >> it or any information contained in it save to the intended recipient.
> >> _______________________________________________
> >> Linuxppc-embedded mailing list
> >> Linuxppc-embedded@ozlabs.org
> >> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >>
> >
>
>
> --
> *--Christopher Dumoulin--*
> Software Team Leader
>
> <http://ics-ltd.com/>
> <http://ics-ltd.com/>
>
> Interactive Circuits and Systems Ltd.
> 5430 Canotek Road
> Ottawa, ON
> K1J 9G2
> (613)749-9241
> 1-800-267-9794 (USA only)
>
> ------------------------------------------------------------------------
> This e-mail is private and confidential and is for the addressee only.
> If misdirected, please notify us by telephone and confirm that it has
> been deleted from your system and any hard copies destroyed. You are
> strictly prohibited from using, printing, distributing or disseminating
> it or any information contained in it save to the intended recipient.
>