linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "RMD" <rmd@altec.com.ar>
To: linux-c-programming@vger.kernel.org
Subject: boot freezes
Date: Thu, 27 Jun 2002 14:47:50 -0300	[thread overview]
Message-ID: <002901c21e02$c1bca9d0$580a020a@rmdlaptop> (raw)

Hi all.
I have an odd behaviour on a linux system to be used in an embedded system
(no vga, 4 serials)
The problem is:
booting on a standard pc, using syslinux as the loader, with syslinux.cfg as
follows:

    serial 0 38400
    default linux
    prompt 0
    label linux
        kernel=vmlinuz
        append console=ttyS0,38400n8 console=tty0 root=/dev/hdc2 rw

it starts ok, I can read all kernel messages on the attached terminal,
ending with:

    Freeing unused kernel memory: 176k freed
    serial console detected.  Disabling virtual terminals

and then runs Busybox v0.6.2 as init.
the rcS file in /etc/init.d initializes an LCD display, and /etc/inittab
runs an application that writes on that display.
the inittab file is as this:

    ::sysinit:/etc/init.d/rcS
    ::once:myapplication

All works fine on a PC
But when I try this disk (it´s really a flashcard) on a SBC (x86 too) system
(no vga), and attaching a terminal to ttyS0, I can see it loads the kernel,
with all of it´s hardware and initializing messages, and the last message
is:

    Freeing unused kernel memory: 176k freed

and the system freezes forever and ever...
What else can I do to solve this issue? I´m using a 2.4.2 kernel, compiled
with support for serial consoles, (it works ok on a pc...)
May be something related to /dev/console??

Thanx very much






Ricardo Derbes
Altec SE
Albarracín 157 - San Carlos de Bariloche
+54-2944-426892
rmd@altec.com.ar

Ricardo Derbes
Altec SE
Albarracín 157 - San Carlos de Bariloche
+54-2944-426892
rmd@altec.com.ar

-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2002-06-27 17:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='002901c21e02$c1bca9d0$580a020a@rmdlaptop' \
    --to=rmd@altec.com.ar \
    --cc=linux-c-programming@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).