Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ... and a possible reason
I'm diligently investigating my problem.
This post is deleted!
exactly same problem here, someone has a solution?
No, this is not the same as the problem you are reporting elsewhere. The subject of this thread is not failures in general, but a very specific one linked to wifi.
Please stop making repetitive posts in multiple threads.
T NT last edited by
These are interesting findings, they suggest there may be a bug in the wifi driver than can be triggered by variations in local circumstance.
Hmmm I am wondering now if that is why out of the 3 APs I have both on G and N my Omega only sees one. I tried playing around with the channels encryption cyphers etc. But to no avail.
Any news regarding this?
Same issue, I had to turn off nearby home routers (same floor) to make work my omega2p.
I could barely avoid the kernel panic to move my home router to 2nd floor and use my omega2p at the 1st floor -_-;;
No more solution via flash update? or it is hardware problem??
I hope the official onion dev team clear this question.
I did a couple of experiments yesterday night. (b160 f/w)
With 5 WIFI routers near me, I changed all the SSIDs which is comprised of some CJK characters with a bit long string length into a simple English characters. And then, no more kernel panic.
I am sure this solved, at least, my problem as if I changed those SSIDs back to original, I got kernel panic again
And I think the problem is only occured by 2.4GHz setting but not by 5GHz.
If the problem is really with this matter, the device driver (or any related kernel code) should be fixed as it could lead to a security problem.
Douglas Kryder last edited by
@kurt-john but, with the number of users that reported an issue with kernel panic it is improbable to think that they were all affected by a cjk ssid string therefore the fact that this change in the string solved your problem is perhaps just a coincidence
@Douglas-Kryder i tested at around 7~8 times changing SSID back and forth; and the result was consistent. Anyway, agreed that, may be, my case is not applied for all the case as you said. I just wonder maybe someone try the SSID "하이네켄인증포어러2.4G" (without quotes) and see if the SSID triggers any kernel panic like me
the panic seems to be occurred in the wifi scan stage during the boot-time.
Douglas Kryder last edited by
i'd be ok with testing on a win10 laptop. there was a download which i guess is a character set so i need to see what the file is sometime tomorrow. my own omega2's , i have 2 that could be testers but can not do it till lunch time tomorrow.
@sunny-lau's omega2+ shutdown every time I turn my mobile AP on post was the key for me.
@zal-to's Omega2 0.1.10 b160 wifi driver buffer overflow - kernel panic (nice post might be true.
Unfortunately I do not have a real solution for this BUG.
Many thanks for your tests and comments.
I created a network with SSID 하이네켄인증포어러2.4G and got the same behavior.
I think that the last build solve this.
Now I'm running LEDE on my board.