Date: Fri, 17 Nov 2000 15:31:14 -0500 (EST) From: sko@eth0.net To: freebsd-alpha@FreeBSD.ORG Subject: RESOLVED - Re: loader issues... Message-ID: <Pine.BSI.4.05.10011171527320.10967-100000@comet.connix.com> In-Reply-To: <Pine.BSI.4.05.10011162138540.13757-100000@comet.connix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Welp, after about a total of a dozen RC1 install iterations, I've
determined what the heck was wrong w/ my bootup.
Since I was reinstalling a few times, I had decided to "make my life
easier" (which of course caused this whole problem, having the exact
opposite effect of what was intended) by creating just 2 partitions (/ and
swap) on the 1Gb drive in my AS200.
SRM doesnt appear to like that one bit (which I ended up thinking of this
because I had the _exact_ same problem w/ OpenBSD & the OpenBoot prom on
my SparcIPX at home).
Anyhoo, I've gone thru 2 complete install iterations w/ no booting issues,
once I carved the disk differently.
-Shawn
On Thu, 16 Nov 2000 sko@eth0.net wrote:
>
> Did a full re-install, including deleting and re-creating the partitions
> and still getting "couldn't find /boot/loader". I'll see what I can do
> from the Emergency Holographic Shell ("please state the nature of your
> FreeBSD Installation emergency *smirk*) tomorrow.
>
> -Shawn
>
> On Thu, 16 Nov 2000, O'Shea. Shawn wrote:
>
> >
> > So I figure, "Well I ifconfig'ed the device manually, let me get a fresh
> > reboot, and then i'll dhclient just de0". So I did a reboot and now i get
> > "Can't open file /boot/loader". I tried doing a reinstall with the same
> > result. I remember seeing a thread on here about loader problems but dont
> > remember what resolution there was...
> >
> > -Shawn
> >
> > On Thu, 16 Nov 2000, Andrew Gallatin wrote:
> >
> > >
> > > sko@eth0.net writes:
> > > >
> > > > I had 4.1 on my AS200 and just reinstalled w/ the 4.2RC1 and had the same
> > > > problem on both. dhclient panics the box and reboots (GENERIC kernel in
> > > > both cases). Can anyone help?
> > > >
> > > > Related output from messages:
> > > > Aug 4 21:08:49 /kernel: looutput: af=0 unexpected
> > > > Aug 4 21:08:49 dhclient: send_packet: Address family not supported by protocol
> > > > family
> > > > Aug 4 21:11:32 /kernel:
> > > > Aug 4 21:11:32 /kernel: fatal kernel trap:
> > > > Aug 4 21:11:32 /kernel:
> > > > Aug 4 21:11:32 /kernel: trap entry = 0x2 (memory management fault)
> > > > Aug 4 21:11:33 /kernel: a0 = 0x0
> > > > Aug 4 21:11:33 /kernel: a1 = 0x1
> > > > Aug 4 21:11:33 /kernel: a2 = 0xffffffffffffffff
> > > > Aug 4 21:11:33 /kernel: pc = 0x0
> > > > Aug 4 21:11:33 /kernel: ra = 0xfffffc00005bccc0
> > > > Aug 4 21:11:33 /kernel: curproc = 0
> > > > Aug 4 21:11:33 /kernel:
> > > > Aug 4 21:11:33 /kernel: panic: trap
> > > > Aug 4 21:11:33 /kernel:
> > > > Aug 4 21:11:33 /kernel: syncing disks... 23 23 23 23 23 23 23 23 23 23 23 23 2
> > > > 3 23 23 23 23 23 23 23
> > > > Aug 4 21:11:33 /kernel: giving up on 23 buffers
> > >
> > > I cannot duplicate the panic on a 4.2RC1 system here. I see everything but the panic.
> > >
> > > According to nm -n on the 4.2RC1 kernel, it is:
> > > fffffc00005bcd00 T do_sir
> > > fffffc00005bcc80 t swi_net
> > > fffffc00005bcd00 T do_sir
> > >
> > >
> > > So it looks like swi_net is trying to schedule a null swi.
> > > Ick.
> > >
> > > What happens if you start dhclient on just the interface you want to
> > > run it on (eg, not lo0, which is somewhat nonsensical anyway..)
> > >
> > > Drew
> > >
> >
> > --------------------------------------------------------------
> > # ifconfig eth0.net "Shawn O'Shea" netmask 255.255.255.0 up
> > # route add -net smtp shawn@eth0.net
> > # route add -net http http://eth0.net
> >
> >
>
> --------------------------------------------------------------
> # ifconfig eth0.net "Shawn O'Shea" netmask 255.255.255.0 up
> # route add -net smtp shawn@eth0.net
> # route add -net http http://eth0.net
>
>
--------------------------------------------------------------
# ifconfig eth0.net "Shawn O'Shea" netmask 255.255.255.0 up
# route add -net smtp shawn@eth0.net
# route add -net http http://eth0.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.05.10011171527320.10967-100000>