[07:23]  * apw yaws
[07:23]  * apw pitches
[07:24]  * apw rolls
[07:24]  * amitk pulls back the rudder
[07:24]  * apw hears "pull up, pull up"
[07:25]  * amitk sucks at flight simulator and promptly crashes the plane
[07:25]  * apw was ok on the bbc back in the day... flying under the bridge upside down was tricky
[07:38] <cking> heh, I learnt my flying skills in Elite
[07:40] <apw> cking, :)  that bbc flightsim had a lot of hours of my time
[07:42] <cking> the wonders of 3d wireframe graphics on the 6502...
[07:43] <apw> yeah amazing
[07:43] <apw> and their GPU was a dac
[07:44] <cking> I hacked up a 6502 line drawing routine that could pop out pixels in 98 cycles
[07:45] <cking> those were the days...
[07:45] <cking> sigh
[07:45] <apw> heh yeah :)  old bugger
[07:55] <_ruben> 6502 .. that's c64'ish?
[07:56] <_ruben> been too long, and am not too old yet :p
[07:56] <apw> _ruben, that era yes.  when computing hit the home for the very first time
[07:58] <cking> when one could get a lot done in 1K of assembler..
[07:59] <apw> a scarey thought indeed, when your logout button takes up more RAM than you had space on all of your disk media
[08:01]  * apw is pretty sure his first hard drive in his PC was 15MB, and the OS and something useful fit on it
[08:01]  * gema thinks this is starting to feel like a kernel channel now :D
[08:01] <_ruben> i recall picking up our first pc with my dad .. a laser xt .. the question was to go witha 20MB hdd or no hdd
[08:02] <_ruben> and my dad upgrading our PET from 64KB to 128KB ram orso .. for 500 bucks .. hadda solder out the old mem chips and replace 'em with new ones :)
[08:03] <apw> heh, the days when you could see the pins on chips
[08:50] <_ruben> apw: fair point :)
[08:50] <_ruben> the good ol' .1" spacing
[09:57] <ppisati> can i have a faster kernel.ubuntu.com for christmas?
[09:57] <apw> ppisati, heh ... she a little reticent to do what you want ?
[09:58] <smb> ppisati, Depends on how many times your sudo attempts fail
[10:02] <cooloney> ppisati: how's your speed to k.u.c
[10:02] <cooloney> ppisati: for me, sometimes 3k
[10:04] <smb> Sounds as fast as from the hotel last week...
[10:06] <soren> That's impossible. It's git, so it doesn't care about bandwidth. It just sprinkles more pixie dust on the bits and bytes and then magically makes everything faster.
[10:06] <ppisati> i'm not talking about network, it's jst that gitweb is so slow...
[10:07] <ppisati> btw, in the last few days since i upgraded to the latest kernel, after 3/4 hours of work. my trusty ps/2 dies
[10:07] <ppisati> and i've to reboot to make it work again
[10:07] <ppisati> did anyone experience this before?
[10:07] <apw> ppisati, nope all stable here
[10:07] <smb> Neither before nor after...
[10:07] <ppisati> :(
[10:07] <apw> ppisati, but what release you running on it
[10:08] <ppisati> Linux newluxor 3.0.0-8-generic #11-Ubuntu SMP Fri Aug 12 20:23:58 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
[10:08] <ppisati> oneiric
[10:08] <ppisati> i update it every morning
[10:08] <smb> adventourous
[10:08] <ppisati> :)
[10:09] <ppisati> in fact half of the desktop is broken
[10:09] <ppisati> btw, this usb eyboard sucks
[10:09] <smb> Seems to have lost its k... :)
[10:18] <apw> ppisati, well there is known death in the archive right now, see ubuntu-devel@ for details
[10:21] <smb> shoot, and I just upgrade a test system...
[10:22] <apw> smb, kiss it goodbye
[10:22] <smb> apw, Definitely should not try to reboot it... :-P
[10:23]  * smb wonders whether it is Friday already...
[10:23] <apw> the end of something :)
[10:27] <cking> heh, I updated my lap-top 10 mins ago and it's working OK
[10:28] <smb> cking, For me, apport seems to be one of those packages not really happy
[10:29] <cking> however, typing seems really laggy on the desktop - it's as if something is getting in the way
[10:32] <apw> cking, i think you should show that to colin king he is great at fixing those toughies
[10:33] <cking> apw, that's just a rumour, anyhow colin king is busy at the mo
[10:34]  * cking double checks his US visa paperwork. gah, I dislike paperwork
[10:35] <ppisati> VISA?
[10:36] <cking> the ESTA stuff
[10:36] <ppisati> ah ok
[10:36] <cking> it's just a faff remembering my number, putting in hotel and flight info.
[10:36] <smb> Isn't that supposed to be no *paper* work?
[10:37] <cking> it's paperwork in electronic form IMHO
[10:37]  * smb never does update the thing. somehow I got in anyways...
[10:38] <smb> Maybe its the reason they ask for the hotel and stuff again after putting the same information into the online checkin (which of course gives you no boarding passes because you could be lying)
[10:39] <apw> cking, putting in what ?
[10:40] <apw> cking, you do know you don't have to do that right ?
[10:40] <smb> apw, In theory you have to update your esta thingy everytime you travel to the us
[10:40] <apw> smb, thats not what it said when i applied.  it said the info was optional (hotel)
[10:40] <cking> well, I like to update it because they may do something nasty to be if I don't. being paranoid as usual
[10:40] <apw> and i've never updated mine
[10:40] <apw> maybe i am meant to. bah
[10:41] <smb> Me neither, but the travel agency brought it up last time
[10:41] <smb> Apparently its optional for the allowance
[10:41] <apw> for the allowance ?
[10:41] <smb> but you should (if you are nice) update it when you know
[10:41] <smb> apw, wrong work maybe
[10:41] <smb> allowing you in
[10:41] <smb> word
[10:41] <cking> they allow apw in?
[10:41] <apw> ahh i see, for the permission perhaps
[10:41] <apw> not if i am with _you_ no
[10:42] <cking> ha
[10:42] <apw> ahh gads, i've just realised, you and scott will be in the same place
[10:42] <smb> cking has done every bit required, of course he *must* be a terrorist
[10:42] <cking> yep, but we won't be travelling on the same plane, therefore it's OK
[10:43] <cking> things only go pear shaped when scott and myself travel on the same plane/train/taxi/etc
[10:46] <apw> cking, you claim ...
[10:49] <cking> assert(trip_cking == trip_scott);
[10:50] <smb> not !=?
[10:51] <apw> yeah
[10:51]  * smb thinks there should be a tripit travel warning if that happens
[10:51] <apw> though cking hides from tripit
[10:52] <smb> Even more reason to get him some glove treatment (apart from acting suspiciously unsuspicious)
[10:53] <cking> very funny
[10:53] <cking> smb, you saying if I act weird then I'm OK?
[10:54] <smb> cking, Of course, only people that want to do evil would not want to stick out, wouldn't they? ;)
[10:54] <cking> smb, I'm doomed
[10:55] <smb> cking, Too normal for the world. But I guess travelling with apw cancels out that a bit... :-P
[10:56] <cking> quite a bit
[10:58] <cking> only another 34 fwts tests to document.. sigh
[11:03]  * ppisati -> lunch
[11:03] <smb> ppisati, A sec
[11:04] <ppisati> smb: what?
[11:04] <smb> ppisati, Just to confirm (since I got some mails about subscriptions to those) you got the tracking bugs for arm topic branch prepeartions too?
[11:07] <smb> bug 800234 and 8000235 just in case not
[11:07] <ubot2> Launchpad bug 800234 in gwibber "gwibber-accounts crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known> (dup-of: 728844)" [Undecided,New] https://launchpad.net/bugs/800234
[11:07] <ubot2> Launchpad bug 728844 in gwibber "gwibber-accounts crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known>" [Medium,Invalid] https://launchpad.net/bugs/728844
[11:07] <smb> errr
[11:08] <apw> heh those are not even close specially the second on
[11:08] <smb> forget it... there seems to be something with wastagin in it...
[11:08] <apw> one
[11:08] <smb> apw, Yeah, I think I got some test runs
[11:08] <apw> bug #8000235
[11:08] <smb> But did not realize
[11:08] <smb> bug 800235
[11:08] <ubot2> Launchpad bug 800235 in firefox "firefox addons web page is not opening just it keep loading" [Undecided,New] https://launchpad.net/bugs/800235
[11:09] <apw> oh i see its actually reading its _own _ output
[11:09] <smb> See
[11:09] <smb> apw, Well the numbers I saw are not valid in the "real lp world"
[11:09] <apw> bug 800234
[11:09] <ubot2> Launchpad bug 800234 in gwibber "gwibber-accounts crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known> (dup-of: 728844)" [Undecided,New] https://launchpad.net/bugs/800234
[11:09] <ubot2> Launchpad bug 728844 in gwibber "gwibber-accounts crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known>" [Medium,Invalid] https://launchpad.net/bugs/728844
[11:10] <smb> Oh you mean that
[11:10] <smb> Yeah
[11:10]  * smb wonders what would happen if a bug title contained its own number again...
[11:11] <ppisati> smb: actually no
[11:11] <ppisati> smb: did yu receive just now?
[11:11] <smb> ppisati, No, I saw some but there were done in the staging system. I got one for ec2 for real, but maybe they just did not get that far for the fsl et al
[11:12] <ppisati> dunn
[11:12] <ppisati> i had some emails about the tracking bugs for the different arm topic branches
[11:13] <ppisati> but didn't receive it right now
[11:13] <smb> Those would be the ones. With "version to be filled". Those would have come yesterday
[11:13] <ppisati> ah ok
[11:13] <ppisati> yes, got them
[11:13] <smb> I just got confused by the test ones
[11:14] <ppisati> bt i didn't have anything to push
[11:15] <smb> For ec2 it was at least the rebase (and actually needed one upstream patch to be brought into the file clones)
[11:21] <apw> ppisati, do you not do the mvl-dove rebases when they are needed
[11:22] <ppisati> apw: last time they did it
[11:22] <ppisati> apw: uhmmm...
[11:23] <smb> ppisati, You saw that email about passing of things to us, did you? :)
[11:23] <apw> ppisati, ok then they may be happy doing so, probabally worth asking who is responsible in case they fall through the cracks
[11:23] <ppisati> apw: maybe i did the rebase, and they closed the release... don't remember exactly...
[11:23] <ppisati> ok
[11:23] <ppisati> smb: you mean the "Updates on topic branches" mail, right?
[11:24] <smb> yep
[11:24] <ppisati> smb: yes, but i think i forgot it... :)
[11:24]  * ppisati goes to reread it...
[11:25] <apw> ppisati, thanks for your feedback on those arm patches ... they have been hangin about for a while.  am happy to carry them if we need to but we don't "know" anything about they at the moment
[11:25] <smb> apw, On related topic, was I able to clarify the libbfd confusion?
[11:26] <apw> not seen your reply yet, i am "better" at my email now, but not great
[11:26] <ppisati> apw: ye, let's see what sakoman says
[11:26]  * smb was hoping... :-P
[11:33] <apw> ogasawara, on burndown, we seem to have two sets now, the pitti ones we've used for sometime, and now the new status.ubuntu.com ones.  There hwe is split out and on the kernel ones we are: http://status.ubuntu.com/ubuntu-oneiric/group/topic-oneiric-kernel-tasks.html
[11:33] <apw> ogasawara, and there we are below the line!
[11:36] <Daviey> Reset the trend line, simples.
[11:36] <apw> Daviey, no they are genuine trend lines, its whats included and whats not that gets us there
[11:37] <apw> the status ones split kernel into kernel and hwe and its hwe who are behind :)
[11:37] <apw> but nothing they are doing is release critical so we don't really care if they are behind
[11:52] <tgardner> ppisati, uploaded the meta package for linux-ti-omap4 3.0.0-1202.6 and sent announcement.
[12:07] <ppisati> tgardner: ok, thanks
[12:15] <ppisati> smb: it's still in demo-mode, right? i mean the new trackign bug etcetc
[12:16] <smb> ppisati, The ec2 one was real. Have not looked out for any other.
[12:17] <ppisati> i've 2 mvl-dove tracking bugs, bt they say "Ignore this bug"
[12:18] <ppisati> and one on bugs.qastaging.launchpad.net
[12:18] <ppisati> ok, i'll ask the SRU when they apper
[12:18] <ppisati> *SRU people
[12:18] <smb> Hm, one of the ec2 ones went to ignore as well
[12:19] <smb> yeah, they should know
[12:19] <herton> ppisati, smb: yep, they were closed because we are respinning today lucid and maverick kernels
[12:19] <ppisati> ah ok
[12:19] <ppisati> btw, in case i've noting to push, wat do i have to do?
[12:19] <herton> so just ignore them for now, you will get new bugs after the new kernels are built again
[12:19] <smb> herton, Seems only one. I've done a rebase to what was in lucid-master
[12:21] <herton> ppisati: if you don't have anything to release, I think you can just close the bug, invalidating everything (you can do with check-release-tracking-bugs --bug=<n> --invalidate)
[12:22] <herton> smb: if you rebased that's fine, but you will have to rebase again, I'll push to master a fix to a CVE patch that brought a regression
[12:23] <smb> herton, Not a problem just more work. Would have been good then to have both tracking bugs marked as, please ignore... :-)
[12:25] <herton> smb: you mean the master lucid bug? it could be done, I just set it as a duplicate of the new tracking bug
[12:26] <smb> herton, No I mean the two ec2 tracking bugs
[12:26] <smb> bug 800236
[12:26] <ppisati> i've to disappear for half an hour
[12:26] <ppisati> brb
[12:26] <apw> smb, luckily the second rebase should be a slam dunk :)
[12:27] <smb> apw, yeah
[12:28] <smb> Argh
[12:28] <herton> smb: 800236 doesn't find any bug here
[12:28] <smb> herton, You really confuse people with those qastaging versions
[12:29] <herton> smb: ah... I used qastaging for testing, everything on qastaging should be ignored :)
[12:29] <smb> herton, Tell that the bug mailer... :-P
[12:31] <herton> smb: hmm, I don't know how qastaging is setup, I thought it shouldn't sent any emails, weird. Never received emails from it, pehaps it's broken for direct people assignments, who knows
[12:31] <smb> herton, It seems so. And unfortunately the mails look completely like real ones. Just with qastaging in the link. :/
[12:38] <herton> ppisati, smb: so just wait for new tracking bugs, they will be opened when the packages are built, nothing to do until then. I'm going to get sconklin review the new releases today and then do the upload, the bot will open the tracking bugs when everything is built.
[12:39] <smb> herton, ack
[12:40] <ogasawara> apw: \o/, I'll update our status wiki's to point to the status.u.c burn downs
[12:41] <apw> ogasawara, :)
[12:44] <apw> ogasawara, what did we decide about SECCOMP (mode 2) in the end
[12:45] <ogasawara> apw: I'm waiting for an updated pull request as it currently breaks the build on arm
[12:45] <apw> ahh yes, i remember now.  cool
[12:47] <tgardner> ogasawara, apw: I'm thinking it won't make the cut since its gonna take  a major revamp to get it working on ARM
[12:47] <apw> tgardner, might there be value to having it availabe on x86.  it sounded like chromium was committed to using it
[12:48] <tgardner> apw, perhaps. in that case we should use it as is and disable for armel ?
[12:49] <apw> tgardner, that was kinda my thinking.  arm is marjinal for users right now
[12:49] <tgardner> apw, don't say that too loud. you'll have ogra_ crawling all over you.
[12:50] <apw> :0
[12:51] <ppisati> back
[13:18] <apw> ogasawara, we normally say EXPERIMENTAL =n, but for filesystems, sensors, etc we tend to say "but they are opt-in and we want them enabled for testing" ... does that sound about right?
[13:18] <ogasawara> apw: yep
[13:19] <apw> ok so i am going to code that in, i am thinking filesystems, sensors, hid, netfilter things
[13:19] <apw> as a first set of exceptions
[13:22] <smb> cking, I now see what you meant with lagging. Seems every keystroke ponders about something. And trying to move a window my mouse pointer is at the target before the window even considers to move...
[13:22] <smb> cking, Have you reported that already?
[13:23] <apw> smb, see if you have kworker threads eating your machine
[13:23] <apw> that sounds liek the symptoms i had when that was occuring
[13:23] <smb> apw, Now compiz is using 8%cpu even when idling
[13:24] <smb> apw, Only have a few kworkers and they do not show up prominently in top
[13:26] <apw> smb, 2-3% on my netbook on oneiric
[13:27] <smb> apw, consistently between 8 and 10 on a dual core dell...
[13:27] <cking> smb, not yet
[13:27] <smb> apw, Its ati gfx
[13:27] <apw> smb, slightly more when there are stupid OSDs on the screen
[13:28] <apw> smb, ok, i don't have those
[13:28] <smb> apw, btw bug 828737
[13:28] <ubot2> Launchpad bug 828737 in ubuntu "The iconify and de-fullsize buttons are barely noticable" [Undecided,New] https://launchpad.net/bugs/828737
[13:29]  * apw confirms it
[13:30] <cking> wow, just moving a window makes compiz consume 12%  of my CPU
[13:30] <apw> cking, it must be falling back to doing something by hand
[13:31] <smb> cking, What gfx card do you have?
[13:31] <apw> does unity 2d work any better
[13:31] <cking> smb, an old ATI Radeon X1300
[13:32] <smb> cking, May be a pattern as apw does not see it. I got some ati card as well
[13:32] <smb> An X1200
[13:32] <cking> smb, since pulling in some updates this morning it feels less laggy
[13:32] <smb> Hm, I just pulled the latest stuff
[13:32]  * smb does not want to know haw it was
[13:34]  * cking tries 2d
[13:35] <cking> yep, 2d much snappier
[13:35] <cking> still, moving a window gives 10% CPU loading
[13:36] <cking> and terminal feels more responsive when typing - although the is a tad subjective
[13:38] <cking> terminal resizing is a pain when you have wobbly touchpad input
[13:39] <smb> cking, bug 828752
[13:39] <ubot2> Launchpad bug 828752 in compiz "Very slow responding system (compiz/ati?)" [Undecided,New] https://launchpad.net/bugs/828752
[13:39] <cking> smb, you verified this with 2d to see if it does the same?
[13:40] <smb> cking, not yet. doing now
[13:42] <smb> cking, Hm so compiz is not right... its the same in 2d but without any process to blame directly
[13:42] <smb> though the typing is quicker
[13:44] <cking> so it looks to me like the keyboard is being read in a timely manner, but rendering it is taking a while
[13:44] <cking> do you see a lay when you switch to a text console?
[13:44] <cking> s/lay/lag/
[13:44] <cking> doh
[13:44] <apw> or s/lay/delay/
[13:45] <smb> cking, no, just on the way backl
[13:46] <smb> cking, But actually typing text is rather normal in 2d (I had a one sec delay before a key typed would appear)
[13:47] <smb> Just dragging windows feels like they are unwilling
[13:47] <smb> Btu maybe that is a new feature...
[13:48] <cking> sluggish windows a good feature?!
[13:49]  * smb did not say good
[13:53] <smb> It feels as "good" as that for a restart you now have to click shutdown and then restart...
[13:58] <tgardner> apw, do you remember how to change the I/O scheduler ? I'm thinking a HW RAID controller doesn't need any kind of elevator sorting.
[13:59] <vanhoof> tgardner: system wide, elevator= in grub, believe on a per fs basis somewhere in sys
[14:00] <tgardner> vanhoof, I remember that there is a sysfs knob, but can't remember the name
[14:01] <vanhoof> tgardner: /sys/block/sda/queue/scheduler
[14:01] <apw> tgardner, i think its per device in sysfs
[14:01] <apw> tgardner, i will be supprised if no elevator is going to be better unless its to IO merging
[14:01] <apw> but i assume you are going to measure
[14:02] <tgardner> apw, how can it know if its talking to a HW RAID controller with 8 spindles ?
[14:03] <apw> tgardner, it can't know, but sending lots of small IO's may not be an improvement over at least merging things nearby
[14:03] <apw> tgardner, but i am all for trying it
[14:04] <tgardner> apw, I'm just watching this Emerald idle along with 10-15 processes running and 1350 sleeping. wtf ?
[14:04] <Guest3769> cking: Nope, no lag here!
[14:04] <apw> tgardner, i would very supprised if that much CPU couldn't kill almost any ammount of disk you add
[14:04] <cking> Guest3769, very droll
[14:05] <tgardner> apw, but only 10 processes running? I'd think a high end RAID controller could keep things busier then that.
[14:06] <apw>  tgardner i am keen to see if changing it helps any, try the others if not too
[14:06] <apw> tgardner, my experience is if there isn't battery backed front end cache on the controller then its not going to like random IO
[14:07] <tgardner> apw, I'm only seing write speeds in the 5M/s range, well below what its capable of.
[14:07] <smb> I actually think even noop does merging. But I am not sure that the other elevators still take any geometry assumptions
[14:07] <apw> and bear in mind this is a write heavy pattern, which is usually hindered by any sort of raid 5 type raid
[14:08] <apw> as we have to write more than one sector for each sector, and often have to cut up the IO into smaller chunks
[14:08] <tgardner> I wonder if there are any white papers on how to tune for HW RAID
[14:08] <Guest3769> cking: :D
[14:08] <Guest3769> cking: lag is in Africa 
[14:08] <apw> that is a goog question
[14:08] <apw> good
[14:09] <tgardner> apw, I think 'goog' is apropos :)
[14:09] <apw> tgardner, heh i did chuckle at my own typo
[14:09]  * ogasawara back in 20
[14:16] <awolfson> Hi all. Are there any plans to include utrace support in onerick?
[14:17] <apw> if that is extra kernel patches then its not in now, and unlikely to be
[14:51] <apw> ogasawara, ok i've done the bulk of the annotations for the P config review we should ahve far fewer oddnesses in the session now
[14:52] <ogasawara> apw: awesome, thanks
[14:57]  * tgardner disappears into his server room
[15:09] <apw> ogasawara, i have just found an NETFILTER match which is inconsistant on O, it really should have been caught in the review, so i am proposing to just fix it and push it up, that ok ?
[15:09] <ogasawara> apw: go for it
[15:10] <apw> now that there are not 1000s of inconsistant entries its easier to find the ones one should worry on
[15:11] <apw> ogasawara, done
[15:12] <apw> ogasawara, also pushed it to u-p, i note that uses master not master-next ... which is a little odd
[15:14] <ogasawara> apw: yah, I didn't make master-next yet since I didn't think there'd be much conflict in pushing
[15:14] <ogasawara> apw: but will do so now
[15:15] <apw> ogasawara, i more think of master as 'whats released' and master-next as 'next stuff'
[15:15] <apw> so we almost could not have a master in there
[15:23]  * ogasawara migrates back to the office
[15:26] <jpds> Can someone take a look at https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/795823 ?
[15:26] <ubot2> Ubuntu bug 795823 in alsa-driver "Dell Studio XPS - Internal Microphone not Working " [Undecided,Triaged]
[15:26] <jpds> I can confirm that the model= workaround works.
[15:27] <apw>  /whois jpds
[15:28] <jpds> apw: Oh hi.
[15:28] <apw> hi, i've pushed it over to the kernel, as it will need a quirk
[15:28] <apw> jpds, you do need to confirm that abolutly everything all the holes and jack detection etc works with that model=
[15:29] <apw> if you can do that and report it in the bug
[15:29] <apw> (not just the one mic you are trying to fix)
[15:29] <jpds> apw: I'll test it and see.
[15:31] <apw> jpds and your machine isn't the one listed on that bug
[15:32] <apw> (or is it)
[15:33] <diwic> jpds, can you please file a new bug for your issue with "ubuntu-bug audio"? (As hw might not be the same)
[15:34] <diwic> jpds, and do so in a state where you're trying to record from the internal mic
[15:34] <apw>         SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x02fe,
[15:34] <apw>                                 "Dell Studio XPS 1645", STAC_DELL_M6_BOTH),
[15:34] <apw> it seems there is already a quirk to a different setting for that machine
[15:34] <diwic> aha
[15:34]  * apw hands over this one over to diwic :)
[15:35] <diwic> we had the same problem with dell studio 1558
[15:35] <apw>         SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0413,
[15:35] <apw>                                 "Dell Studio 1558", STAC_DELL_M6_DMIC),
[15:35] <apw>         SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x0413,
[15:35] <apw>                                 "Dell Studio 1558", STAC_DELL_M6_DMIC),
[15:35] <apw> yeah we have _two_ entries for that puppy
[15:36] <diwic> oh, anybody want to have their name in the kernel? Some low-hanging fruit here :-)
[15:37] <apw> oh no that is my incompetance, i'd copied it to add the new one before i dicovered it was already there
[15:38] <apw> diwic, ok this 1645 was only set to STAC_DELL_M6_BOTH cause a reporter said it worked, they may have never tested the mic
[15:39] <diwic> apw, m6_both creates two mics whereof one does not work, and so user gets confused
[15:40] <diwic> apw, it would be good to have jpds alsa-info or apport info to see if that's the case
[15:41]  * apw pokes jpds
[16:04] <apw> ogasawara, can you make "
[16:04] <apw> UBUNTU: Stop ARM boards crashing when CUPS is loaded" (no-up) on your next rebase please
[16:04] <ogasawara> apw: yep
[16:05] <apw> ogasawara, then thats lag's patched done and dusted, i've closed that WI
[16:05] <ogasawara> apw: sweet
[16:08] <apw> tjaalton, hey you have a patch hanging around on our tree, and we are wondering if it is going upstream or ... "UBUNTU: SAUCE: Added quirk to recognize GE0301 3G modem as an interface"
[16:10] <tjaalton> apw: yeah I got a ping about it while on vacation, and actually refreshed my tree to create a patch for upstream, but didn't finish it yet :)
[16:11] <apw> tjaalton, so can i say "its upstreamable and timo is sorting it out as time allows" ?
[16:12] <apw> as i think from the review point of view that means keep it till it collides on rebase which is fine
[16:12] <tjaalton> apw: yeah, I believe it's still a valid patch
[16:12] <apw> tjaalton, thanks :)  i call that reviewed
[16:12] <tjaalton> cool :)
[16:14] <apw> ogasawara, we should look a lot better in a few
[16:14] <ogasawara> apw: indeed.  I think we only have one work item left for the delta review now.
[16:16] <apw> ogasawara, two i think, both inprogress
[16:16] <ogasawara> apw: heh, I overlooked yours
[16:17] <ogasawara> apw: so I'm going to rip out master from P for now
[16:19] <apw> ogasawara, yeah always me, sigh
[16:19] <apw> ogasawara, works for me
[16:25]  * apw bails
[16:31] <Sarvatt> mdeslaur: building a kernel now with what jbarnes posted on the fdo bug
[16:34] <mdeslaur> Sarvatt: cool, thanks
[16:34] <Sarvatt> mdeslaur: amd64 or i386?
[16:34] <mdeslaur> Sarvatt: please build it for oneiric, I'm on oneiric now
[16:34] <Sarvatt> oh, ok
[16:35] <mdeslaur> Sarvatt: I couldn't postpone updating any longer :)
[16:52] <Sarvatt> mdeslaur: http://kernel.ubuntu.com/~sarvatt/fdo40172/
[16:53] <mdeslaur> Sarvatt: cool, thanks, give me a few minutes
[16:57]  * tgardner is off to buy a house.
[16:57] <sforshee> cnd, you around?
[17:01] <cnd> yep
[17:02] <sforshee> more touchpad questions for you :)
[17:02] <cnd> ok
[17:03] <sforshee> in reference to this: http://pastebin.ubuntu.com/669405/
[17:03] <sforshee> it seems like the ABS_[XY] report in the last packet is making utouch's drag or flick detection get confused
[17:03] <sforshee> since their 0, it detects an upward flick
[17:04] <sforshee> but the buttons are being released
[17:04] <cnd> hmmm, our stack doesn't look at ABS_{X,Y}
[17:04] <sforshee> so is that a driver problem (the driver shouldn't send the position) or a utouch problem?
[17:04] <sforshee> really?
[17:04] <cnd> it looks at ABS_MT_POSITION_{X,Y}
[17:05] <sforshee> because if I modify the driver so that those aren't sent, there's no upward flick at the end of my downward drag
[17:05] <cnd> hmm, maybe for semi-mt devices it looks at ABS_{X,Y}
[17:05] <cnd> we should check out the code of utouch-frame
[17:05] <cnd> (which I'm currently rewriting :)
[17:05] <sforshee> I'd think since BTN_TOUCH and BTN_DOUBLETAP are released in that frame, it should ignore the position
[17:06] <sforshee> this is something I'm encountering in testing the driver changes elantech sent earlier
[17:07] <cnd> ahh
[17:07] <cnd> what are you using to test touch?
[17:08] <cnd> to test utouch* that is
[17:08] <sforshee> I have an oneiric install, and I'm just testing drag-to-scroll in various application windows
[17:08] <cnd> sforshee: is ginn running?
[17:08] <cnd> ps aux | grep ginn
[17:09] <sforshee> nope
[17:09] <cnd> ok, good
[17:09] <cnd> so outside of a development version of ginn, we don't do scrolling through utouch (yet)
[17:09] <cnd> so this is an issue in xserver-xorg-input-synaptics
[17:09] <sforshee> oh, okay
[17:10] <cnd> though it's in the code that I added
[17:10] <cnd> :)
[17:10] <sforshee> at least I'm asking the right person then :)
[17:10] <cnd> well, actually, maybe not
[17:10] <cnd> let me try to remember
[17:10] <cnd> yeah, I don't think I touch scrolling
[17:10] <cnd> that's still handled through ABS_{X,Y} and BTN_TOOL_DOUBLETAP
[17:10] <cnd> which would explain why this is throwing things off
[17:11] <cnd> really, the driver shouldn't be emitting ABS_{X,Y} of any value when BTN_TOUCH is released
[17:11] <sforshee> that's what I was thinking
[17:11] <cnd> so I would consider that a bug
[17:11] <sforshee> but
[17:12] <sforshee> it's pretty trivial to not send them from the driver too, so I'll probably suggest they make that change
[17:12] <sforshee> not that the bug shouldn't be fixed :)
[17:12] <cnd> hmm?
[17:12] <cnd> I think we're talking about the same bug
[17:12] <cnd> the driver should be fixed
[17:12] <sforshee> sorry, didn't read carefully enough (trying to multitask...)
[17:13] <cnd> if you mean that synaptics shouldn't be using an X and Y event when BTN_TOUCH is released
[17:13] <cnd> well, that would be great too :)
[17:13] <cnd> but it shouldn't have to check that
[17:13] <cnd> sforshee: thanks for testing it out!
[17:13] <sforshee> either way, I'll just tell them to fix it in the driver
[17:14] <sforshee> cnd, thanks!
[17:16] <mdeslaur> Sarvatt: unfortunately, I can still reproduce
[17:17] <Sarvatt> mdeslaur: darn.. mind commenting that on https://bugs.freedesktop.org/show_bug.cgi?id=40172 ?
[17:17] <ubot2> Freedesktop bug 40172 in DRM/Intel "[arrandale] Fuzzy screen after dpms cycles on lenovo t510 [bisected, 3.0+]" [Normal,New]
[17:17] <mdeslaur> Sarvatt: just did
[17:17] <Sarvatt> thanks a ton!
[17:18] <mdeslaur> np
[17:25] <cnd> sforshee: in return you can help jog my memory
[17:25] <cnd> how do I build the generic kernel from git
[17:25] <cnd> fdr clean
[17:25] <cnd> fdr binary-image (but I know there's something to select just generic)
[17:25] <sforshee> fdr binary-generic
[17:25] <sforshee> is that what you want?
[17:25] <cnd> ahh, yes
[17:26] <cnd> is there still an env var to make it not build the dbg package?
[17:26] <sforshee> no, you have to give a var in order to get the dbg package built
[17:26] <sforshee> by default it doesn't build the dbg package
[17:27] <cnd> ahh, that's a change from when I last built stuff
[17:28] <cnd> what about building with make -j16?
[17:28] <cnd> do I need to do anything special?
[17:28] <cnd> nm, I see it did it automatically
[17:29] <sforshee> just what I was about to say :)
[17:29] <sforshee> I don't know how to override the decision the scripts are making tho
[17:29] <sforshee> wrt how many jobs to use, that is
[17:29] <Sarvatt> DEB_BUILD_OPTIONS=parallel=16
[17:30] <sforshee> Sarvatt, thanks!
[17:33] <cnd> hmmm, I'm trying to rebuild the 3.0-0.1 kernel but I get the following:
[17:33] <cnd> WARNING: drivers/built-in.o(.data+0x1c898): Section mismatch in reference from the variable ab3550_driver to the function .init.text:ab3550_probe()
[17:33] <cnd> The variable ab3550_driver references
[17:33] <cnd> the function __init ab3550_probe()
[17:33] <cnd> If the reference is valid then annotate the
[17:33] <cnd> variable with __init* or __refdata (see linux/init.h) or name the variable:
[17:33] <cnd> *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
[17:34] <cnd> anyone seen this type of error before?
[17:34] <sforshee> cnd, I see those sometimes, but I didn't think it caused the build to fail
[17:34] <cnd> maybe it's something else
[17:35] <cnd> ugh
[17:35] <sforshee> probably, looks like ab3550_probe shouldn't be marked __init but the build shouldn't fail as a result
[17:35] <cnd> something else, but I'm not sure how to fix it
[17:35] <cnd> I'll have to play a bit
[17:35]  * ogasawara goes out for lunch, back in a bit
[17:47] <cnd> stupid rtl driver
[17:47] <cnd> glad we got rid of it
[18:29]  * jjohansen -> lunch