Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-26 Thread Clint Olsen
On Nov 11, Chris H. wrote:
 It's as simple as making your swap slice available for dumping, and
 adding a line in your rc.conf file. Of course you'll need to lift the
 information of interest from the vmcore, for the dump to be of any value.
 :)
 
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
 
 It's really a simple process.

Heh, simple is relative :)  But it doesn't look that bad -- thanks for the
information.  I'll likely need this at some point.

Unfortunately I did not have the luxury to embroil myself in debug hell
with this problem since this is my mail/web machine and others depend on
it.  I can tolerate some downtime, but this was just getting to be too
much.  I just backed up the system, and installled FreeBSD 6.2-RELEASE from
scratch and most things are back up and running after a night until 3am.
Yuck, I don't ever want to have to deal with something like this again.

Hopefully after I get brave enough I /might/ entertain jumping onto a
STABLE branch again...

Thanks,

-Clint
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-11 Thread [LoN]Kamikaze
Clint Olsen wrote:
 On Nov 02, [LoN]Kamikaze wrote:
 I think you might have no choice but to omit the reboots, because the
 world contains lots of stuff that has to do with the kernel (like
 mounting).

 So just go into single user mode and do the usual stuff:
 # make installkernel
 # mergemaster -p
 # make installworld
 # mergemaster
 # shutdown -r now

 and pray to your deity of choice.

 If the reason for your problem is something else however you're stuck
 with a system that can not run with your old kernel. So better backup
 before you try.
 
 I attempted to just do a binary upgrade, assuming that I botched the source
 upgrade somehow.  After installing FreeBSD 6.2-RELEASE, I was left with a
 system that would not boot (similar errors on boot as before).  Reverting
 the kernel of course was of limited help because userland was all expecting
 6.2.  So, I had a couple of tarballs from my last backup and I attempted to
 bandage up / and /usr and was able to resurrect my 5.5-STABLE image.
 
 This is f'n scary.  I've never had this much trouble upgrading a system
 before.  Does anyone have any idea what remnant could be remaining after a
 binary upgrade that would keep it from booting yet I can boot from the
 6.2-RELEASE iso's just fine?  I am very apprehensive to do a newfs and wipe
 the drives now that I've failed both source and binary upgrade paths.
 
 -Clint

That's strange, I've gone right from 5.3 through to RELENG_7 without ever
doing the reboots during the install process (I know that's not recommended)
and I never ran into trouble. Did you accidently turn off compat6x in the
kernel before you built? Did your remember to install the misc/compat6x port?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-11 Thread Clint Olsen
On Nov 11, [LoN]Kamikaze wrote:
 That's strange, I've gone right from 5.3 through to RELENG_7 without ever
 doing the reboots during the install process (I know that's not
 recommended) and I never ran into trouble. Did you accidently turn off
 compat6x in the kernel before you built? Did your remember to install the
 misc/compat6x port?

Well, I wasn't upgrading to RELENG_7, so compat6x shouldn't have been an
issue.  And any compatibility library should not have been necessary when
doing a binary upgrade.  I was trying to boot a GENERIC kernel in the
upgrade process.  My 5.5 kernel is only slightly customized as a superset
of the original 5.X kernel.  I don't have the misc/compat5x installed on my
system.  I don't remember seeing that in the upgrading section of the
handbook, so I didn't do that.  I can see this as being necessary for
running certain legacy applications, but I should still be able to boot the
kernel.

Thanks,

-Clint
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-11 Thread Dimitry Andric

Clint Olsen wrote:

I attempted to just do a binary upgrade, assuming that I botched the source
upgrade somehow.  After installing FreeBSD 6.2-RELEASE, I was left with a
system that would not boot (similar errors on boot as before).


Any chance you could post some of these error messages?  And if
possible, backtraces, etc?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-11 Thread Clint Olsen
On Nov 11, Dimitry Andric wrote:
 Any chance you could post some of these error messages?  And if possible,
 backtraces, etc?

The messages amounted to page fault while in kernel mode or similar.  The
problem is the system attempts to reboot itself within 15 seconds.  I know
there is a way to postpone that, but how do I get more information from the
crash other than the screen dump?  I know in some crash instances it's
possible to get a kernel image dump, but I've never seen this as far as I
know.

Thanks,

-Clint
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-11 Thread Chris H.

Quoting Clint Olsen [EMAIL PROTECTED]:


On Nov 11, Dimitry Andric wrote:

Any chance you could post some of these error messages?  And if possible,
backtraces, etc?


The messages amounted to page fault while in kernel mode or similar.  The
problem is the system attempts to reboot itself within 15 seconds.  I know
there is a way to postpone that, but how do I get more information from the
crash other than the screen dump?  I know in some crash instances it's
possible to get a kernel image dump, but I've never seen this as far as I
know.


It's as simple as making your swap slice available for dumping, and adding a
line in your rc.conf file. Of course you'll need to lift the information of
interest from the vmcore, for the dump to be of any value. :)

Further reading/details can easily be obtained at the following links:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html

It's really a simple process.

Best wishes.

--Chris



Thanks,

-Clint
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]



--
panic: kernel trap (ignored)



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails

2007-11-10 Thread Clint Olsen
On Nov 02, [LoN]Kamikaze wrote:
 I think you might have no choice but to omit the reboots, because the
 world contains lots of stuff that has to do with the kernel (like
 mounting).
 
 So just go into single user mode and do the usual stuff:
 # make installkernel
 # mergemaster -p
 # make installworld
 # mergemaster
 # shutdown -r now
 
 and pray to your deity of choice.
 
 If the reason for your problem is something else however you're stuck
 with a system that can not run with your old kernel. So better backup
 before you try.

I attempted to just do a binary upgrade, assuming that I botched the source
upgrade somehow.  After installing FreeBSD 6.2-RELEASE, I was left with a
system that would not boot (similar errors on boot as before).  Reverting
the kernel of course was of limited help because userland was all expecting
6.2.  So, I had a couple of tarballs from my last backup and I attempted to
bandage up / and /usr and was able to resurrect my 5.5-STABLE image.

This is f'n scary.  I've never had this much trouble upgrading a system
before.  Does anyone have any idea what remnant could be remaining after a
binary upgrade that would keep it from booting yet I can boot from the
6.2-RELEASE iso's just fine?  I am very apprehensive to do a newfs and wipe
the drives now that I've failed both source and binary upgrade paths.

-Clint
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]