Comment 13 for bug 659030
Revision history for this message
| Guillaume Melquiond (guillaume-melquiond) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
No, it didn't help. I'm using 2-channel output (the profile is called "analog stereo duplex").
During the last occurrence of the issue, pulseaudio -k didn't bring back the system in a completely workable state. The system would stop until I had pressed a few keys, then it would work for a short time and stop again. The duration of each work phase must have been short since it took about 5 sleep/wake cycles between the time I pressed ctrl+alt+del and the time the confirmation dialog box finally popped up. Note that it was really my pressing keys that was making the system wake up.
Looking at dmesg output, there are some differences regarding the "HDA Intel" lines between the old and the new kernel. The old kernel was using irq 22 for the device, while the new one is using irq 51. More importantly perhaps, the new driver is associating irq 52 to device 02:00.1 (the graphic card), while the old driver was leaving it untouched.