Linus Torvalds writes: (Summary) Pretty much by
definition compiler bugs tend to be about rare situations, so it's
some odd special case that triggers.
some odd special case that triggers.
Since it's apparently fairly repeatable for you, a bisection between 4.13.8 and 4.13.11 would be very interesting, and shouldn't take all that long. And even a full bisection should only take something like 8 build/test cycles.
something like 8 build/test cycles.
Arnd pointed to some commits that might be relevant for the cp210x module, but those are all already in 4.13.8, so if 4.13.8 really is rock solid for you, I don't think that's it.
rock solid for you, I don't think that's it.
I really don't see anything that looks even half-way suspicious in that 4.13.8..11 range.
some odd special case that triggers.
Since it's apparently fairly repeatable for you, a bisection between 4.13.8 and 4.13.11 would be very interesting, and shouldn't take all that long. And even a full bisection should only take something like 8 build/test cycles.
something like 8 build/test cycles.
Arnd pointed to some commits that might be relevant for the cp210x module, but those are all already in 4.13.8, so if 4.13.8 really is rock solid for you, I don't think that's it.
rock solid for you, I don't think that's it.
I really don't see anything that looks even half-way suspicious in that 4.13.8..11 range.