/srv/irclogs.ubuntu.com/2012/05/01/#ubuntu-kernel.txt

=== Edgan_ is now known as Edgan
ayan_is tangerine down?00:42
=== ayan_ is now known as ayan
bjfayan: yes00:42
bjfayan: more like, it's unreachable at this time00:43
ayanheh.  okay.00:43
* ayan will retry later.00:43
bjfayan: we think it's a networking issue and since most of IS is in oakland now ...00:43
ayanoh!00:43
bjfayan: yup, not likely to get fixed anytime soon00:44
ayanokay -- i need to build kerel with some firewire patches from upstream.00:44
* ayan will slum it and use his own machine.00:44
* apw yawns08:07
* xnox passes a cup of Dolce Gusto Grande coffee to apw 08:17
apwhmmm that sounds rather nice08:17
ohsixlots of sugar coffee08:18
apwhasn't been through a cat has it ?08:18
ckingapw, i've got this in my sources.list: http://ppa.launchpad.net/webupd8team/java/ubuntu09:43
apwdileks, thanks for the emails with the testing results, that is good feedback thanks11:56
dileksapw: yeah. unfortunately, testcase scripts are rare for overlayfs. but the one from jordi I liked very much12:02
dileksmaybe, I should mention that squashfs-tools are required12:03
dileksapw: will you send your inode_only_permissions stuff (again) plus 3.4 fixes as a series to miklos and linuxfs-devel ML?12:07
apwdileks, thats the plan indeed, want to do that today12:07
dileksgood12:07
dileksyou can give me a pointer to ubuntus live-system framework?12:08
apwtgardner, ogasawara, am looking at the quantal build failure12:08
tgardnerapw, didn't know there was one yet.12:08
apwlacking a build depend on flex by the looks of it12:09
dileksmaybe I tease dba on #debian-live with overlayfs12:09
apwdileks, i beliebe we use live-builder for most of it12:10
dileksOK12:11
apwtgardner, resolve_symbol_wait() implies we waited for the module init12:30
apw                printk(KERN_WARNING "%s: gave up waiting for init of module %s.\n",12:30
tgardnerapw, yeah, was just looking at kernel/module.c12:31
apwtgardner, in init_module we call do_mod_ctors() which looks to be where the module inits are called, then we call wake_up(&module_wq) only after we have done that and marked it live, so i think module_init(xx) has been called12:33
tgardnerapw, actually, that only makes sense. it just about _has_ to be that way, else nothing would work.12:33
apwcirtainly it would be hard to write anything which initialised anything ... so i tend to concur it has to be intended12:34
tgardnerapw, I don't think do_mod_ctors(mod) calls the module init function. it looks like that is the job of do_one_initcall() 'cause thats the only place that an error return is recognized.12:37
apwtgardner, yeah same logical place either way12:42
tgardnerapw, right.12:43
tgardnerapw, its like they've implemented the ability to call C++ constructors, but not used it anywhere.12:43
tgardnerthere must be some other kind of constructor12:43
apwtgardner, its do_one_initcall, as apparently there can only be one initcall per module12:46
tgardnerapw, that is also correct, lest you incur a linker error12:46
ogasawaraapw: thanks for fixing up the build failures, am curious why the test builds didn't see the same error13:05
ogasawaraapw: will get it uploaded13:05
apwogasawara, already uploaded and building13:06
ogasawaraapw: ah cool, thanks13:06
apwogasawara, we install the builddeps at chroot build time13:06
apwand so we never see this kind of thing, its something we need to think about probabally13:07
apwhow to best do it and still be quick, perhaps have some virgin chroots which we can use13:07
apwfor that13:07
apwogasawara, bah the archive is inconsistant for i386 right now, somethign wrong with docbook-utils ... i suspect we need to wait a bit and retry it13:10
ogasawaraapw: ack13:10
apwgiven that part of your build was ok i think, if not then we'll want to disable docs for a bit13:10
apwogasawara, just confirmed your 1.1 got past this, so it may be transitional ...13:11
ogasawaraapw: yep, it would appear so13:11
tgardnerogasawara, apw: shouldn't we be uploading to -proposed ? that way we can get all of the components built, then just pocket copy.13:14
apwas far as i know that is only safe in freezes13:15
tgardnerapw, actually, I think its meant to be policy for Quantal.13:15
tgardnerprolly should ask cjw13:16
ogasawaratgardner: I'll follow up with the release team13:17
tgardnerogasawara, Rick has proposed that the release pocket always be installable. given our upload order we rarely have issues with that, but it might be simpler to just upload to -proposed and get everything built.13:19
ogasawaratgardner: yep, it was easier with proposed as we'd just shove all the packages up at the same time13:19
* tgardner notes the combination of mumble+pulseaudio consumes 55% of the CPU whilst doing absolutely nothing.13:22
ogasawaratgardner: cjwatson confirmed that for now while the archive is still settling it doesn't matter much if we upload to the release pocket or -proposed13:26
ogasawaratgardner: once it does settle though, we should go the route of uploading to -proposed first13:27
tgardnerogasawara, ack13:27
dileksapw: its live-build not -builder. dunno if (3.0~a24-1ubuntu1) is recent enough14:20
dileksdebian/sid has live-build (3.0~a47-1) 14:20
dileksis there a repo containing higher versions of live-build/live-boot?14:28
dilekshttp://nopaste.snit.ch/13691414:30
* ogasawara back in 2014:36
ckingtgardner, here are some notes I crufted up yesterday: http://zinc.canonical.com/~cking/fs-tests/ureadahead-notes.txt14:57
tgardnercking, thanks14:57
* cking slips off early today, started at 7am...14:59
apwbjf, yes things going well on that front16:28
apwbjf, but i've bust my machine here :/16:28
apwi can hear you but the load on my machine is over 20, so i am not going to be talking to you for a bit16:29
apwtill i work out what the hell i did16:29
bdmurraycould somebody look at bug 922647 and the ata error messages there?  are those indicative of a hardware problem or maybe a driver?16:30
tgardnerbug #92264716:37
bdmurrayhttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/99264716:41
ubot2Launchpad bug 992647 in ubiquity "Problema ao instalar ubunto no HD" [Undecided,New]16:41
apwbjf, recovered, recursive ssh runes are ... BAD16:42
tgardnerapw, doh !16:42
bjfheh16:42
apwload hit 48 before i got it under control, perhaps 20m of paging like a pig16:43
tgardnerbdmurray, what little I've discovered indicates it is a drive issue: http://shadowm.rewound.net/blog/archives/206-Giving-Debian-Wheezy-another-whirl,-and-an-unpleasant-surprise-from-Reicore.html16:49
bdmurraytgardner: I don't see any media errors in this bug report which is typical for drive issues16:52
tgardnerbdmurray, hell if I know. I'm not skilled at parsing ATA noise16:52
bdmurrayhttps://ata.wiki.kernel.org/articles/l/i/b/Libata_error_messages.html16:53
tgardnerbdmurray, repeated instances of 'failed command: READ FPDMA QUEUED' followed by 'hard resetting link' don't seem too healthy to me.16:55
bdmurraytgardner: sure but it continues to report DRDY16:55
bdmurraythe wiki pages mentions 'try booting with 'pci=nomsi' or 'acpi=off' or 'noapic'' for timeouts16:56
bdmurraymaybe I'll have them try that16:56
tgardnerbdmurray, works for me.16:57
JanCsomebody should write a tool to interpret kernel/driver/hardware errors like that...  ;)17:13
JanCtgardner: I had a drive issuing such "hard resetting link" messages for some time, now it's (almost) dead (but strange enough, SMART never reported anything wrong...)17:14
greearbIt seems that if you have a USB stick in the machine when booting the live-cd, it will not mount that USB stick untill you remove it and re-install it.  Anyone know if there is some tool/script that can cause it to mount w/out physically unplugging/plugging the USB key?17:19
JanCgreearb: you could probably run "sudo udevadm trigger"17:22
JanCor use mount, udisks, GParted or the udisks GUI frontend17:22
apwgreearb, udisks probabally17:23
greearbthanks..will try that17:23
JanCalso depending on how you wnat it mounted17:23
greearbjust want it to show up in /media/17:23
JanCI think the udevadm command will cause the same events as if it were unplugged & replugged17:25
JanCat least from the GUI apps PoV17:25
greearbno luck17:37
=== tgardner is now known as tgardner-lunch
=== tgardner-lunch is now known as tgardner
slangasekapw: ping19:31
apwslangasek, hi19:32
slangasekapw: hey there!  ogasawara was just telling me that aufs was re-enabled in the kernel for precise at the last minute?19:32
slangasekapw: was the plan for us to use that as the unionfs in precise for the liveCDs?  Because we didn't19:33
apwslangasek, it was around the betas indeed.  there was concern from the lxc people that they wanted a fallback if they couldn't cope with overlayfs19:33
slangasekok19:33
apwslangasek, we had used overlayfs for all the tested CDs so no not intended that we'd change19:33
slangasekah, ok then19:33
apwas far as i know noone is using aufs for anything19:34
slangasekso I shouldn't be fretting over this and trying to change it for .1 ;)19:34
apwi don't think so no19:34
slangasekok19:34
slangasekany chance of overlayfs getting fixed to stop claiming it supports inotify, btw?19:34
slangasek(wouldn't fix all our liveCD bugs, but it would fix some of them)19:34
apwslangasek, i made a version which claimed it didn't, userspace didn't like it much vomitting errors everywhere19:35
slangasekoh, neat19:35
slangasekso much for that then19:35
apwoverlayfs may get some support for inotify if i get time, but it won't fix anything which uses fstat on already open files19:35
apwsuch as tail does19:35
slangasekmm?  tail prefers to use inotify19:36
slangasekor is fstat() separately broken?19:36
apwyes, but it uses a specific combination which doesnt work out19:37
apwit opens the file, asks for inotify, we tell it the file changed, it fstats the old file, sees the notify was a 'lie' and does nothing19:37
apwa side effect of the known posix violation that overlayfs has which makes it simple and performant19:38
apwso none of the calls are broken per-see just the meaning is subtle altereed,  if tail used 'stat' on the pathname it would work just fine with my patches19:39
slangasekright19:40
apwobviously not without any working inotify as we have now19:40
apwi n19:40
slangasekperformance over posix - grr19:40
slangasek:)19:40
apwwell its less performance and more simpliciyt.  aufs and vfs-union-mounts are massive as a result of having the entire posix implementation19:41
apwand they can't get into the kernel, somethinig small enough to be acceptable seems to be19:41
apwfialing cause its not complete enough, its ... a problem19:41
* slangasek nods19:42
apwif upstream was more helpful in guiding direction rather than just being "ick vile no" to everything we might make some more progress19:43
slangasekbut then you'd be contributing upstream... and we can't have that now can we ;)19:43
apwslangasek, tsk19:59
apwslangasek, its a good job the 5 patches i pushed today don't count (at least when we are measured_19:59
slangasek:-)19:59
bdmurrayjsalisbury: I was looking at ubuntu bugs with the same title by the same reporter the other day20:24
bdmurrayjsalisbury: eg bug 820031 and bug 82004020:25
ubot2Launchpad bug 820031 in linux "WARNING: at /build/buildd/linux-2.6.38/net/mac80211/rx.c:2881 ieee80211_rx+0xad/0x1d0 [mac80211]()" [Undecided,Incomplete] https://launchpad.net/bugs/82003120:25
ubot2Launchpad bug 820040 in linux "WARNING: at /build/buildd/linux-2.6.38/net/mac80211/rx.c:2881 ieee80211_rx+0xad/0x1d0 [mac80211]()" [Undecided,Incomplete] https://launchpad.net/bugs/82004020:25
=== tgardner is now known as tgardner-afk
=== tgardner-afk is now known as tgardner
* tgardner -> EOD20:50
=== yofel_ is now known as yofel
bjfogasawara: supposedly gomesia is back22:12
bjfs/gomesia/gomeisa/22:13
=== yofel_ is now known as Guest77193
=== elmo_ is now known as elmo
=== Madkiss_ is now known as Madkiss
=== _Traxer is now known as Traxer

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!