[10:59] <sacarde> hi
[10:59] <sacarde> https://ubuntuforums.org/showthread.php?t=2342399
[15:31] <sacarde> https://ubuntuforums.org/showthread.php?t=2342399
[16:35] <rtg> tseliot, there is a 4.9-rc5 based kernel in -proposed that you ought to have a look at wrt nvidia
[16:37] <tseliot> rtg: right, thanks for letting me know. I'll have a look at it as soon as I'm done with a high priority oem bug (i.e. very soon)
[16:37] <rtg> tseliot, thanks
[16:55] <sacarde> how can I solve this error building kernel 4.8 : kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
[17:10] <smb> sacarde, you could just simply pick the disable-pie patch from the mainline builds (-> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.8/)
[19:41] <sacarde> smb, thankyou, I folloow your hint
[19:41] <sacarde> now I aply patch, and works
[19:42] <sacarde> thanks
[19:59] <sforshee> tyhicks: could you take a look at bug 1636890? I'm thinking it might be an ecryptfs problem, but I'm not sure.
[19:59] <ubot5`> bug 1636890 in linux (Ubuntu) "invalid file times with overlayroot and encrypted home" [Undecided,Confirmed] https://launchpad.net/bugs/1636890
[20:02] <tyhicks> sforshee: hey - I won't be able to take a look until next week
[20:02] <tyhicks> sforshee: is that ecryptfs mounted on top of overlay mounted on top of ext4?
[20:03] <tyhicks> sforshee: nevermind, I see your breakdown of the mounts in comment #15
[20:11] <sforshee> tyhicks: yeah, it's a weird one. I've been trying to generate the behavior indepentently of overlayroot without success - this doesn't do it: http://paste.ubuntu.com/23492117/
[20:16] <tyhicks> sforshee: bummer, that was going to be my first thing to try
[23:32] <vdavidoff> Hello. Does anyone know what it takes to make a ata_dev_dbg print? I have tried a variety of things and a message I think I should be seeing, I am not. I'm trying to confirm I'm doing the right things to make ata_dev_dbg work before deciding that message just isn't getting triggered.
[23:33] <vdavidoff> I have tried setting the console loglevel to 8 and enabling dyndbg on everything at boot time. Maybe I'm still missing something, though.
[23:34] <vdavidoff> Ultimately I'm trying to determine if a particular device is blacklisted in libata for TRIM in the running kernel. Based on what I think is the right source code, it is, but I'd like to confirm somehow on the running machine.