Need help for Linux hangs

Need help for Linux hangs

[jimmy liu]

I have U-Boot running on a board similar to
MPC8260ADS.
bootargs=root=/dev/ram rw console=ttyS0,115200
When I run command: bootm ff060000 ff260000, the
prompt shows message:
## Booting image at ff060000 ...
   Image Name:   Linux-2.4.25
   Image Type:   PowerPC Linux Kernel Image (gzip
compressed)
   Data Size:    621131 Bytes = 606.6 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at ff260000 ...
   Image Name:   Simple Embedded Linux Framework
   Image Type:   PowerPC Linux RAMDisk Image (gzip
compressed)
   Data Size:    1591658 Bytes = 1.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 00e07000, end 00f8b96a ... OK

The system hangs here. I have checked in the FAQs
provided in the Denx's site, could not find the
similar case.

I would appreciate any help.

Thanks & Regards,

Jimmy


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Need help for Linux hangs

[Vitaly Bordug]

jimmy liu wrote:
> I have U-Boot running on a board similar to
> MPC8260ADS.
> bootargs=root=/dev/ram rw console=ttyS0,115200
try to set console=ttyCPM0,115200 in the bootargs.
> When I run command: bootm ff060000 ff260000, the
> prompt shows message:
> ## Booting image at ff060000 ...
>    Image Name:   Linux-2.4.25
>    Image Type:   PowerPC Linux Kernel Image (gzip
> compressed)
>    Data Size:    621131 Bytes = 606.6 kB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> ## Loading RAMDisk Image at ff260000 ...
>    Image Name:   Simple Embedded Linux Framework
>    Image Type:   PowerPC Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    1591658 Bytes = 1.5 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Loading Ramdisk to 00e07000, end 00f8b96a ... OK
> 
> The system hangs here. I have checked in the FAQs
> provided in the Denx's site, could not find the
> similar case.
> 
> I would appreciate any help.
> 
> Thanks & Regards,
> 
> Jimmy
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 


-- 
Sincerely, 
Vitaly

Re: Need help for Linux hangs

[Wolfgang Denk]

In message <20051208151926.74524.qmail@web53105.mail.yahoo.com> you wrote:
>
...
>    Loading Ramdisk to 00e07000, end 00f8b96a ... OK
> 
> The system hangs here. I have checked in the FAQs
> provided in the Denx's site, could not find the
> similar case.

