Date: Tue, 21 Mar 2000 00:36:18 +0100 From: Harold Gutch <logix@foobar.franken.de> To: Mike Smith <msmith@FreeBSD.ORG> Cc: stable@FreeBSD.ORG, jlemon@flugsvamp.com Subject: Re: booting 3.x from CD? Message-ID: <20000321003618.A7626@foobar.franken.de> In-Reply-To: <20000320155420.B6058@foobar.franken.de>; from Harold Gutch on Mon, Mar 20, 2000 at 03:54:20PM %2B0100 References: <20000105191920.D11588@foobar.franken.de> <200001060829.AAA01025@mass.cdrom.com> <20000106144633.A13911@foobar.franken.de> <20000320155420.B6058@foobar.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 20, 2000 at 03:54:20PM +0100, Harold Gutch wrote:
> On Thu, Jan 06, 2000 at 02:46:33PM +0100, Harold Gutch wrote:
> > On Thu, Jan 06, 2000 at 12:29:18AM -0800, Mike Smith wrote:
> > > > On a (semi-)related topic - I tried to install FreeBSD
> > > > 3.3-RELEASE on my "Gericom" notebook last week and _always_
> > > > failed when booting from either the CD or from the 3.3 bootdisks
> > > > I had created.
> > > > The booting process would halt at either the point where it says
> > > >
> > > > Timecounter "i8254" frequency 1193182 Hz
> > > >
> > > > or it would pass exactly this point and then halt at the next
> > > > screen (the one where you select wether you want to config your
> > > > kernel in visual mode etc.). At one of these points it would
> > > > simply freeze, no panic, no dump, nothing.
> > >
> > > More details (eg. the output when you use 'boot -v' on the install
> > > floppies) would be helpful.
> >
> > Whoops, yes, I forgot to attach it to my last mail.
> > This is the output when booting from the CD. I doubt that the
> > verbose output from a bootdisk will look different, but I could
> > give it a try...
> >
> >
> > > It'd be interesting to know if you have the same problem with the boot
> > > floppies for a recent 4.0 snapshot.
> >
> > It halts at exactly the same point.
>
> I tried upgrading my notebook to 4.0-RELEASE last night and
> it froze at exactly the same point again.
>
> Two things to note:
> a) When booting with boot_ddb set, the kernel drops to DDB, but
> that's it - I can't do/type anything in DDB
> b) A GENERIC kernel from 4.0-CURRENT as of January 23rd 1999
> (just a few days after 4.0 got split off) boots just fine.
> I just started a "binary search" trying to nail down the last
> day it worked (and perhaps even the commit that broke it).
This is the commit that broke things for me. A kernel built from
the sources just before it boots, a kernel built from the sources
right after it "freezes" at the point above.
jlemon 1999/06/01 11:20:37 PDT
Modified files:
sys/dev/syscons scvesactl.c syscons.c
sys/i386/apm apm.c
Log:
Unifdef VM86
Reviewed by: silence on on -current
Revision Changes Path
1.10 +3 -4 src/sys/dev/syscons/scvesactl.c
1.306 +4 -5 src/sys/dev/syscons/syscons.c
1.88 +1 -8 src/sys/i386/apm/apm.c
Modified files:
sys/i386/conf LINT files.i386 options.i386
Log:
Make vm86 a standard component
Reviewed by: silence on on -current
Revision Changes Path
1.605 +2 -9 src/sys/i386/conf/LINT
1.246 +2 -2 src/sys/i386/conf/files.i386
1.115 +1 -2 src/sys/i386/conf/options.i386
Modified files:
sys/i386/i386 exception.s genassym.c globals.s locore.s
machdep.c mp_machdep.c mpboot.s pmap.c
swtch.s sys_machdep.c trap.c vm86.c
vm86bios.s vm_machdep.c
sys/i386/include globaldata.h globals.h pcb.h vm86.h
sys/i386/isa apic_vector.s ipl.s vesa.c
sys/i386/svr4 svr4_locore.s svr4_machdep.c
sys/kern subr_prf.c
sys/modules/vesa Makefile
Log:
Unifdef VM86.
Reviewed by: silence on on -current
Revision Changes Path
1.61 +1 -4 src/sys/i386/i386/exception.s
1.70 +1 -10 src/sys/i386/i386/genassym.c
1.12 +1 -6 src/sys/i386/i386/globals.s
1.123 +1 -17 src/sys/i386/i386/locore.s
1.337 +363 -285 src/sys/i386/i386/machdep.c
1.102 +1 -4 src/sys/i386/i386/mp_machdep.c
1.11 +1 -5 src/sys/i386/i386/mpboot.s
1.237 +1 -2 src/sys/i386/i386/pmap.c
1.82 +1 -14 src/sys/i386/i386/swtch.s
1.42 +1 -8 src/sys/i386/i386/sys_machdep.c
1.138 +1 -10 src/sys/i386/i386/trap.c
1.26 +18 -97 src/sys/i386/i386/vm86.c
1.14 +1 -3 src/sys/i386/i386/vm86bios.s
1.122 +1 -14 src/sys/i386/i386/vm_machdep.c
1.10 +1 -3 src/sys/i386/include/globaldata.h
1.3 +1 -5 src/sys/i386/include/globals.h
1.28 +1 -5 src/sys/i386/include/pcb.h
1.11 +3 -2 src/sys/i386/include/vm86.h
1.39 +1 -3 src/sys/i386/isa/apic_vector.s
1.28 +1 -7 src/sys/i386/isa/ipl.s
1.24 +3 -4 src/sys/i386/isa/vesa.c
1.4 +0 -2 src/sys/i386/svr4/svr4_locore.s
1.5 +0 -4 src/sys/i386/svr4/svr4_machdep.c
1.52 +18 -1 src/sys/kern/subr_prf.c
1.6 +3 -7 src/sys/modules/vesa/Makefile
I noticed that when booting with older sources, the kernel
reports:
[...]
sio0: system console
[...]
which looks pretty wrong to me, as the console are the keyboard
and the screen attached to it (I didn't even connect anything to
the serial ports).
I have absolutely no idea how to debug the problem I described
above, as not even setting "boot_ddb" managed to break into a
debugger where I would be able to at least try to have a closer
look at this problem.
Does somebody have any ideas what I could try out?
bye,
Harold
--
Someone should do a study to find out how many human life spans have
been lost waiting for NT to reboot.
Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000321003618.A7626>