=== emma_ is now known as emma
=== lifeless_ is now known as lifeless
=== RAOF_ is now known as RAOF
=== fmasi is now known as Guest20935
=== tjaalton_ is now known as tjaalton
=== ivoks_ is now known as ivoks
ppisatimoin world08:07
=== psivaa_ is now known as psivaa
=== lan3y is now known as Laney
=== Laney is now known as Guest1882
=== Guest1882 is now known as Laney
apwmoin moin09:16
ppisatiapw: moin tech lead :)09:16
smbapw, No yawn (and bees)?09:16
* smb feels like lead, too :-P09:18
apwppisati, heh thanks :)09:20
apwsmb, very droll, very droll ... and man i feel like lead more than anything09:20
smbapw, Oh btw, looking at  bug 1244176... (asked already on #ubuntu-devel but not sure it had been noticed) I think the reply there would be that Saucy images won't get re-spun. I have to figure out whether netboot mini-isos are. Otherwise do you have a howto for replacing kernels in isos?10:02
ubot2Launchpad bug 1244176 in linux (Ubuntu Trusty) "Server 13.10 Install Fails with USB Keyboard (Appears to Hang)" [High,Fix released] https://launchpad.net/bugs/124417610:02
=== Guest20935 is now known as fmasi
ppisatismb: well, after all, who is using usb keyboards nowadays?10:04
ppisaticouldn't resist sorry... :P10:04
smbppisati, Just about everyone... :-P But I guess the secret also is whether they are coming in through usb2 or 3... or actually i think there was ehci and ohci for usb1... 10:05
pkernppisati: People that use remote KVMs?10:05
smbYeah those too10:06
smbBut ppisati just "forgot" the sarcasm tags10:06
ppisatii was ironic dude...10:06
pkernI thought you'd argue that everybody installs within virtualization nowadays. :P10:08
smbIt was unfortunately ambiguous. :) But true, I think it was a mix of reporters doing installs on physical hw with the "wrong" usb keyboard type and those doing remote kvm installs. Like I did but just was lucky that the remote just means basement to me and there the machine has a ps2 keyboard... :-P10:11
smbAh, ok, not that it matters much but ohci and uhci where usb1 drivers... So that explains a bit why this was not hurting more people...10:30
apwi assume the simplest work around here is to install raring and upgrade to saucy instead10:31
smbHm, yeah might be some other way... maybe not the most elegant but working10:35
eagles0513875apw: are you around? there was a post to bug #+11:14
eagles0513875bug #96739911:14
ubot2Launchpad bug 967399 in linux (Ubuntu) "[11.10] Elantech trackpoint does not work Lenovo " [High,In progress] https://launchpad.net/bugs/96739911:14
eagles0513875another person was asking if this was going to get pushed to an SRU in terms of the kernel. Nobody else seems to have responded about this patch making it upstream11:15
apweagles0513875, has anyone followed up on the upstream email thread do you know?11:16
eagles0513875apw: nobody that im aware of as nobody filed a comment on that bug11:17
eagles0513875is there an upstream bug filed for this issue?11:17
apweagles0513875, mostly they just use the mailing lists as they 'issue tracker'11:19
eagles0513875im not subscribed there.11:20
eagles0513875can we at least get this backported and then for 14.04 have a push for it to be in mainline11:20
apwi have added some clarification on the position to the bug so everyone knows11:20
eagles0513875apw: thanks :) do you have any reference to what thread it was so i can revivie it or just start another one.11:21
eagles0513875apw: stupid question i cant seem to sign up wiht their mailing list11:22
eagles0513875apw: what list should i subscribe to11:25
apwhttp://www.spinics.net/lists/linux-input/msg26869.html is the list it is on i think11:32
eagles0513875ok apw subscribed there. and will send an email to the mailing list11:35
apweagles0513875, ask avout that specific patch11:36
eagles0513875will do11:36
eagles0513875apw: what is the address to send to the list11:40
apwits on the subscribe page i think11:41
eagles0513875http://vger.kernel.org/vger-lists.html  all im seeing are the links to archives11:42
=== rbasak_ is now known as rbasak
apwlinux-input@vger.kernel.org is the main list send, linux-input-request to join i thiknk13:00
rtgapw, I updated a Lenovo laptop yesterday with 3.13 and it now cannot find the SSD. Stupidly I did not have an alternate version to make sure it really isn't HW failure. I'm checking that out this morning.13:16
rtga different laptop with the same SSD (although larger) works fine.13:17
apwrtg, well that is typical isn't it13:20
smbrtg, If that isn't one of these fastboot ones, you could check whether the ssd at least appears as a boot selection in the bios13:20
rtgsmb, good idea.13:21
apwwhen you say canot find it, who says that?  the kernel13:21
apwif so you know bios and grub found it13:21
rtgyeah, the BIOS finds the drive 'cause grub loads and launches the kernel. it drops to busybox after awhile because it could not mount the rootfs13:22
apwok then not completely gone13:22
smbapw, Typically it would be if it happened when we are traveling13:22
apwdoes dmesg have any indication of the device13:22
smbYeah, better than my state last time13:22
apwsmb, heh yeah13:22
rtgchecking dmesg.13:23
rtghmm, dmesg|grep sd shows nothing13:24
apwwhat version did you have before the update i wonder13:24
rtg3.13.0-13 I think. what is the one I just uploaded ?13:25
rtgthat is the one that isn't booting13:25
smbrtg, anything grepping for ata13:25
apwso i think that is -rc5 -> rc713:25
rtgapw, nothing about ata except false positives.13:26
smbInteresting, so not even found the controller13:27
rtgI'll boot the daily as soon as  its done flashing.13:27
rtgit doesn't help that I left the charger 100 miles away. doh! hopefully I've still got enough battery.13:30
apwrtg, it is one of those days for sure13:30
rtgtuesday is the new monday13:31
smbIt might be a bit far fetched but at some point there was some discussion/patch that partially reverted fiddling with some bus master bit (iirc) when not doing kexec. Not sure but maybe the good old, remove battery and wait a bit trick works here13:32
rtgsmb: can't hurt to try13:34
rtgsmb, no joy on pulling the battery13:40
smbsmb, ok, so at least not that. hm13:40
rtgI'm just reinstalling from the daily first, then I'll get 3.13 on it.13:41
smbDuring the install you could check lspci -vvvnn and see which driver the SATA controller is attached to (I guess ahci)13:43
smbNot that we forgot some vital other driver in the initrd13:44
=== n0u is now known as nou
eagles0513875apw: their mailing list setup is so complex holy cow13:49
eagles0513875apw: how do i send it to the proper list once im subscribed? 13:51
apwlinux-input@vger.kernel.org is the main list send address14:02
=== ricmm|sick is now known as ricmm
rtgsmb, apw: reinstalled from the daily, updated to 3.13-rc7. now everything works. wtf ?14:40
apwrtg, these things are sent to try us and no mistake14:43
apwrtg, oh do you have any dkms packages installed ?14:44
rtgapw, nope, it was pretty much stock14:44
apwrtg, as we have been ignoring abi on these kernels which has been causing me issues14:44
apwrtg, not even for testing?14:44
apwlike vbox or similar14:44
rtgnot on my travel laptop14:44
apwthen it is a mystery indeed14:44
smbrtg, what driver does the disk use (I may have missed it)? I could only think of a case where initrd was misbuild14:58
rtgsmb, checking14:58
rtgsmb, [    2.765203] ata1: SATA max UDMA/133 cmd 0x2148 ctl 0x215c bmdma 0x2060 irq 1915:02
rtg[    4.112147] ata1.01: failed to resume link (SControl 0)15:02
rtg[    4.268151] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)15:02
rtg[    4.268168] ata1.01: SATA link down (SStatus 0 SControl 0)15:02
rtg[    4.327579] ata1.00: ATA-8: TOSHIBA MK5065GSXF, GP006B, max UDMA/10015:02
rtg[    4.327599] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)15:02
rtg[    4.332543] ata1.00: configured for UDMA/10015:02
smbrtg, looking in "lspci -vvvnn" for SATA should yield which module is used15:03
smbor driver15:03
rtgsmb: oops, wrong dmesg. this one is 'ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB0Q, max UDMA/133'. lspci says 'Kernel driver in use: ahci'15:05
smbAh ok ahci then. I would think that one should be built-in15:07
smbhm... ok not. :P15:07
rtgmaybe it was just an initrd problem15:07
infinityIt's been =m for ages.15:08
infinityBut yeah, mismatched initrds or some other wonkiness would make that blow up.15:08
rtgits possible. we've been ignoring ABI changes15:09
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting15:52
jsalisbury## Kernel team meeting in 5 minutes16:56
xnox\o/ 3.13 \o/ 17:16
rtgxnox, its coming. gimme a bit17:16
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues January 14th, 2014 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
xnoxrtg: as soon as it lands, i'd want some config changes to be ported to nexus kernels to match the distro configs ;-) maybe after some user testing / 3.13 landing in release pocket + some time.17:17
rtgdang, forgot the meeting17:17
tseliotrtg: I haven't updated the binary drivers yet, just FYI17:17
rtgtseliot, so you're kinda behind the eight ball17:18
tseliotright :)17:18
rtgtseliot, I imagine it'll take at least another day to propagate through the archive17:19
tseliotrtg: I'll try to finish fixing at least nvidia 331 tomorrow17:20
* ppisati -> EOD17:31
=== davmor2_ is now known as davmor2
=== stgraber_ is now known as stgraber
medberryinfinity, does the raring kernel in precise lose support on January 27th? linux-generic-lts-raring-eol-upgrade?18:32
medberrymetadata in that package shows:18:33
medberrySupported: 18m18:33
_bjfmedberry, no, we support it until 14.04.118:34
medberry_bjf, cool Thanks.18:34
medberryhttps://wiki.ubuntu.com/Kernel/LTSEnablementStack says the same.18:34
=== _bjf is now known as bjf
pkern_bjf: Will there be any overlap for the saucy kernel where saucy and trusty are supported?18:34
bjfpkern, same deal .. the lts-backport-saucy kernel will be supported until 14.04.118:35
pkernbjf: So that's a "no" then.18:35
medberrypkern, .1 comes after the dot nothing18:36
medberryso a bit of overlap18:36
bjfpkern, 14.04.1 is the first point release which is after 14.0418:36
bjfpkern, so yes, there is overlap18:36
pkernSo the trusty stack comes with a 12.04 point release.18:36
pkernHow much later will the first trusty point release be?18:37
bjfpkern, one sec ..18:37
bjfpkern, it's about 3 mo. after the initial release18:38
pkernSo the 12.04.x after 14.04 will come about 1 mo. later and saucy+trusty will be supported together for about 2 then?18:39
pkernJust to get the timeline straight.18:39
pkernBecause the picture on LTS Enablement Stack is different and suggests a hard transition from saucy to trusty.18:39
bjfpkern, 14.04 (april 17)  14.04.1 (around end of aug.)  lts-backport-saucy will end support around end of aug. when 14.04.1 comes out18:41
pkernbjf: Thanks.18:41
bjfpkern, np18:41
pkernOh hm. So no overlap then because it's only then when the trusty kernel hits precise?18:42
pkernBecause August is also the line on that picture.18:42
bjfpkern, the lts-backport-trusty kernel for precise will be out about a week after 14.04 release18:43
pkernbjf: But without installer support?18:44
bjfpkern, if you mean that it there isn't a point release that has it as the default, you are correct18:44
pkernWell, it might as well miss the necessary installer bits in proposed.18:45
xnoxpkern: we rebuild d-i shortly after lts-backport landing, and one has all installer bits / images in precise/daily generated.19:01
xnoxpkern: although we will not cut .5 isos, there is no reason to not have d-i / netboot available with lts-backport-trusty kernel.19:02
pkernxnox: Ok, thanks, I guess that's something we can test, then.19:04
=== manjo` is now known as manjo

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