-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu Core Kernel Panics on Intel NUC: BUG: unable to handle page fault for address #3174
Comments
Could you please open a bug on launchpad against the linux package, this requires the kernel team to look at it ... |
@ogra1 I've noticed quite a few open bugs of this nature on Launchpad with no resolution. I'm happy to file another bug mentioning this specific hardware, but can you advise where best to file the bug in order to get it noticed? Edit: Do you mean here? https://bugs.launchpad.net/ubuntu/+source/linux
|
Note: I don't think this is actually a WebThings Gateway bug, it's an issue with Ubuntu Core. I'm filing it here for now because I don't yet have an upstream issue to track.
I'm testing WebThings Gateway on an Intel NUC 11. Specifically the NUC 11 CMCR1ABA i3 (Austin Beach rugged chassis + Elk Bay compute module). I don't think this particular version of the Intel NUC is officially certified by Canonical, but it does run Ubuntu Core (ubuntu-core-22-amd64.img).
However, I've recently noticed that when I leave it running for long periods of time (e.g. overnight) Ubuntu Core freezes with what I think is a memory-related kernel panic.
I've attached screenshots (sorry for the photos but because the machine freezes it's difficult for me to capture the text) of two separate occasions when this happened, with slightly different errors:
My first thought was that it could be a hardware problem, but at least on a first pass memtest hasn't found any faults, see attached screenshot. (Update: No failures after 12 passes).
I've seen quite a few open bugs of this nature on Launchpad with no resolution so I've contacted Canonical for support.
The text was updated successfully, but these errors were encountered: