[04:03] <RAOF> Hm.  I wish aufs wouldn't go all “Apport would like to pop up and annoy you about this kernel oops” for each build I do in schroot.
[06:09] <YokoZar> Hi, I've been campaigning for an increase to the hard ulimit (leaving soft ulimit in place) for some time now.  It's a simple change, but I'm worried it'll be lost by the wayside this release: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663090
[06:09] <ubot2> Launchpad bug 663090 in linux "Please raise file descriptor hard limit to 4096 (but keep soft limit at 1024)" [Wishlist,Confirmed]
[09:01] <fairuz> Hi, morning
[09:02] <fairuz> if I do taskset -c 0,1 myprog, Its up to the kernel to decide which cpu myprog will run?
[09:03] <jk-> fairuz: if it's a single-process, yeah
[09:04] <fairuz> jk-: ok.. taskset -c 0,1 myprog is the same as taskset 0x3 myprog right?
[09:05] <jk-> fairuz: yep
[09:05] <fairuz> jk-: thanks
[09:09] <fairuz> jk-: I don't know it's the right channel to ask, but I'm trying to flush my L2 cache controller ( I have the register's addr and all )
[09:09] <jk-> fairuz: flush a single cache line?
[09:09] <fairuz> jk-: but when I try to write to the flush register of the controller, the kernel freezes
[09:09] <fairuz> jk-: no, flush by Way
[09:09] <fairuz> jk-: I mean I want to flush all caches
[09:10] <fairuz> jk-: Does the kernel have any protection whatsoever thats prevents me from flushing the L2 cache?
[09:10] <jk-> heh:
[09:10] <jk-> BUGS
[09:10] <jk->        The  current  implementation  ignores  the  addr  and nbytes arguments.
[09:10] <jk->        Therefore, the whole cache is always flushed.
[09:11] <jk-> (man 2 cacheflush)
[09:11] <jk-> fairuz: I don't *think* so
[09:11] <jk-> I'm not too familiar with x86 cache control
[09:12] <fairuz> jk-: I think cacheflush is only flushing L1 caches
[09:12] <fairuz> (I'm using ARM by the way), maybe  thats the problem
[09:12] <jk-> ah
[09:13] <jk-> so you're using mrc ... c7 ?
[09:14] <fairuz> For flushing L1 cache, yes
[09:14] <fairuz> I use CP15 instructions to flush the cache
[09:14] <fairuz> but since my L2 cache is external, I think I cant use MRC...... to cache L2
[09:14] <fairuz> *to flush L2
[09:15] <fairuz> flushing L1 cache works well in my case
[09:15] <fairuz> just L2 that brings problems
[09:15] <fairuz> the registers are memory mapped and I dont know how it dont want to work
[09:17] <jk-> man, the operands to mrc always get me confused
[09:19] <jk-> fairuz: which platform?
[09:19] <fairuz> jk-: OMAP4
[09:20] <fairuz> cortex-A9 MP
[09:22] <fairuz> jk-: you work on ARM too?
[09:22] <jk-> fairuz: yeah, a bit
[09:23] <jk-> what are you looking to do?
[09:23] <fairuz> jk-: Actually I have a program that needs to flush both caches to make it works properly
[09:24] <fairuz> in my platform the L2 cache is external
[09:24] <fairuz> but all the registers are memory mapped
[09:24] <fairuz> and I thought it should be easy :D
[09:24] <jk-> fairuz: take a look at v7_flush_kern_cache_all, in arch/arm/mm/cache-v7.S
[09:24] <fairuz> I can read some of the registers
[09:25] <fairuz> but when it comes to the cache operation register, it freezes the kernel
[09:25] <jk-> I'm not sure how your L2 behaves though.
[09:25] <fairuz> jk-: Yes, I already took a look at it, I think it just flushes L1 caches
[09:25] <fairuz> jk-:  It's a PL310 L2 cache controller
[09:26] <jk-> might it snoop the L1 invalidates?
[09:26] <fairuz> jk-: You mean? Actually I follow a sequence that are recommended in PL310 TRM
[09:27] <fairuz> which is Clean L1, DSB, Clean & Invalidate L2, Cache Sync, Clean & invalidate L1, DSB
[09:27] <jk-> I'm just guessing :)
[09:29] <fairuz> jk-: It makes me frustrated..It should be easy =(
[09:30] <fairuz> and I dont even know how to debug
[09:30] <fairuz> does the kernel log even if it freezes?
[09:30] <fairuz> i mean just before it freezes
[09:36] <jk-> fairuz: I think it's going to wedge on the register write, so no logging.
[09:37] <fairuz> jk-: =( bad news to me... I already tried to disable the interrupts before writing to the register but still no luck
[09:37] <fairuz> jk-: I wonder what makes the kernel freezes
[09:38] <fairuz> jk-: I'm thinking that the cache controller trying to clean the cache but the kernel is trying to write on it? So it's a never ending work
[09:38] <fairuz> jk-: which explains the freeze?
[09:38] <fairuz> jk-: is that possible?
[09:39] <jk-> no idea sorry, I don't have any details about that cache
[09:39] <jk-> you might be able to get some help on #armlinux though
[09:39] <jk-> or #linaro, or #linaro-kernel
[09:39]  * jk- heading out
[10:19] <sconklin> 7873ca4e4401f0ecd8868bf1543113467e6bae61
[11:47] <Kano> hi, is there a linux-meta 38-6 update somewhere
[14:26] <fairuz> what static mapping means? can i still ioremap an address that is already mapped?
[14:46] <sconklin> akgraner: you here?
[15:05] <lool> Oy
[15:06] <lool> linux-image-virtual seems to be missing some .kos (nls_cp*.ko notably) in maverick/i386, but they seem enabled in the config?
[15:12] <lool> smoser: ^
[15:14] <lool> Ok; at least the modules are missing consistently since lucid on both amd64 and i386
[15:16] <lool> but they were present pre lucid, with 2.6.32 kernels
[15:17] <apw> lool, can't be very important if they have been missing for 18 months without anyone noticing :)
[15:17] <lool> Ok, debian.master/control.d/virtual.inclusion-list is the reason
[15:17] <lool> apw: Yes, that's what's reassuring me
[15:17] <lool> It seems like a bogus entry in debian.master/control.d/virtual.inclusion-list
[15:18] <apw> likely excluded indeed
[15:19] <lool> I would suggest that an exclusion-list should be maintained in parallel and that any mismatch shall fail the build  :-)
[15:19] <apw> heh, sounds lovely
[15:19] <apw> lool, actually the module lists in the abi stuff would catch a regression
[15:20] <lool> apw: How would you catch a new module which you fail to install?
[15:20] <lool> e.g. upstream adds cpxyz
[15:20] <apw> well we'd only want to add those if they are useful
[15:20] <apw> and generally we are including by class
[15:21] <lool> apw: I guess that's fair enough, my personal preference is for the tool to be hard on me and force me to document it both ways  :-)
[15:21] <lool> apw: What I find odd is that these things get built but not installed
[15:22] <lool> apw: Why not disable the configs instead?
[15:22] <lool> This would make the delta apparent in the config handling mechanism
[15:22] <lool> fuse is missing too
[15:23] <apw> that bloats the config delta, too.  this was a compromise
[15:24] <lool> I wonder whether the config factorizer could keep most common configs at the top of the tree, and have overrides for the most uncommon ones instead of splitting configs as soon as one differs
[15:24] <lool> oh well
[15:26] <apw> i did try that, and it can be done, but it does make it much more confusing
[15:28] <lool> Ok
[15:28] <lool> I filed LP #732046 to let smoser and others chime in
[15:28] <ubot2> Launchpad bug 732046 in linux "Missing filesystem modules in -virtual package" [Undecided,New] https://launchpad.net/bugs/732046
[15:28] <lool> I propose fixing this in SRUs as well, but feel free to dsiagree
[15:54] <lool> smb: Hey, to workaround LP #732046, I'd like to switch to another kernel; would you know whether I can run -server or -generic under EC2 vms?  do you have hints on how to do that?
[15:54] <ubot2> Launchpad bug 732046 in linux "Missing filesystem modules in -virtual package" [Undecided,New] https://launchpad.net/bugs/732046
[15:55] <lool> Daviey: Ah I think I'm a bit naive to do it from the vm, you are supposed to pass a kernel when starting the instance, so I'm supposed to provide an alternate aki
[15:55] <smb> lool, That was Maverick?
[15:55] <lool> I guess I should pass a pvgrub one
[15:55] <lool> smb: yes
[15:56]  * lool starts a kernel build to get the modules in the background
[15:56] <smb> lool, So pvgrub is there already. I'd try to install a server kernel. 
[15:57] <lool> smb: I did, then I did a grub-reboot on it and it didn't come up
[15:57] <lool> but maybe I messed it up, I might not have waited long enough
[15:57] <smb> lool, was that an m1.large?
[15:57] <lool> No, c1.medium
[15:57] <lool> i386
[15:58] <smb> I think that got more than one cpu too. There is a bog that make reboot from within the instance not working
[15:58] <smb> I think it is still waiting to get into proposed
[15:58] <smb> You would need to reboot either from the web interface or the ec2 tools
[15:59] <smb> And even that seemed to take a long time
[15:59] <Daviey> EC2 makes me cry.
[15:59] <lool> smb: right reboot didn't work indeed, but I used ec2-stop-instance -f
[16:00]  * lool tries again, waiting longer for the machine to come up
[16:00] <lool> Server.InternalError: Request could not be executed due to an internal service error
[16:00] <lool> oh wow
[16:00] <smb> lool, I was using ec2-reboot-intance
[16:00] <smb> instance even
[16:00] <smb> or instances
[16:00] <smb> Command completion makes one forget details
[16:01] <smb> lool, When looking for that bug it felt like taking 5minutes or so
[16:08] <bdmurray> JFo: bug 707353 seems rather important
[16:08] <ubot2> Launchpad bug 707353 in linux "[STAGING] Broadcom 4313 firmware fails to load because it is not present" [High,Confirmed] https://launchpad.net/bugs/707353
[16:09]  * smb wonders whether that is that firmware that needs to be obtained with fw-cutter...
[16:09] <smb> tgardner, ^ Do you happen to know that from memory?
[16:13] <JFo> tagged it kerne;-key so it shows on our list
[16:13] <JFo> thanks bdmurray 
[16:18] <bdmurray> JFo: thank you
[17:03] <JFo> <-lunch
[17:11] <lool> smb: Couldn't get this pv thing to work; I installed linux-image-server which installed the -generic-pae flavor, and it's the first entry in grub.cfg, I grub-reboot 0 and sudo halt, then stop-instance, start-instance, and it still comes up as -virtual
[17:12] <smb> lool, pv-grub is based on grub1, its /boot/grub/menu.lst that matters
[17:18] <lool> apw: Sorry, was wrong earlier, lucid is unaffected
[17:20] <lool> smb: aha, grub isn't installed anymore and grub2 is instead, that's why
[17:21] <smb> lool, There should be some ec2-grub-bla-legacy too. I know its not the least confusign solution to have both files hanging around
[17:22] <lool> grub-legacy-ec2
[17:22] <smb> That should be the one
[17:22] <smb> It generates menu.lst in parralel to grub.cfg
[17:23] <lool> /usr/sbin/update-grub-legacy-ec2 doesn't pick up the generic-pae flabor
[17:23] <lool> flavor
[17:23] <smb> But on EC2 grub.cfg is just there to confuse people
[17:23] <lool> Ignoring non-Xen Kernel on Xen domU host: vmlinuz-2.6.35-27-generic-pae
[17:24] <lool> it seems to be looking for xen in the kernel name
[17:24] <smb> Hm, I guess virtual
[17:25] <lool> I just added the entry manually
[17:25] <smb> I thought that there was some normal kernel installed too. But maybe again just to confuse
[17:27] <smb> jjohansen, Do you remember whether there was any other kernel flavour that may be bootable in ec2? Until the missing modules is solved...
[17:28] <jjohansen> smb: only -ec2 and -virtual
[17:29] <lool> 2.6.35-27-generic-pae
[17:29] <lool> wee
[17:29] <lool> jjohansen: I just used -server which is /boot/vmlinuz-2.6.35-27-generic-pae
[17:29] <jjohansen> smb: -generic and -server are close
[17:29] <lool> it booted fine, just had to force the grub entry as the script wouldn't want to install it
[17:30] <smb> jjohansen, sounds like it is possible 
[17:30] <smb> ;)
[17:30] <jjohansen> smb: yeah possible
[17:30] <jjohansen> on maverick
[17:30] <lool> yup
[17:30] <lool> modinfo nls_cp437 is there, cool
[17:30]  * jjohansen was thinking there was a config missing but, that isn't right either
[17:30] <smb> practical proof. qed. pub.
[17:31] <lool> smb: the next thing I would have done is rebuild linux-virtual myself with the same sources
[17:31] <jjohansen> yeah I did end up booting some -server and -generic kernels during early dev
[17:31] <lool> I would hope the modules would be accepted in this case
[17:31] <lool> I do miss console output with the -generic-pae kernel
[17:32] <smb> Well that could be the missing config
[17:32] <smb> That xen console is not enabled
[17:34]  * smb -> away
[19:11] <smoser> lool, did you get what you were looking for ?
[19:11] <smoser> i can hopefully help
[19:11] <smoser> regarding reboot on ec2, that works fine.
[19:12] <smoser> i reboot in tests that we run for every release, and loads of times when i'm testing cloud-init.
[19:12] <smoser> it is as reliable as rebooting hardware
[19:14] <smoser> well, i'll be around a bit today, and i'm back in tomorrow, if someone has questions. 
[19:15] <kristian-aalborg> hi all... I have some kind of project going on: http://ubuntuforums.org/showthread.php?p=10541660#post10541660 - building a custom kernel, then moving it to another box
[19:22] <lool> smoser: I found a workarund
[19:22] <lool> smoser: I've sub-ed you to the kernel bugs
[19:22] <lool> *bug
[19:23] <lool> smoser: thanks!
[19:23] <smoser> the -virtual kernels should be almost identical to -server... in natty we had some issues, so there are some differences.
[19:23] <smoser> but other than that, they're largely just subsets.
[19:23] <smoser> but it is now a full flavour rather than sub-flavor
[20:07] <soren> smoser: orly? Since natty?
[20:09] <smoser> maverick i think it is its own.
[20:15] <jjohansen> yep, maverick is where it became its own flavor
[20:20]  * soren is failing to keep up, apparantly. :(
[20:56] <tumbleweed> how do I easily build an ubuntu kernel from the kernel git repo? I just want to test a single patch, so build-mkppa looks like it'll give me a source package I can build, but it seems to expect a debian/changelog to exist
[20:56] <tumbleweed> s/kernel git repo/kernel-team git repo/
[21:49] <jjohansen> tumbleweed: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[21:50] <tumbleweed> jjohansen: oh, duh, I missed the clean