From owner-freebsd-alpha Thu Nov 16 9:24:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6FE6B37B4C5 for ; Thu, 16 Nov 2000 09:24:29 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA12791; Thu, 16 Nov 2000 12:24:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAGHOS139852; Thu, 16 Nov 2000 12:24:28 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Nov 2000 12:24:28 -0500 (EST) To: sko@eth0.net Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: DHCP broken? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14868.6006.689718.940301@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message