ml300 system init very slow

ml300 system init very slow

[Lou Rickard]

Thanks to people on the list, I finally got the ml300
booting on it's own filesystem.  Thank you.

And of course, another question.  After kernel boot is
done, the system begins intialization, but it goes
REALLY slow.

It gets to the:
"Freeing unused kernel memory: 64k init"
line just fine, but from that point, it takes about
five minutes to finish coming up and  providing a
login prompt.

>From the following lines:
"INIT: version 2.78 booting
INIT: Entering runlevel: 3
Entering non-interactive startup"
and on it's just super slow.

At a certain point it starts inetd and telnet
services, so I can acually telnet into the box and
everything in that session seems nice an perky, just
like normal, but everything over the serial line is
slower than molasses.  This is both over the NFS mount
and using the flash file system.

Any ideas?

Thanks,

~lr


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ml300 system init very slow

[Lou Rickard]

Well, I think I may have a solution to my problem,
though I don't understand it, and am hoping that maybe
someone here can explain it too me.

I was trying to work on some driver modules, but was
having a hard time with it, I'd turned module support
off in the kernel.  So I turned module support back
on, and that kernel seems to boot up just fine.

I'm guessing it was failing to load some module, but I
don't know what really is going on there.  I'm going
to keep looking, but if anyone has advice, please
shoot it at me.

~lr


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: ml300 system init very slow

[VanBaren, Gerald (AGRE)]

Just in case nobody answered yet (I didn't see an answer), the problem 99.9999% certainty is that your serial interrupts are not interrupting so the kernel is polling for serial I/O.  This is a fallback operation with REALLY LONG timeouts.  The symptoms are REALLY SLOW console interaction == your symptoms.  Your follow-up message indicates the problem is in your serial driver module.

gvb


> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Lou
> Rickard
> Sent: Monday, March 01, 2004 7:08 PM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: ml300 system init very slow
>
>
>
> Thanks to people on the list, I finally got the ml300
> booting on it's own filesystem.  Thank you.
>
> And of course, another question.  After kernel boot is
> done, the system begins intialization, but it goes
> REALLY slow.
>
> It gets to the:
> "Freeing unused kernel memory: 64k init"
> line just fine, but from that point, it takes about
> five minutes to finish coming up and  providing a
> login prompt.
>
> From the following lines:
> "INIT: version 2.78 booting
> INIT: Entering runlevel: 3
> Entering non-interactive startup"
> and on it's just super slow.
>
> At a certain point it starts inetd and telnet
> services, so I can acually telnet into the box and
> everything in that session seems nice an perky, just
> like normal, but everything over the serial line is
> slower than molasses.  This is both over the NFS mount
> and using the flash file system.
>
> Any ideas?
>
> Thanks,
>
> ~lr
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: ml300 system init very slow

[Lou Rickard]

And as the kernel boots, it loads an improved serial
module stored on the root filesystem, which works
fine?  Would that explain why it works fine with
module support turned on, but doesn't work well with
module support turned off (and hence stuck using the
serial module that is built into the kernel)?

~lr

--- "VanBaren, Gerald (AGRE)"
<Gerald.VanBaren@smiths-aerospace.com> wrote:
>
> Just in case nobody answered yet (I didn't see an
> answer), the problem 99.9999% certainty is that your
> serial interrupts are not interrupting so the kernel
> is polling for serial I/O.  This is a fallback
> operation with REALLY LONG timeouts.  The symptoms
> are REALLY SLOW console interaction == your
> symptoms.  Your follow-up message indicates the
> problem is in your serial driver module.
>
> gvb


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: ml300 system init very slow

[Peter Ryser]

Lou,

make sure you don't have a mismatch between
arch/ppc/platforms/xilinx_ocp/xparameters_ml300.h and your system.mhs
especially when looking at the interrupt signals and defines. If you
made changes to xparameters_ml300.h you might want to rebuild the kernel
completely:
$ make clean dep bzImage modules.

Besides that I assume that you use a recent kernel (eg. the one in
MVL3.1) and EDK (vs. V2PDK) as a development tool kit.

- Peter


Lou Rickard wrote:

>And as the kernel boots, it loads an improved serial
>module stored on the root filesystem, which works
>fine?  Would that explain why it works fine with
>module support turned on, but doesn't work well with
>module support turned off (and hence stuck using the
>serial module that is built into the kernel)?
>
>~lr
>
>--- "VanBaren, Gerald (AGRE)"
><Gerald.VanBaren@smiths-aerospace.com> wrote:
>
>
>>Just in case nobody answered yet (I didn't see an
>>answer), the problem 99.9999% certainty is that your
>>serial interrupts are not interrupting so the kernel
>>is polling for serial I/O.  This is a fallback
>>operation with REALLY LONG timeouts.  The symptoms
>>are REALLY SLOW console interaction == your
>>symptoms.  Your follow-up message indicates the
>>problem is in your serial driver module.
>>
>>gvb
>>
>>
>
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/