[07:53] <apw> nsfx, i would file a bug indeed, maybe this can be upstreamed so it goes away forever
[10:16]  * apw hates debugging filesystems, it is so hard to know what is going to do what
[10:16] <apw> there is so much reference counted poo in here
[10:18] <ohsix> cking: on an oooold blog post you were wondering about other uses for the fibmap ioctl. i just had another drive failure and i use debugfs to see which files were damaged, it directly looks at fs structures, but you could check every file on the disk with fibmap and try and find it too
[10:19] <ohsix> cking: old = circa 2009
[10:19] <ohsix> found the post when i was looking to see if the vfs or ext4 had an ioctl or method to do it directly, from the bad block to an inode
[10:20] <cking> ohsix, i'm glad it was helpful, these ioctl's are not well documented
[10:22] <ohsix> from the vfs .txt in <kernel>/Documentation it says it's used internally to find out which blocks are used in a file if it's going to be used for swap, since the swapper accesses the disk directly
[10:23] <ohsix> before there were special vfs calls for it, it was used to read the sparse areas of a file in xfs
[10:23] <ohsix> and that's about all i know about it
[10:46]  * ppisati -> out for lunch
[10:56]  * cking has to confess he's forgotten most of the details, the blog is an aide-mémoire 
[12:09] <rtg> apw, ogasawara: I uploaded grouper yesterday. turned out to be gcc as well as some config options (most likely LOCKD). Gonna sync with distro config today.
[12:24]  * henrix -> lunch
[13:00] <apw> rtg, great stuff, so 4.7 or 4.6 needed
[13:00] <rtg> apw, 4.6, I didn't try 4.7 since I ran out of interest
[13:00] <apw> yep
[13:01]  * apw goes back to debugging his overlayfs loop lockup
[13:01] <rtg> apw, now I have to figure out how to enable lttng again and clean up compile issues
[13:03] <rtg> biab
[13:37] <maxb> I seem to be having a new problem since upgrading to raring - every so often my mouse pointer becomes corrupt / disappears. The GPU is radeon, and this is a dual screen setup. Is there anything specific I should bear in mind in filing a useful bug?
[13:40] <maxb> https://bugs.freedesktop.org/show_bug.cgi?id=55819 is the sort of thing I mean
[13:40] <ubot2> Freedesktop bug 55819 in DRM/Radeon "Mouse cursor corruption when moving between monitors" [Normal,New]
[14:48] <rsalveti> compilers fun
[14:49] <rsalveti> amazing that it only works with 4.6
[14:50] <rtg> rsalveti, it stands to reason since we encountered the same issu on all the other Nexus kernels.
[15:10] <apw> rsalveti, it is most  liklely a bug in the kernel asm which is exposed by later compilers doing things right
[15:14] <rsalveti> apw: right
[15:39] <Guest14125> hummm I see some familiar faces here, hi dannf and lamont, this is eddie quinteros
[15:40] <dannf> hey Guest14125! good to see you - you might wanna /nick eddie or similar :)
[15:40] <lamont> hi eddie
[15:40] <eddieq> eddie was taken
[15:42] <eddieq> hi guys, I'm sorry to bother you, but I have been looking all over the Ubuntu pages and can not find answers to 2 problems I have with crash, they are simple can you guys help?
[15:42] <dannf> eddieq: possible, but most likely not - though feel free to ask
[15:43] <eddieq> ok I have 10.04 installed kernel 3.5.0-23-generic and i forced a vmcore
[15:43] <eddieq> go the dbg package for it
[15:44] <eddieq> running crash vmlinux-3.5.0-23-generic /var/crash/vmcore /boot/System.map-3.5.0-23-generic gives me crash: cannot resolve: "xtime"
[15:45] <eddieq> there is a BZ https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1075745 but it says it was fixed
[15:45] <ubot2> Ubuntu bug 1075745 in crash (Ubuntu) "crash fails cannot resolve xtime" [Medium,Fix released]
[15:46] <eddieq> Now, I run the same command on a RH system and it runs fine, but bt -l does not gives me line numbers
[15:53] <zequence> apw: so, did you come up with a solution on how I could take over dev release as well?
[15:54] <zequence> apw: since updates don't need to be as frequent, perhaps it is not as big of a project?
[15:55] <eddieq> I am at the latest crash release and still get the xtime error
[15:58] <rtg> caribou, ^^ you've used crashdump extensively IIRC
[16:20] <eddieq> humm I know caribou too, hello
[16:29] <apw> zequence, thanks for the reminder, i'll put that in large on my todo
[17:09] <eddieq> ls
[17:28]  * rtg -> lunch
[18:01] <BenC> rtg: I'm going to be working on linux-ppc for saucy today and tomorrow
[18:02] <BenC> rtg: any caveats I should be aware of?
[18:02] <rtg> BenC, 3.9 or 3.10 ? I've got an unstable branch for 3.10. we'll likely have time to adopt 3.11 before release.
[18:03] <BenC> rtg: Where do you suggest I start? 3.10 branch?
[18:03] <BenC> If 3.10 holds me off from uploading, I'll start with 3.9
[18:03] <rtg> BenC, yeah, its in pretty good shape (though it won't boot on my laptop)
[18:03] <BenC> Ok, I'll work from there and see what I'm in for
[18:45] <cking> rtg, i'm getting "Error: Unable to list kernel events" with the lttng enabled grouper kernel when I invoke "lttng list -k"
[18:49] <rtg> cking, ok, I'll have a look tomorrow. 
[18:50] <cking> rtg, I'll poke around with it a bit more and see what's up
[18:50] <rtg> cking, its late. it can wait until your tomorrow :)
[18:50] <cking> yup, that's true 
[18:51] <cking> also I just get a blank screen, not sure if that's intended :-(
[18:51] <rtg> cking, using the raring daily ?
[18:52] <cking> yep, daily image + the saucy kernel, I did roll in some updates, so who knows what's causing it
[18:52] <rtg> hmm
[18:53] <cking> indeed hmm, most curious
[18:57] <cking> rtg, which version of lttng was added into grouper?
[19:02] <rtg> cking, should be tip of git://git.lttng.org/lttng-modules.git (or close to it)
[19:02] <cking> ta
[19:22] <cking> rtg, my fail, I installed the zImage manually but didn't install the kernel image .deb which has the lttng modules - doh, anyhow, got it to work: http://paste.ubuntu.com/5717758/
[19:23] <rtg> cking, oh cool. I didn't think about it being a module
[19:25] <cking> rtg, do you have a Nexus 7 then?
[19:25] <rtg> cking, yep
[19:25] <rtg> cking, but I've only installed the zimage
[19:27] <cking> rtg, ok, well, can you install the kernel .debs and sanity check that they look fine - I had to pull in wireless-crda, not sure if that makes sense to me
[19:28] <rtg> cking, ah, unnecessary package dep. I'll fix that.
[19:29] <cking> rtg, ok, cool, maybe worth you looking at what else dpkg says, I lost my scrollback so I can't recall all the output it spewed out
[19:29] <rtg> cking, no problem. its on my todo list for tomorrow.
[19:29] <cking> cool, me -> EOD
[19:29] <rtg> I'm close to EOD myself
[20:26]  * rtg -> EOD
[21:51] <houkouonchi-work> anyone know why installing a linux-image package would not update the symlinks?  http://pastebin.com/raw.php?i=cyiaYFbF
[23:24] <houkouonchi-work> damn its dead in here =(