On Sat, 2010-03-06 at 12:41 +0100, Wouter Verhelst wrote: > On Fri, Mar 05, 2010 at 05:41:34PM +0000, Ben Hutchings wrote: > > On Fri, Mar 05, 2010 at 04:51:55PM +0100, Wouter Verhelst wrote: > > [...] > > > ** Tainted: W (512) > > > * Taint on warning. > > [...] > > > > Please send the warning messages. > > Whoa. I hadn't even noticed that. > > [ 0.000000] ------------[ cut here ]------------ > [ 0.000000] WARNING: at /build/buildd-linux-2.6_2.6.32-8-amd64-DCxXqz/linux-2.6-2.6.32/debian/build/source_amd64_none/drivers/pci/dmar.c:616 check_zero_address+0x91/0x19b() > [ 0.000000] Hardware name: HP Compaq 2230s (FU312EA) > [ 0.000000] Your BIOS is broken; DMAR reported at address zero! [...] > Now it is true that around the time when things first got wrong, my BIOS > had been reset due to the battery running out when I was using the > laptop. I had almost forgotten, also because everything seemed to work > fine after the reboot, and didn't connect the dots until just now. > > I'll do a reflash of my BIOS and see whether that fixes things. Will let > you know what the result is. 'Your BIOS is broken' means the BIOS provided has provided an invalid ACPI table. This is likely a bug, not the result of any corruption. So far as I can see the warning is actually harmless; DMAR will simply be disabled. DMAR is a generic name for what Intel calls VT-d. It may be that there is a BIOS option to disable/enable this and enabling it will result in a valid ACPI table. The iwlagn problem is unrelated to this warning. I will forward your report to the linux-wireless list. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less.
Attachment:
signature.asc
Description: This is a digitally signed message part