Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-22 Thread poma
On 23.04.2014 02:53, poma wrote: > > This one comes and goes... > > [ cut here ] > WARNING: CPU: 2 PID: 521 at lib/dma-debug.c:593 > debug_dma_assert_idle+0x159/0x1d0() > snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped > cacheline [cln=0x03019000] >

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-22 Thread poma
This one comes and goes... [ cut here ] WARNING: CPU: 2 PID: 521 at lib/dma-debug.c:593 debug_dma_assert_idle+0x159/0x1d0() snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped cacheline [cln=0x03019000] [ cut here ] WARNING: CPU:

Re: zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
Am 22.04.2014 20:34, schrieb Jóhann B. Guðmundsson: > On 04/22/2014 05:31 PM, Reindl Harald wrote: >> why do you need a sub-package? > > To add the files and configuration similar to what you are using. > > Zram does not work out of the box as in it requires manual administrator or > user setu

Re: zram module should not be autoloaded

2014-04-22 Thread Jóhann B. Guðmundsson
On 04/22/2014 05:31 PM, Reindl Harald wrote: why do you need a sub-package? To add the files and configuration similar to what you are using. Zram does not work out of the box as in it requires manual administrator or user setup so there is no point in enabling it by default JBG __

Re: zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
Am 22.04.2014 19:17, schrieb Jóhann B. Guðmundsson: > On 04/22/2014 01:38 PM, Josh Boyer wrote: >> I have a rawhide VM here too, it has nothing related to zram >> configuration, and the module isn't loaded. > > Nor should it be it's going to take us sometime to implement this correctly > into t

Re: zram module should not be autoloaded

2014-04-22 Thread Jóhann B. Guðmundsson
On 04/22/2014 01:38 PM, Josh Boyer wrote: I have a rawhide VM here too, it has nothing related to zram configuration, and the module isn't loaded. Nor should it be it's going to take us sometime to implement this correctly into the distribution and arguably that module should be packaged sep

Re: [PATCH 1/1] Split kernel into kernel-core and kernel-drivers subpackages

2014-04-22 Thread Josh Boyer
On Tue, Apr 1, 2014 at 12:50 PM, Josh Boyer wrote: > This creates kernel-core and kernel-drivers subpackages. The kernel package > remains as a meta-package the requires both of the subpackages. This allows > most installs to continue on as-is with upgrades working. I've had this out for review

Re: zram module should not be autoloaded

2014-04-22 Thread Josh Boyer
On Tue, Apr 22, 2014 at 9:05 AM, Reindl Harald wrote: > Am 22.04.2014 15:00, schrieb Josh Boyer: >> On Tue, Apr 22, 2014 at 8:58 AM, Reindl Harald >> wrote: >>> >>> Am 22.04.2014 14:55, schrieb Josh Boyer: On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald wrote: > interesting, i hav

Re: zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
Am 22.04.2014 15:00, schrieb Josh Boyer: > On Tue, Apr 22, 2014 at 8:58 AM, Reindl Harald wrote: >> >> Am 22.04.2014 14:55, schrieb Josh Boyer: >>> On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald >>> wrote: interesting, i have that behavior on a Rawhide VM with no services except sshd w

Re: zram module should not be autoloaded

2014-04-22 Thread Josh Boyer
On Tue, Apr 22, 2014 at 8:58 AM, Reindl Harald wrote: > > Am 22.04.2014 14:55, schrieb Josh Boyer: >> On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald >> wrote: >>> interesting, i have that behavior on a Rawhide VM >>> with no services except sshd which explains the >>> systemd device-unit from my

Re: zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
Am 22.04.2014 14:55, schrieb Josh Boyer: > On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald wrote: >> interesting, i have that behavior on a Rawhide VM >> with no services except sshd which explains the >> systemd device-unit from my mail some time ago > > Yeah, you answered your own question on t

Re: zram module should not be autoloaded

2014-04-22 Thread Josh Boyer
On Tue, Apr 22, 2014 at 8:46 AM, Reindl Harald wrote: > interesting, i have that behavior on a Rawhide VM > with no services except sshd which explains the > systemd device-unit from my mail some time ago Yeah, you answered your own question on that thread, so I didn't look into it. Reading back

Re: zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
interesting, i have that behavior on a Rawhide VM with no services except sshd which explains the systemd device-unit from my mail some time ago for now blacklist it and load it later with the zram.service works fine [root@buildserver:~]$ cat /etc/modprobe.d/disable-zram.conf blacklist zram -

Re: zram module should not be autoloaded

2014-04-22 Thread Josh Boyer
On Tue, Apr 22, 2014 at 8:25 AM, Reindl Harald wrote: > Hi > > currently you need to remove the zram module > because it's autoloaded in case you want > to use the zram num_devices-param > > maybe it should not be autoloaded implicitly I don't have any machine that has zram autoloaded. There's s

zram module should not be autoloaded

2014-04-22 Thread Reindl Harald
Hi currently you need to remove the zram module because it's autoloaded in case you want to use the zram num_devices-param maybe it should not be autoloaded implicitly /usr/sbin/rmmod zram 2> /dev/null > /dev/null /usr/sbin/modprobe -q zram num_devices=$num_cpus 2> /dev/null > /dev/nul _