(In reply to Ralf Corsepius from comment #29)
> Yeah! Petr, I own you a beer!
>
> In my case, this definitely is Linux Kernel 43191.
>
> Googling around for this bug has led me to find passing "ss_en=0" to
> the ums_realtek kernel module
> works-around (fixes ?) this issue.
>
> E.g. Add a file
> /etc/modprobe.d/ums-realtek.conf
> with this contents:
> options ums_realtek ss_en=0
Ralph, thanks for the excellent comment. Any news on the success (or not) of using ss_en=0?
Anybody, if I see these messages and am without ss_en=0, does this just result in log noise or does it cause ill behavior besides?
I'm getting these messages, but on stateless deployments that boot from a SD card so I can't really test without a respin.
(In reply to Ralf Corsepius from comment #29) d/ums-realtek. conf
> Yeah! Petr, I own you a beer!
>
> In my case, this definitely is Linux Kernel 43191.
>
> Googling around for this bug has led me to find passing "ss_en=0" to
> the ums_realtek kernel module
> works-around (fixes ?) this issue.
>
> E.g. Add a file
> /etc/modprobe.
> with this contents:
> options ums_realtek ss_en=0
Ralph, thanks for the excellent comment. Any news on the success (or not) of using ss_en=0?
Anybody, if I see these messages and am without ss_en=0, does this just result in log noise or does it cause ill behavior besides?
I'm getting these messages, but on stateless deployments that boot from a SD card so I can't really test without a respin.