-
Notifications
You must be signed in to change notification settings - Fork 12
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
Benign unexpected system failure #12
Comments
Someone reported something similar before and it was due to multiple dmesg traces. One was due to an outdated MrChomebox firmware (yours is not), another from a wifi bug that was fixed in the upstream kernel since, and possibly a third I am familiar with, but I've been disabling the module in the kernel. dmesg output would probably help. |
#5 for additional reference. |
That's not pixelbook specific. Something to do with btrfs (As mentioned elsewhere I tend to stick with xfs as a personal choice). See: There are reports for this going back to at least 2019. |
Recent BZ where someone hit it https://bugzilla.redhat.com/show_bug.cgi?id=1996507 |
Here it's mentioned it's usually not a real bug; also not sure it's btrfs specific even though it showed up on the ntrfs list. See some traces mentioning xfs. |
https://yhbt.net/lore/all/CAJCQCtRrAoNtukFev8-zTHOcEYzTzxtp9ENRLkKPH4_mB882Yw@mail.gmail.com/t/
|
i can see that sine this is not a bug related to this project, i'll close it |
I really appreciate your work here, and its been extremely enjoyable using my pixelbook again! |
Glad to hear you are enjoying it. I like the Pixelbook hardware a lot. It's a good light system for most stuff, and being able to run a standard Linux distribution makes it superb. Hopefully my git and copr repos are a short term requirement and everything makes it upstream in the right places. |
Is anyone else getting a message from the "Problem Reporting" app that shows a "system failure"?
Here is what i am getting, with a bug saying "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!" does this have to do with a kernel config setting somewhere making the LOCKDEP values too low?
the details of the bug backtrace has the following snippet
The text was updated successfully, but these errors were encountered: