From owner-freebsd-alpha Thu Nov 16 18:42:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from comet.connix.com (comet.connix.com [198.69.10.4]) by hub.freebsd.org (Postfix) with ESMTP id E04BB37B479 for ; Thu, 16 Nov 2000 18:42:13 -0800 (PST) Received: from localhost (booga@localhost) by comet.connix.com (8.9.3/8.9.3) with ESMTP id VAA08143 for ; Thu, 16 Nov 2000 21:41:28 -0500 (EST) X-Authentication-Warning: comet.connix.com: booga owned process doing -bs Date: Thu, 16 Nov 2000 21:41:28 -0500 (EST) From: sko@eth0.net X-Sender: booga@comet.connix.com To: freebsd-alpha@FreeBSD.ORG Subject: Re: loader issues... will get back to Re: DHCP broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message