File corruption? Or memory corruption?
Posted Dec 21, 2006 10:55 UTC (Thu) by rankincj
Parent article: A gnarly 2.6.19 file corruption bug
My 126.96.36.199 kernel tripped up when all I was doing was compiling xine-lib with gcc-4.1.1. Yes, I was compiling on an ext3 filesystem. No, I wasn't using BitTorrent.
See bug 7707 in Bugzilla: "Eeek! page_mapcount(page) went negative! (-1)"
to post comments)