[alsa-devel] interesting message, but not sure where its coming from
![](https://secure.gravatar.com/avatar/761adae65a0dbc8459689f3ac4301f9e.jpg?s=120&d=mm&r=g)
I'm working on a complicated program that uses the ALSA library in an embedded environment. I have things working pretty well, although occasionally I get the following message printed on the console:
buffer empty, loop_cnt 4727, loop_cnt_of_last_copy 4682, last period elapsed 4700, elapsed flag 0, chip_data->prev_cnt F000
buffer empty, loop_cnt 4758, loop_cnt_of_last_copy 4727, last period elapsed 4700, elapsed flag 0, chip_data->prev_cnt F000
I know this isn't my code, and I can't find anything that looks like this in the alsa library or the kernel. Does anybody recognize this?
![](https://secure.gravatar.com/avatar/5b19e9d0e834ea10ef75803718ad564b.jpg?s=120&d=mm&r=g)
At Wed, 19 Dec 2007 12:47:50 -0500, Christopher Johnson wrote:
I'm working on a complicated program that uses the ALSA library in an embedded environment. I have things working pretty well, although occasionally I get the following message printed on the console:
buffer empty, loop_cnt 4727, loop_cnt_of_last_copy 4682, last period elapsed 4700, elapsed flag 0, chip_data->prev_cnt F000
buffer empty, loop_cnt 4758, loop_cnt_of_last_copy 4727, last period elapsed 4700, elapsed flag 0, chip_data->prev_cnt F000
I know this isn't my code, and I can't find anything that looks like this in the alsa library or the kernel. Does anybody recognize this?
Looks like a debug message of your driver. At least these message aren't in the upstream codes.
Takashi
participants (2)
-
Christopher Johnson
-
Takashi Iwai