creataphysics
27th April 2012, 09:12 PM
I reinstalled fedora yesterday and everything worked great as per usual.
I then went ahead and did a full update and now my new kernel is getting this error and preventing fedora from booting:
Kernel panic - not syncing: stack-protector:
Kernel stack is corrupted in: c0bd4600
Kernel 3.3.2-8.fc17.i686
Before I reinstalled I was running that exact kernel, I believe it's been out since 4-21-12 and this issue hasn't seem to came up for anybody else before.
So I'm wondering what I did wrong to create this issue. I didn't do anything besides install fedora and perform the update. I went ahead and played Skyrim while it was updating, so nothing other than the update was being performed while I was waiting.
---------- Post added at 03:12 PM ---------- Previous post was at 01:42 PM ----------
I'm really sorry for wasting space in this forum with this topic.
I should have tried to reinstall the kernel before posting, I really don't know what made me jump the gun and post a topic in the forum.
Anyway, reinstalled the kernel fixed the issue. Once again, sorry for the waste of time/space.
I then went ahead and did a full update and now my new kernel is getting this error and preventing fedora from booting:
Kernel panic - not syncing: stack-protector:
Kernel stack is corrupted in: c0bd4600
Kernel 3.3.2-8.fc17.i686
Before I reinstalled I was running that exact kernel, I believe it's been out since 4-21-12 and this issue hasn't seem to came up for anybody else before.
So I'm wondering what I did wrong to create this issue. I didn't do anything besides install fedora and perform the update. I went ahead and played Skyrim while it was updating, so nothing other than the update was being performed while I was waiting.
---------- Post added at 03:12 PM ---------- Previous post was at 01:42 PM ----------
I'm really sorry for wasting space in this forum with this topic.
I should have tried to reinstall the kernel before posting, I really don't know what made me jump the gun and post a topic in the forum.
Anyway, reinstalled the kernel fixed the issue. Once again, sorry for the waste of time/space.