Ok, I tracked DPLBASE and posbuf before and after suspend/resume and they look pretty similar. In both cases, the lowest bit of DPLBASE is set, so it should report back the position. Before: posbuf 0x340, lpibpos 0x294, posbuf=0x1b881020 DPLBASE=0x1b881001 posbuf 0xfe0, lpibpos 0xf40, posbuf=0x1b881020 DPLBASE=0x1b881001 posbuf 0x1fe0, lpibpos 0x1f40, posbuf=0x1b881020 DPLBASE=0x1b881001 and after: posbuf 0x340, lpibpos 0x294, posbuf=0x1b881020 DPLBASE=0x1b881001 posbuf 0x340, lpibpos 0xf40, posbuf=0x1b881020 DPLBASE=0x1b881001 posbuf 0x340, lpibpos 0x1f40, posbuf=0x1b881020 DPLBASE=0x1b881001 (another test showed that DPUBASE remains zero) So the issue remains: how is the re-initialisation different on resume?
** Attachment added: "posbuf-trace-03.txt" http://launchpadlibrarian.net/8414822/posbuf-trace-03.txt -- snd-hda-intel: distorted sound after resume, until the module is reloaded https://bugs.launchpad.net/bugs/100114 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
