[08:51] <apw> tjaalton, i am seeing some graphics corruption in firefox in the last few kernels ... looks a bit like the sort of mushing of "active" areas what we saw when we had fence issues before
[08:54] <apw> Kano (N,BFTL) dailies should now be fixed
[09:10] <tjaalton> apw: what's your gpu?
[09:12] <apw> Intel Corporation Broadwell-U Integrated Graphics [8086:1616]
[09:12] <apw> tjaalton, ^
[09:13] <tjaalton> I got a ping about https://lists.freedesktop.org/archives/intel-gfx/2016-April/092300.html
[09:13] <tjaalton> yesterday
[09:13] <tjaalton> you could try that, though I believe it's probably caused by the x driver
[09:13] <apw> well that is a believeable description ...
[15:52] <rbasak> Minor mistake in https://wiki.ubuntu.com/Kernel/LTSEnablementStack: In the 14.04.x Ubuntu Kernel Support Schedule diagram, it says 15.04 against Wily, not 15.10.
[15:53] <apw> ogasawara, ^
[15:53] <ogasawara> rbasak: ah, thanks, I'll fix that up
[15:54] <rbasak> np. It confused me for a bit until I figured it out, so thought I'd mention it.
[15:54] <ogasawara> I'll add 16.04 related diagrams while I'm at it
[15:55] <rbasak> They are really helpful diagrams BTW, so thanks :)
[19:01] <lamont> jsalisbury: am I stuck running a forked kernel?  bug 1543683
[19:01] <ubot5`> bug 1543683 in linux (Ubuntu Xenial) "Fails to detect (second) display" [Medium,In progress] https://launchpad.net/bugs/1543683
[19:04] <jsalisbury> lamont, you won't be forever.  We're still waiting for an update from upstream on how to proceed.  I'll ping em again.
[19:05] <lamont> jsalisbury: ack
[19:06] <lamont> jsalisbury: in the meantime, it sounds like I want xenial/current with 237ed86c reverted, yes? or do I need to also revert the partial fix, too?
[19:06] <lamont> Apr 13 13:06:07 tigernut kernel: [165764.303718]  [<ffffffff81711fe8>] netdev_rx_csum_fault+0x38/0x40
[19:07] <jsalisbury> lamont, yes,  xenial/current with 237ed86c reverted
[19:07] <lamont> is there any way to tell with any degree of accuracy (understanding that bit rot is a real thing there) what mac the bad packet came from?
[19:07] <lamont> (topic changed, of course)
[19:07] <jsalisbury> hmm, I'm not sure off hand
[19:08] <lamont> awk '{print $5}' /var/log/syslog | sed 's/\[.*$//' | sort | uniq -c | sort -nr | head
[19:08] <lamont>   57590 kernel:
[19:08] <lamont>    2668 lldpd
[19:08] <lamont> because the kernel is totally winning
[19:08] <lamont>    1468 snmpd
[19:09] <lamont> and yes, there's undoubtedly crap wire involved in this fine vintage building
[19:09]  * lamont is playing cable monkey this weekend, and would love to have a target or two to attack
[23:41] <ehegnes> Does anybody know how to generate a kernel source package with a .changes or .dsc file?