Will do that once the scrub finishes/I get home from work. On Wed, Dec 2, 2015 at 7:30 AM, Austin S Hemmelgarn <ahferroin7@xxxxxxxxx> wrote: > On 2015-12-01 15:12, Gareth Pye wrote: >> >> On Wed, Dec 2, 2015 at 2:14 AM, Duncan <1i5t5.duncan@xxxxxxx> wrote: >>> >>> So if you're running into the same problem gentoo's live-git build did, >>> it's likely because you're building the devel branch cloned from >>> kernel.org, which is no longer updated. >> >> >> >> Woah, kernel.org is making a log that looks like it's up to date but >> isn't that's awkward :( >> >> Building now from the github you mentioned. >> >> Also running a scrub, but I'm starting to suspect something else is >> responsible. It ran fine overnight but crashed in less than a minute >> after I logged back in on ssh this morning . . . >> > Hmm, the fact that it's intermittent is the most concerning part IMHO. It > means it's a lot harder to track down. If your hard drives aren't any > noisier than normal (most traditional hard disks get noticeably noisier when > they're failing), then I'd suggest running something like memtest86+ for at > least a full cycle with default options to verify if your RAM is working > correctly. Usually, when I see intermittent crashes like this it's either a > race condition in software somewhere, or bad RAM, and it's a lot easier to > test for bad RAM than it is to test for race conditions. > -- Gareth Pye - blog.cerberos.id.au Level 2 MTG Judge, Melbourne, Australia "Dear God, I would like to file a bug report" -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
