[08:13] * apw yanws === lag` is now known as lag [08:29] * smb scanning email... 120+ uploads to precise. It cannot be a feature, so it must be a bug [08:29] :) [08:31] henrix, hey welcome [08:40] apw, hi! and thanks :) [08:40] sorry for the delay. i have connected to irc and when straight for coffee [08:41] henrix, no worries, it was luck i saw you at all as i have login messages suppressed anyhow [08:41] henrix, oh and its still early in our timezone [08:41] apw, yes, still early [08:42] and /me hasn't had an tea yet [08:42] apw, i can't get started w/o my coffee. or tea [08:43] henrix, me either mostly, i can just about cope with irc before [08:43] henrix, Oh yeah, welcome 2 [08:43] smb, thanks! [08:44] smb, also uk? [08:44] henrix, No, de :) [08:44] smb, ah! close enough :) [08:45] henrix, yeah, just an hour, which sometimes can be confusing enough [08:45] yeah and he is about an hour lazier than me, so we align pretty well [08:45] heh. i guess most of the people will be in a US timezone, or am i wrong? [08:45] henrix, and probably a word of "warning" that some of apw's hours are in +1, as well :) [08:46] we have a pretty good spread now not quite half are .eu now, as we have ppisati as well and colin [08:46] great [08:47] so, i was just checking if i already had access to the wiki but it looks like i don't [08:49] henrix, did you get your welcome email from pete with all the pointers on it [08:49] henrix, the wiki needs a special group assigned in lp [08:50] apw, no, not yet. unless he used the canonical email, which i still don't know how to access [08:50] * apw suspects we need pete or tim for that, and i don't they have done that yet [08:50] (at least the canonical one, the ubuntu one should be at least readable) [08:50] smb, just checked my lp and no new group assigned [08:50] henrix, expect today to be a bust ... wht wheels grind slow [08:50] * apw will ask IS if they are processing you [08:50] right, think one of tim or pete need to add the canonical one [08:51] well, i received the initial email from IS and i have replied w/ all info requested. but haven't got any reply from them [08:51] so, i guess i just need to wait [08:52] henrix, ahh good, yeah IS won't be around till 9, so you get to talk to us till then [09:40] * ppisati loves sshfs === hughhalf is now known as hugh_afk [09:42] ppisati, its pretty cool indeed [09:44] henrix, so, as we'll be in the office tommorrow, you might take advantage there of the b/w to get the big repos you'll need [09:44] apw, yep, i guess that's a good idea [09:45] best thing to do was to get linus tree and have a --reference to that for all of our trees when pulling [09:46] yes, keep the disk usage lower. and it's faster [09:47] A lot for the initial clone [09:47] * smb remembers not knowing that when starting and waiting looooong dark coffetimes of it [09:47] yeah so if you have nothing else to do, then i'd make sure you have an up to date linux-linus [09:48] i recommend a bare clone, so you don't accidentally use it ever [09:48] and use that as reference for all our trees, as they are all pretty close to linus [09:49] ok, i do have the linus tree. i used that method to follow some -tip branches some time ago [09:51] hi [09:52] Elboras, hi [09:52] henrix, thats good, one less thing to wait for to download [09:53] henrix, you might want to clone down say the precise tree and look at that [09:53] apw, right. i will [09:53] henrix, i'll let you try and find the information in the wiki :) [09:54] apw, ;) [09:54] henrix, one of your tasks is to update any wiki information you find is unhelpful or incomplete [09:54] henrix, feel free to ask anything you need to, and we just ask you add anything you think is missing to the wiki so the next person finds it easier [09:55] henrix, if you are unsure you can ask for review of the changes or whatever works [09:55] but we no longer can see any issues with the wiki, it appears purfect, but its clearly not [09:55] apw, ok, cool. i'll keep it in mind while going through all the info there [09:56] and that reminds me i should document all the cross-stuff [09:56] when i find something that does not sound ok, i'll flag it and eventually update [09:57] henrix, yep you are a virgin eye on the data, something which you only are this once, so we need you to be critical of what you read, and where you have to ask ... that tells you and us there is something missing and it needs adding [09:57] henrix, don't put it off, just change it ;) [09:57] apw, got it! === popey_ is now known as popey === chrisccoulson_ is now known as chrisccoulson === shadeslayer_ is now known as shadeslayer [10:48] bug 922799 [10:48] Launchpad bug 922799 in linux "Oneiric update to 3.0.18 stable release" [Undecided,New] https://launchpad.net/bugs/922799 [12:24] * ppisati -> lunch === tsimpson_ is now known as tsimpson === ehw_ is now known as ehw [13:12] apw, you're not hearing me on mumble ? I can hear you guys. [13:13] tgardner, yeah try switching from pulse to alsa and back again, apply both ways, in mumble [13:13] tgardner, as we are not seeing red lips at all === yofel_ is now known as yofel [14:37] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/936308 [14:37] Launchpad bug 936308 in linux "BUG: unable to handle kernel NULL pointer dereference at 00000004 (sd_revalidate_disk+0x21/0x290)" [Undecided,Incomplete] [14:37] smb, yan sd_validate_disk jobbie ^^ [14:39] apw, bah, removing usb has become kind of a game of luck... [14:40] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/936652 [14:40] Launchpad bug 936652 in linux "BUG: unable to handle kernel NULL pointer dereference at 00000004 (locks_free_lock+0x9/0x50)" [Undecided,Confirmed] [14:40] bah [14:41] * tgardner reboots tangerine [17:01] hullo kernel people! [17:01] I have an x220 which seems to have a fit every now and then and whilst it has an IP, no traffic will pass over the network interface [17:02] wondered what diagnostics I could get from it before I reconnect to the network and file a bug? [17:02] I have dmesg, ifconfig, a ping, lsmod... anything else? [17:03] info on what type of AP it is talking to [17:03] what encryption mode, periodicity of failure [17:08] apw: ta [17:10] * apw calls it a day before it gets any worse ... === harshpb is now known as harsh_dinner [17:41] tgardner, hi [17:41] tkamppeter, hi [17:43] tgardner, I have a USB problem, I have recently updated my Oneiric box to the newest 3.0.0-16 kernel and now, after connecting a USB printer it takes several minutes until UDEV kicks in setting the group ownership to "lp" and running /lib/udev/udev-configure-printer. [17:44] tgardner, this can also have led to some people still complaining in bug 872711 or telling that the bug reappeared with kernel 3.0.0-16. [17:44] Launchpad bug 872711 in linux "Kernel does not report some USB printers correctly, making them not being detected by CUPS" [High,Fix released] https://launchpad.net/bugs/872711 [17:45] tkamppeter, possibly. do any of these devices require firmware to be loaded ? [17:46] tgardner, no. The only printer needing firmware is not connected currently. [17:46] tkamppeter, and it works reliably with 3.0.0-15 ? if so, then we ought to be able to bisect down to the offending patch. [17:47] tgardner, probably but not absolutely sure. [17:48] tkamppeter, it would help to be sure that it really is a kernel regression. [17:48] tgardner, should I paste the syslog for you? [17:48] tkamppeter, pastebin it [17:49] tgardner, this is what I mean with pasting ... [17:51] tgardner, http://paste.ubuntu.com/850262/ [17:54] tkamppeter, the kernel doesn't seem real happy, 'usb 7-1: device descriptor read/64, error -110'. can you check if 3.0.0-15 has those errors? [17:56] tgardner, OK, will try to boot the old one ... [18:02] tgardner, booted 3.0.0-15 now and the printer is recognized and processed by UDEV within a second or two. [18:06] tkamppeter, good. please catch jsalisbury or bjf tomorrow when they return to work. the'll build bisect kernels for you so we can narrow down the offending patch. [18:06] tgardner, but error seems still to be there: http://pastebin.ubuntu.com/850279/ [18:06] tkamppeter, seems like it might be a red herring [18:09] tgardner, false positive. [18:10] tgardner, now I tried to connect more than one printer and connected a hub with one of these firmware-hungry printers and now it is all like before with 3.0.0-16. [18:11] tgardner, seems that the firmware-hungry printer contaminates the USB stack somehow. [18:11] tkamppeter, did you have a udev update recently ? [18:15] tgardner, I do not know. The system is up-to-date, as I updated yesterday. Which version should I have? [18:16] tgardner, my UDEV is 173-0ubuntu4.1. [18:16] tkamppeter, I don't know what version it should be. I just know that udev can have an impact on firmware loading. [18:16] just looking at what might have changed recently [18:17] tgardner, when I connect several printers at once, some already connected get immediately UDEV-processed. Also some of the newly connected ones. But there can still remain unprocessed printers which get only processed after some minutes. [18:19] tkamppeter, can you correlate that delay from timing information in /var/log/udev ? === harsh_dinner is now known as harsh === harsh is now known as harshpb === tgardner is now known as tgardner_lunch [18:28] tgardner, will try. [18:35] tgardner, in the moment of plugging ther printer does not appear in /var/log/udev [18:40] tgardner, it seems that my udev stoipped logging with the last boot, last entry is from around the time when I booted into 3.0.0-15. === Guest65979 is now known as albrigha