Why is my syslog filling up with 'wakeup int at ci_hdrc.1' 'ci_hdrc ci_hdrc.1: at ci_controller_resume' 'ci_hdrc ci_hdrc.1: at ci_runtime_suspend' ?

2015-09-06 Thread Rick Thomas
Hey folks! Yesterday I rebooted my Cubox-i4Pro running Debian Sid, and ever afterwards my /var/log/syslog file is filling up with endless repetitions of > Sep 6 06:25:30 cube kernel: [26889.599129] wakeup int at ci_hdrc.1 > Sep 6 06:25:30 cube kernel: [26889.599147] ci_hdrc ci_hdrc.1: at > ci

Re: I/O issues with writing to mtdblock devices on kirkwood

2015-09-06 Thread Ian Campbell
On Sat, 2015-09-05 at 23:08 +0200, Andrew Lunn wrote: > On Fri, Aug 21, 2015 at 01:24:17PM +0100, Ian Campbell wrote: > > Hi kirkwood-upstream, > > > > We (Debian) have had a couple of reports of I/O errors running > Debian > > on kirkwood, specifically it seems to relate to later kernels (e.g. >

Re: flash-kernel puts QNAP on its knees

2015-09-06 Thread Ian Campbell
On Sun, 2015-09-06 at 13:02 +0200, Rob J. Epping wrote: > Hi, > > On 08/21/2015 02:11 PM, Ian Campbell wrote: > > On Sun, 2015-08-09 at 09:39 +0200, JM wrote: > >> > >> This is just a hunch, but perhaps a part of the problem is because > >> flash-kernel simply cats the image to mtdblock, which is

Re: flash-kernel puts QNAP on its knees

2015-09-06 Thread Rob J. Epping
Hi, On 08/21/2015 02:11 PM, Ian Campbell wrote: On Sun, 2015-08-09 at 09:39 +0200, JM wrote: This is just a hunch, but perhaps a part of the problem is because flash-kernel simply cats the image to mtdblock, which is not the recommended way to deal with flash storage [1]. I'm afraid I disagr