LocutusOfBorghello folks, can you please sponsor the fix for bionic/cosmic? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 ? anything we should do to have it?09:17
ubot5`Ubuntu bug 1798921 in linux (Ubuntu Cosmic) "sky2 ethernet card don't work after returning from suspension" [Undecided,New]09:17
=== cpaelzer__ is now known as cpaelzer
socratisHello everyone, slight problem with my Mint 19 (based on 18.04) and its sleep-wake-NoNetwork problem. Two Marvell 88E8053 with the "sky2" driver, both lose their network with a "Network cable disconnected".09:53
socratisI found this workaround script that works great (https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend) but it seems to me that it's a bug.09:53
socratisAnd then I found the exact bug for the exact "sky2" driver: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/179892109:53
ubot5`Ubuntu bug 1798921 in linux (Ubuntu Cosmic) "sky2 ethernet card don't work after returning from suspension" [Undecided,New]09:54
socratisNow, since the Linux world is something far in the past for me, that I took a renewed interest upon, and since I'm on Mint but all the fingers point to Ubuntu, how does one handle this? What am I supposed to do? Create a new Mint ticket? Tag along the existing Ubuntu one? 09:55
socratisTicket 1798921 talks about the issue being fixed a week ago, on 2019-04-02, but it's only available on kernel 4.4.0-145.171. What's the norm in these situations? Do the changes/fixes propagate? Should I just stick with the workaround script and forget about the whole thing?09:57
socratisTIA for any thoughts/comments on this...09:57
LocutusOfBorghello folks, can you please sponsor the fix for bionic/cosmic? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 ? anything we should do to have it?09:58
ubot5`Ubuntu bug 1798921 in linux (Ubuntu Cosmic) "sky2 ethernet card don't work after returning from suspension" [Undecided,New]09:58
LocutusOfBorgsocratis, I asked this before your join09:59
socratisAh, thanks LocutusOfBorg!!!09:59
socratisIt needs a ... sponsor? Like the Olympics? MasterCard and Heineken? :D09:59
socratisGenerally speaking, if I find an issue with the kernel, should I be talking to the Mint people or the Ubuntu people? Do the Ubuntu people "hate" the Mint people/distro? ;)10:00
LocutusOfBorgarighi, ^^ maybe you are the best person to answer this... can you consider adding that one-line patch on next bionic/cosmic update?10:01
LocutusOfBorgsocratis, the kernel should be the same, so "we" are the best people to ask10:01
socratisExcellent! Nice to know...10:02
LocutusOfBorgsmb, since you fixed it on trusty... may I ask why you didn't forward the patch to bionic, cosmic and disco?10:05
socratisFunny you should mention that "nickname", I'm trying to solve a read-only SaMBa share issue! :D10:06
socratisOh, and since I have your attention, and since this is the Ubuntu channel, and since we've known each other for a long time from the #vbox channel...10:07
socratisLocutusOfBorg: Did you get any reports from people that couldn't install VirtualBox 6.0.x on Ubuntu 16.04 LTS?10:07
socratisJust since yesterday, I've had 3 reports already!10:08
socratis(methinks I should double-post in #vbox or #vbox-dev just to be safe...)10:08
LocutusOfBorgsocratis, lets move on vbox10:11
socratisOkie dokie...10:11
smbLocutusOfBorg, if you talk about the sky2 bug, that was xenial. And as to why not port to newer releases, it seems nobody reminded us (in the sense of having the issue with those kernels) and there was just too many other things going on10:13
socratisI do! Put me on the list smb... ;)10:14
LocutusOfBorgsmb, I see disco is already ok, so it should be a matter of bionic and cosmic, if you can add it to the patch queue...10:15
socratisI'm simply a n00b in this and I didn't even know whether I should first talk to the Mint people (Mint19 here), the Ubuntu people or the kernel people...10:15
smbLocutusOfBorg, I had already added nominations for those to the bug report. We will see whether this would be an easy pick. socratis you probably can help by adding a comment about having this on bionic/cosmic10:18
socratisOkie dokie... On it. I have to register, right? (of course...)10:18
apwsocratis, is how we control spam indeed10:20
socratisI know... ;)10:24
smbsocratis, ok, looks like simple pick and I sent it to our mailing list (the sky2 patch). So it should make it at some point10:51
socratisExcellent! Thanks smb...10:51
TJ-Is there a known issue with linux-headers-hwe-lowlatency-18.04-edge from bionic-proposed, via linux-headers-5.0.0-8-lowlatency, which is preventing DKMS module builds due to missing symlink targets. E.g. "lrwxrwxrwx 1 root root 39 Mar 19 21:22 /usr/src/linux-headers-5.0.0-8-lowlatency/block -> ../linux-hwe-edge-headers-5.0.0-8/block" ? apt-file search does not find the target path and I cannot find it12:11
TJ-in a .postinst script either 12:11
=== chrisccoulson_ is now known as chrisccoulson
smbsince edge is now coming from disco... sforshee, cascardo ^?13:44
=== ddstreet_away is now known as ddstreet
cascardoI will look at that soonish13:55
sforsheeTJ-, cascardo: I just downloaded and extracted linux-headers-5.0.0-8-lowlatency_5.0.0-8.9~18.04.1_amd64.deb and the symlink is there13:57
TJ-sforshee: hmmm! let me check what's installed again13:58
TJ-sforshee: whih package do you see the target path (/usr/src/linux-hwe-edge-headers-5.0.0-8/block) being installed/created from ? I can't see it here with the same package installed (Installed: 5.0.0-8.9~18.04.1) 14:05
sforsheeTJ-: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/16519051/+files/linux-headers-5.0.0-8-lowlatency_5.0.0-8.9~18.04.1_amd64.deb14:05
sforsheeI just downloaded and extracted it, I did not install it14:06
TJ-sforshee: I don't see the path in the data.tar.gz of that package14:07
sforshee$ wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/16519051/+files/linux-headers-5.0.0-8-lowlatency_5.0.0-8.9~18.04.1_amd64.deb14:11
sforshee$ dpkg-db -R linux-headers-5.0.0-8-lowlatency_5.0.0-8.9~18.04.1_amd64.deb ext14:11
sforshee$ ls -l ext/usr/src/linux-headers-5.0.0-8-lowlatency/block14:11
sforsheelrwxrwxrwx 1 sforshee sforshee 39 Mar 19 16:22 ext/usr/src/linux-headers-5.0.0-8-lowlatency/block -> ../linux-hwe-edge-headers-5.0.0-8/block14:11
sforsheeTJ-: ^14:11
sforsheetypo, s/dpkg-db/dpkg-deb/14:11
TJ-I got that one :D14:12
TJ-as in, the typo14:12
sforsheefunny thing is that it was a copy/paste, so I have no idea where it went14:18
TJ-sforshee: Sometihng weird going on, I replicated your commands and there is no ./usr/src/linux-hwe-edge-headers-5.0.0-8/ created14:21
TJ-sforshee: in case there is some confusion here, the sym-links are there, the *target* is missing14:21
sforsheeTJ-: ok, I misunderstood I thought you said the symlink was missing14:22
TJ-sforshee: no, target of the symlinks are all 'dead', and I can't find which package is supposed to install to /usr/src/linux-hwe-edge-headers-5.0.0-8/ 14:22
sforsheeTJ-: yeah that does look like a problem, I'd expect those headers to come from linux-headers-5.0.0-8 but that also produces symlinks14:28
sforsheecascardo: ^14:28
TJ-phew! not me going lala!14:28
TJ-It knocked out wireguard else I wouldn't have noticed, which was unexpected since there is no problem with the mainline 5.0 builds and the OS had switched on last reboot14:29
sforsheeit should have been caught in testing, but it looks like adt has never run for that kernel for some reason14:32
cascardoyeah, so I will look at the problem there, and probably have it fixed on a 5.0.0-9 upload14:32
sforsheecascardo: or -10, I built a -9 in bootstrap but there's an apparmor regression that needs fixing so I don't plan to put that into -proposed14:33
sforsheecascardo: for the main kernel that is, I didn't build an hwe-edge kernel14:35
cascardosforshee: ack, will work on the fixes, and wait for a -10 before rebasing14:35
cascardosforshee: I will drop snapdragon altogether from main and meta package14:36
sforsheecascardo: hmm now that brings up a problem, I guess we've had hwe/hwe-edge packages for snapdragon but will not have them moving forward14:37
sforsheeapw: ^ any suggestions on how to handle that?14:37
apwsforshee, keep building them in the -hwe ?14:40
cascardofor the main package, I don't think that's an easy thing to do14:40
sforsheeapw: even if we don't expect they will work?14:40
cascardoduring rebase for 5.1, I had to drop them all, lots of snapdragon patches causing build failures14:41
apwhmmm, are you intending to break them14:41
sforsheewe dropped support for snapdragon from the main kernel branch and are using a topic branch now14:41
apwwe might need to ask pp for a 5.1 version14:41
apwor whatever hwe is14:41
cascardoand we will have double the work?14:41
sforsheewhatever we had for 5.0 was never confirmed to work, afaik14:41
cascardomaybe we could have the hwe meta package point to the generic arm64 one14:42
apwcascardo, that is at an older version no ?14:42
cascardothough that would likely not work, or have lots of "bugs"14:42
sforsheeI think he means the generic arm64 5.0 kernel14:42
apwwe signed up for double the work when we split it out ...14:43
cascardootherwise, just keep them at an older version, ie, do not provide a new meta package14:43
apwthat effectivly abandons them without cves14:43
apwwe will have a 5.1 and so on linux-snapdragon, right ?14:44
sforsheeI'm assuming we will14:44
cascardoI don't disagree. but if we love those snapdragon hwe users so much, we will take not only double the work, but risk regressions for other users of the master kernel14:44
cascardoapw: would you suggest we provide yet another repo for a snapdragon-hwe?14:45
sforsheeit's sounding to me like we'll have to start producing linux-snapdragon-hwe packages14:45
cascardobased on disco/linux-snapdragon, for example?14:45
apwcascardo, i am struggling to see how we can avoid doig something, if we supported snapdragon in an hwe kernel14:45
sforsheetoo bad we just didn't support it14:45
apwwe may be able to leave them on this version and not roll them, but it is this version we are breaking14:46
apwits a problem indeed, if we had never had hwe version of it, we would be better off14:47
apwsforshee, you could look at the anonuncement to see if we ever said we supported it on snapdragon14:47
apwsforshee, whetner we might expect anyone to be using it14:47
sforsheeapw: which announcement would that be? I do wonder whether anyone uses it at all14:48
apwsforshee, that is the worry, that you have to do it, and it is never used14:48
sforsheeapw: I'm just wondering where we would have announced it. In the release notes for one of the point releases maybe?14:49
apwsforshee, yeah it would be the point release announcement i guess14:50
apwsforshee, that is the only place i can imagine it could have been listed14:50
sforsheeapw: it's all your fault - bug 1798352 ;-)14:51
ubot5`bug 1798352 in linux-meta-snapdragon (Ubuntu Cosmic) "linux-snapdragon: missing meta packages for this flavour" [Critical,Fix released] https://launchpad.net/bugs/179835214:51
apwsforshee, i am sure i didn't do that off my own bat; i imagine i was doing it because someone noticed14:51
sforsheeapw: yeah and it wasn't just for -hwe. That bug was mentioned here - https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/ChangeSummary/18.04.214:52
sforsheethat's the closes I've found to us announcing anything14:52
apwsforshee, yeah that was an adam request iirc14:53
cascardoright now, 5.0 will work just fine with snapdragon, we haven't dropped patches yet14:59
cascardoso, we could just leave them as it is, until we get to later kernels, like 5.115:00
sforsheecascardo: I did drop the patches. We could reapply them, but I had already had to drop some because of conflicts. Afaik the support we had in the 5.0 master kernel was never tested at all15:12
sforsheeeven if we dodged the issue that way for 5.0 we have to solve it later15:14
cascardoyeah, so we'd better just have that linux-snapdragon-hwe instead of reapplying them. if there are conflicts, it's not worth fixing them15:18
=== Orphis_ is now known as Orphis
=== SimonNL is now known as SimonNL_Afk
cascardoTJ-: found the cause for the missing files on the headers package, will fix it on the next upload17:32
cascardoapw: so, I will follow up with dropping the snapdragon flavour from the bionic/hwe-edge kernel, we'll have to sort it out some other way17:33
TJ-cascardo: great news :)17:33
=== tdaitx_ is now known as tdaitx

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!