Comment 11 for bug 268857

Revision history for this message
Tormod Volden (tormodvolden) wrote :

memtest86+ not detecting an error does not prove anything. However, if you can reproduce on another piece of hardware, it would indicate a software problem. Your BIOS counts as your hardware in this situation, unless other people have the same problem. Ubuntu is not going to fix the BIOS of one particular user's PC. You will also spend less of your valuable time if you keep the reports more concise and listen and act to the comments that people give you.

There are no bug reports deleted, they can be found with the search interface, just enable the "Invalid" ones. I doubt your closed reports are "useful". They are not "incorrectly" closed, but closed because there is nothing that can be done about them from the OS side. They don't indicate anything is wrong in the Ubuntu software.

"on correct hardware being unable to verify md5checksums" - you should rather contact your hardware manufacturer, this is probably not correct hardware. Please understand that the BIOS is part of the motherboard and not of the OS.

There is still a slight chance that the kernel doesn't cope with your motherboard/BIOS/memory combination, but then you have to file a bug on the kernel ("linux" package) and provide concise, relevant information. If you have a contract with Canonical maybe they can help you with this.