Come on. "Linux hangs after uncompressing the kernel"
(http://www.denx.de/wiki/view/DULG/LinuxHangsAfterUncompressingKernel)
is not a "similar case"? To me it is.


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
Is the glass half empty, half full, or twice as large as it needs to

Re: Need help for Linux hangs

[Wolfgang Denk]

Dear Vitaly,

in message <439859BA.6060600@ru.mvista.com> you wrote:
> jimmy liu wrote:
> > I have U-Boot running on a board similar to
> > MPC8260ADS.
> > bootargs=root=/dev/ram rw console=ttyS0,115200
> try to set console=ttyCPM0,115200 in the bootargs.
                     ^^^^^^^
> > When I run command: bootm ff060000 ff260000, the
> > prompt shows message:
> > ## Booting image at ff060000 ...
> >    Image Name:   Linux-2.4.25
                           ^^^^^^

That's bad advice.

The 2.4.25 kernel will definitely NOT work with console=ttyCPM0

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
Immortality consists largely of boredom.
	-- Zefrem Cochrane, "Metamorphosis", stardate 3219.8

Problems starting /init

[David H. Lynch Jr.]

 I have  a kernel for a new board (Linux 2.6.14.5, Pico E12/Xilinx V4
PPC405) booting to the point of starting /init.

/init appears to be getting loaded correctly - the execve call seems
happy. But I get no output on the console.

I have tried:

	executing
		sys_write(1,"Test",4);

		inside init/main.c immediately before starting /init - works fine.
	starting a "hello World" application written in PPC asm as /init -
works fine. The kernel panics on exit but that is normal, /init is not
supposed to exit.

	starting a c "Hello World" application that uses glibc, fputs, printf,
fwrite, to display a string - again works fine.

	But I can not get busybox to output a thing either run as /init or run
as /bin/sh.

	I have aslo tried /bin/sash - no output.
	I have even cross compiled sash - with all kinds of "I am here"
debugging scattered through main(), If I runn it on a powerbook, I get
what I expect. If I run it as /bin/sh on the e12 I get no output.


	Does anyone even have any ideas what I can look at ?
	

Problems starting /init

[David H. Lynch Jr.]

 I have  a kernel for a new board (Linux 2.6.14.5, Pico E12/Xilinx V4
PPC405) booting to the point of starting /init.

/init appears to be getting loaded correctly - the execve call seems
happy. But I get no output on the console.

I have tried:

	executing
		sys_write(1,"Test",4);

		inside init/main.c immediately before starting /init - works fine.
	starting a "hello World" application written in PPC asm as /init -
works fine. The kernel panics on exit but that is normal, /init is not
supposed to exit.

	starting a c "Hello World" application that uses glibc, fputs, printf,
fwrite, to display a string - again works fine.

	But I can not get busybox to output a thing either run as /init or run
as /bin/sh.

	I have aslo tried /bin/sash - no output.
	I have even cross compiled sash - with all kinds of "I am here"
debugging scattered through main(), If I runn it on a powerbook, I get
what I expect. If I run it as /bin/sh on the e12 I get no output.


	Does anyone even have any ideas what I can look at ?
	

RESEND:Problems starting /init

[David H. Lynch Jr.]

 I have  a kernel for a new board (Linux 2.6.14.5, Pico E12/Xilinx V4
PPC405) booting to the point of starting /init.

/init appears to be getting loaded correctly - the execve call seems
happy. But I get no output on the console.

I have tried:

	executing
		sys_write(1,"Test",4);

		inside init/main.c immediately before starting /init - works fine.
	starting a "hello World" application written in PPC asm as /init -
works fine. The kernel panics on exit but that is normal, /init is not
supposed to exit.

	starting a c "Hello World" application that uses glibc, fputs, printf,
fwrite, to display a string - again works fine.

	But I can not get busybox to output a thing either run as /init or run
as /bin/sh.

	I have aslo tried /bin/sash - no output.
	I have even cross compiled sash - with all kinds of "I am here"
debugging scattered through main(), If I runn it on a powerbook, I get
what I expect. If I run it as /bin/sh on the e12 I get no output.


	Does anyone even have any ideas what I can look at ?
	

Re: Problems starting /init

[Geoff Thorpe]

On January 4, 2006 06:03 pm, David H. Lynch Jr. wrote:
[snip]
> 	starting a c "Hello World" application that uses glibc, fputs,
> printf, fwrite, to display a string - again works fine.
>
> 	But I can not get busybox to output a thing either run as /init or
> run as /bin/sh.

busybox tries to open the console device and does fairly extensive 
surgery with the stdio descriptors. So your apps that assume fds 
0,1,2 to be stdin/stdout/stderr are functioning fine, but busybox is 
probably choking because it's opening/configuring the console 
devices. I've worked through this with someone before when we wanted 
busybox to just run with the existing fds - we eventually beat it 
into submission but then ended up changing/replacing the console 
driver instead and going back to vanilla busybox. If you take a look 
through the busybox source, you should find the various 
fork/dup/ctrl/exit gymnastics and with a little patience, you might 
be able to hack around it. But it might be easier in the long run to 
figure out where the opening/manipulation of /dev/console (or 
whatever it's opening) is going wrong.

Sorry I can't help you further. Good luck.

Cheers,
Geoff

-- 
Geoff Thorpe
Freescale Semiconductor

Re: RESEND:Problems starting /init

[Shawn Jin]

>         But I can not get busybox to output a thing either run as /init o=
r run
> as /bin/sh.
>
>         I have aslo tried /bin/sash - no output.
>         I have even cross compiled sash - with all kinds of "I am here"
> debugging scattered through main(), If I runn it on a powerbook, I get
> what I expect. If I run it as /bin/sh on the e12 I get no output.
>
>
>         Does anyone even have any ideas what I can look at ?

Another thing you may try is to make sure the UART works correctly
with interrupt mode. So set some breakpoints in UART's IRS to see what
happens.

Regards,
-Shawn.

Re: Problems starting /sbin/init

[David H. Lynch Jr.]

srideep.devireddy@wipro.com wrote:
> Hello David ,
> 
>   I am bringing up  Montavista Linux on mpc8272 custom board .But as we completed almost all the configurations and linux is booting well till the NFS or Ramdisk file system is mounted . then it hangs  .. when i tried to debug i saw the /sbin/init in the init/main.c is not getting executed . i had printk and checked all the printks are executed but not the /sbin/init and the printks after the init is also executed .so this /sbin/init is not getting excecuting and i am not getting any messages .
> 
> Thanks & Regards
> Srideep Reddy D
> Wipro Technologies
> 
> 
Srideep;

	I was eventually able to resolve my problem. My serial console driver
was inadvertently using the physical address of the uart and not the
virtual address. When the TLB entry created in head_4xx.S for that
physical address eventually got overwritten - which coincidentally
occured after loading /init (or /bin/sh or ....) but prior to their
outputting anything.

	It is possible but unlikely you are having a similar problem.

	Regardless, you can isolate your problem further. You can sprinkle
prink's inside init/main.c to figure out exactly how far you are getting.
	If you are actually getting to attempting to start /init, you can
change main.c to start the program of your choice instead of init.
I started with "Hello World" in ppc assmebler with no library dependencies.
	You can enable SHOW_SYSCALLS and find out what system calls are
occuring immeditely prior to your system running off the rails.

	And I am sure others may have even more and better ideas.


Dave