[alsa-devel] snd-bebob : from kernel 4.13 to 5.3.19 and .20

Jean-Paul Argudo jpa at argudo.org
Wed Oct 30 09:10:38 CET 2019


Hi there,

I wrote 1st this here: 
https://github.com/takaswie/snd-firewire-improve/issues/25

But I think it was the bad place, sorry for that.

I think this ML is better?

My problem in one line:

I upgraded my Ubuntu Disco (kernel 4.13) to Ubuntu Eoan (kernel 5.3.19)
and I can report my SaffireLE / Firewire doesnt work anymore, snd-bebob reports "discontinuity of CIP" on dmesg...


At startup it lights green ok, but no sound is playable, then the
lights turn orange (like it is when it's not working), I hear a "relay
sound" (a electric clic of a relay), then, the Saffire LE disapears from the sound menu in Ubuntu sound menu.

I can see this in dmesg:

[   19.083583] snd-bebob fw1.0: Detect discontinuity of CIP: 10 50
[   19.746665] snd-bebob fw1.0: Detect discontinuity of CIP: A0 A8
[   19.846775] snd-bebob fw1.0: Detect discontinuity of CIP: 70 B0
[   20.335861] snd-bebob fw1.0: Detect discontinuity of CIP: 90 D0
[   20.856301] snd-bebob fw1.0: Detect discontinuity of CIP: 78 B8
[   21.312770] snd-bebob fw1.0: Detect discontinuity of CIP: 30 70
[   21.796716] snd-bebob fw1.0: Detect discontinuity of CIP: 00 40
[   22.347664] snd-bebob fw1.0: Detect discontinuity of CIP: 00 40
[   22.818247] snd-bebob fw1.0: Detect discontinuity of CIP: A8 E8
[   23.306079] snd-bebob fw1.0: Detect discontinuity of CIP: 98 D8
[   29.544652] snd-bebob fw1.0: Detect discontinuity of CIP: 10 50
[   30.272090] snd-bebob fw1.0: Detect discontinuity of CIP: A8 E8
[   30.776168] snd-bebob fw1.0: Detect discontinuity of CIP: 00 40
[   31.268123] snd-bebob fw1.0: Detect discontinuity of CIP: E0 20
[   31.766085] snd-bebob fw1.0: Detect discontinuity of CIP: E0 20
[   32.267903] snd-bebob fw1.0: Detect discontinuity of CIP: 88 C8
[   32.767989] snd-bebob fw1.0: Detect discontinuity of CIP: F8 38
[   33.263808] snd-bebob fw1.0: Detect discontinuity of CIP: 78 B8
[   33.757156] snd-bebob fw1.0: Detect discontinuity of CIP: 08 48
[   34.258860] snd-bebob fw1.0: Detect discontinuity of CIP: 80 C0
[   34.755571] snd-bebob fw1.0: Detect discontinuity of CIP: 40 80
[   35.261252] snd-bebob fw1.0: Detect discontinuity of CIP: 60 A0
[   35.753980] snd-bebob fw1.0: Detect discontinuity of CIP: 78 B8
[   36.253547] snd-bebob fw1.0: Detect discontinuity of CIP: C0 00
[   36.752500] snd-bebob fw1.0: Detect discontinuity of CIP: 08 48
[   37.255203] snd-bebob fw1.0: Detect discontinuity of CIP: B0 F0
[  277.760550] snd-bebob fw1.0: Detect discontinuity of CIP: 40 80
[  278.488972] snd-bebob fw1.0: Detect discontinuity of CIP: C0 00
[  278.986290] snd-bebob fw1.0: Detect discontinuity of CIP: E0 20
[  279.485998] snd-bebob fw1.0: Detect discontinuity of CIP: 18 58
[  279.983838] snd-bebob fw1.0: Detect discontinuity of CIP: D0 10
[  280.486776] snd-bebob fw1.0: Detect discontinuity of CIP: C0 00
[  280.979487] snd-bebob fw1.0: Detect discontinuity of CIP: 30 70
[  281.480952] snd-bebob fw1.0: Detect discontinuity of CIP: 78 B8
[  281.975413] snd-bebob fw1.0: Detect discontinuity of CIP: 38 78
[  282.475487] snd-bebob fw1.0: Detect discontinuity of CIP: 60 A0
[  282.979446] snd-bebob fw1.0: Detect discontinuity of CIP: 88 C8
[  283.472403] snd-bebob fw1.0: Detect discontinuity of CIP: 88 C8
[  283.968484] snd-bebob fw1.0: Detect discontinuity of CIP: 68 A8
[  284.471585] snd-bebob fw1.0: Detect discontinuity of CIP: 30 70
[  284.562886] usb 3-4.1: reset high-speed USB device number 5 using
xhci_hcd
[  284.965508] snd-bebob fw1.0: Detect discontinuity of CIP: D0 10
[  285.469348] snd-bebob fw1.0: Detect discontinuity of CIP: 68 A8
[  285.965174] snd-bebob fw1.0: Detect discontinuity of CIP: 20 60
[  285.981618] firewire_core 0000:05:01.0: phy config: new root=ffc1,
gap_count=5
[  290.103982] firewire_core 0000:05:01.0: phy config: new root=ffc1,
gap_count=5
I tried update the kernel with eoan-proposed I know run 5.3.20 and I
have the same problem (the trace above is made with 5.3.20.

First, I hope I report this the best way, really not sure here.

If not, please tell me what to bring (files? logs?) and where (on this
list? elsewhere?).

I have spare time to investigate anything that could help here.


Thanks!

-- 
Jean-Paul Argudo




More information about the Alsa-devel mailing list