=== JanC is now known as Guest86327 === JanC_ is now known as JanC [08:56] apw, we got probably the virtualbox kernel issue [08:57] >I haven't taken a look at the in-kernel version, but in RC1 the reason [08:57] >was that the arguments to out*() calls got swapped: the Linux kernel [08:57] >reverses them compared to everyone else I know of, and I failed to do [08:57] >that during clean-up to match kernel style. Will be committing soon. [08:57] LocutusOfBorg, wonderful [08:58] when will we have updated packages for that to take form ? [08:58] from ? [09:10] I already asked for a patch [09:11] but if you have time, you can swap the parameters inside that outw call and see what happens [09:11] after re-enabling it [09:17] sforshee, ^^ [12:15] LocutusOfBorg: I grepped the vboxguest code in our kernel tree, I only found out* being used in one file (include/VBox/VBoxVideoGuest.h). The arguments are reversed, but best I can tell they aren't compiled in, looks like ASMOutU* is called instead, for example [12:15] #ifdef VBOX_XPDM_MINIPORT [12:15] VideoPortWritePortUchar((PUCHAR)Port, Value); [12:15] #elif defined VBOX_GUESTR3XORGMOD [12:15] outb(Port, Value); [12:15] #else /** @todo make these explicit */ [12:15] ASMOutU8(Port, Value); [12:15] #endif [12:16] what's the problem with vbox? [12:16] sforshee: btw, when will next artful kernel be tagged? [12:16] tjaalton: look at the code I pasted, the arguments to outb are reversed [12:17] tjaalton: not sure, in theory the current artful-release kernel would be what we release with, so after release [12:18] but if we have any critical bugs we may do another before then [12:18] there was some wifi bug that the new stable release fixed [12:19] 4.13.5? [12:19] sforshee, I don't know honestly... I'll wait for the next vbox beta, and then see if at least vbox is fixed [12:19] in the meanwhile I hope somebody fixes the kernel too [12:20] LocutusOfBorg: are you talking about the vboxvideo staging driver? [12:20] I had to disable that in our kernel because it was causing problems [12:21] sforshee, yes, I'm talking about it [12:21] but the current vbox beta has the same trouble [12:21] because the kernel driver has been merged back into vbox code [12:21] sforshee: yep, 255432ecc6cbaf4 mac80211: fix deadlock in driver-managed RX BA session start [12:21] so, they "copied" the issue [12:22] and one issue discovered in vbox was that out* stuff [12:22] maybe this is not enough, I don't know [12:23] LocutusOfBorg: okay. Thanks for the heads up, let us know when you have more information. But wrt to the mainline driver we won't have issues because it is disabled. [12:23] maybe that is why we had problems [12:23] sure I know it is disabled [12:23] and the driver in 5.1.28 is working [12:23] fact is: the mainline driver is broken [12:24] vbox 5.2 beta2 was still ok [12:24] in 5.2 rc1 they merged the mainline into vbox again, and they broke vbox bundled driver too [12:24] they discovered such "swap" out function error, so maybe this is the problem in the kernel too [12:24] tjaalton: how bad is that bug? Will it prevent users from installing or from updating after they install? [12:24] this is what I know, the next RC of vbox 5.2 will have a "fixed" driver [12:25] so I'll do some more testing and then see what the mainline kernel driver misses, and maybe we can re-enable it [12:25] sforshee: "Can't switch wireless connection between several WiFi APs" [12:25] so not too bad I guess [12:26] tjaalton: yeah from that description at least sounds like something that could be fixed after release [16:10] from the linux-firmware changelog (artful) it should include the latest iwlwifi firmware - but the files differ [16:10] http://pastebin.ubuntu.com/25721005/ [16:28] my mistake! nvm === cachio is now known as cachio_afk === cachio_afk is now known as cachio