furkan | hi, i'm just trying to test a regression before submitting a bug report for 3.19.0-12, but i can't seem to download 3.19.0-10 any longer via apt-get - any advice? | 00:59 |
---|---|---|
furkan | the problem is basically that dpms no longer works - it still works on mainline 4.0 rc7, and it used to work on the vivid 3.19 kernel, so it's definitely an update that broke it, but i just don't know which one | 01:00 |
furkan | on 4.0 rc7 it also stops working after suspend/resume, which is how it was originally with vivid's 3.19, but now it doesn't work at all, even after a fresh boot | 01:01 |
tmpRAOF | furkan: You can get it from launchpad directly. | 02:03 |
=== tmpRAOF is now known as RAOF | ||
RAOF | furkan: Start at https://launchpad.net/ubuntu/vivid/+source/linux and work through the “releases in ubuntu” links. | 02:04 |
=== gerald is now known as Guest91177 | ||
furkan | thanks RAOF i'll work through those when i get the chance | 02:23 |
=== tmpRAOF is now known as RAOF | ||
rtg | henrix, what are those CVE numbers so I can get them in the commit log ? | 13:18 |
henrix | rtg: CVE-2015-2666: f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4; CVE-2015-2922: 6fd99094de2b83d1d4c8457f2c83483b2828e75a | 13:18 |
rtg | henrix, thanks | 13:18 |
henrix | rtg: i can also give you the bug # in a min... | 13:19 |
henrix | for CVE-2015-2922: bug #1441103 | 13:19 |
ubot5 | bug 1441103 in linux-manta (Ubuntu Vivid) "CVE-2015-2922" [Medium,New] https://launchpad.net/bugs/1441103 | 13:19 |
henrix | and bug #1438504 | 13:20 |
ubot5 | bug 1438504 in linux-manta (Ubuntu Vivid) "CVE-2015-2666" [Medium,New] https://launchpad.net/bugs/1438504 | 13:20 |
rtg | henrix, done | 13:22 |
henrix | rtg: cool, thanks | 13:22 |
=== bladernr` is now known as bladernr_ | ||
mssbrg | Hi, I'm doing some testing with thunderbolt on a 14.10 machine, kernel 3.17.8 and I'm experiencing some odd behavior. When I connect my machine to a thunderbolt display, the display works, however there is no thunderbolt driver loaded. Any help? | 18:44 |
mssbrg | I'm really just curious how this is happening | 18:44 |
apw | mssbrg, well the display is probabally exposed using another driver, and the bus itself is builtin | 18:45 |
apw | so you don't necessarily expect to see a driver for the bus enumerator | 18:45 |
mssbrg | i would expect to see `thunderbolt` in lsmod, no? | 18:46 |
mjg59 | No | 18:48 |
mjg59 | Unless it's an Apple | 18:48 |
mssbrg | this is all apple hardware | 18:48 |
mjg59 | And also still no unless you're running 3.19 | 18:49 |
mssbrg | apw: also, i don't really follow what you mean by display exposed using another driver/bus is builtin | 18:49 |
mssbrg | mjg59: why is that? | 18:50 |
mjg59 | mssbrg: The Thunderbolt hardware isn't exposed to the OS until we start pretending to be Darwin | 18:50 |
mjg59 | The hardware itself will handle the displayport layering setup | 18:51 |
mssbrg | by hardware, do you mean the intel thunderbolt controller? then what kind of interface is exported to the OS? | 18:52 |
mjg59 | It just looks like Displayport to the OS | 18:56 |
mssbrg | mjg59: so if I upgrade to 3.19 can I expect to see a thunderbolt driver? | 19:00 |
mjg59 | mssbrg: Yes | 19:06 |
mssbrg | mjg59: also, should I currently expect to see a displayport driver in lsmod? | 19:08 |
mjg59 | No | 19:08 |
mjg59 | That's handled by the individual graphics drivers and the drm core | 19:08 |
mssbrg | ah interesting. but there is /some/ driver in lsmod I should see that is handling the display, right? | 19:10 |
mjg59 | Yeah, either nouveau or i915 | 19:10 |
mssbrg | ok cool, i see i915 | 19:10 |
mssbrg | mjg59: and so in 3.19, I would potentially see thunderbolt instead of i915? | 19:12 |
mjg59 | mssbrg: No, as well as | 19:13 |
mjg59 | The thunderbolt driver handles the PCIe hotplug part of Thunderbolt (on Apple - on other systems it's managed by the firmware) | 19:13 |
mssbrg | ah ok | 19:15 |
mssbrg | unrelated, but are there logs for this channel anywhere? | 19:16 |
mssbrg | mjg59: out of curiousity, if I plugged in a non-display thunderbolt device would things be different? still no thunderbolt driver in lsmod? | 19:28 |
mjg59 | On that kernel? Yeah, and also it wouldn't work. | 19:28 |
mssbrg | oh. i thought 3.17 was the first to support thunderbolt | 19:29 |
apw | mssbrg, yes this is logged, erm | 19:30 |
mjg59 | mssbrg: Kind of | 19:31 |
mssbrg | apw: are they available? I don't see a url in the topic. | 19:31 |
mjg59 | It'll work if there's a Thunderbolt device plugged in at boot | 19:31 |
mjg59 | And it'll stop working if you suspend | 19:31 |
apw | http://irclogs.ubuntu.com/2015/04/08/%23ubuntu-kernel.html | 19:31 |
apw | mssbrg, ^ they are logged in the same place as "all" ubuntu channels | 19:32 |
mssbrg | apw: ty | 19:32 |
mssbrg | mjg59: so if I understand correctly, the driver itself only implements the low level pcie communications, and the actual functionality of whatever device is always implemented by another driver? | 19:34 |
mjg59 | Yes | 19:34 |
=== apw changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues April 14th, 2015 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! If the question is should I file a bug for something, likely you can assume yes. || Channel logs: http://irclogs.ubuntu.com/ | ||
mssbrg | mjg59: hm, still no thunderbolt driver in lsmod in 3.19. hotplug also doesn't work, even with it manually loaded in. any thoughts? | 20:09 |
mjg59 | mssbrg: Huh. That surprises me. I'm afraid I don't have time to look at it right now, though | 20:09 |
mssbrg | No problem! Any recommendations on anything to try on my own? Either way, thanks for all the help! | 20:11 |
=== kamal_ is now known as Guest43595 | ||
RAOF | Oh, that's right. Attempting to restart this box will hang because btrfs has blown up. | 23:19 |
RAOF | Damn you, cking, for asking me to test that! :) | 23:21 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!