From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] missing space in 2.11_rp_unknown
Date: Mon, 25 Feb 2002 09:16:31 -0800 (PST) [thread overview]
Message-ID: <200202251716.g1PHGVT16246@moe.2bsd.com> (raw)
Hi -
> > I see Greg mentioned running fsck. That sounds like an excellent
> > suggestion.
>
> Yes, but it didn't help :-(
> What can this be?
It might be necessary to use the '-s' option . "fsck -s" will
unconditionally rebuild the freelist.
> I tried something else, I copied the contents of the root fs
> elsewhere, newfs'd the root partition and copied the contents back.
Did you use dump+restor?
> But now booting stops when it normally starts init,
>
Oh no!
> -------------
> : unix
> Boot: bootdev=05010 bootcsr=0176700
>
> 2.11 BSD UNIX #1: Fri Feb 15 18:47:18 PST 2002
> chris at pdp11:/usr/src/sys/PDP11CPG
>
> attaching qe0 csr 174440
> qe0: DEC DEQNA addr 08:00:2b:07:82:6c
> attaching lo0
>
> phys mem = 2097152
> avail mem = 1647872
> user mem = 307200
>
> -------------
>
> ... and here it hangs. Do I have to consider something else when I
> newfs the root partition?
The boot block, /boot, /unix, /netnix and /etc/init, /bin/sh are
intact since the system got as far as printing the memory numbers.
After the memory stats the '/etc/autoconfig' process should be
run ('init' runs it) and the device probes should take place.
The only thing I can think of (and it's a wild guess) is that the
"clock" isn't running - thru the boot process clock interrupts
aren't used but when 'init' goes to run 'autoconfig' the system nees
clock interrupts in order to drive the context switching. Either
the clock isn't running or /etc/autoconfig got corrupted somehow
in the copying.
Steven Schultz
sms at 2bsd.com
next reply other threads:[~2002-02-25 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 17:16 Steven M. Schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 16:38 Christian Groessler
2002-03-03 9:47 Steven M. Schultz
2002-03-01 22:28 Christian Groessler
2002-02-28 16:53 Steven M. Schultz
2002-02-28 16:32 Christian Groessler
2002-02-27 23:25 Steven M. Schultz
2002-02-28 2:24 ` Frank Wortner
2002-02-27 21:35 Christian Groessler
2002-02-26 23:29 Steven M. Schultz
2002-02-26 11:56 Christian Groessler
2002-02-25 11:57 Christian Groessler
2002-02-23 3:31 Steven M. Schultz
2002-02-22 14:52 Christian Groessler
2002-02-23 1:29 ` Greg Lehey
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=200202251716.g1PHGVT16246@moe.2bsd.com \
--to=sms@2bsd.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;
as well as URLs for NNTP newsgroup(s).