[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: macppc snapshot blows up on g4 pbook 400mhz



Jared Yanovich wrote:
> 
> The latest snapshot cd35.iso produces the following:
> 
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>         The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2004 OpenBSD. All rights reserved.  http://www.OpenBSD.org
> 
> panic: uvm_km_init: could not reserve space for kernel
> Stopped at      0x23db00:       lwz r0,20(r1)
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> ddb>
> 
> I am unable to type at the keyboard, else I would have attached some trace
> output.  

Hrmph.  Well, I guess we gotta tollerate that, then. 8)

> The 3.4 cd34.iso works fine.  The machine is a PowerBook G4 400MHz,
> the revision A model.  Any suggestions?


Can you boot a 3.5 bsd.rd and see if you get the same result?
  install 3.4 or whatever, boot it, download a new bsd.rd to /, then
get to openfirmware (command-option-o-f), then enter:
   0> boot hd:,ofwboot /bsd.rd 

If the same thing happens, we got a problem.
If this works, sounds like bad cdrom, bad file burned to a good cdrom,
etc (i.e., you have a problem 8).

While this sounds far fetched, I recently lost a bit more hair when a
new install on my iMac crashed VERY early in the boot process.  System
wouldn't boot either bsd or bsd.rd.  (this has an awful lot to do with
why I remember those Openfirmware commands. 8)

Turned out to be that my favorite ftp mirror had a corrupted copy of
BOTH bsd and bsd.rd on it.  Pulled from a different mirror, cmp'd
them, and found a problem in both files.  Go figure.  (yes, FTP
operator was contacted and problem fixed).  In that case, it turned
out cd35.iso was fine (that's how I booted), it was the files that it
installed that were dammaged.

Nick.
-- 
http://www.holland-consulting.net