Comment # 2 on bug 1206948 from 1st last

What do you refer to by "type-C"?

> Does the problem still persist with the latest 6.1.x kernel?

Since the issue occurred first to me on the 6.1.3-lp153.4.1.g2e19141.x86_64
kernel, which was the last 6.1.3 I got, I can only let you know if it will
persist on the 6.1.4-lp153.2.1.g4b9b43c.x86_64 kernel, which I received by
update today, but which did not cause the same issue yet.

For me the problem is, that I don't understand from the log what might have
been causing the Oops. Do you have a more specific idea?