[00:48] <ogasawara> bjf: thanks.  out of curiosity, which test?
[00:48] <bjf> ogasawara: seccomp_filter
[09:39]  * ppisati -> dentist
[10:53] <ppisati> anyone with upload rights, could you bump linux-meta-ti-omap4 in P? thanks
[11:00] <apw> ppisati, will do, could you rebase linux-ti-omap4 again, there is an important security fix in the -10 series which you are missing, though i presume you'd go straigt to -11
[11:01] <apw> ppisati, your bits are still in the new queue, so i can't do -meta yet
[11:03] <ppisati> ah ok
[11:04] <ppisati> i wanted to unf*ck the kernel first
[11:04] <ppisati> since the images are screwed without this update
[11:04] <ppisati> i'll do all the rebase today
[11:04] <apw> ppisati, yep, thats reasonable
[11:05] <apw> ppisati, oh that reminds me, sometime soon we want to retire the lucid/mvl-dove and start doing the work on maverick/mvl-dove
[11:08] <ppisati> uhm, i din't touch any LMN kernels because i thought we were going to retire them soon
[11:08] <apw> that has yet to be decided, those manager types are still talking
[11:34] <smb> herton, Morning, you probably had not much time yet to settle down, but there has been a new release of 2.6.32.y since yesterday. Would you plan on pulling that for the next round of proposed that was just started?
[11:35] <herton> smb, no, I think it can wait for the next round, unless there is something we want from this update
[11:39] <smb> herton, Must admit I have not looked too deeply in there. Some random mmap thing sticks out in the headers. But things can be rather theoretical. This one does not yet seem to include anything about the ioctl fixup.
[11:39] <smb> So I am fine either way. Just means I can do the ec2 rebase now. ;)
[11:39] <apw> there is always a new round of -stable, they never end
[11:39] <smb> exactly
[11:40] <apw> at least with a 3 week candance we don't get more than 2 in any release
[11:40] <smb> Was just wondering because this week is preparation week
[11:40] <apw> smb, they all went up yesteday i think, so missed
[11:40] <herton> smb, what's this ioctl issue?
[11:40] <smb> apw, Indeed they did
[11:41] <ppisati> the only thing certain in life is death, taxes and SRUs
[11:41] <herton> hehe. yes, lucid finished build yesterday, we already have the packages done now for this round
[11:43] <apw> smb, have we lost voice between you and me?  i heard you, ...
[11:43] <apw> smb, herton and cking can hear me
[11:43] <apw> smb, yay
[11:45] <smb> herton, something to prevent / reject some ioctl calls on block devices. Not 100% sure whether that included also checking capabilites or just irgnoring some
[11:45] <herton> ok
[11:49] <ppisati> upgrading a beagle to P is a royal PITA!
[11:50] <apw> ppisati, surly not for an ARM expert like you :)
[12:03] <ogra_> ppisati, just estimate a week or two for it aynd dont be impatient ;)
[12:04] <ppisati> :(
[12:05]  * ogra_ hasnt touched beagles since two releases to prevent people around me from getting hurt and furniture in my house from breaking all of a sudden :)
[12:06] <ppisati> do you use the boards to keep the furniture in place? :)
[12:06] <ogra_> lol
[12:06] <ogra_> well, one is my printserver, one monitors my heating system for the house and one sits on a shelf collecting dust 
[12:07] <ogra_> the printserver one is actually nailed to the bottom of the printer table so you could say it keeps the furniture together at least :)
[12:08] <cking> apw, http://uncyclopedia.wikia.com/wiki/Linux
[12:11]  * ppisati -> lunch
[12:58]  * tgardner bounces tangerine at the top of the hour
[13:09] <ppisati> no patch applied to fsl-imx51 in 3 weeks?
[13:18]  * tgardner reboots gomeisa for security kernel update
[13:22] <herton> ppisati: yep, no new patches
[13:22]  * herton having extra fun this morning with a dying hard disk
[13:40] <ppisati> uhm
[13:41] <ppisati> my natty repository is hosed
[13:41] <ppisati> error: refs/remotes/origin/ti-omap4 does not point to a valid object!
[13:41] <ppisati> why it happens?
[13:53] <smb> because
[13:55] <apw> ppisati, does your repo have an alternative (.git/objects/info/alternatives) and is it still there
[14:00] <ppisati> apw: nope
[14:01] <apw> then thats not normal
[14:02] <apw> .git/objects/info/alternates <- sorry its alternates
[14:02] <apw> ppisati, &&
[14:02] <ppisati> [flag@newluxor ubuntu-natty]$ ls -la .git/objects/info/*
[14:02] <ppisati> -rw-rw-r-- 1 flag flag 54 2012-01-26 14:51 .git/objects/info/packs
[14:02] <ppisati> btw
[14:03] <ppisati> it doesn't complain anymore now
[14:34] <herton> ppisati: the maverick ti-omap4 pull is missing the tracking bug in the changelog
[14:45] <joshhunt__> I've got a question about USNs if anyone can help. USN-1336-1 and USN-1342-1 provide the same patch. I see that 1342 applies to 10.04 and is a backport of oneiric. Is that the only difference?
[14:46] <apw> ppisati, its stopped complaining, be afraid
[14:47] <apw> joshhunt__, i believe that there is a USN per release yes, so thats entirly possible, touch you might like to confirm on #ubuntu-security
[14:48] <ppisati> herton: sh*t! i was sure i ran the verify-release-check script
[14:49] <ppisati> ah
[14:49] <ppisati> herton: i had it local but i din't add/commit the change
[14:50] <herton> ok, yeah sometimes happens :)
[14:50] <joshhunt__> apw: thanks I'll check there
[14:52] <ppisati> herton: ok, i fixed it now
[14:53] <herton> ppisati: ack
[15:02] <apw> ppisati, tgardner, they have just new'd linux-ti-omap4, am doing meta
[15:03] <tgardner> apw, ack
[15:04] <apw> ppisati, ok its in the pipe
[15:08]  * herton -> lunch
[15:11] <apw> ogasawara, so -8 -> -9 was 3.2.1 and "top down" coming in, the kexec vomit, and a small number of configs
[15:13] <ogasawara> apw: definitely looks like some arm changes that went in
[15:13] <apw> ogasawara, its a biggie, ppisati has a fun day ahead of him
[15:13] <apw> ppisati, you might want to see if     UBUNTU: [Config] CONFIG_USB_FILE_STORAGE is deprecated
[15:13] <apw> anything to do with it
[15:13] <ppisati> ok, i'll do
[15:15] <ogasawara> ppisati: keep us posted.  I'm planning one more upload anyways before the milestone, so I'll hold the upload until I hear from you.  I ideally want to upload by end of day tomorrow.
[15:15] <ppisati> ogasawara: ok, i'll do
[15:16] <tgardner> ogasawara, am running Precise master-next w/3.2.2 stable on several machines. seems OK so far.
[15:17] <ogasawara> tgardner: cool.  was just about to do a build and test.
[15:17] <ogasawara> tgardner: thanks for doing the rebase by the way.
[15:18] <tgardner> ogasawara, I was motivated 'cause xfstests was causing some oops on  my emerald. gonna retry it this AM
[15:18] <diwic> ogasawara, thanks for uploading the kernel yesterday, but is it normal for it to not be published at this time?
[15:19] <ogasawara> diwic: normally it would have been built and published by now, but it seems powerpc is taking longer than usual to build.
[15:19] <diwic> ogasawara, ok, so a little slower than usual, but no need to worry yet. Right?
[15:21] <ogasawara> diwic: I hope not.  when I checked this morning powerpc was estimated to start building in about 2 more hours.
[15:21] <diwic> ok.
[15:26]  * ogasawara back in 20
[15:49] <apw> tgardner, alt-F10 should toggle max by defualt it seems
[15:50] <tgardner> apw, it maximizes, but down't minimize (which isn't a toggle)
[15:59] <apw> tgardner, thats poo
[16:00] <apw> documentation for this thing isn't worth a shit
[16:07] <tgardner> apw, is this the correct invocation: sudo client/bin/autotest --output_dir=$HOME/autotest.wrk client/tests/xfstests/control
[16:07] <apw> that should work if the control file makes sense
[16:07] <apw> tgardner, the normal form is that, but remember the control files in the test directories are mean as samples
[16:07] <tgardner> well, everything is failing at this point, but it does build the xfstests correctly
[16:08] <apw> and you are meant to put together one representing the tests combinations you want to run
[16:10] <tgardner> apw, the xfstests control file appears to be correct, but I did have to add TEST_DEV and TEST_DIR
[16:10] <apw> tgardner, as the commentary there indicates, thats why they can only be seen as samples
[16:50] <jsalisbury> tgardner, who is our omap expert, Palo?  bug 921934
[16:50] <ubot2`> Launchpad bug 921934 in linux "mmc no longer detected on omap (BeagleXM) since 3.2.0.9" [Critical,Confirmed] https://launchpad.net/bugs/921934
[17:02] <tgardner> jsalisbury, he is, and I think he's aware of this bug
[17:02] <jsalisbury> tgardner, cool, thanks.  
[17:08] <tgardner> ppisati, ^^
[17:10] <__cr3> hi guys,i have a question.what do u guys expect from a fresher who wants to work in a company like canonical,redhat..etc which concentrates on kernel development...
[17:13] <jsalisbury> smb, are you our virtual guy :-)  bug 921816
[17:13] <ubot2`> Launchpad bug 921816 in linux "BUG: unable to handle kernel NULL pointer dereference at 00000030" [Medium,Confirmed] https://launchpad.net/bugs/921816
[17:13] <mfilipe> hi guys! is there kernel-3.2 for oneiric?
[17:14]  * apw calls it a day ...
[17:14] <jsalisbury> smb, actually it's an EC2 issue
[17:16] <arges> sforshee, could you hear me on mumble? 
[17:16] <jsalisbury> arges, we can hear you
[17:16] <sforshee> arges, we can hear you but you can't hear us
[17:16] <arges> jsalisbury, sforshee yea I've had this problem for the last couple of weeks
[17:16] <arges> let me try to fix it
[17:18] <herton> ppisati: the oneiric ti-omap4 has a problem in the changelog, the email closing the change is outdated (and with extra <>)
[17:18] <mfilipe> ogasawara, is there any kernel 3.2 for oneiric?
[17:19] <ogasawara> mfilipe: not to my knowledge.  We only do the backport kernels for the previous LTS release.
[17:19] <mfilipe> hum... thanks!
[17:20] <ogasawara> mfilipe: if it's just for testing purposes, you could try installing the precise kernel in oneiric.
[17:22] <mfilipe> no, I went a 3.2 official for oneiric. I didn't know that you won't backport kernels for oneiric and this is only for LTS release.
[17:25]  * ogasawara bails for appointment, back in a bit
[17:27] <ppisati> jsalisbury: yep, i'm already on it
[17:27] <ppisati> herton: let me check...
[17:27] <jsalisbury> ppisati, thanks
[17:30] <lamont> herton: fwiw, -33 has been happy for about 24 hours
[17:31] <lamont> I'm going to go to -35 a bit later today
[17:33] <herton> lamont: hmm good to know. Points to a possible regression in the kernel indeed. I was playing with adjtimex, could help debugging in the bad kernel if it is indeed a kernel issue
[17:33] <lamont> will advise
[19:46] <ppisati> lpMMC on Beagleboard depends on TWL4030's GPIO lines, re-enable it.
[19:46] <ppisati> See also:
[19:46] <ppisati> ops
[19:46] <ppisati> lp921934
[19:46] <ppisati> bug 921934
[19:46] <ubot2`> Launchpad bug 921934 in linux "mmc no longer detected on omap (BeagleXM) since 3.2.0.9" [Critical,Confirmed] https://launchpad.net/bugs/921934
[19:47] <ppisati> ogasawara: ^^ - fix sent to the ml
[19:47] <ogasawara> ppisati: ack, thanks.
[20:24] <tgardner> ogasawara, pushed with some ABI directory module file corrections
[20:25] <ogasawara> tgardner: cool thanks.  I was also going to add it to the config enforcer, just about have the patch done.
[20:25] <tgardner> ogasawara, is that one worthy of enforcement ? I guess I don't know what it even does.
[20:26] <tgardner> sconklin, xfstests: Failed 26 of 167 tests
[20:26] <ogasawara> tgardner: we'll we'd flipped it to =m across the board per our review policy, so I'd like to have it in the enforcer so we don't forget and make the same mistake again.
[20:26] <sconklin> Are you running the test list that I modified, or all tests?
[20:26] <tgardner> ogasawara, ah, good idea.
[20:27] <sconklin> see changes to control file
[20:27] <patrickmw> bjf, I've run into all types of situations which is why I asked for more info
[20:27] <tgardner> sconklin, I got tired of trying to get autotest to work, so I just ran ./check
[20:27] <patrickmw> bjf, you have a few options here
[20:27] <bjf> tgardner: i had no trouble getting it to work
[20:28] <sconklin> tgardner: then you get to keep all the pieces. A bunch of the xfstest tests don't apply to ext4, so you have to set up a list of ones to run
[20:28] <tgardner> I don't seem to be able to get any of the tests to run under the autotest umbrella
[20:28] <tgardner> wonder what I've got wrong
[20:29] <tgardner> sconklin, mostly I was looking for kernel crashes, which is why I ran everything.
[21:14]  * cking bails out
[21:58]  * tgardner -> EOD
[22:51] <manjo> sconklin, SRU Question.. 
[22:52] <manjo> will this patch make it in 11.10 though updates? or do I need to SRU it ? 
[22:52] <manjo> commit c510eae377c773241ff0b6369a8f3581da941a51
[22:52] <manjo> Author: Oliver Neukum <oneukum@suse.de>
[22:52] <manjo> Date: Wed Sep 21 11:41:45 2011 +0200
[22:52] <manjo>     btusb: add device entry for Broadcom SoftSailing
[22:56] <manjo> ogasawara, ^ ? you know ? 
[22:56] <sconklin> manjo: ask Brad or Herton, I'm on rotation to QA this cycle and I'm not following stable
[22:56] <manjo> ah ok 
[22:57] <manjo> bjf, ^ :)
[22:57] <manjo> oops looks like its in 11.10 already ... 
[22:58] <herton> manjo, it's included in 3.0.9, probably going in -proposed or already released
[22:58] <manjo> herton, thanksa ton ... 
[22:59] <herton> manjo, released in 3.0.0-14.23
[23:00] <manjo> hmmm I seem to have 3.0.0.15 (that is what uname says)
[23:02] <manjo> herton, sorry my bad... I think I messed up the IDs when I did a search
[23:10] <Fudge> hi is this audio device supported in precise kernels Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
[23:10] <Fudge> been getting scratchy sound for first few minutes until seemingly extra audio streams come in
[23:10] <ohsix> it wouldn't be showing up or making any sound if it wasn't supported
[23:11] <Fudge> ok
[23:11] <Fudge> so should ask pulse guys about scratchy sound?
[23:13] <Fudge> thanks ohsix