Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by osivertsson on Saturday August 05, 2017 @06:09PM
(#14938188)
This particular call trace looks surprisingly well-formed to be a random segfault caused by a bad CPU.
My shallow guess is that this warning is caused by the btusb module trying to load a firmware file while the kernel disallows this because suspend/resume is in progress or something like that. Take a look at the referenced drivers/base/firmware_class.c:1225 in your 4.13.0-0.rc3.git1.2.fc27.x86_64 sources for more details. I think this looks like a normal software bug in the Linux kernel.
You are running bleeding edge hardware and software and that has always been a bumpy ride. I would expect the software to mature as your hardware grows old...
My shallow guess is that this warning is caused by the btusb module trying to load a firmware file while the kernel disallows this because suspend/resume is in progress or something like that. Take a look at the referenced drivers/base/firmware_class.c:1225 in your 4.13.0-0.rc3.git1.2.fc27.x86_64 sources for more details. I think this looks like a normal software bug in the Linux kernel.
You are running bleeding edge hardware and software and that has always been a bumpy ride. I would expect the software to mature as your hardware grows old...