[01:21] <krakrjak> I'm wanting to test out some kernel patches I'm authoring and I can't seem to get a build. My patches are not applied yet, I updated the debian/changelog and now can't get a build.
[01:22] <krakrjak> I think this has to do with using the linux-signed package. Any pointers?
[01:40] <bjf> krakrjak, have you looked at: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[01:55] <krakrjak> bjf: yes, that's what I was following. It says to update the debian/changlog to inclue a +test1 version so I won't get confused when I install the patched version.
[01:56] <krakrjak> When I do that I get KeyError: 'linux-libc-dev: package version not found'
[01:57] <bjf> krakrjak, show me what "head -1 debian.master/changelog" looks like
[01:58] <bjf> krakrjak, which sries are you building? i assume bionic
[02:00] <krakrjak> bjf: I am building bionic, using the apt method not the git method.
[02:03] <krakrjak> bjf: here are the two changelog entries that matter, mine at the top and the extant one below it https://paste.ubuntu.com/p/M5TdMRdRVN/
[02:06] <bjf> krakrjak, yes, it's the change to linux-image that it's not pointing at the signed package that is making it impossible for those instructions
[02:07] <bjf> krakrjak, the best thing is to use the git method
[02:09] <krakrjak> bjf: ok, will try that.
[02:12] <krakrjak> bjf: does the apt method work then? what would it still be good for if you can't do local version bumps? just curious
[02:12] <bjf> krakrjak, looks like you can also try "apt-get source linux-image-unsigned-$(uname -r)"
[02:15] <krakrjak> bjf: worth a shot. I'll try that too :) thanks for the tip!
[02:18] <bjf> krakrjak, with the git method you can easily get to your current version, past versions and possibly the next version. you use git tags to build the one you want.
[02:19] <krakrjak> bjf: yeah, it's just super heavy on disk for the small patch I want to test. starting with the packaged version is much better for me to play with in this situation.
[02:20] <krakrjak> bjf: I'll have to do the git method eventually anyway, I just wanted to start playing with the code right away to see if I'm no the right track and I'm still at 2% cloning while I can get a test build before that even completes.
[02:24] <bjf> krakrjak, you can also play with --depth with git. that doesn't grab quite so much
[02:31] <krakrjak> bjf: In the end it will be fine. I do want the whole git tree...
[02:35] <krakrjak> bjf: Thank you for your help, I'm able to apply my patches and build the linux-image-unsigned packages with the proper version bump. I'll test with that for a bit.
[02:35] <krakrjak> What do I need to do to get code upstreamed if I do get something going well? In particular I'm extending the caiaq usb sound driver.
[02:36] <krakrjak> Any pointers on what to do to play nicely with the process would be really helpful.
[02:38] <bjf> krakrjak, you want to subscribe to the linux kernel mailing list (kernel.org)
[02:39] <bjf> krakrjak, and then probably start googing for "how to contribute to the linux kernel"
[02:44] <krakrjak> bjf: I'm trying to find the team that is responsible for this driver and I'm coming up empty... If you have any suggestions I'll take them, but if not I'll just keep digging.
[02:49] <krakrjak> thanks again for all your help! I'm well on my way :)
[03:16] <bjf> krakrjak, look in the MAINTAINERS file in the root of the kernel sources
[03:58] <krakrjak> bjf: thank you. I will poke through that in more detail.
[04:12] <krakrjak> so I build a kernel with an updated changelog entry, but it didn't seem to add my +test1 version to the deb packages. Am I editing the wrong file?
[04:15] <krakrjak> is it right to edit the debian/changelog or debian.master/changelog when using the linux-image-unsigned binary package?
[18:26] <lokus> hi- (u16.04.4) i installed kernel 4.15.0-13-generic, and had a kernel crash which produced a vmcore for me in /var/crash. i installed package linux-image-4.15.0-13-generic-dbgsym to be able to go through the kernel dump, but crash utility is telling me this when i go to view it: "crash: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic and vmcore.201805251123 do not match!" <--- how could 
[18:26] <lokus> this be?
[18:45] <cascardo> what's the output of file vmcore.201805251123 ?
[18:48] <lokus> vmcore.201805251422: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style
[18:49] <lokus> turns out i had 4.15.0-13.14 and not 4.15.0-13.14~16.04.1 for dbgsym, to match my kernel. i found the right matching dbgsym and i no longer get that mismatch error.  instead in its place i get 'crash: cannot resolve "init_level4_pgt"' . i'll keep googling
[18:50] <lokus> ah looks like i just need crash 7.2.
[18:50] <cascardo> don't you have a dump file?
[18:51] <cascardo> if you are running xenial, you certaily need a newer crash
[18:51] <lokus> yes i have a dump file. see vmcore.201805251422 output above
[18:51] <cascardo> the one from bionic should work
[18:51] <lokus> thanks
[18:52] <cascardo> there is a backport in ppa:cascardo/kdump2
[18:53] <lokus> nice, i'm in business :) thank you
[18:54] <cascardo> you are welcome
[18:54] <cascardo> so, you don't have a compressed dump because you were using an old makedumpfile
[18:54] <cascardo> the one in that ppa should help with that as well
[18:54] <cascardo> let me know if you find any problem with those tools
[18:55] <lokus> cheers.
[18:55] <cascardo> I hope those packages hit xenial-proposed next week