You are not logged in.
Hi all,
Been using arch for quite a while (years) and this is actually the first time my arch install decided to do something really wonky.
Basically, just after a normal boot-up a kernel panic occurred with the titular error. No recent upgrades, or any other actions that would bring cause for alarm. I'm using a vanillia 3.8.4-1-ARCH kernel on a 64bit HP laptop.
Sorry for the vague question and lack for info; just tell me what you need and I'll try to get back to you ASAP.
If you're reading this; you're awesome.
Offline
Does it continue to happen?
Offline
It has only happened once before within a month ago. The other time I was simply coding a new project and then it panicked.
If you're reading this; you're awesome.
Offline
I don't think you have anything to worry about. It happens every so often. I don't have it happen very often either, but it certainly has before. I think you need to worry only f it starts happening consistently.
Offline
Well.. it just happened just now (as of the time of this post).
Just gotta say I haven't had this much kernel panics in the last month or so in last (6)? years that I've been using Arch.
So far the only consistency is my browser being open (but who's isn't nowadays?).
Oh well, will continue posting updates..
If you're reading this; you're awesome.
Offline
This is obviously some bug in 3.8.4.
Does it print anything besides this "kernel panic" line?
Offline
Nope, nothing; just the standard garbage that comes along with the kernel panic line. Searching google images for "kernel panic fatal exception in interrupt" pretty much shows what pops up when it does.
If you're reading this; you're awesome.
Offline
This is obviously some bug in 3.8.4.
Does it print anything besides this "kernel panic" line?
I don't know that there has been enough information in this thread to really come to this conclusion.
@Ari'osika, can you try using the testing kernel and see if that proves more stable? I think if you can find stability in a different kernel, then that might be an actual indication that this is a bug in the kernel as mentioned above. I have used the new kernel a bit actually, as I have the testing repo enabled currently so that I can use pacman 4.1, and it seems just fine.
Offline