[04:56] <BinnyHill> How is it that a kernel module that was not there priorly just appears on a system?
[07:35] <infinity> zequence_: You around?
[09:06] <infinity> zequence_: Will pay big money for you to quickly smoketest your kernels from the last cycle.
[09:15] <slangasek> apw: bug #1324028
[14:04] <bullgard4> Is there a difference between »kernel configuration option« and »kernel command line option«?
[14:45] <apw> bullgard4, yes ... "kernel configuration option" == CONFIG_FOO type options which are options we set when we build a kernel from source; a kernel command line option is something you supply to the kernel on boot and can change on each boot
[15:18] <bullgard4> apw: Ah! Thank you very much for explaining and your help.
[16:39] <lamont> every 2 seconds, I get this on my trusty box:
[16:39] <lamont> May 28 10:33:35 kailan kernel: [503122.916681] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPC_.SMBR] (Node ffff88007c352f28), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[16:39] <lamont> May 28 10:33:35 kailan kernel: [503122.916712] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPC_.INIT] (Node ffff88007c352f00), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[16:39] <lamont> May 28 10:33:35 kailan kernel: [503122.916730] ACPI Error: Method parse/execution failed [\_GPE._L00] (Node ffff88007c34c2d0), AE_AML_INFINITE_LOOP (20131115/psparse-536)
[16:39] <lamont> May 28 10:33:35 kailan kernel: [503122.916750] ACPI Exception: AE_AML_INFINITE_LOOP, while evaluating GPE method [_L00] (20131115/evgpe-580)
[16:40] <lamont> thoughts on how to make it shut up?
[16:40] <mjg59> Are you passing any strange kernel options?
[16:41] <lamont> stock boot, atom 330 on an Intel D945GCLF2D MB
[16:42] <lamont> BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/KAILAN-root ro BOOTIF=01-00-1c-c0-c9-33-a2 quiet splash nomdmonddf nomdmonisw vt.handoff=7
[16:42] <mjg59> Ok
[16:42] <mjg59> I have a vague recollection of this
[16:42] <mjg59> With the conclusion being "This firmware is broken"
[17:01] <TJ-> lamont: see workaround (custom DSDT) https://communities.intel.com/thread/11742?start=0&tstart=0
[17:01] <lamont> TJ ta
[17:02] <lamont> mjg59: somehow, this does not surprise me at all
[17:02] <lamont> the good news is that I'll get incredibly good compression on syslog
[17:02] <lamont> :/
[17:02] <lamont> and lunch.  bbl