Yes, I just checked that CONFIG_DMAR is still turned off in the config used for 2.6.32-21. Testing the upstream build is kind of meaningless -- this is not really a kernel bug per se, but rather a problem with the configuration chosen as part of the Ubuntu packaging.
I understand that the message is automated but it would take about half a second to see that it is not appropriate for this bug.
Yes, I just checked that CONFIG_DMAR is still turned off in the config used for 2.6.32-21. Testing the upstream build is kind of meaningless -- this is not really a kernel bug per se, but rather a problem with the configuration chosen as part of the Ubuntu packaging.
I understand that the message is automated but it would take about half a second to see that it is not appropriate for this bug.