[01:35] <aberrant> hi all
[01:36] <sarnold> wb
[01:38] <aberrant> thanks.
[01:38] <aberrant> Does `make bindeb-pkg` make the modules? I don't have any .deb that has the word "modules" in it.
[01:40] <connor_k> Sorry I’m not at my computer right now to confirm but I think maybe the bindeb-pkg target might just roll them all up into the *images*.deb
[01:40] <connor_k> If you run “dpkg -x | grep nvme” the modules might be listed
[01:40] <aberrant> ok, thanks. let me check
[01:41] <aberrant> sorry for being so high-maintenance
[01:41] <connor_k> Wanting to learn something new is hardly high maintenance :-) if anyone tells you that then they’re wrong
[01:42] <connor_k> Er sorry “dpkg -x *image*.deb | grep nvme”
[01:42] <sarnold> I don't see anything else in the make help output that looks like it'd generate modules debs
[01:42] <aberrant> seth@hydrogen:~/kernel$ dpkg -c linux-image-5.3.10+_5.3.10+-1_amd64.deb | grep -i nvme
[01:42] <aberrant> drwxr-xr-x root/root         0 2019-12-16 15:39 ./lib/modules/5.3.10+/kernel/drivers/nvme/
[01:42] <aberrant> drwxr-xr-x root/root         0 2019-12-16 15:39 ./lib/modules/5.3.10+/kernel/drivers/nvme/host/
[01:42] <aberrant> -rw-r--r-- root/root    163713 2019-12-16 15:39 ./lib/modules/5.3.10+/kernel/drivers/nvme/host/nvme-core.ko
[01:42] <aberrant> that's dpkg -c
[01:42] <connor_k> Okay cool, looks like they’re all rolled up into *image*.deb
[01:42] <aberrant> does that mean the modules are loaded?
[01:43] <aberrant> ok
[01:43] <aberrant> is that the right image deb?
[01:43] <aberrant> I don't want dbg, right?
[01:43] <connor_k> I think the *modules*.deb is purely an ubuntu artifact with how the scripts are set up
[01:43] <connor_k> Yes that’s the right deb
[01:43] <aberrant> linux-headers-5.3.10+_5.3.10+-1_amd64.deb    linux-image-5.3.10+_5.3.10+-1_amd64.deb
[01:43] <aberrant> linux-image-5.3.10+-dbg_5.3.10+-1_amd64.deb  linux-libc-dev_5.3.10+-1_amd64.deb
[01:43] <connor_k> Dbg will only be helpful if you want to run that kernel under a debugger 
[01:43] <aberrant> those are my choices
[01:43] <aberrant> second one, I guess.
[01:43] <connor_k> Yeah
[01:44] <aberrant> ok, now a dpkg -i on the HV, right?
[01:44] <aberrant> wish me luck.
[01:44] <connor_k> Good luck!
[01:45] <aberrant> W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu
[01:45] <aberrant> W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
[01:45] <aberrant> I seem to recall having that earlier too
[01:45] <aberrant> so I'm going from 5.3.0 to 5.3.10.
[01:45] <aberrant> will be back after reboot, hopefully. :)
[01:45]  * aberrant waves
[01:47] <connor_k> o/
[01:50] <aberrant> w000000
[01:50] <aberrant> seth@elemental:~$ sudo fstrim -v /
[01:50] <aberrant>  seth@elemental:~$ sudo fstrim -v /
[01:50] <aberrant> damnit, that's not pasting
[01:50] <aberrant> suffice to say it works
[01:51] <aberrant> we need to get this patch into the kernel :)
[01:51] <sarnold> TIL there's a -v to fstrim :)
[01:51] <aberrant>  /: 758.3 GiB (814159003648 bytes) trimmed
[01:51] <aberrant> there
[01:52] <aberrant> I'll update the bug report.
[01:52] <sarnold> hmm which irc client do you have? I thuoght most? all? had paste detection to handle a leading / in a paste correctly
[01:53] <sarnold> that might be worth a bug report for your irc client, heh
[01:53] <connor_k> Nice job aberrant!! 
[01:55] <aberrant> sarnold: I'm using irssi
[01:55] <aberrant> connor_k: I couldn't have done it without you. Thanks so much!
[01:55] <sarnold> hm. now I've got to try.. :)
[01:55] <connor_k> What’s the bug number, aberrant?
[01:55] <aberrant> 1856603
[01:56] <sarnold> # fstrim -v /
[01:56] <sarnold> /: 6.7 GiB (7215800320 bytes) trimmed
[01:57] <sarnold> irssi 0.8.19-1ubuntu1.9 on this machine
[01:58] <aberrant> sarnold: from what I understand the fstrim issue only manifests in certain nvme drives that don't follow the spec precisely.
[01:58] <aberrant> 758.3 GiB trimmed seems like an awful lot though.
[01:59] <sarnold> aberrant: heh, I was more just interested in the / leading char thing, the actual issue you and connor_k are discussing I haven't followed at all, hehe
[01:59] <aberrant> I don't think I've gone past 20% utilization on the drive.
[01:59] <aberrant> hahahaha
[01:59] <connor_k> Cool! I wrote it down and can look at it tomorrow for SRU’ing the patch into the kernel 
[01:59] <sarnold> aberrant: how long has it been since you've done an fstrim on this system? what kind of write churn does it have? do you have the weekly fstrim timers running correctly?
[01:59] <aberrant> CTCP VERSION reply from aberrant: irssi v1.2.1-1ubuntu2
[02:00] <aberrant> sarnold: the machine is less than a week old. I've never done an fstrim on it.
[02:00] <sarnold> 700G trimmed *does* feel like a huge trim if you're getting it done weekly already..
[02:00] <sarnold> sheeeeeesh
[02:00] <aberrant> I set up some vms on it, and transferred a bunch of data.
[02:00] <aberrant> but currently I'm at 19% utilization
[02:01] <aberrant> (1TB)
[02:01] <aberrant> I wonder if the first fstrim on a brand new disk is somehow large. The subsequent one I did was 0 GiB.
[02:01] <aberrant> oh, look
[02:03] <aberrant> that's roughly the size of the total free space
[02:03] <sarnold> yeah, any more and I'd have been very worried :)
[02:03] <aberrant> so maybe it had to do a complete fstrim on the entire free list.
[02:03] <sarnold> it's possible that the 'first' fstrim on the filesystem does have to start from scratch and trim it all, whether or not it'd been used
[02:05] <sarnold> 250ish gigs, though, the average data would only need to be overwritten three times.. between write amplifications on small writes, OS updates on host and guests.. maybe 700-ish gigs of dirtied but no longer needed data isn't crazy for a 250-ish gig used system
[02:05] <sarnold> I shudder to think about eg atime updates on all those bloody files. relatime is a good thing, but even then..
[02:06] <aberrant> I'm mounting relatime
[02:07] <aberrant> let's see what happens next sunday :)
[02:07] <sarnold> :)
[02:07] <aberrant> this channel is fantastic. Thanks for all the support here.
[02:07] <sarnold> hmm does the timer use fstrim -v? or fstrim? or .. just run the ioctls raw?
[02:07] <aberrant> as it turns out I have to RMA my motherboard.
[02:07] <aberrant> it won't take a BIOS update. It's stuck on the penultimate version.
[02:10] <sarnold> here's the logs from three of my machines http://paste.ubuntu.com/p/GGJHQKFDJj/
[02:11] <sarnold> that's frustrating :(
[02:15] <aberrant> yeah, so I confirmed: if I add the trimmed GiB to the used GiB I get exactly the capacity of the disk
[02:15] <aberrant> so the first trim probably trims the entire free space
[02:16] <aberrant> 758.3 + 158
[02:17] <aberrant> well, not *exactly* but close enough for government work
[02:20] <aberrant> ok. That's enough stress for one day. thanks again. Have a great evening, all.
[02:20]  * aberrant waves.
[18:23] <aberrant> morning all :)
[18:24] <aberrant> after that patch everything is wonderful.
[20:34] <tharrrk> hi there. may i have a question regd. mainline kernels here or is there a better channel to ask?
[20:36] <sarnold> this may be fine, but there's also a #kernelnewbies on irc.oftc.net that's more about kernel programming. maybe ask and see what happens :)
[20:37] <tharrrk> cool thanks
[20:42] <tharrrk> so, all builds on kernel.ubuntu.com/~kernel-ppa/mainline/ from v5.3.7 failed for i386. Is that intentional? I mean, i386 is kind of dead these days but if there is a build recipe i think it should either build successfully or it should go away... If there's something i could help with..?
[20:49] <sarnold> heh that's indeed one that wouldn't be useful for #kernelnewbies :)
[20:51] <tharrrk> :)