Date: Mon, 15 Jul 2002 11:47:38 -0700 From: "Balaji, Pavan" <pavan.balaji@intel.com> To: "'Fernando Gleiser'" <fgleiser@cactus.fi.uba.ar>, "Balaji, Pavan" <pavan.balaji@intel.com> Cc: freebsd-questions@FreeBSD.ORG Subject: RE: Unable to compile the kernel Message-ID: <3D386AED1B47D411A94300508B11F18703BC5BAF@fmsmsx116.fm.intel.com>
next in thread | raw e-mail | index | archive | help
> 1. faulty memory > 2. faulty cache > 3. cooling problems > 4. overclocking > 5. Bad timing settings in the BIOS Can I do something about these? > How did you add the syscall? Is it a KLD or is it built into > the kernel? > Did you modify syscalls.master. How did you get the syscall > #?. Could you > post your syscall code and *any other modifications to the > kernel* you made? I built it into the kernel -- changed the syscalls.master file. The system calls are empty functions. No problem with the functions , am able to use them from user-level programs. It's just when I modify it for the second time (whatever the modification be), that this problem comes up. How do I use kld to add syscalls dynamically? Can you send me some link or a brief how-to. Thanx! Pavan Balaji, CIS Graduate Student, Ohio State University "Being happy doesn't mean that everything is perfect... It just means that you have decided to see beyond the imperfections" -- Rash > -----Original Message----- > From: Fernando Gleiser [mailto:fgleiser@cactus.fi.uba.ar] > Sent: Monday, July 15, 2002 1:36 PM > To: Balaji, Pavan > Cc: freebsd-questions@FreeBSD.ORG > Subject: RE: Unable to compile the kernel > > > On Mon, 15 Jul 2002, Balaji, Pavan wrote: > > > > > > > Which error? > > > > No fixed error. I just core dumps at random places. It > sounds weird, since > > it's only a compilation and not a runtime library, but it's > been happening > > since last night. > > gcc dying and dumping core at random places is an indication > of harware > problems. The most common are: > > 1. faulty memory > 2. faulty cache > 3. cooling problems > 4. overclocking > 5. Bad timing settings in the BIOS > > > If it were related to your new kernel, it would be more deterministic. > > > > > > > > > > > Which system call? > > > > My own system call. It's an empty function right now. > > > > How did you add the syscall? Is it a KLD or is it built into > the kernel? > Did you modify syscalls.master. How did you get the syscall > #?. Could you > post your syscall code and *any other modifications to the > kernel* you made? > > > > > > > > > Did anyone else have such a problem? Any suggestions? Tips? > > > > > > Could you post more details? > > > > I suspect some dumb a** must have hardcoded the number of > system calls > > somewhere in the kernel and that's what is giving the problem. > > No, it is not. You can even add syscalls dynamically via a KLD. > It is easier to develop the syscall as a KLD and then add it > statically > to the kernel. > > > > Fer > > > > > > Pavan Balaji, > > CIS Graduate Student, > > Ohio State University > > > > "Being happy doesn't mean that everything is perfect... It > just means that > > you have decided to see beyond the imperfections" -- Rash > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D386AED1B47D411A94300508B11F18703BC5BAF>