On Sun, 2014-10-12 at 23:46 +0200, Svenska wrote: > > If you were able to try 3.16-1~exp1[0] > > from snapshot.debian.org that might help rule that out. > > I downloaded linux-image-3.16-trunk-kirkwood_3.16-1~exp1_armel.deb from > your link and flashed it into the NAS. I have not done a deeper > analysis, but it looks like the problem is gone. > > For now, I will revert back to the known-working 3.14-2 (3.14.15-2) > anyway, but if you want me to test another binary image, I could do that > if given a week or two. > > Hope this helps.
Thanks, it narrows it down to a change on the Debian side rather than a generic 3.16 upgrade breakage. Looking at the changelog the most plausible looking candidate is still the enabling of CONFIG_HIGHMEM. Your system has far less RAM than I would expect to need highmem though. If you are comfortable building a kernel for yourself (see [0] for details) then it might be interesting to try rebuilding without CONFIG_HIGHMEM. Ian. [0] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
