Chris,
Does your serial output stop after "Freeing unused kernel memory..."
If it does, you may have an interrupt problem with the UART. I had to
track down that very problem the other day. As a test, even if my UART
interrupt was purposely misconfigured, I still saw all of the output up
to and including "Freeing unused kernel memory..."
Scott
___________________________________________________________________
Scott N. Coulter
Senior Software Engineer
=20
Cyclone Microsystems =20
370 James Street Phone: 203.786.5536 ext. 118
New Haven, CT 06513-3051 Email: scott.coulter@cyclone.com
U.S.A. Web: http://www.cyclone.com
___________________________________________________________________
-----Original Message-----
From: linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+scott.coulter=3Dcyclone.com@ozlabs.org]=
On Behalf Of Chris Dumoulin
Sent: Friday, June 09, 2006 3:15 PM
To: Steve Iribarne (GMail)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: help with inittab
The init is from Busybox. Since I'm getting output from my serial port=20
during the kernel boot process, I think it's safe to say that my=20
/dev/ttyS0 is properly configured. Besides passing the kernel argument=20
console=3DttyS0,57600, is there anything else I need to do to properly=20
configure the console? I've looked through my kernel configuration to=20
make sure that any serial device or console related stuff was enabled=20
and configured.
I'm feeling pretty stumped.
- Chris
Steve Iribarne (GMail) wrote:
On 6/9/06, Chris Dumoulin [off-list ref] wrote:
quoted
I've now determined that my kernel seems to stop in the following
line
quoted
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?
quoted
I've determined that it stops at this call by stepping through the
code
quoted
with a BDI2000.
My boot arguments are:
console=3DttyS0,57600n8 ip=3Doff root=3D/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
quoted
if I'll get some error message, but I still see nothing. Is it
possible
quoted
that /sbin/init is dying before it gets to the point of reading
inittab?
quoted
Any ideas?
Regards,
Chris Dumoulin
Wolfgang Denk wrote:
quoted
In message [off-list ref] you wrote:
quoted
I am using the linux kernel 2.6.15 and initrd ramdisk image from
ELDK
quoted
quoted
quoted
4.0. Currently, I seem to be able to boot without errors, but after
quoted
the
quoted
quoted
root filesystem is mounted, things just stop.
And what's your console device? Are you passing any
console=3D
quoted
quoted
arguments on the command line? Is the corresponding device
entry
quoted
quoted
present in the /dev/directory?
Best regards,
Wolfgang Denk
--=20
*--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)
------------------------------------------------------------------------
quoted
This e-mail is private and confidential and is for the addressee
only.
quoted
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
quoted
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
--=20
*--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.=20
If misdirected, please notify us by telephone and confirm that it has=20
been deleted from your system and any hard copies destroyed. You are=20
strictly prohibited from using, printing, distributing or disseminating=20
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
Hi Scott,
That is where my output stops. What was the cause of your interrupt
problem? Were you able to fix it?
- Chris
Scott Coulter wrote:
Chris,
Does your serial output stop after "Freeing unused kernel memory..."
If it does, you may have an interrupt problem with the UART. I had to
track down that very problem the other day. As a test, even if my UART
interrupt was purposely misconfigured, I still saw all of the output up
to and including "Freeing unused kernel memory..."
Scott
___________________________________________________________________
Scott N. Coulter
Senior Software Engineer
Cyclone Microsystems
370 James Street Phone: 203.786.5536 ext. 118
New Haven, CT 06513-3051 Email: scott.coulter@cyclone.com
U.S.A. Web: http://www.cyclone.com
___________________________________________________________________
-----Original Message-----
From: linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+scott.coulter=cyclone.com@ozlabs.org]
On Behalf Of Chris Dumoulin
Sent: Friday, June 09, 2006 3:15 PM
To: Steve Iribarne (GMail)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: help with inittab
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:
quoted
On 6/9/06, Chris Dumoulin [off-list ref] wrote:
quoted
I've now determined that my kernel seems to stop in the following
line
quoted
quoted
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?
quoted
I've determined that it stops at this call by stepping through the
code
quoted
quoted
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
quoted
quoted
if I'll get some error message, but I still see nothing. Is it
possible
quoted
quoted
that /sbin/init is dying before it gets to the point of reading
inittab?
quoted
quoted
Any ideas?
Regards,
Chris Dumoulin
Wolfgang Denk wrote:
quoted
In message [off-list ref] you wrote:
quoted
I am using the linux kernel 2.6.15 and initrd ramdisk image from
ELDK
quoted
quoted
quoted
quoted
4.0. Currently, I seem to be able to boot without errors, but after
quoted
quoted
the
quoted
quoted
root filesystem is mounted, things just stop.
And what's your console device? Are you passing any
console=
quoted
quoted
quoted
arguments on the command line? Is the corresponding device
entry
quoted
quoted
quoted
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)
------------------------------------------------------------------------
quoted
quoted
This e-mail is private and confidential and is for the addressee
only.
quoted
quoted
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
quoted
quoted
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.
For debugging or single user purposes you do not need to run init or
have an inittab.
There have been several sugestions that there may be a hardware
problem - there are a number that are possible.
I was stalled here for some time because my UartDriver was
accidentally using the physical IO address instead of the virtual one
and I had created a temporary phys=virtual entry in the tbl that was
conveniently getting blow away just here.
You can try to isolate your problem by changing your boot ramdisk
(inramfs or initrd)
Eliminate or rename /init /sbin/init /linuxrc and any of the other
permutations that linux tries to execute in init/main.c they are all
listed very near where you stopped.
make sure you have /bin/sh
reboot on that ramdisk if you have an "init" related problem then
you should get a standalone shell.
If you have a hardware problem you will likely still stop at the
same place.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein