Comment 70 for bug 1009312

Hmm... so I've just finished a first set of tests with reverting that commit, and I definitely have results, though they aren't as cut-and-dry as I hoped. When I reverted the commit, there were merge conflicts in:
drivers/acpi/scan.c
drivers/dma/acpi-dma.c

Since I really have no clue how these files work, I used git mergetool to try simple ways of resolving the conflicts. I tried completely reverting both files to the older version and leaving them as they are at the tip of the master branch. In both of those cases, the kernel failed to build, with make throwing an error when it reached the appropriate file, then completely stopping soon after with a [deb-pkg] error. What's interesting is that when I kept acpi/scan.c in its up-to-date form but entirely reverted /dma/acpi-dma.c, the kernel built successfully.

Unfortunately, when I tried testing it, that kernel build froze during boot, and when I logged in with a stable kernel to check the dmesg logs, the bug was still there. I would need to actually take the plunge and spend a while learning how the code works before I could resolve the conflict more precisely. However, I noticed the build process created a debug package this time; is there some debug setting that I could enable that would shed light on anything?