Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: Is this reproducible? If so, what specific steps should we take to recreate this bug? Is this only on resume (after suspend-to-ram or suspend-to-disk)? How does your BIOS identify itself (mark and version)?
According to: http://lkml.indiana.edu/hypermail/linux/kernel/0808.3/1869.html this check was added to check for BIOS corruption, but I am unsure how much abnormal it is on a resume. Just a note about an other bug with similar warning: https://bugs.launchpad.net/bugs/350192 ** Changed in: linux (Ubuntu) Status: New => Incomplete -- WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:719 check_for_bios_corruption+0xdd/0xe0() https://bugs.launchpad.net/bugs/350704 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
