Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
John Hasler wrote: Confirmed. I had forgotten to look in there. But this is a workaround rather than a bug identification and fix isn't it? Yes, it's just a workaround. Well, thanks anyway. I guess that we don't even know if the problem is with chronyd or with alsa or something more generic around the rtc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
I guess that we don't even know if the problem is with chronyd or with alsa or something more generic around the rtc. I'm thinking that it is a kernel bug, but it will still probably be necessary to fix it in either Chrony or Alsa. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
Edit /etc/chrony/chrony.conf and comment out the line rtcfile /var/lib/chrony/chrony.rtc This should allow Chrony to operate without interfering with your Midi stuff. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
John Hasler wrote: Edit /etc/chrony/chrony.conf and comment out the line rtcfile /var/lib/chrony/chrony.rtc This should allow Chrony to operate without interfering with your Midi stuff. Confirmed. I had forgotten to look in there. But this is a workaround rather than a bug identification and fix isn't it? I don't mean to sound ungrateful :-) A E Lawrence -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
Confirmed. I had forgotten to look in there. But this is a workaround rather than a bug identification and fix isn't it? Yes, it's just a workaround. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
I forgot to ask if there was anything interesting in the Chrony logs. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400499: timer.c patch from alsa bugtracking #0001645 does not change the situation.
I have applied the timer.c patch https://bugtrack.alsa-project.org/alsa-bug/file_download.php?file_id=963type=bug from https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1645 to a 2.6.18.3 kernel. The situation is exactly as before. aplaymidi blocked and chronyd showing high CPU usage as reported by top. The comments by TimMann about his patch looked very plausible and I wonder if there are not several race conditions lurking in the alsa drivers. Perhaps another is ultimately responsible for this problem? For the moment, at least. I am out of ideas of what more I can do to help given my limited familiarity with the kernel, alsa and chrony. Of course, I am happy to try out any suggestions or explore further with gdb if that would help. A E Lawrence -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
