Re: General Protection Fault in openafs, 2.6.25 and 2.6.26 kernels
Update: this issue is now bug 500850 in openafs-modules-source. The solution is to set the following in the kernel .config: CONFIG_KEYS=y CONFIG_KEYS_DEBUG_PROC_KEYS=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y -- Andrew J Perrin - andrew_perrin (at) unc.edu - http://perrin.socsci.unc.edu Associate Professor of Sociology; Book Review Editor, _Social Forces_ University of North Carolina - CB#3210, Chapel Hill, NC 27599-3210 USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: General Protection Fault in openafs, 2.6.25 and 2.6.26 kernels
On Mon, 29 Sep 2008, Andrew Perrin wrote: Using debian testing (lenny) and self-compiled 2.6.25 or 2.6.26 kernels, I get the following GPF: Sep 29 16:08:47 che kernel: general protection fault: [#1] SMP ... Sep 29 16:08:47 che kernel: Call Trace: Sep 29 16:08:47 che kernel: [] afs_osi_TraverseProcTable+0x12/0x5e [openafs] Sep 29 16:08:47 che kernel: [] afs_GCPAGs+0x9e/0x164 [openafs] Sep 29 16:08:47 che kernel: [] afs_Daemon+0x4ce/0x512 [openafs] Sep 29 16:08:47 che kernel: [] afsd_thread+0x484/0x656 [openafs] Sep 29 16:08:47 che kernel: [] afsd_thread+0x0/0x656 [openafs] Sep 29 16:08:47 che kernel: [] kernel_thread_helper+0x7/0x14 Sep 29 16:08:47 che kernel: === ... This does *not* happen using 2.6.24 compiled with essentially the same .config file. Using the latest openafs-modules-source: 1.4.7.dfsg1-5. Odd... I'm on Sid, openafs 1.4.7-dfsg1-5 and 2.6.26.5 without issues The failing function seems like maybe you didn't enable some legacy proc stuff that OpenAFS may be depending upon -- Rick Nelson #if _FP_W_TYPE_SIZE < 32 #error "Here's a nickel kid. Go buy yourself a real computer." #endif -- linux/arch/sparc64/double.h -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: General Protection Fault in openafs, 2.6.25 and 2.6.26 kernels
Andrew Perrin wrote: > Using debian testing (lenny) and self-compiled 2.6.25 or 2.6.26 kernels, > I get the following GPF: [GPF trace snip] > This does *not* happen using 2.6.24 compiled with essentially the same > .config file. Using the latest openafs-modules-source: 1.4.7.dfsg1-5. > > Any adivce? Thanks. I think you should 'reportbug' it as soon as possible to Debian BTS. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RE: General Protection Fault
Try with a better and larger cpufan. My K6-2 400 was so hot that Linux crached all the time. Nearly all those who sells computer with K6-2 and K6 use a to small cpufan. Sad but true.. Once upon a time someone wrote: > Are you sure the K6 hasn't been over clocked by some bastard salesman ? > > -- > From: Ron Rademaker[SMTP:[EMAIL PROTECTED] > Sent: Monday, 24 April 2000 5:57 AM > To: debian-user@lists.debian.org > Subject: General Protection Fault > > How do I solve a General Protection Fault (Oops = 0002), I get it when I > boot with the rescue disk, when trying to install (right after mounting > the root filesystem (RAM)) it gives the errors, and ends with: Aiee, > killing the interrupt handler > If you need more information, I wrote all the output down so I can post it > if that would help you... > > The system started giving general protection faults after I upgraded it > (general protection faults both in linux as in windows) from a P166 with > 32 M to a amd k6-2 533 with 128 M. > > HELP!!! > > Ron Rademaker > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
RE: General Protection Fault
The K6 says it's 533, it runs on 520, so I don't think that can be a problem, or am I mistaken? On Sat, 29 Apr 2000, C. Falconer wrote: > Are you sure the K6 hasn't been over clocked by some bastard salesman ? > > -- > From: Ron Rademaker[SMTP:[EMAIL PROTECTED] > Sent: Monday, 24 April 2000 5:57 AM > To: debian-user@lists.debian.org > Subject: General Protection Fault > > How do I solve a General Protection Fault (Oops = 0002), I get it when I > boot with the rescue disk, when trying to install (right after mounting > the root filesystem (RAM)) it gives the errors, and ends with: Aiee, > killing the interrupt handler > If you need more information, I wrote all the output down so I can post it > if that would help you... > > The system started giving general protection faults after I upgraded it > (general protection faults both in linux as in windows) from a P166 with > 32 M to a amd k6-2 533 with 128 M. > > HELP!!! > > Ron Rademaker > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
RE: General Protection Fault
Also, What, exactly, did you upgrade? What type of motherboard did you have before? now? This is definately a HW issue, so we'll need details on the system. Bryan On 29-Apr-2000 C. Falconer wrote: > Are you sure the K6 hasn't been over clocked by some bastard salesman ? > How do I solve a General Protection Fault (Oops = 0002), I get it when I > boot with the rescue disk, when trying to install (right after mounting > the root filesystem (RAM)) it gives the errors, and ends with: Aiee, > killing the interrupt handler > If you need more information, I wrote all the output down so I can post it > if that would help you... > > The system started giving general protection faults after I upgraded it > (general protection faults both in linux as in windows) from a P166 with > 32 M to a amd k6-2 533 with 128 M. > >
RE: General Protection Fault
Are you sure the K6 hasn't been over clocked by some bastard salesman ? -- From: Ron Rademaker[SMTP:[EMAIL PROTECTED] Sent: Monday, 24 April 2000 5:57 AM To: debian-user@lists.debian.org Subject:General Protection Fault How do I solve a General Protection Fault (Oops = 0002), I get it when I boot with the rescue disk, when trying to install (right after mounting the root filesystem (RAM)) it gives the errors, and ends with: Aiee, killing the interrupt handler If you need more information, I wrote all the output down so I can post it if that would help you... The system started giving general protection faults after I upgraded it (general protection faults both in linux as in windows) from a P166 with 32 M to a amd k6-2 533 with 128 M. HELP!!! Ron Rademaker -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: General Protection Fault
Ron Rademaker wrote: > The system started giving general protection faults after I upgraded it > (general protection faults both in linux as in windows) from a P166 with > 32 M to a amd k6-2 533 with 128 M. Hmmm. Sounds like bad RAM to me. Try the old 32M or RAM from a working machine and see if the problem persists. MfG Viktor -- Viktor Rosenfeld E-Mail: mailto:[EMAIL PROTECTED] HertzSCHLAG:http://www.informatik.hu-berlin.de/~rosenfel/hs/
Re: General Protection Fault
On Sun, Apr 23, 2000 at 07:57:27PM +0200, Ron Rademaker wrote: > How do I solve a General Protection Fault (Oops = 0002), I get it when I > boot with the rescue disk, when trying to install (right after mounting > the root filesystem (RAM)) it gives the errors, and ends with: Aiee, > killing the interrupt handler > If you need more information, I wrote all the output down so I can post it > if that would help you... Yes, more information would help. Can you boot your system normally? Did you update your rescue disk after updating your system? Did you reformat any partitions? The new ext2 format works with 2.2.x+ kernels, but not 2.0.x. What's your rescue disk kernel? > The system started giving general protection faults after I upgraded it > (general protection faults both in linux as in windows) from a P166 with > 32 M to a amd k6-2 533 with 128 M. Hmmm... Can you boot anything with the system? There are some posts regarding 500MHz and better CPU problems. I believe there's a MS Windows bug WRT 533 MHz chips specifically. I'd recommend some online research. -- Karsten M. Selfhttp:/www.netcom.com/~kmself What part of "Gestalt" don't you understand? http://gestalt-system.sourceforge.net/ GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgpvSUfmJuXxV.pgp Description: PGP signature
