[07:21] <ppisati> moin
[08:22] <smb> moin
[10:06] <ppisati> brb
[10:55] <apw> zequence, did you see there is yet another respin ?
[10:57] <apw> zequence, also which is the latest version you have tested ... just so we can work out which ones can be released
[11:28] <zequence> apw: I usually don't test until they end up in -proposed, so for this ABI, no tests so far
[11:34] <zequence> I'll build new ones this evening
[11:52] <zequence> apw: Doesn't seem like people are getting assigned as usual. I've marked the eariler bug reports as duplicates. bug #1160196
[11:52] <ubot2> Launchpad bug 1160196 in Kernel SRU Workflow "linux-lowlatency: <version to be filled> -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1160196
[11:52] <zequence> ..to these
[11:53] <zequence> bug #1160182
[11:53] <ubot2> Launchpad bug 1160182 in Kernel SRU Workflow "linux-lowlatency: <version to be filled> -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1160182
[12:14] <apw> zequence, marking dup, that seems appropriate ... henrix, bjf, sounds like shankbot may not be assigning things right
[12:15] <apw> zequence, sounds good, poke me when they are done and i'll get them copied out, before they can find an issue with them this time
[12:39]  * cking grabs some nosh
[12:40]  * smb is surprised to find that in the dictionary
[12:45] <rtg_> smb, makes me think he's grabbing something out of a bucket
[12:47] <smb> rtg_, Apparently (according to my dictionary at least) it seems to be something you (Americans) invented for a snack. But then nosh-up seems to mean the opposite (of small)
[13:13]  * ogra_ thinks that fits well and points smb to http://www.addedbytes.com/blog/if-php-were-british/
[13:13] <ogra_> :)
[13:16] <smb> ogra_, Its not as if the UK folk would not slam in new words into their language if they feel like it. ;) 
[13:16] <ogra_> heh
[13:18] <ppisati> rtg_: wait with the phablet kernel
[13:18] <ppisati> rtg_: i misread the email
[13:18] <rtg_> ppisati, ack
[13:18] <ppisati> ppisati: the brightness bug was on the desktop img
[13:18] <ppisati> rtg_: &
[13:18] <ppisati> argh
[13:18] <ppisati> ^
[13:18] <ogra_> iirc the plan was to use the same kernel on both 
[13:19] <ogra_> but we dont have a proper plan how to upgrade it on phablet yet 
[13:19] <rtg_> cking, smb, henrix: need to reboot gomeisa for kernel and SSL update
[13:20] <henrix> rtg_: can it wait 1 min? my build should be finish soon
[13:20] <ppisati> ogra_: and it uses a separate partition where we can't write, right?
[13:20] <rtg_> henrix, yep, just lemme know
[13:20] <henrix> rtg_: will do
[13:20] <henrix> thanks
[13:20] <smb> rtg_, I am off
[13:21] <ogra_> ppisati, theoretically it shouldnt differ much so abootimg on /dev/mmcblok0p2 should work to just update it ... but nobody tried yet
[13:21] <ppisati> ogra_: no i mean
[13:21] <ogra_> */dev/mmcblck0p2
[13:21] <ppisati> ogra_: i flash my nexus, ssh into it
[13:21] <ppisati> ogra_: can't i mount it?
[13:21] <ogra_> mount ?
[13:22] <rtg_> ppisati, jjohansen: bouncing tangerine for kernel and SSL update
[13:22] <ppisati> rtg_: ack
[13:22] <jjohansen> rtg_: give me 30s
[13:22] <ppisati> ogra_: ok, redo from start
[13:22] <rtg_> jjohansen, ack
[13:22] <jjohansen> rtg_: okay I'm good
[13:23] <ppisati> ogra_: where does the kernel reside?
[13:23] <ogra_> ppisati, to update the kernel on desktop we run "abootimg -u /dev/mmcblk0p2 -k /path/to/vmlinuz"
[13:23] <henrix> rtg_: ok, i'm off gomeisa
[13:23] <ogra_> from flash-kernel
[13:23] <ppisati> ogra_: ok
[13:23] <ogra_> ppisati, to update on phablet we should theroetically be able to do: "abootimg -u /dev/block/mmcblk0p2 -k /path/to/vmlinuz"
[13:24] <ogra_> but practically nobody tested that 
[13:24] <ppisati> ogra_: since the bootloader is untouched, there's no bricking risk, right?
[13:25] <ogra_> right, but check with abootimg -i if /dev/block/mmcblk0p2 is actually the right partition
[13:25] <ppisati> ogra_: i'll do
[13:25] <ogra_> (flash-kernel loops over all devices with abootimg -i to find teh biggest one and then flashes to that)
[13:27] <rtg_> tangerine is back
[13:31] <bjf> apw, shankbot fixed (i broke it with my previous change)
[13:45] <rtg_> ogra_, is there a trick to getting adb to talk to an N7 running 4.2.2 ?
[13:46] <ogra_> rtg_, https://wiki.ubuntu.com/Touch/Install#Step_3_-_Initial_Device_Setup ... see step 2 and the different suggestions there 
[13:46] <ppisati> rtg_: usb debugging?
[13:47] <ogra_> 4.2.2 adds a silly host key check to the process
[13:47] <rtg_> ppisati, how to enable USB debugging in that Android version ?
[13:47] <ogra_> and they have hidden the developer options 
[13:47] <ppisati> rtg_: tap 7 times in a row on the release version field
[13:48] <rtg_> ah, both 4.1 _and_ 4.2 require this
[13:48] <ppisati> rtg_: in... settings -> ... status?
[13:48] <ogra_> right
[13:48] <ogra_> it tells you "now you are a developer" if you did it right ... 
[13:48] <ppisati> right
[13:49] <ogra_> if you dont, you will never be a developer :''(
[13:49] <ppisati> then go back one level, enter the developer menu and enable usb debugging
[13:49] <cking> the magic 7 taps is a fun hidden feature
[13:49] <rtg_> ok, got that far
[13:50] <rtg_> alright, phablet-flash appears to be working
[14:01] <gQuigs> I can't seem to find documentation on the Ubuntu 10.04 Kernel Backports; the best I could find was http://askubuntu.com/questions/29961/why-are-only-some-versions-of-the-kernel-backported-to-certain-releases
[14:01] <gQuigs> specifically I'm wondering if support for the 3.0 kernel ends in April with Oneiric 
[14:17] <ogasawara> apw, rtg_: so beta freeze is on Thurs and I see ppisati has sent his highbank pull request.  I'm thinking we get ppisati's pull request applied and upload today or tomorrow.  Thoughts?
[14:17] <bjf> gQuigs, yes it does end in April with Oneiric
[14:17] <rtg_> ogasawara, I'm in the middle of it
[14:17] <ogasawara> rtg_: sweet
[14:17] <rtg_> ogasawara, I'm a sweet guy :)
[14:19] <rtg_> ppisati, am looking at your highbank patch. it appears we can drop the highbank flavour and load the OF enabled common kernel on the highbank platform ?
[14:19] <ppisati> rtg_: right
[14:19] <ppisati> rtg_: i wanted to send a patch later to axe the highbank flavour
[14:19] <rtg_> ppisati, cool, then I'll rip out the highbank cruft from the tree as well
[14:19] <ppisati> rtg_: but if you want to do that now, go ahead
[14:20] <rtg_> ppisati, I assume I can set CONFIG_SATA_HIGHBANK=n for x86'en ?
[14:21] <ppisati> rtg_: i guess so
[14:21] <rtg_> ppisati, its na OF driver. I don't think thats supported on x86, right ?
[14:21] <rtg_> its an*
[14:22] <ppisati> rtg_: yep
[14:22] <ppisati> rtg_: at least until highbank is arm based :)
[14:23] <rtg_> ppisati, you mean, "at least as long as highbank is arm based"
[14:23] <ppisati> rtg_: yes
[14:23] <rtg_> ok
[14:24] <ppisati> apw: besides, i was using your tool to do a cfg review
[14:25] <ppisati> apw: and a) i'm doing something stupid or b) there's something wrong with our cfg/flavour setu
[14:25] <ppisati> apw: since i got: 
[14:25] <ppisati> apw: amd64-generic - armhf-armhf - armhf-generic - armhf-highbank - i386-generic
[14:25] <ppisati> apw: notice the second one
[14:32] <ppisati> apw: ok, i just updated kteam-tools (fetch & rhard), and i think it's broken
[14:32] <ppisati> apw: http://paste.ubuntu.com/5649520/
[14:32] <ppisati> apw: '/home/flag/git2/.../'
[14:41] <gQuigs> thank you bjf
[14:44]  * ogasawara back in 20
[14:50] <gQuigs> bjf: is that written down somewhere?
[14:51] <bjf> gQuigs, i'm sure it's in the wiki somewhere but I can't point you at it right off the top of my head
[15:00] <jsalisbury> **
[15:00] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:00] <jsalisbury> **
[15:13] <rtg_> apw, can you take a pass through the Raring enforcer and annotations to harmonize them wrt dropping highbank and omap
[15:25] <robher> ppaisati, rtg_: btw, for highbank you need to revert "UBUNTU: SAUCE: arm highbank: add support for pl320-ipc driver" and there is a SATA fix needed to avoid matching the ahci_platform driver. I can send a patch for the latter.
[15:26] <rtg_> robher, sooner is better please
[15:29] <robher> rtg_: okay. Now that things seem to be moving I'll review the config and provide anything else I find. I do also need to add cpufreq driver that went into 3.9.
[15:30] <rtg_> robher, note that beta freeze is thursday, so it would be great if you could get that done soonest.
[15:30] <robher> rtg_: should be all doable by today or tomorrow.
[15:30] <rtg_> ack
[15:31] <rtg_> robher, what is the name of the cpufreq driver ? perhaps I can work on cherry-picking it whilst you are looking at other stuff.
[15:34] <ppisati> ogra_: mmcblk0p1 is the biggest, so that should be
[15:35] <robher> rtg_: git log --oneline -6 74c46c6
[15:35] <robher> plus "091930a mailbox, pl320-ipc: remove __init from probe function"
[15:36] <ppisati> robher: btw, do you know that there's a problem with reboot?
[15:37] <robher> ppisati: this is the bug from 3.5?
[15:37] <ppisati> robher: don't know where it comes from
[15:37] <ppisati> robher: but i know 9 out of 10 times, when i issue a reboot
[15:38] <ppisati> robher: using a 3.8 kernel
[15:38] <ppisati> robher: it gets stuck at the end
[15:38] <ppisati> robher: didn't debug it yet
[15:40] <robher> ppisati: hadn't seen that. there had been some intermittent problems, but those were more like 1 out of 10 and I thought I'd fixed all of them. I'll look into it.
[15:47] <rtg_> robher, rebased 'UBUNTU: SAUCE: arm highbank: add support for pl320-ipc driver' et al out of existence and cherry-picked the patches you requested. pushed +master-next
[15:48] <ppisati> rtg_: about the R/omap4 kernel, what do we do? shall i send a pull req to sync it with Q or do we just copy the package from Q to R?
[15:48] <rtg_> ppisati, I think that is a good question for infinity. are we ever gonna touch omap4 again ?
[15:50] <rtg_> ppisati, AFAICT the raring ti-omap4 branch has never been used, right ?
[15:50] <ppisati> rtg_: never touched it
[15:51] <ppisati> rtg_: it's an old Q/omap4 kernel
[15:51] <rtg_> right, still stuck on 3.4
[15:51] <ppisati> rtg_: but i think R/omap4 desktop images are generated out of it
[15:52] <rtg_> ppisati, generated from the Q kernel ?
[15:52] <ppisati> rtg_: yeah, since they need the pvr kernel module to work (unity 3d opengl etcetc)
[15:53] <rtg_> ppisati, so I guess the issue is what if we ever change the Q kernel ? The Q kernel won't get auto-synced into R
[15:57] <rtg_> ppisati, rmadison linux-ti-omap4
[16:01] <ppisati> ogra_: my kernel update didn't go as expected
[16:01] <ppisati> ogra_: first i 'abootimg -u .../mmcblk0p1 -k vmlinuz', rebooted
[16:01] <ppisati> ogra_: but i still had the old one
[16:01] <ppisati> ogra_: so i thought "maybe is mmcblk0p2"
[16:01] <ppisati> ogra_: redo
[16:02] <ogra_> what was the output of abootimg doing that ?
[16:02] <ppisati> linuz-3.1.10-10-nexus7 ablet# abootimg -u /dev/block/mmcblk0p2 -k foobar/boot/vm
[16:02] <ppisati> reading kernel from foobar/boot/vmlinuz-3.1.10-10-nexus7
[16:02] <ppisati> Writing Boot Image /dev/block/mmcblk0p2
[16:02] <ogra_> (and also the output of abootimg -i )
[16:02] <ppisati> ogra_: for both p1 and p2
[16:02] <ogra_> hmm
[16:02] <ppisati> ogra_: anyhow, i ended up in cynogen recovery
[16:02] <ogra_> we probably need to update abootimg 
[16:03] <ogra_> might be that 4.2.2 needs a newer version of it or so
[16:03] <ppisati> ogra_: let me tinker with it a bit more
[16:04] <ogra_> ok, i'll jump on it myself around the weekend ... currently i'm busy convincing the amd64 livefs builder to produce pahblet android cross built images
[16:04] <ogra_> that will keep me busy until friday
[16:09] <ppisati> ogra_: ok so, the correct partition is mmcblk0p2 since it's LNX
[16:10] <ppisati> ogra_: p1 is recovery
[16:31] <apw> rtg_, will do indeed
[16:32] <apw> rtg_, given i have been playing with that across n7 today, it is all shiney and fresh in my mind
[16:33] <rtg_> apw, there are a number of references to omap, etc that are no longer appropriate
[16:33] <apw> rtg_, now to work out why i am not being given notifications in irc any more
[16:33] <rtg_> no flashy thingy ?
[16:34] <jsalisbury> apw, fyi, commit 3e8f4f40 fixed bug 1157952 but it introduced other errors, posted in comment #19
[16:34] <ubot2> Launchpad bug 1157952 in linux (Ubuntu) "SCSI keysense errors on console with Raring (3.8 kernel) within Windows Azure" [High,Incomplete] https://launchpad.net/bugs/1157952
[16:34] <apw> jsalisbury, heh ... oh so typical of that lot
[16:35] <apw> rtg_, yep will 'redo' the review and sort them out
[16:36] <apw> rtg_, indeed i have no OSDs fro irc all of a sudden, strange thing
[16:54] <apw> ppisati, i take it the armhf-generic is bootable on omap4 as it is currently
[16:54] <ppisati> apw: yep
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:11]  * ppisati goes to find some food, later
[17:37] <apw> rtg_, ok ... initial fixups for arm -generic etc pushed ...
[17:37] <rtg_> apw, ack
[17:37] <apw> there are some bits which need investigation which i'll poke next
[17:38] <apw> ppisati, know of any reason we cannot enable CONFIG_SERIAL_8250_DMA on armhf -generic ?
[17:38] <rtg_> apw, ACPI was an issue, but I think there is a patch for it
[17:41] <zequence> apw: I'm a little confused on versions. pull-lp-source pulls 3.5.0-26.28, but when I look here https://launchpad.net/ubuntu/+source/linux-lowlatency, it seems it's still in proposed. What's the best way to check which is the last released kernel? I'm about to build quantal and need to know which version I should use (suddenly, I'm not that confident on this)
[17:41] <zequence> I mean, which version I should use for the -v argument..
[17:45]  * rtg_ -> lunch
[17:47] <apw> zequence, for -v you can use 'rmadison -a source linux-lowlatency' which will show you the versions in alll pockets
[17:48] <apw> linux-lowlatency | 3.5.0-25.25 | quantal-security/universe | source
[17:48] <apw> linux-lowlatency | 3.5.0-25.25 | quantal-updates/universe | source
[17:48] <apw> linux-lowlatency | 3.5.0-26.28 | quantal-proposed/universe | source
[17:48] <apw> zequence, for exasmple that is quantals entries which shows -25.25 in -security and -updates, and -26.28 in -proposed
[17:49] <apw> ppisati, CONFIG_USB_MUSB_HDRC is marked as =y (boot essential on omap) but is m on -generic, any issues or shall i lose the annoataion
[17:50] <apw> ppisati, CONFIG_EXT2_FS isn't that 'flash-kernel essential' on arm ?
[17:50] <apw> ppisati, let me knwo on those and i'll get them cleaned up
[18:08] <zequence> apw: kernel sources ready
[18:29] <ppisati> apw: loose annotation on MUSB
[18:30] <ppisati> apw: vfat is essential on omap
[18:30] <ppisati> apw: ext2 might be essential on imx6, lemme check
[18:56] <rtg_> ppisati, did you figure out the magic runes for updating an N7 kernel after installing the touch image ?
[18:56] <ppisati> rtg_: not yet
[18:56] <ppisati> rtg_: 'abootimg -u /dev/block/mmcblk0p2 -k vmlinuz' should be enough
[18:56] <ppisati> rtg_: but it's not :P
[18:57] <rtg_> hmm, too bad. it seems like it wuold be rightr
[18:58] <ppisati> rtg_: rtg_ i'll give it another shot later
[18:58] <rtg_> ppisati, ok, it'll come in handy for testing where one doesn't wanna reinstall the whole image (nor make one from scratch)
[18:59] <ppisati> apw: ok so, ext2 is not mandatory for imx6
[19:00] <ppisati> apw: but on highbank, /boot is uses it
[19:00] <ppisati> apw: actually we can mount using ext3 on it
[19:00] <ppisati> apw: so it's either ext2 or ext3
[19:00] <ppisati> apw: uhm no
[19:00] <ppisati> apw: it's really ext3
[19:00] <ppisati> apw: /dev/sda1       /boot           ext3    defaults        0       2
[19:01] <ppisati> apw: i think you can turn off ext2 and leave ext3 compield in
[19:02] <rtg_> CONFIG_EXT2_FS=m
[19:02] <rtg_> which looks OK
[19:09] <apw> rtg-afk, yep, it is the annotations which are wrong in that case, ppisati lets catch up in the morning :)
[19:38]  * ogasawara lunch
[20:07] <mdalacu> Hi, how can i report a kernel bug, if it does not boot? Can someone help me? I have read the guidlines, but it is very difficult for me to follow them.
[20:08] <mdalacu> The problem is simple, i can't boot with IOMMU option in BIOS active with any kernel above 3.7 version. It drops to busybox.
[20:20] <jsalisbury> mdalacu, Can you boot from a LiveCD, or a prior kernel, or even with the IOMMU option disabled?  You should be able to report a bug with 'ubuntu-bug linux' if you can boot with one of these three options
[20:21] <infinity> apw: BenC fixed the ACPI/CONFIG_SERIAL_8250_DMA conflict in linux-ppc.  If that's not upstream, you might want to cherry-pick from him.
[20:21] <mdalacu> With kernel version 3.6 and oneric kernels i can boot raring just fine. Any raring live cd with IOMMU disabled boots fine.
[20:22] <BenC> infinity: rtg said he was grabbing it, IIRC
[20:22] <BenC> It is upstream
[20:22] <infinity> BenC: Ahh, cool.  Check.
[20:22] <mdalacu> I have already reported the bug, but this is as far as i can go...
[20:22] <mdalacu> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159219
[20:22] <ubot2> Launchpad bug 1159219 in linux "Ubuntu Raring , IOMMU, fails to boot" [High,Triaged]
[20:23] <jsalisbury> mdalacu, ok, I've seen that bug.  I can perform a bisect to identify the commit that introduced the regression in 3.6.  I'll post some comments to the bug.
[20:24] <mdalacu> Thank you , should i post any new files to that bug, a dmidecode or something?
[20:24] <rtg_> BenC, 'serial: 8250_dw: Use ifdef with ACPI' ?
[20:25] <BenC> rtg_: yep
[20:27] <jsalisbury> mdalacu, no need to post additional info.  The apport data should be good enough for now.
[20:28] <mdalacu> jsalisbury, OK, thank you very much. I will go now. Bye.
[20:32]  * rtg_ -> EOD
[21:17] <markus-j> does someone here know if the next precise/quantal-lts kernel will contain the patches mentioned here? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157649/comments/15
[21:18] <ubot2> Launchpad bug 1157649 in xserver-xorg-video-intel "GPU hang" [Undecided,Fix released]
[22:43] <greearb> hello!  I'm starting work on re-mastering a 12.10 live-cd image, and I'm curious if anyone knows if the 'raging' kernel can be used on 12.10 (as live-cd)?