[02:34] <cyphermox> any reason we don't have CONFIG_JFS_DEBUG set? the doc says "very little overhead" :)
[06:10] <apw> cyphermox: debug stuff is mostly off unless someone asks for it, with a good use case. especially as they are rarely free
[09:10] <tseliot> apw: hey, what git branch shall I use to get a patch into the kernel of 16.04.3?
[09:16] <apw> tseliot, that had the linux-hwe kernel in it, which is 4.10 derived, which is zesty base, so againts zesty/master-next if its a code change
[09:17] <tseliot> apw: and will that also get the patches into the xenial 4.10 kernel too automatically?
[09:18] <apw> tseliot, yes, that is a direct backport
[09:19] <tseliot> apw: ok, then I will have to send the patches to the mailing list and tag them as [zesty] , right?
[09:21] <apw> SRU zesty yeah
[09:21] <tseliot> ok, thanks
[12:31] <apoz> Hi all
[12:31] <apoz> I’m having some problem with a kernel error in syslog for some IPv6 packets (ICMPv6)
[12:31] <apoz> what would be the best way to have some support?
[12:32] <apoz> (I just posted a question in launchpad for the moment)
[12:39] <apw> apoz, if you have a kernel trace then filing a bug against the kernel (ubuntu-bug linux) and attaching that is a good start
[12:39] <apw> then drop the bug number in here
[12:39] <apoz> ok, I’ll try that
[12:40] <apoz> a trace with systemtap is ok?
[12:40] <apoz> or I should try to get something else?
[12:41] <apw> apoz, i mean if you are getting a kernel message in dmesg
[12:41] <apw> not a "make a trace" the kernel message dump is often called a kernel trace
[12:41] <apoz> ok, I’ll include all the info I’ve got already in the bug
[12:50] <apoz> I just filled the bug with all the info I’ve got in Bug #1711124
[12:50] <apoz> thanks!
[20:19] <apw> tjaalton, hey ... my touchpad seems to (as of today) a very small bottom click area ... if my finger is on the touchpad more than a few mm the other finder can no longer move the cursor ... mean anyting to you ?
[20:20] <apw> (lenovo x250)
[20:43] <apw> tjaalton, ahh ok ... removng xserver-xorg-input-synaptics sorted it ...
[21:03] <tjaalton> apw: yeah we've essentially migrated to -libinput by now
[21:04] <tjaalton> synaptics could have issues