Yeah... sorry you are also having the problem.. if you have an evening to start from scratch... I think you could fix it though.

I am not sure about this moving back from current to stable. This is what I did (and it could have been more efficient)

1) Downloaded the source trees (src.tar.gz sys.tar.gz)
2) Updated to -stable from CVS
3) Changed the offending code
   FROM:
    #define VM_PHYSSEG_MAX        5
   TO:
   #define VM_PHYSSEG_MAX        16
   IN:
   /usr/src/sys/arch/i386/include/vmparam.h
3) Built a release (this requires that you build the kernel, the userland and then do the actual release) 4) I took the cd41.iso and burnt it to disk. I then burned the other release files to a second disk. 5) I started my install from the cd41.iso cd and it was fine. When it asked for my files... I went ahead and used the ftp for all but the kernel. I then used my cd to install the kernel (bsd)
6) Everything has been working fine

I don't see why you wouldnt be able to go from current back to stable. Couldn't you delete your whole source tree... follow steps 1 and 2 above... then make a new release and reinstall. It sounds like you would want to do that because you wouldnt feel very certain of your production server in the state it is in now (at least it sounded that way)

To do the build... please read:
http://www.openbsd.org/faq/faq5.html#Bld
From 5.3 through 5.4. I had never done it before and I stupidly skimmed the
reading and it didn't work. So don't take shortcuts and read it unless you have done it before. If you run into problems read:
http://www.openbsd.org/cgi-bin/man.cgi?query=release&sektion=8
It is the authoritative set of instructions for this.

There is a chance that you don't have to change the code... but when I did this... the change was not applied to -stable

For a history of this change see:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/include/vmparam.h
It is revision 1.37 and if you click the link that says "colored" you can see a nice pretty diff of the change.

Well.. I hope this was of help.. if you are having trouble with making the release.. feel free to email me directly about this.

[EMAIL PROTECTED]

Good luck



----- Original Message ----- From: "Marcos Laufer" <[EMAIL PROTECTED]>
To: "Ben Calvert" <[EMAIL PROTECTED]>; <misc@openbsd.org>
Sent: Friday, May 11, 2007 8:27 AM
Subject: Re: OpenBSD 4.1 install issue??


Looks like i'm miximng kernel and userspace versions because
i did get the -release cd and installed it, but it didn' recognize my
hardware , it wouldn't boot:
http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg

http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg

So i found this thread wich says i should install the latest snapshot .
What i didn't consider is that it was not possible to move to -stable
from -current. I did tried to move to -stable (compiled kernel and booted)
and it crashed like in those images up there, the same does when
booting with -release cd , so i had to keep with -current
kernel (and -current userland of course)

I just wish OpenBSD 4.1 -release (too late for -release) or -stable could
boot on my hardware, i can't fix that myself , i don't know how to backport
the changes i need


----- Original Message ----- From: "Ben Calvert" <[EMAIL PROTECTED]>
To: "Marcos Laufer" <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2007 12:33 AM
Subject: Re: OpenBSD 4.1 install issue??



On May 10, 2007, at 7:25 PM, Marcos Laufer wrote:

I upgraded to stable , rebooted with the new kernel, and i
was stuck with this uvm_page_physload  problem again.
It looks like moving to stable from this snapshot is not possible .
I had to go back to the snapshot kernel .

1. you can't upgrade down ( current > stable )
2. ths is not linux - from the above it sounds like you were mixing
different kernel and userspace versions..  you can't do that either
( as you seem to have found out )


Will it be possible to move to stable from this point?

possible? maybe. supported?  no.

I really
wouldn't like to have a production server running -current

so then you need to get the -release cd, and upgrade to -stable from
there.


Has anyone sorted this out?

Marcos

Reply via email to