=== defendguin [n=supertux@cpe-72-181-7-135.houston.res.rr.com] has joined #ubuntu-kernel === pkl_ [n=phillip@unaffiliated/pkl/x-764568] has joined #ubuntu-kernel === jml_ [n=jml@203-113-250-169-static.TAS.netspace.net.au] has joined #ubuntu-kernel === zdzichuBG [i=matthew@ogrody.nsm.pl] has joined #ubuntu-kernel === RemoteViewer [n=555@stan.physik.fu-berlin.de] has joined #ubuntu-kernel === sdrik [n=sdrik@ip-93-4.dsl.newel.net] has joined #ubuntu-kernel === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-kernel === rtg [n=rtg@rtg.theglobal.net] has joined #ubuntu-kernel === blenderhead001 [n=blenderh@adsl-068-209-133-121.sip.jax.bellsouth.net] has joined #ubuntu-kernel === rtg [n=rtg@rtg.theglobal.net] has joined #ubuntu-kernel === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-kernel === jml [n=jml@121.44.219.152] has joined #ubuntu-kernel === rtg [n=rtg@rtg.theglobal.net] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === mdomsch [n=mdomsch@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === scarter [n=scarter@24-247-21-19.dhcp.trcy.mi.charter.com] has joined #ubuntu-kernel === akio [n=lucifer@250.203.189.72.cfl.res.rr.com] has joined #ubuntu-kernel [05:49] hello === poningru [n=poningru@adsl-074-245-140-197.sip.gnv.bellsouth.net] has joined #ubuntu-kernel === n2diy [n=darryl@ppp-42d42804.wlks.losch.net] has joined #ubuntu-kernel === gicmo_ [n=gicmo@p5491DF84.dip.t-dialin.net] has joined #ubuntu-kernel === mdomsch [n=mdomsch@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel === m0rg0th [n=manugarg@220.225.228.97] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === ivoks [n=ivoks@1-178.dsl.iskon.hr] has joined #ubuntu-kernel === elmarco|away is now known as elmarco === Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-kernel === ivoks [n=ivoks@backup.grad.hr] has joined #ubuntu-kernel === keturn [n=kevint@pdpc/supporter/sustaining/keturn] has joined #ubuntu-kernel === Lure [n=lure@external-1.hermes.si] has joined #ubuntu-kernel === keturn [n=kevint@pdpc/supporter/sustaining/keturn] has joined #ubuntu-kernel === jml [n=jml@121.44.219.152] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === EtienneG [n=etienne@ubuntu/member/EtienneG] has joined #ubuntu-kernel === elmarco is now known as elmarco|away === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === scarter [n=scarter@24-247-21-19.dhcp.trcy.mi.charter.com] has joined #ubuntu-kernel === mdomsch [n=Matt_Dom@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel === mdomsch is now known as mdomsch_qtr [03:18] BenC: ping? [04:25] Keybuk: pong === elmarco|away is now known as elmarco [04:27] hey BenC [04:27] hey [04:28] BenC: what would be the estimated timeline for getting http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d9aca22cf443f5ed77d15a320abbab055ae4a976 into our kernels? [04:29] BenC: i will pretty soon need 2 things from you.... pull from gfs2-nmw tree and export the 3 symbols i need for gfs1. [04:29] BenC: but i will give you a ping when it's time. I need 2 more fixes to hit gfs2-nmw [04:29] fabbione: why isn't gfs2-nmw in 2.6.22? [04:30] I really wanted to avoid pulling in other trees, especially when there's time to push things upstream still [04:30] BenC: not all of it yet. but i need it before otherwise new userland doesn't build/work [04:30] Keybuk: Should be next upload, hopefully on or before Friday [04:31] BenC: i understand, but there is a change on dlm headers and gfs2 headers that i need to propagated to build the new userland.. otherwise i am blocked. [04:31] BenC: i still want these 2 extra fixes in before you pull [04:31] Keybuk: We need to talk about bug #115616 [04:31] BenC: also.. i saw kernel.u.c [04:32] fabbione: any assurance that those changes will be pushed upstream for 2.6.22 or are we stuck with the divergence in gutsy? [04:32] fabbione: you might have an account on kernel.u.c, try ssh to zinc.u.c [04:32] BenC: they will be pushed upstream for sure.. when it's something i can't say right now, but i can ask [04:32] you can clone, and put whatever changes you want to push to me there [04:32] BenC: i already have an account there [04:32] how do i setup a tree that shows up in gitweb? [04:33] fabbione: are you in kernel_team group? [04:33] i was planning to put gfs2/ocfs2 and gfs1 team [04:33] i guess so... checking [04:33] if so, mkdir /srv/kernel.ubuntu.com/git/fabbione/ [04:33] then clone a tree, mv newtree/.git /srv/kernel.ubuntu.com/git/fabbione/fabbione-gutsy.git [04:33] yes i am [04:34] BenC: ok :) [04:34] fabbione: you might want to look at 115616 too, since it involves evms, and I could use some feedback [04:35] BenC: i saw that bug. i will need to look at whatchanges [04:35] The basic issue is described here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/115616/comments/3 [04:35] BenC: not sure i can get there by today [04:35] Mainly that I want to ditch the horrible bd_claim patch, but we need a way for users not to have broken systems that were based on the work around [04:36] BenC: ah, ok, it was a patch we dropped? [04:36] Keybuk: yeah, we've been carrying it around for a few releases, and it really is evil, and in actuality creates more room for breakage than it fixes [04:37] agree [04:37] the evms FAQ doesn't offer a better solution though [04:37] Actually, it does, which is to convert to evms totally, or ignore devices that evms isn't using [04:37] fixing it is easy. Move partition discovery out of the kernel and just use devmapper devices. [04:37] fsvo easy, that is. [04:38] Mithrandir: actually, that doesn't help, since evms would still fight over the devmapper devices [04:38] claim applies to the devmapper ones too [04:38] it still tries to lock the physical block dev, which is the problem [04:38] BenC: ok.. i have the tree cloned as you say... now? [04:38] evms for all => well, if you're using evms, you're doomed anyway [04:39] fabbione: "mv newtree/.git /srv/kernel.ubuntu.com/git/fabbione/fabbione-gutsy.git" [04:39] we actually have udev set to prefer to *not* use the evms-supplied devices right now [04:39] BenC: done that === Mithrandir will not be very happy if somebody decides to break all his systems. [04:39] evms to exclude => it doesn't seem easy to do that either, since we don't know what to exclude or not? [04:39] fabbione: the main gitweb page is hourly generated...let me run the script [04:40] BenC: ok [04:40] fabbione: shows up now [04:40] oh neay [04:40] neat [04:40] Keybuk: make it not lock the whole device unless it contains an evms volume, and if so, see if it can just claim a partition? [04:40] how do i setup the repo description? [04:40] fabbione: vi ubuntu-gutsy-gfs2.git/description [04:40] Mithrandir: do you know how to do that? [04:41] Keybuk: a) get drunk, b) dive into the evms source code. [04:41] it's a big and scary chunk of code. [04:41] talking to upstream might be a good start, though [04:41] given that upstream haven't felt inclined to fix it yet, I doubt they'll be responsive [04:42] yeah, their FAQ is sort of "eh, deal with it" [04:42] depends.. I've found them very good in the past when I've managed to catch their attention. [04:42] BenC: ok.. all done.. can you regenerate the page? [04:42] BenC: coolness it works [04:43] fabbione: weez cookin' now === Keybuk never understood why evms creates all those devmapper'd copies anyway [04:47] I think we have two choices: [04:47] - apply the bd-claim patch [04:47] - stop supporting evms [04:54] Keybuk: what's the fallout from option 2? === bleinmono [n=toffel@ppp85-141-151-191.pppoe.mtu-net.ru] has joined #ubuntu-kernel [04:55] upsetting some users === AlinuxOS [n=vsichi@host122-198-dynamic.8-87-r.retail.telecomitalia.it] has joined #ubuntu-kernel [05:03] is there any way we can make option 2 work without asking users to hack a config file? [05:07] BenC: let see if the git-send-pack works :) [05:07] yeps [05:07] gfs1 tree updated... [05:09] BenC: the gfs2 author is in vacation this week. there are a set of patches in there that will be pushed to Linus (like the 2 i am waiting for), others will make .23 for sure [05:10] BenC: if you really really feel unconfortable with that, i can start diverging userland, but it's just shifting one problem from one place to another [05:10] BenC: also note that gfs2 tree touches "only" dlm and gfs2.. meaning none of the core kernel functionalities [05:11] and not stuff people will use regularly [05:11] fabbione: that's good [05:11] anyway. i will let you take a breath on it and ping you once the other fixes are in === scarter [n=scarter@24-247-21-19.dhcp.trcy.mi.charter.com] has joined #ubuntu-kernel [05:23] BenC: how do you mean? [05:24] Keybuk: I mean our work arounds include: 1) uninstall evms, 2) edit evms.conf to ignore the disks, 3) switch to evms completely [05:25] none of which seem easy to do with update-manager or something [05:25] the problem with 2) is that it's not obvious to me why evms doesn't just do that by default [05:26] (ignore volumes without evms metadata) [05:26] yeah, that does seem pretty broken [05:26] the people having the problem so far are not even using evms at all [05:26] it's just being stupid [05:26] yeah [05:26] we installed it by default once [05:26] yay us [05:26] which release was that, dapper? === AvengerMoJo [n=alex@onenet.ximian.com] has joined #ubuntu-kernel [05:32] warty [05:32] +/** [05:32] + * activate_on_kernel_partition [05:32] + * The normal activation failed. If we're running on a 2.6 kernel, this could [05:32] + * be due to bd_claim, meaning the user may have a kernel partition mounted on [05:32] + * the same disk that we're trying to activate on. In this case, lets try to [05:32] + * activate the segment on top of the kernel partition instead of the disk. [05:32] + * The only things that change are the minor number for the target device and [05:32] + * the starting offset. [05:32] + * [05:32] + * If this succeeds, we must indicate that this segment is active on top of a [05:32] + * kernel partition, since it means certain other functionality cannot be used. [05:32] + **/ [05:33] sounds like it's supposed to work around things === scarter [n=scarter@24-247-21-19.dhcp.trcy.mi.charter.com] has joined #ubuntu-kernel [05:34] yeah, trying to work out exactly how === johanbr [n=j@JBrannlund.MathStat.Dal.Ca] has joined #ubuntu-kernel === gortiz [n=gortiz@88.87.105.4] has joined #ubuntu-kernel === AvengerMoJ1 [n=alex@onenet.ximian.com] has joined #ubuntu-kernel === pmjdebruijn [n=pmjdebru@home.pcode.nl] has joined #ubuntu-kernel === Lure [n=lure@89-212-19-55.dynamic.dsl.t-2.net] has joined #ubuntu-kernel === kylem_ [n=kyle@amnesiac.heapspace.net] has joined #ubuntu-kernel === lfittl [n=lfittl@212.41.228.52] has joined #ubuntu-kernel [07:21] what is the ti multimedia card reader bug number? [07:23] bdmurray: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/53923 [07:25] rtg: thanks === ivoks [n=ivoks@39-126.dsl.iskon.hr] has joined #ubuntu-kernel === bdgraue [n=bdgraue@dyndsl-085-016-087-054.ewe-ip-backbone.de] has joined #ubuntu-kernel === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel [07:56] I've never been bitten by the above bug, but I noticed SD cards no longer automount with the Gutsy kernel. They work fine after manually mounting, though. === __keybuk [n=scott@wing-commander.netsplit.com] has joined #ubuntu-kernel === __keybuk [n=scott@wing-commander.netsplit.com] has left #ubuntu-kernel [""] === drez22 [n=elementz@pD9E569D0.dip.t-dialin.net] has joined #ubuntu-kernel === elementz [n=elementz@pD9E569D0.dip.t-dialin.net] has joined #ubuntu-kernel === elementz [n=elementz@pD9E569D0.dip.t-dialin.net] has joined #ubuntu-kernel === doko [n=doko@dslb-088-073-100-164.pools.arcor-ip.net] has joined #ubuntu-kernel === m0rg0th [n=manugarg@219.64.120.181] has joined #ubuntu-kernel [08:38] rtg: is dmidecode helpful with bugs like 116185? [08:41] bdmurray: /proc/acpi/dsdt is more helpful, but in reality, most bugs like that are BIOS bugs [08:41] dsdt will help find out [08:43] BenC: okay, thanks === allee [n=ach@lapex-mcallee.mpe.mpg.de] has joined #ubuntu-kernel === bleinmono [n=toffel@ppp85-141-151-191.pppoe.mtu-net.ru] has joined #ubuntu-kernel === n2diy [n=darryl@66.212.43.129] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === cassidy [n=cassidy@host-85-27-113-193.brutele.be] has joined #ubuntu-kernel === mdomsch [n=Matt_Dom@cpe-70-113-73-138.austin.res.rr.com] has joined #ubuntu-kernel === elmarco is now known as elmarco|away === macd [n=d@adsl-35-254-87.msy.bellsouth.net] has joined #ubuntu-kernel === racarr [n=robb@pool-71-163-244-36.washdc.fios.verizon.net] has joined #ubuntu-kernel === bdgraue [n=bdgraue@dyndsl-085-016-087-054.ewe-ip-backbone.de] has joined #ubuntu-kernel