http://bugzilla.opensuse.org/show_bug.cgi?id=966631
http://bugzilla.opensuse.org/show_bug.cgi?id=966631#c9
--- Comment #9 from Borislav Petkov
I updated my firmware less than two months ago when I bought the machine.
That "BIOS" revision is still listed as current on the Gigabyte web site.
http://www.gigabyte.com.au/products/product-page.aspx?pid=5471#bios
The date is actually 2015-08-17 according to the above page.
So the BIOS says 05/13/2015 but the website has 2015/08/17 and yet the
version is the same. See what I mean with a stinking pile?!
--- Comment #10 from Borislav Petkov
It's worse than that, I'm actually running 4.4.0-3-default because of another bug I'm trying to diagnose. (964621)
That other bug is talking about suspend/resume and suspend/resume can be one of the reasons for that memory corruption. As the memory corruption option suggests, you could try booting with memmap=. Judging by the error message, that's always 0x8000 physical address, i.e., 32K. You could try to mark the first 64K as reserved by booting with memmap=64K$0 so that the kernel doesn't scribble over it. HTH. -- You are receiving this mail because: You are on the CC list for the bug.