Hm.. I didn't see any "I request you to test it" !?
anyway, I cannot test it on edgy kernel, but with my own kernel "iommu=off" doesn't work (see attached dmesg). I guess the reason why no ubuntu user ever reported this bug is because the linux literacy level of an average user of this distro is not very high (and this is a good thing, it means you attract new followers from the "dark side"). People just give up when the system they just installed refuses to boot no metter what.
A more appropriate thing for me would be to submit this bug to kernel.org, but since after a few years since it was first reported on the net it is still not fixed, and based on my own experience of bug-reporting to kernel.org, their back-log time is not even 2 months like here, but tends to infinity.
It is up to you to fix a bug in the kernel (turn off CONFIG_MMC_WBSD). You are not doing me a favour. I already did the hardest part -- diagnosed the problem.
Hm.. I didn't see any "I request you to test it" !?
anyway, I cannot test it on edgy kernel, but with my own kernel "iommu=off" doesn't work (see attached dmesg). I guess the reason why no ubuntu user ever reported this bug is because the linux literacy level of an average user of this distro is not very high (and this is a good thing, it means you attract new followers from the "dark side"). People just give up when the system they just installed refuses to boot no metter what.
A more appropriate thing for me would be to submit this bug to kernel.org, but since after a few years since it was first reported on the net it is still not fixed, and based on my own experience of bug-reporting to kernel.org, their back-log time is not even 2 months like here, but tends to infinity.
It is up to you to fix a bug in the kernel (turn off CONFIG_MMC_WBSD). You are not doing me a favour. I already did the hardest part -- diagnosed the problem.