aconnect occasionally causes kernel oopses
Takashi Iwai
tiwai at suse.de
Mon Aug 2 08:59:53 CEST 2021
On Mon, 02 Aug 2021 08:18:45 +0200,
folkert wrote:
>
> > In which situation?
>
> I was testing something that listens for alsa events and for that I ran
> a continuous loop that did:
>
> while true
> do
> aconnect 128:1 14:0
> aconnect -d 128:1 14:0
> aconnect -d 128:2 128:1
> aconnect 128:2 128:1
> done
>
> I ran 5 instances in parallel.
>
> 14 is midi through
> 128 is rtpmidi
So rtpmidi process keeps running during the loop, that is, it's only
about connection and disconnection, right?
Also, you're listening to an event during that -- but how?
In general when you report a bug, more detailed description about the
test itself would be really helpful. At best, provide a PoC, which
makes the debug much easier. Posting only the stack trace without any
other information is, OTOH, almost pointless. One can't decode the
address for a binary built for a different system easily, either.
thanks,
Takashi
More information about the Alsa-devel
mailing list