Re: [sysvinit-devel] the sysvinit pause

[niqingliang2003]

On Wednesday, January 16, 2013 09:44:10 AM address@hidden wrote:
> On Tuesday, January 15, 2013 04:56:44 PM Dr. Werner Fink wrote:
> > On Tue, Jan 15, 2013 at 11:11:21PM +0800, Yi Qingliang wrote:
> > > On Tuesday, January 15, 2013 12:16:46 PM Dr. Werner Fink wrote:
> > > > On Tue, Jan 15, 2013 at 06:42:26PM +0000, address@hidden
why the close(fd) freeze for 30seconds?
is it related with serial setting? or serial driver?

> wrote:
> > > > > great thanks for the response.:)
> > > > > the 'print' openned /dev/console.
> > > > > I'm using s3c2442, the argument of kernel is console=ttySAC0,115200.
> > > > > 
> > > >                                                        ^^^^^^^
> > > > 
> > > > Shouldn't that be /dev/ttySA0
> > > 
> > > what you mean? my kernel argument should be ttySA0?
> > 
> > This is what /usr/src/linux/Documentation/devices.txt describes.
> > 
> > > > > and I have another problem, the getty(busybox) only print out the
> > > > > issue,
> > > > > but no login prompt, after disable the issue( add -i got gettty in
> > > > > inittab), it can display the login prompt.
> > > > > 
> > > > > the two problems are both related with the serial console, but I
> > > > > have
> > > > > no
> > > > > idea.
> > > > 
> > > > The serial console of the ARM(?) does not respond ...
> > > 
> > > forgive my poor English, I can't catch you.
> > 
> > The device ttySA0 is found on StrongARM as described in
> > /usr/src/linux/Documentation/devices.txt
> 
> on the s3c2442, the ttySAC is correct, it is define in the samsung uart
> driver. I don't think it is the problem.
> 
> I have checked the getty code, the display issue code section called the
> ioctl to change the serial setting, after that restore serial setting, and
> then no login prompt, If I comment out the two ioctl, the login prompt
> appear, but no help on the sysvinit freeze 30seconds.