On Sat, 13 Mar 2004 02:18:25 -0500 Ken Smith <kensmith@cse.Buffalo.EDU>
> On Fri, Mar 12, 2004 at 10:10:16PM -0800, Wes Peters wrote:
> > Ok, I bumped into this problem too. Now when I try to boot my previous
> > kernel I get:
> > Type '?' for a list of commands, 'help' for more detailed help.
> > OK unload kernel
> > OK load /boot/kernel.old/kernel
> > /boot/kernel.old/kernel data=0x2bbc08+0x3c568
> > syms=[0x8+0x4ad18+0x8+0x3d2b2] OK boot
> > nothing to autoload yet.
> > jumping to kernel entry at 0xc0040000.
> > Copyright (c) 1992-2004 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > The Regents of the University of California. All rights
> > reserved.
> > FreeBSD 5.2-CURRENT #1: Wed Feb 18 22:58:52 PST 2004
> > email@example.com:/usr/obj/usr/src/sys/SPARKY
> > panic: trap: fast data access mmu miss
> > at line 364 in file /usr/src/sys/sparc64/sparc64/trap.c
> > Uptime: 1s
> > Not good. Time to burn a 5.2.1 CD?
> Ouch. I'm having trouble figuring out why the old kernel won't boot.
> As Kris said someone has suggested this is similar to the problem we
> had with make_dev() on the Alphas. That's certainly possible but if
> that kernel had been running before I'm not so sure that's the problem,
> I don't understand how the kernel would have been able to run before if
> it's really the make_dev() issue.
> You might want to give the ISO in snapshots/sparc64 on the mirror
> sites a try instead of the 5.2.1 CD, especially if you had already
> made the leap to 64-bit time_t. I was in the process of trying to
> create a newer version of that when I came across the problem with
> the root drive not being mountable. Now that it's fixed I'm trying
> again but it will be a day or so before that's ready (if all goes
> well this time :-).
> Can you let us know what hardware you have? I'm most interested in
> general model (e.g. Ultra-30?) and whether it has a graphical console
> that's supposed to work (e.g. Creator-3D?). If it does have the
> graphical console as a last resort you could try detaching the keyboard
> and connecting a serial console to see if you can coax it into booting
> the older kernel that way. I haven't been having problems with serial
> console machines at all recently...
Ultra-5 with 333MHz cpu module, (currently not) booting on serial console.
I have a keyboard and mouse, but they are currently resting in the closet
nearby. The kernel config is GENERIC with features I don't have hacked out;
nothing esoteric at all. I do usually remove and _ROOT options
I'll snag the latest snapshot and try that.
Where am I, and what am I doing in this handbasket?
Wes Peters firstname.lastname@example.org