Please do not presume the required testing was pointless. As per Ubuntu Kernel Team and Ubuntu Bug Control policy, one must test the newest mainline kernel available, and provide the necessary debugging information, to have this marked Triaged, or a state where a developer could begin working on this. For more on this please see https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Bug_Triage .
Ed S, thank you for testing the newest mainline kernel.
Regarding your comments https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/755518/ comments/ 87 :
"Please don't ask for pointless testing..."
Please do not presume the required testing was pointless. As per Ubuntu Kernel Team and Ubuntu Bug Control policy, one must test the newest mainline kernel available, and provide the necessary debugging information, to have this marked Triaged, or a state where a developer could begin working on this. For more on this please see https:/ /wiki.ubuntu. com/KernelTeam/ KernelTeamBugPo licies# Bug_Triage .
Regarding your comments https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/755518/ comments/ 88 , no need exists at this time to provide debugging information not requested of you from the debugging articles previously mentioned, triager, or developer.
Despite this, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ kernel# KernelTeam. 2BAC8-KernelTea mBugPolicies. Overview_ on_Reporting_ Bugs_Upstream ?
Thank you for your understanding.
Marking Triaged as mainline tested and all required debugging information provided.