Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@dot.at>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Christoph Plattner <christoph.plattner@alcatel.at>,
	Richard Hirst <rhirst@linuxcare.com>,
	parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Many experience done on 720, but `init' fails !!
Date: Sun, 08 Apr 2001 19:08:11 +0200	[thread overview]
Message-ID: <3AD09AFB.EBDFF975@dot.at> (raw)
In-Reply-To: 20010404180518.C11435@parcelfarce.linux.theplanet.co.uk

A week ago, I reported the problem booting PA-Linux 0.5 with the new
kernel and new selfmade cross tool chain.

The last week I used to experience with cross toolchain setup.
The aim was to find away having "one" glibc-2 for cross development
and for the target (to mount, NFS-ROOT). I also used tricks like
	--prefix=/usr and
	make install install_root=/usr/parisc/target....
but the result and discussion with other showed following:

	There must be TWO glibc trees, one for the cross toolchain,
	the other for the target. The second one is built with the 
	method defining prefix to /usr and install it in a target tree.

SO I build sash, a also build a bash (shared and static !), I build
fileutils, text-utils, shell-utils, etc, etc.....
The system boots with bash and I can mount, run programs, etc....

The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx
and so on. I also build a sysvinit-2.78 (and 2.77 before), but the
`init'
has it's problems. The error message is:

VFS: Mounted root (nfs filesystem) readonly.
break 0,0: pid=9 command='init'
init[9]: Breakpoint 0

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111
r0-3     00000000 102de010 00000000 00000000
r4-7     00000000 00000000 00000000 00000000
r8-11    00000000 00000000 00000000 00000000
r12-15   00000000 00000000 00000040 1012544c
r16-19   13f085c0 13f08000 c804c804 00000001
r20-23   102efcc0 102efcc0 10022800 102efcc0
r24-27   0000002e 00001000 00000000 1024c010
r28-31   00000000 00000000 13f089c0 101312a0
sr0-3    00000000 00000000 00000000 00000001
sr4-7    00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 00000000 00000004
 IIR: 00000000    ISR: 00000000  IOR: 00000000
ORIG_R28: 00000000

How can I follow up the thing ?
Is the GDB of the CVS usable  (for example starting gdbserver init 
instead of init and `target remote' via the second serial interface ?)

By the way: I did a "super hack" in the kernel. In the serial interrupt 
routine, I catch the charcater `^\', filter it for `/dev/ttyS0' and 
do a machine_restart(). This is perfect for development !!

With friendly regards
	Christoph P.






-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at

  parent reply	other threads:[~2001-04-08 17:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 22:51 [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ? Christoph Plattner
2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27   ` Matthew Wilcox
2001-04-02 23:41     ` Richard Hirst
2001-04-03  6:55   ` Christoph Plattner
2001-04-03  9:12     ` Richard Hirst
2001-04-03  9:23       ` Christoph Plattner
2001-04-03 13:16         ` Richard Hirst
2001-04-03 21:34     ` Matthew Wilcox
2001-04-04  7:08       ` Christoph Plattner
2001-04-04 17:05         ` Matthew Wilcox
2001-04-04 20:31           ` Christoph Plattner
2001-04-08 17:08           ` Christoph Plattner [this message]
2001-04-08 17:32             ` [parisc-linux] C180 Progress Marc Eisenbarth
2001-04-09 13:36               ` Matt Taggart
2001-04-09 17:05                 ` Marc Eisenbarth
2001-04-08 21:02             ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
2001-04-09 20:52             ` [parisc-linux] Many experience done " Matt Taggart
2001-04-09 21:12               ` Christoph Plattner
2001-04-10  8:46                 ` Richard Hirst

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=3AD09AFB.EBDFF975@dot.at \
    --to=christoph.plattner@dot.at \
    --cc=christoph.plattner@alcatel.at \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rhirst@linuxcare.com \
    /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