/srv/irclogs.ubuntu.com/2015/04/08/#ubuntu-kernel.txt

furkanhi, 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
furkanthe 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 one01:00
furkanon 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 boot01:01
tmpRAOFfurkan: You can get it from launchpad directly.02:03
=== tmpRAOF is now known as RAOF
RAOFfurkan: 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
furkanthanks RAOF i'll work through those when i get the chance02:23
=== tmpRAOF is now known as RAOF
rtghenrix, what are those CVE numbers so I can get them in the commit log ?13:18
henrixrtg: CVE-2015-2666: f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4; CVE-2015-2922: 6fd99094de2b83d1d4c8457f2c83483b2828e75a                                                                 13:18
rtghenrix, thanks13:18
henrixrtg: i can also give you the bug # in a min...13:19
henrixfor CVE-2015-2922: bug #144110313:19
ubot5bug 1441103 in linux-manta (Ubuntu Vivid) "CVE-2015-2922" [Medium,New] https://launchpad.net/bugs/144110313:19
henrixand bug #143850413:20
ubot5bug 1438504 in linux-manta (Ubuntu Vivid) "CVE-2015-2666" [Medium,New] https://launchpad.net/bugs/143850413:20
rtghenrix, done13:22
henrixrtg: cool, thanks13:22
=== bladernr` is now known as bladernr_
mssbrgHi, 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
mssbrgI'm really just curious how this is happening18:44
apwmssbrg, well the display is probabally exposed using another driver, and the bus itself is builtin18:45
apwso you don't necessarily expect to see a driver for the bus enumerator18:45
mssbrgi would expect to see `thunderbolt` in lsmod, no?18:46
mjg59No18:48
mjg59Unless it's an Apple18:48
mssbrgthis is all apple hardware18:48
mjg59And also still no unless you're running 3.1918:49
mssbrgapw: also, i don't really follow what you mean by display exposed using another driver/bus is builtin18:49
mssbrgmjg59: why is that?18:50
mjg59mssbrg: The Thunderbolt hardware isn't exposed to the OS until we start pretending to be Darwin18:50
mjg59The hardware itself will handle the displayport layering setup18:51
mssbrgby hardware, do you mean the intel thunderbolt controller? then what kind of interface is exported to the OS?18:52
mjg59It just looks like Displayport to the OS18:56
mssbrgmjg59: so if I upgrade to 3.19 can I expect to see a thunderbolt driver?19:00
mjg59mssbrg: Yes19:06
mssbrgmjg59: also, should I currently expect to see a displayport driver in lsmod?19:08
mjg59No19:08
mjg59That's handled by the individual graphics drivers and the drm core19:08
mssbrgah interesting. but there is /some/ driver in lsmod I should see that is handling the display, right?19:10
mjg59Yeah, either nouveau or i91519:10
mssbrgok cool, i see i91519:10
mssbrgmjg59: and so in 3.19, I would potentially see thunderbolt instead of i915?19:12
mjg59mssbrg: No, as well as19:13
mjg59The thunderbolt driver handles the PCIe hotplug part of Thunderbolt (on Apple - on other systems it's managed by the firmware)19:13
mssbrgah ok19:15
mssbrgunrelated, but are there logs for this channel anywhere?19:16
mssbrgmjg59: out of curiousity, if I plugged in a non-display thunderbolt device would things be different? still no thunderbolt driver in lsmod?19:28
mjg59On that kernel? Yeah, and also it wouldn't work.19:28
mssbrgoh. i thought 3.17 was the first to support thunderbolt19:29
apwmssbrg, yes this is logged, erm19:30
mjg59mssbrg: Kind of19:31
mssbrgapw: are they available? I don't see a url in the topic.19:31
mjg59It'll work if there's a Thunderbolt device plugged in at boot19:31
mjg59And it'll stop working if you suspend19:31
apwhttp://irclogs.ubuntu.com/2015/04/08/%23ubuntu-kernel.html19:31
apwmssbrg, ^ they are logged in the same place as "all" ubuntu channels19:32
mssbrgapw: ty19:32
mssbrgmjg59: 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
mjg59Yes19: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/
mssbrgmjg59: 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
mjg59mssbrg: Huh. That surprises me. I'm afraid I don't have time to look at it right now, though20:09
mssbrgNo 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
RAOFOh, that's right. Attempting to restart this box will hang because btrfs has blown up.23:19
RAOFDamn 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!