Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 26 Mar 2001 21:33:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 26 Mar 2001 21:33:45 -0500 Received: from ma-northadams1-47.nad.adelphia.net ([24.51.236.47]:10759 "EHLO sparrow.net") by vger.kernel.org with ESMTP id ; Mon, 26 Mar 2001 21:33:35 -0500 Date: Mon, 26 Mar 2001 19:47:16 -0500 From: Eric Buddington To: linux-kernel@vger.kernel.org Subject: oops while futzing with nfsboot 2.4.2-ac24 Message-ID: <20010326194716.E59@sparrow.nad.adelphia.net> Reply-To: ebuddington@wesleyan.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: ECS Labs X-Eric-Conspiracy: there is no conspiracy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This ooops happened while trying to nfsboot a 386, and restarting nfsd halfway through the boot process. I bet it's not a common problem... Server is 2.4.2-ac23, client (the Oopser) is 2.4.2-ac24. The oops is partial because I had to hand-copy from the console, and it blanked after a few minutes. The client was trying to mount its root fs at the time (it failed). -Eric ------ ksymoops 2.4.1 on i586 2.4.2-ac23. Options used -V (default) -K (specified) -L (specified) -O (specified) -m /packages/linux/2.4.2-ac24/i386-nfsroot/boot/System.map (specified) *pde = 00000000 Oops: 0000 EIP: 0010:[<00000000>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010286 eax: 00000000 ebx: fffffff4 ecx: c0095420 edx: c0095380 Call Trace: [ ] Code: Bad EIP value >>EIP; 00000000 Before first symbol Trace; c0139c37 Trace; c0139fe7 Trace; c013aa2f Trace; c012fb22 Trace; c012fe25 Trace; e0108d73 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/