"It looks like a problem occurred" message on nearly every login #5
Comments
|
I have not experienced this. Can you tell me more about where you are seeing it? Is it being reported by abrt or something? We can try to get to the bottom of it. It's possible there is something wrong with the kernel options I have set up even though I tried to emulate the default Fedora config for the most part. |
|
And can you let me know which kernel you currently have. |
|
The current one available in your Copr repo (I literally did the install this week. I think it was 5.14 or 5.15) |
|
Here's a video: https://photos.app.goo.gl/CpzLPbSB8HkMkkcP6 |
|
Thanks. Looks like it's abrt for something about the kernel. I'll look further tonight. Have enough to at least try to reproduce it and dig further if I can... |
|
Let me know if fyou need to me try something -- it'll take me a few hours to do though, since I've restored my Ubuntu installation in the meantime (so I can continue using it -- I can just restore the Fedora install to test anything you need me to) |
|
I'm not able to reproduce this. the output from dmesg might be helpful if you can reproduce it. |
|
dmesg log attached. |
|
I see two things: This is filed here and doesn't seem Pixelbook specific. I've commented that I am also seeing it at the bottom already. I also see the last line: I wonder if you stop using Chrome if the issue (and perhaps your sound errors will go away? I use Chromium on occasion, but not Chrome. I do use Chromium with audio and haven't noticed an issue. Are you using Spotify via Flatpak or something else? I saw your video demoing the audio issue and that is... odd. |
|
Actually I do see another, And from this I note the BIOS you're uing is pretty old: Mine is: Can you see if updating the BIOS gets rid of your problems? |
|
Yeah, I had to downgrade the BIOS because for some reason, the left hand USB-C wouldn't send an HDMI signal, while the right hand one did (I use two screens in the office), after downgrading the BIOS, the dual-screen worked. That's why I haven't upgraded since then. Let me check if the downgraded BIOS is still available as a backup. If it is, I'll try upgrading. |
|
You could probably file an issue on the Chromebox git repos for the HDMI issue if it persists in the newest version. It would be interesting to know if this and your audio issues go away with the update as well. Might be 2 steps forward, 1 step back... |
|
FWIW HDMI works from the left port for me with this version. |
|
Does it work when you plug two screens in (one on each side)? |
|
I flashed the latest version on MrChromebox's site, I still get the Kernel error (and the audio issue in #6 still occurs New dmesg output: You'll see the BIOS now reports:
|
|
In response to an earlier comment -- it's not just Google Chrome. Chromium and Bitwarden have the same "audio cut out" problem. But Firefox doesn't for some reason. I did wipe the entire Google Chrome cache/config folder to reset its state as test and that didn't help (that's why the Google Chrome in the video demo was default) |
|
It looks like there is a two line patch for the wireless trace. It should be easy to apply. I'll build a kernel and see if I can get rid of that and see if that gets rid of the oops for you. That's all I see in your secIond dmesg output unless I'm just missing it. |
|
There's a new kernel up. I no longer see the trace for wifi with it. Can you see if it improves this? |
|
Just so I'm sure, I just need to use `sudo dnf upgrade` to update the
kernel, right?
…On Sat, 4 Dec 2021 at 19:07, Jason Montleon ***@***.***> wrote:
There's a new kernel up. I no longer see the trace for wifi with it. Can
you see if it improves this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVA5O3TKQLWKMFQONQWZJ3UPJRIZANCNFSM5JDYWC7A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
|
|
|
|
Upgraded the kernel and so far the error has not appeared. The audio issue still remains, however. |
|
Cool. Let's consider this issue solved and use the other one for the audio issue. I'll do some reading and see if I can come up with some ideas to try. |
|
This error occurs when you copy all firmware files from chromeos to fedora.. |
|
When you say all, do you mean everything in the directory, not just the select audio firmwares? If so I'm not surprised. As far as I know there are ranges of at least some kernels and firmwares that line up so copying from a system with a drastically kernel version might not work. That would be good information here though as another point for folks to check if they encounter this. |
|
You are totally correct! If you copy the entire /lib/firmware from chromeos to fedora, this error occurs. If you keep strict to the files you mentioned this problem does not occur. Best solution is to remove the entire directory, reinstall linux-firmware and copy only the dsp/tplg files you mentioned or are copied by ansible. I have not identified which firmware files are causing this error... just remove directory and reinstall. the quickest and cleanest! |
|
I am mistaken! I checked all files, but think the cause is the driver skl_sst. Have updated alsa-libs , alsa etc and I think kernel. And crash... This message that is spammed in dmesg has been resolved in a commit by Chromium Googe. Maybe it has slipped again into it. |
|
I would hazard a guess they did not work on pushing any fixes upstream. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just found this repo and tried it on my Pixelbook (Eve)
The setup so far is no problem. I installed the copr repo and did
dnf update. The kernels got replaced and now, nearly every reboot and login, the auto reporting tool gives a notification saying a component failed -- and points at the pixelbook custom kernel. It doesn't allow me to report the problem, obviously.Should I be concerned about the error?
The text was updated successfully, but these errors were encountered: