[22:02] <chrss> should i be worried about this? https://bpaste.net/show/aa9f79587a2f
[22:07] <apw> chrss, that is just telling you your bios is broken
[22:16] <chrss> does that mean danger? my system can hang at any moment?
[22:16] <chrss> i'm just trying to get sense of the potential severity
[22:17] <chrss> like, if i was driving in a car and it said "your airbags aren't going to work" i'd be a little worried
[22:17] <chrss> but if i was driving and it said "your brakes aren't going to work" i'd be REALLY worried
[22:35] <mjg59> chrss: It means you're not going to have a working iommu
[22:35] <mjg59> Which, unless you're doing hardware passthrough in virtualisation, is basically not important
[22:35] <chrss> i don't know what "hardware passthrough in virtualization" means
[22:35] <chrss> so you're probably right
[22:37] <chrss> i seem to be affected by this bug: https://bugzilla.kernel.org/show_bug.cgi?id=86231
[22:37] <chrss> but i can't seem to figure out which ubuntu kernel i can install that has the fix
[22:39] <chrss> accordign to that bug report, the fix went into that tree on Nov 3
[22:39] <chrss> i don't know when it was accepted into mainline
[22:40] <chrss> but i don't see any utopic kernels that recent anyway: http://kernel.ubuntu.com/~kernel-ppa/mainline/
[23:40] <chrss> is it possible the fix was put into vivid kernels but not utopic kernels on purpose?
[23:40] <chrss> based on the nature of the bug, i can't see why it would be