-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Caroline] Instability and dmesg spam from AVS driver on Samsung Chromebook Pro (Caroline) running Fedora 39 #110
Comments
The dmesg spam is normal and it should stop once the audio server fully loads. Not sure about the random lock ups though. Did it only start after running the audio script? |
I ran the audio script right after installing, so I guess I'll have to uninstall/disable to test if AVS is causing the instability. |
You can delete the modprobe config (in |
That does indeed disable AVS. When I re-enabled it, I got a stack trace in Here it is:
I'm not sure if this is related to my as of yet undetermined stability with my Caroline machine, but I figured it was worth investigating since I feel it isn't normal to get a stack trace in |
Maybe I should report this to the AVS repo? I'm guessing this may not be a problem with your scripts.. |
Someone from intel said the stack trace from AVS is normal, for some reason. |
Describe the bug
Fedora 39 randomly locks up, I checked dmesg and AVS is spamming it 10 or 20 times with the same errors. Other than that, AVS works fine, headphone jack works, speakers work, and the internal microphone seems to work (strange since AVS seems to be looking for another DMIC).
Boardname
Caroline
Logs
dmesg snippet:
I wasn't able to get the ChrUltrabook debugging script to work. I suspect it might be because Fedora has CONFIG_IO_STRICT_DEVMEM enabled and something else on top of that that
iomem=relaxed
doesn't disable.I already tried updating to the latest Mr. ChromeBox coreboot.
The text was updated successfully, but these errors were encountered: