From: "Jeremy Rosen" <Rosen.Jeremy@tms-pty.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: problem in kernel with Stty initialisation
Date: Thu, 18 Oct 2001 17:49:58 +1100 [thread overview]
Message-ID: <sbcf165e.034@tms-pty.com> (raw)
Hello everybody
I am slowly going further with my FADS860T board, and now I have a
ppcboot up and running.
I am feeding it with the kernel from denx (2.4.4 07 23 ) and it boots
properly until ttyS initialisation where it tryes to access forbidden
memory.
I have modified the source to skip that initialisation, and except
that, the kerrnel is booting OK.
The problem is that I need the ttyS for my console :-)
the exact output is Oops kernel access of bad area, sig 11
generated by line 417 : return inb(info->port + offset);
called by line 3635 : scratch = serial_inp(info, UART_IER);
the Oops is here with the three ttyS.
Is this a known bug ?
did I do something wrong in the config ???
the serial port works well under ppc boot, I use a baud rate of 115200,
and the printk messages are output correctly on ttyS1.
thx
Jeremy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-10-18 6:49 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=sbcf165e.034@tms-pty.com \
--to=rosen.jeremy@tms-pty.com \
--cc=linuxppc-embedded@lists.linuxppc.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).