Kernel panic

Hello, just updated to the kernel 2.6.36.2 contained in this repository:

Index of /repositories/Kernel:/stable/openSUSE_11.3

The x86_64 type.

And im getting a kernel panic after about 15 minutes of machine usage.

Is it an error in packaging or what?

So what does the Kernel Panic say or complain about? I have not used this repository before, but I have used the 2.6.36.2 kernel and it works fine with openSUSE 11.3. May I suggest you revert back to your original Kernel while you can and consider using S.A.K.C. to upgrade your kernel version? Message #17 has the most recent version of the script file.

S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.00

Thank You,

The only way i could post what the kernel panic says is taking a photograph of my screen.

I dont think i need a script to update the kernel. I have updated it many many times through YAST and it has worked fine.

You’ll have to check your log files. ‘/var/log/messages’ should contain the stack trace.

On 12/16/2010 10:06 PM, assas1n wrote:
>
> The only way i could post what the kernel panic says is taking a
> photograph of my screen.
>
>
> I dont think i need a script to update the kernel. I have updated it
> many many times through YAST and it has worked fine.

Post that picture.

How should it be called? Im seeing alot of log files in there !!

Oh, and i tried replicating the kernel panic, left the computer running Folding@Home, 100% CPU usage all night, woke up and it was still running, so its weird !

Try

grep panic /var/log/messages

No output from that command

On 12/17/2010 09:36 AM, assas1n wrote:
>
> How should it be called? Im seeing alot of log files in there !!
>
> Oh, and i tried replicating the kernel panic, left the computer running
> Folding@Home, 100% CPU usage all night, woke up and it was still
> running, so its weird !

The stack trace for a kernel panic is NOT in the system logs. By definition, a
panic is triggered only when the kernel state is such that trying to write disk
would be tempting disaster and potential file-system corruption. The only place
the dump occurs is on a text console, or on serial or network consoles if you
set them up in advance.

Random panics are often a sign of memory errors. Rather than test with folding
proteins, you might try a 12 hour run with memtest86+.

Use the memtest on the CD/DVD.

I doubt is has anything to do with memory corruption. Problem started just at the precise moment that i updated the kernel.

Besides, Folding@Home is very sensitive so corruptive memory and would have failed on the 10 hours i left it running.

Well, just happened again today, so i took a picture:

http://img24.imageshack.us/img24/7632/failkernel.jpg](http://img24.imageshack.us/i/failkernel.jpg/)

Uploaded with ImageShack.us

What is FahCore_a3.exe???

VampirD wrote:
> What is FahCore_a3.exe???

folding@home


DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
I feel annoyed that I can’t put my wide range of languages on stupid
Facebook. For example, I speak Sarcasm, fluently spoken and written,
and Various Forms of Geek…

I have just three thoughts on the subject, based on the fact that this problem did not start until the Kernel was upgraded to 2.6.36.2:

  1. Downgrade back to openSUSE Kernel 2.6.34.7
  2. Downgrade to Kernel 2.6.35.9

OR

  1. Upgrade to Kernel 2.6.37-rc7

And see what you get.

Thank You,

Well, the problem must me related to folding@home and the kernel upgrade. So ill stop folding for the days left on the 2.6.37 kernel release.

Strange though that i couldnt find any more people having this same issue with the .36 kernel.

Oh, and thanks for looking into this topic !

Well, the problem must me related to folding@home and the kernel upgrade. So ill stop folding for the days left on the 2.6.37 kernel release.

Strange though that i couldnt find any more people having this same issue with the .36 kernel.

Oh, and thanks for looking into this topic !
Good luck there assas1n and your work with folding@home. It would seem that kernel 2.6.37 will be coming out very soon. I just loaded 2.6.37.rc7 tonight using sakc and all seems good so far.

Thank You,

Thanks :slight_smile:
I’ve been contributing on a quad core Athlon II since 2 years already. To my old country OC team, “Overclockers Chile”, team number 33478

Just tried updating to 2.6.37-rc8 and got another kernel panic or kernel Oops.

It said something like this:
BUG: Unable to handle kernel paging request
Oops: Preemt SMP

And now it had nothing to do with folding, but mentioned something about the Opera browser i was using at the time.

My 2 cents: run memtest, not for an hour or so, but 24 hours at least. There should be exactly zero errors. Stop working on this machine until you have 100% OK result from memtest. Have backups.