[SOLVED] Kernel panic for an unknown reason

Question

[Solved] Steps done to solve it:
0. Panic because I couldn't play starcraft2 (this step is sooo important! ;)
1. Updated my mirrorlist.
2. Forced a refresh on the package list from the new mirrorlist. "pacman -Syy"
3. Downgraded the kernel.
4. Deleted the latest kernel package from the pacman cache.
5. Updated the system. (pacman -Syu)
6. Thanked lilsirecho for helping out!
7. Profit
Hi all
I just did a "pacman -Syu" this afternoon and after that I'm getting kernel panics for unknown reasons.
edit: I had kernel 3.0.4 befure syu and I have kernel 3.0.7 now. I tried downgrading wine and the kernel with no success.
It first happened when I tried to run StarCraft2 with wine. I even created a post looking for help because of that.
Later on I tested another game, just in case, and it crashed too.
Looks like a wine problem, right? Or even a graphics driver problem.
That's what I thought too. But then I tried to update with "yaourt -Syu --aur" and in the first package compression it freezed once again. And it does fail everytime I try to update with yaourt during the compression phase.
What do this situations have in common?
My opinion is that they all require a lot of resources. StarCraft 2 puts my PC at 100% almost all the time. The other game is pretty old, but it freezed during an "environment loading" phase, right when the map was loading. The compression phase of yaourt also consumes a lot of resources.
This is my view of this problem, but I could be completely wrong.
What I need is help finding what is the real source of this kernel panics. I don't know where to look for the logs or the error reports when a kernel panic occurs.
I hope someone can help me trace the problem somehow. I think I'm lost
ty in advance.
cheers!
Last edited by fatum (2011-11-10 23:16:10)

Answer 1

lilsirecho wrote:
Possibly caused by a mirror download.
Perhaps you need to revert kernel and insure you have the latest mirrorlist and then syu again.
When I saw your response I thought: "Why should that be true? I downgraded the kernel with no success. Doesn't make much sense".
But then I did what you said:
Downgraded the kernel back to 3.0.4.
Moved the latest mirrorlist.pacnew I had to be the mirrorlist in use.
Then did a "pacman -Syyu".
And, miraculously, it works fine now.
How in the world did you know that could be the reason? It would have been the last possibility I would have thought about, no doubt about that
Thank you very much lilsirecho. Your post really helped me.
Not gonna mark this as SOLVED yet. Yesterday I marked my other thread as solved too soon and I regretted my decision.
I will leave a 1week time-frame to be 100% sure that it is fixed, just in case.