Date: Thu, 14 Feb 2002 09:23:27 -0700 From: "Jan L. Peterson" <jlp@softhome.net> To: martijn <martijn@pacno.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: panic on 4.5-RELEASE Message-ID: <20020214162327.8795541EF4@mail.flipdog.com> In-Reply-To: Your message of "Thu, 14 Feb 2002 10:40:37 %2B0100." <20020214094037.GC92426@drain.hofnet> References: <20020213230828.34F3341EF4@mail.flipdog.com> <20020214094037.GC92426@drain.hofnet>
next in thread | previous in thread | raw e-mail | index | archive | help
martijn@pacno.net said: > My situation was that i was copying a bunch of stuff from a linux > machine, which had options for nfs mounts set to 16384 byte blocks. > When i set them to 8192, FreeBSD didn't crash any more. I don't think this is the problem. The host I'm copying from is also FreeBSD (4.5-RC from about January 24th). Here's an interesting data point. In an effort to get more information out of the debugger, I re-config'd the kernel with "config -g". After booting the new kernel, I tried to get it to fail in the same spectacular way, but it doesn't want to crash now. Could it be dodgy hardware in my case, as well? This install is going to be for my laptop, but I currently have the (new) drive in another (borrowed) laptop of the same brand/version/configuration (so I don't lose my workstation while I do this upgrade). This machine has been running Win2k for a year or so without any trouble. I find it odd that merely compiling the kernel with -g would make it suddenly not fail. -jan- -- Jan L. Peterson <jlp@softhome.net> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020214162327.8795541EF4>