linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: diekema@bucks.si.com (diekema_jon)
To: linuxppc-embedded@lists.linuxppc.org
Cc: all@cideas.com
Subject: init is running (didn't trigger the wait queue panic)
Date: Tue, 13 Jun 2000 09:14:38 -0400 (EDT)	[thread overview]
Message-ID: <m131qWd-001SyaC@bucks> (raw)


	* To: linuxppc-embedded@lists.linuxppc.org

	I tried running init again with Linux 2.4.0-test1-ac10
	(through changeset 1.247.1.6 00/06/12 18:04:09-04:00
	dmalek@geefour.netx4.com), and I was surprised to find that it
	worked.  Previously, init was triggering a wait queue panic in the
	scheduler.

	With init active, inetd is running and it is possible to use
	telnet to establish a connection.  cool very cool :)

	Target: EST SBC8260 with MPC8260 Rev A.1 at CPU/CPM/BUS 200/167/66

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-06-13 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-13 13:14 diekema_jon [this message]
2000-06-14  3:33 ` init is running (didn't trigger the wait queue panic) Dan Malek

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=m131qWd-001SyaC@bucks \
    --to=diekema@bucks.si.com \
    --cc=all@cideas.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).