|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Re: RAM Upgrade problems
|
On Fri, Dec 08, 2000 at 03:08:24PM -0500, Kevin Falcone wrote:
> >>>>> "GL" == Greg Lopp <lopp@earthlink.net> writes:
> GL> On Fri, Dec 08, 2000 at 01:52:20PM -0500, Kevin Falcone wrote:
> >>
> >> this allows you to tell the kernel how much ram you have. The hihgmem
> >> options shouldn't kick in until 1gig of RAM.
>
> GL> As I mentioned on a separate thread, I tried this and received a
> GL> general protection fault.
>
> A what? Did the BIOS give you issues or did the kernel OOPs or what?
> I've never heard the term general protection fault outside of a
> windows environment. If you got an oops, and it logged, try running
> it through ksymoops and posting to linux-kernel.
General protection fault is an architecture term. If some opcode
attempts to access a physical memory location that is not currently
allowed due to the state of the processor(real mode/protected mode,
priority, paged and/or segemented, gdt or ldt, descriptor value,
etc.), then you get a GPF. What that translates to, is that the
processor saves its state and starts processing from whatever
interrupt service routine has been installed for INT 13.
Is OOPS an acronym, or is it really just "oops" like "that's not
supposed to happen"? I read
/usr/src/linux/Documentation/oops-tracing.txt, so I've added that to
my list of things to try after work....
______________________________________________________________________
Philadelphia Linux Users Group - http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|