On Mon, 16 Jul 2001, Bill Moran wrote: > Virtual Bob wrote: > > > > I got 4.3-S running on Xeon and was compiling a custom kernel. On another > > console, I was doing telnet and then this message suddenly popped up: > > > > Jul 16 12:43:07 kablooi /kernel: got bad cookie vp 0xc876c740 bp > > 0xc3394950 > > ... > > > > I'm suddenly getting several lines every few minutes. I searched Yahoo and > > FreeBSD mail list but couldn't get any results that has to do with it. > > What is it? > > It's an NFS error. What are you doing with NFS while this is going on? Wow, interesting. On my network, a 3.5-S is the NFS server exporting only /usr/src (updated every night). I looked at the dates of /bin/* etc., and see that 3.5-S's last "made world" was on May 6 this year. Anyway, I got this Xeon 4.3-S workstation that was compiling a custom kernel, which accesses NFS:/usr/src and it's the only time NFS would get accessed. No wonder I don't recall seeing that error before. This workstation just got brand spanking new make world this weekend. But since I just left it running on its own, I guess I never saw the error if it did appeared then. I just did a quick browse of the link provided by Mike. Looks like problems with theories vs. reality. Did NFS client code on RELENG_4 get a touch-up recently? Who's at fault here? 4.3-S NFS client or 3.5-S NFS server? ------------- clip here with virtual scissors -------------- ************************************************************ Keyboard stuck error. Press F1 to continue. Any unsolicited e-mails will be charged US$500 per e-mail, plus court cost. Your contribution to Bill Gates' personal wealth: US$359.17 ************************************************************ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
