From: Raz Ben Yehuda <rbenyehuda@manz.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] boot error.
Date: Tue, 27 Dec 2011 17:15:14 +0200 [thread overview]
Message-ID: <1324998914.26409.9.camel@raz> (raw)
In-Reply-To: <201112271556.27540.jbe@pengutronix.de>
On Tue, 2011-12-27 at 15:56 +0100, Juergen Beisert wrote:
> Raz Ben Yehuda wrote:
> > Any idea anyone what the bellow messages mean ?
> >
> > getty -L 115200 ttyS0 vt100' (pid 1015) exited. Scheduling for restart.
> > starting pid 1068, tty '/dev/console': '/sbin/getty -L 115200 ttyS0
> > vt100'
> > process '/sbin/getty -L 115200 ttyS0 vt100' (pid 1068) exited.
> > Scheduling for restart.
>
> Device nodes are missing. Your udev seems not to run or is somehow broken.
yes. great thank you.
> jbe
>
> --
> Pengutronix e.K. | Juergen Beisert |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-12-27 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 14:26 Raz Ben Yehuda
2011-12-27 14:56 ` Juergen Beisert
2011-12-27 15:15 ` Raz Ben Yehuda [this message]
2012-01-09 14:11 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1324998914.26409.9.camel@raz \
--to=rbenyehuda@manz.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox