Please do not subscribe that team, the team's own description explicitly asks you not to.
This bug clearly is nothing to do with userspace, it should not be possible for userspace to cause problems in this way (that's what the kernel is there for). It smells like a kernel driver bug to me, especially given the reports of fiddling with DMA. The high number of similar SSDs mean it could be a hardware company being creative with the spec, but that's still a kernel driver bug for failing to quirk them properly. I'm not a kernel developer, but I would recommend the following debugging technique: - those affected should supply detailed information about not only their SSD, but the I/O controller in their laptop (dmesg, lcpci -vvnn, etc.) - if one release of Ubuntu is affected more than the other, that suggests a regression - first try a mainline kernel build from http://kernel.ubuntu.com /~kernel-ppa/mainline/ of the equivalent release; if that fixes the problem (unlikely, but still possible), then it is with an Ubuntu patch - if that does not fix the problem, start working backwards through the kernel releases until you find one that does fix the problem - if the first kernel is still affected, try kernels from previous Ubuntu releases (one assumes that the kernel from the release where things work fine, installed on karmic, will work) - Given a loose idea, narrow it down using the kernel packages you can download from https://launchpad.net/ubuntu/+source/linux/+publishinghistory Basically what would be ideal would be to find one kernel that works, and then the *immediate next kernel* that doesn't work. This would give a limited number of changes that broke it, and start to reveal what the bug might be -- SSD stall during boot https://bugs.launchpad.net/bugs/445852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
