=== himcesjf_ is now known as him-cesjf
[08:28] <purple1> can 64bit binars run on 32bit with some emulator
[08:30] <smeso> yes, you can use qemu
[08:32] <aaa_> Cannot join #mysql (You are banned).
[08:32] <aaa_> :'(
[08:33] <apw> phil42, what TJ- said, you traid one kind of backporting for another, backporting lots of needed h/w changes against backporting fixes in the life of the release
[08:33] <apw> phil42, generally speaking ubuntu prides itself on having the latest of things in its releases
[08:34] <phil42> idunno,  just seems a longterm kernel would be better for a longterm release
[08:35] <apw> phil42, it we didn't have people supporting the kernel you would be right, but we do
[08:35] <phil42> still...
[08:36] <apw> you can make your own kernel on 4.14 if that makes you happy 
[08:36] <phil42> no, thanks anyway
[08:36] <apw> all they are doing in upstream stable is collecting patches marked for stable
[08:36] <apw> that isn't in and of itself a hugly hard task, yes there are some backports to be done
[08:37] <TJ-> phil42: kernel.org LTS kernels are intended for embedded device manufacturers in the main, so they can easily add security/bug fixes without needing to do major changes, which should feed through to device owners being able to receive security updates
[08:37] <apw> but it is a patch collection process
[08:37] <TJ-> Devices where the hardware isn't changing
[08:37] <apw> and yes, us taking 4.15 is more work for us no doubt about it
[08:37] <TJ-> And where the manufacturer doesn't have kernel developers, just devs who can tweak and package it
[08:37] <apw> but it meets our goals for hardware support
[08:37] <phil42> that's all i'm saying
[08:38] <apw> we are already carrying huge backports for things even in 4.15
[08:38] <apw> and even then the oem people are getting ahead of us
[08:38] <purple1> smeso what is the package name?
[08:39] <apw> but particularly after the meltdown nightmare we have thought hard about it
[08:39] <phil42> they say being a night owl is bad for your health
[08:40] <purple1> how finding the iso with 64bit 14.04 LTS, running the 3.13.0-57-generic kernel.          
[08:40] <purple1> ubuntu has simple beginner webpage
[08:40] <purple1> not sort by kernel version
[08:41] <TJ-> apw: meltdown vis-a-vis backporting to 4.4/4.13 ? 
[08:41] <apw> yeah, getting non-aligned kernels fixed was clearly more work than those in sync
[08:42] <phil42> 3.13.0-57 was near june 19, 2015
[08:42] <apw> though with some wood tapping and crossing of things we won't have anything of that magnitude for a few years
[08:43] <purple1> yeah phil42
[08:43] <purple1> old hardware
[08:43] <purple1> what 64bit cpu I have
[08:43] <purple1> tested on that kernel 
[08:44] <purple1> how finding
[08:44] <TJ-> purple1: via old-releases, see for 14.04.0 (original release) http://old-releases.ubuntu.com/releases/14.04.0/
[08:45] <TJ-> purple1: go up to the parent directory to see *all* release versions
[08:49] <TJ-> apw: are you aware of issues with nouveau ? We're seeing quite a few users in #ubuntu+1 reporting severe problems on some devices, segfault-ing, or "trapped write/read" spam in the thousands, causing failure to boot.
[08:50] <purple1> searched hard for the even older hp factory ubuntu with the mobile internet interface
[08:51] <purple1> the newer versions gloss over rare hardware
[08:54] <purple1> how can tell if it has the same kernel version
[08:54] <purple1> before download near 1gb
[08:56] <phil42> i doubt it does,   the dates don't match
[08:56] <phil42> maybe try it,  it might also work
[08:56] <TJ-> purple1: read the matching .manifest file which lists all included packages and their versions
[08:58] <TJ-> purple1: shows me "linux-image-3.13.0-24-generic 3.13.0-24.46" for  in ubuntu-14.04-desktop-amd64.manifest
[09:55] <purple1> how finding which pack contains iso-hybrid
[09:56] <TJ-> purple1: all ISOs are hybrid images. They are designed to boot in ISO-9960/El Torito, BIOS/MBR, BIOS/GPT, UEFI/MBR UEI/GPT modes
[09:57] <purple1> file says dos mbr
[09:58] <TJ-> purple1: you should move to the #ubuntu channel; this channel is for kernel development issues
[10:13] <apw> TJ-, i have not heard any complaints on nouveau no, i'll ask about
[10:13] <apw> TJ-, any particular series ?
[10:14] <apw> oh is #ubuntu+1 bionic focused
[10:18] <TJ-> apw: it's generally the new beta testers
[10:18] <TJ-> apw: might be something that'll appear more as folks start trying/installing 18.04
[10:19] <TJ-> apw: yes, #ubuntu+1 is for people testing the in-devel version 
[10:19] <TJ-> apw: in some cases it could be due to not having the (restricted) Nvidia firmware blobs
[10:23] <purple1> sounds like bs
[10:23] <purple1> you call that focused?
[10:26] <apw> sforshee, ^ for awareness
[10:26] <apw> who
[13:29] <eyal> Hello! you probably get this asked frequenty, so apologies if this is documented (i have gone through the FAQ/triage texts). Anyway, I have filed a kernel bug report at the end of January, and have seen no indication of anything on it.
[13:30] <eyal> The texts do indicate some automatic script is doing initial triaging... but haven't seen anything of the sort :)
[13:31] <jsalisbury> eyal, what is the bug number?  I'll take a look.
[13:32] <eyal> jsalisbury: bug #1746474. thanks!
[13:32] <ubot5`> bug 1746474 in linux-hwe (Ubuntu) "unregister_netdevice: waiting for eth0 to become free. Usage count = 5" [Undecided,New] https://launchpad.net/bugs/1746474
[13:34] <jsalisbury> eyal, ahh, wasn't on my radar because it was filed against linux-hwe instead of linux.  I"ll build a test kernel with that commit and post it to the bug.
[13:35] <eyal> jsalisbury: cool. thanks. fwiw i filed it using 
[13:36] <eyal> 'ubuntu-bug linux', so you could have more of those :)
[13:36] <jsalisbury> eyal, ok, thanks
[13:57] <tomreyn> -hwe has 200 "new" bug reports