From owner-freebsd-current Sat Mar 30 19:22:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id C5E6137B400; Sat, 30 Mar 2002 19:22:37 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g2TMxQN01765; Fri, 29 Mar 2002 14:59:26 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200203292259.g2TMxQN01765@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Crist J. Clark" Cc: current@freebsd.org Subject: Re: nfsclient module panics In-reply-to: Your message of "Wed, 27 Mar 2002 00:58:12 PST." <20020327005812.P89885@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Mar 2002 14:59:26 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It would be good to see where this actually is when it traps; DDB would help. (Sorry if this has already been dealt with) > For a couple of days, I have been consistent panics whenever I mount > an NFS filesystem on a newly made -CURRENT. Things seem to work fine > when NFS is actually built into the kernel. But when mount(8) is auto > loading the nfsclient.ko module, I get an immediate panic when > something actually tries to access the filesystem, > > IdlePTD at phsyical address 0x00411000 > initial pcb at physical address 0x00340ac0 > panicstr: bdwrite: buffer is not busy > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xc2 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc942baeb > stack pointer = 0x10:0xc8ea1c10 > frame pointer = 0x10:0xc8ea1cbc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 7 (syncer) > trap number = 12 > panic: page fault > > syncing disks... panic: bdwrite: buffer is not busy > Uptime: 2m10s > > dumping to dev ad0s2b, offset 264864 > dump ata0: resetting devices .. done > 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 1 > 07 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 8 > 4 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 > 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 > 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 > 5 4 3 2 1 0 > --- > #0 0xc01b6b8a in dumpsys () > > Is this a known issue (I haven't noted mention of it on here) or does > someone want to see some more debugging info? > -- > Crist J. Clark | cjclark@alum.mit.edu > | cjclark@jhu.edu > http://people.freebsd.org/~cjc/ | cjc@freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message