[03:14] jsalisbury, apw 4.13.0-38-generic #43~lp1745646ThreeRevert fixed the bug === himcesjf_ is now known as him-cesjf [11:59] s10gopal, that's good news. So multiple commits are at fault here. That kernel had 3 reverted, so I have to review them to narrow it down further. I'll post another kereel in a bit. [12:00] jsalisbury, :) it will be fixed on ubuntu 18.04 ? [12:00] s10gopal, eventually. Still more work to do first. [13:53] anyone alive? both hwe-16.04 and -edge are broken for thousands [13:53] ntd: bug report reference? [13:53] and if you publish 18.04 with current kernel you're in for a nasty surprise [13:54] lemme dig em up, red hat/centos went through these issues a while back [13:54] ntd: we're not seeing any reports in #ubuntu+1 or #ubuntu [13:55] it's not like i haven't tried to mention these issues [13:55] i was referred to this channel which has been dead at every visit [13:55] https://bugzilla.redhat.com/show_bug.cgi?id=1549042 [13:55] bugzilla.redhat.com bug 1549042 in xorg-x11-drv-intel "Kernels 4.15.x are not booting on docking" [High,Closed: errata] [13:55] ntd: that's not an Ubuntu bug report [13:56] broad strokes, every => haswell thinkpad user with a dock won't be able to boot [13:56] still applies to your kernel [13:56] and between 4.13.0-37 and -38 networkmanager no longer works for wired interfaces for the same users [13:58] TJ-, they fixed it, you haven't. who can i talk to about this? [14:00] ntd: we need an Ubuntu bug report and the evidence from logs and so forth [14:01] you have a redhat bugreq with three duplicates with logs and such [14:02] and since the system won't boot, how are users supposed to provide relevant logs? [14:07] TJ-, any such system won't boot and there will be no screen output [14:11] ntd: we're already carrying the patch [14:12] as of version? [14:13] it's in master-next [14:14] ok, which version number will this be? current is 4.15.0-13 [14:15] It'll be the next release [14:16] k, thanks [14:17] i saw BB beta2 yday, fixed kernel? [14:24] TJ-, now, for 4.13.0-38 breaking networkmanager for wired NICs? [14:29] !bug | btd [14:29] btd: If you find a bug in Ubuntu or any of its derivatives, please report it using the command « ubuntu-bug » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs. [14:29] oops, typo! [19:22] sforshee: I still don't have upstream sha1s for the apparmor bug fix pull, should I wait a few hours, or pull a patchset together without the upstream shas1 [19:26] jjohansen: are they in a maintainer tree? Even if not we can apply them as sauce though. [19:27] sforshee: yes, and the pull-request is upstream, its just waiting for them to be merged. I know we can do them as sauce, its just nice to have upstream shas [19:28] but it is getting very late [19:28] jjohansen: you can cherry pick them from the maintainer tree and make the provenance say "cherry picked from commit xxx ", we do that quite frequently [19:29] yeah I'll do that [19:29] plenty of examples if you run git log [19:29] will ubuntu-bionic/master-next make it's way to xenial hwe-edge packages? [19:29] TJ-: yes, around the same time it makes it's way into bionic [19:29] so if it's in the current -proposed kernel that should be fairly soon [19:30] if not a bit longer [19:30] sforshee: thanks. That clears up my last check vis-a-vis ntd's 'bug report' earlier today about the docking station 4.15 bug [19:31] TJ-: yeah that one is not in -proposed I think. We'll likely spin a new kernel for -proposed before much longer, with the kernel freeze being tomorrow and all [19:31] iirc the commit is currently at HEAD in master-next, or was a few hours ago [19:31] not anymore, we've shoved a lot of stuff on today [19:31] I start early :) [19:31] the last minute rush before kernel freeze === broder_ is now known as broder === icey_ is now known as icey === zioproto_ is now known as zioproto === aaa_ is now known as aaa__ [22:14] sforshee: sent [22:14] jjohansen: thanks