/srv/irclogs.ubuntu.com/2010/05/27/#ubuntu-kernel.txt

cndRAOF: yep, I confirmed through testing earlier :)00:45
cndupgraded the kernel and it still worked00:46
Sarvattcnd: sure you aren't just using nv now?00:57
RAOFI'm using nouveau.00:59
RAOFI can tell, because my system both suspends *and* resumes.01:00
lifelesslol01:03
bjfakgraner, just saw that the kernel team meeting minutes showed up on The Fridge01:27
=== kamal is now known as kamal-away
=== panda is now known as Guest56210
jk-pgraner: ping?02:35
=== vanhoof[bbiab] is now known as vanhoof
RAOFcnd: Hm.  I was missing some important context there.  You mean to say that you're using the Maverick 2.6.34 kernel *on Lucid* and nouveau is working?  Can I get an Xorg.0.log?02:44
JFoRAOF, Tim is using it too and it works03:27
JForather tgardner03:27
* JFo heads off to bed03:27
cndRAOF: correct04:16
cndlet me send you an email with my log04:17
* smb awakens08:06
ckingmorning smb08:07
smbmorning cking 08:07
amitkmorning guys08:08
* smb waves to amitk 08:08
cooloneysmb: cking and amitk morning08:14
smbHey cooloney 08:14
cooloneysmb: GrueMaster tested lucid security kernel for imx5108:14
cooloneyit boots 08:14
smbOk, so I can tick that off08:14
cooloneysmb: but i just wander, is this security updates rebased on our lucid latest fsl-imx51 code?08:15
smbcooloney, Just for completeness, though likely less important. Anything on the Kamric fsl-imx51. Think that needs different hw08:15
cooloneyhttp://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=shortlog;h=refs/heads/fsl-imx5108:16
smbcooloney, No there are some changes that were never uploaded in them (see one of the notes in the original email)08:16
smbThose will need to wait until I do a rebase for proposed uploads08:16
cooloneysmb: ok, understood. hehe08:17
cooloneysmb: since GrueMaster said the eth0 ifdown issue is still there in the security kernel. 08:17
smbSo it certainly might be. :)08:18
smbs/might/will/08:18
cooloneysmb: and GrueMaster will test Karmic kernel when he wake up 08:20
smbcooloney, Ah ok, most excellent08:20
ikepanhcapw: smb: I am going to submit a talk on Taiwan conference for open source coders. current plan is talking about how to packaging ubuntu kernel (ex:git,base,delta... etc), regression (and why we take it serious). You are the expert of this. Can you help me review after I finish the slide for it?08:38
smbikepanhc, Sure will do08:38
ikepanhcsmb thanks :D08:39
apwikepanhc, yep08:40
ikepanhcapw: thanks :) it may take me 1 or two weeks08:41
krauthi09:47
krautanyone an idea what's going wrong while umounting cifs shares? http://pastebin.com/dvwnH51h09:47
krautit's reproduceable09:47
cooloneyikepanhc: that's a great topic09:57
cooloneyikepanhc: can you share your slide for me as well?09:57
ikepanhccooloney: sure, after I finish it09:58
cooloneyikepanhc: maybe next time we can give this kind of speech in Shanghai or Beijing. 09:58
ikepanhccooloney: I plan to use it on COSCUP and UHS09:58
smbkraut, Hm, I am not sure. Sounds a bit familiar. Have the feeling there might be something in latest stable. Let me look09:59
krautthanks10:00
krautsearched in launchpad but found nothing. via google i found one entry but when i clicked on it, i got a 40410:01
krautreally strange10:01
smbkraut, commit 793c338bac6fa1fb94504a0346f43e87d24b5daa10:01
smbAuthor: Jeff Layton <jlayton@redhat.com>10:01
smbDate:   Tue May 11 14:59:55 2010 -040010:01
smb    cifs: guard against hardlinking directories10:01
smb    10:01
smb    commit 3d69438031b00c601c991ab447cafb7d5c3c59a6 upstream.10:01
apwsmb, YEEKS10:01
smb    When we made serverino the default, we trusted that the field sent by the10:01
smb    server in the "uniqueid" field was actually unique. It turns out that it10:01
smb    isn't reliably so.10:01
smb    10:01
smb    Samba, in particular, will just put the st_ino in the uniqueid field when10:01
smb    unix extensions are enabled. When a share spans multiple filesystems, it's10:01
kraut+ * uh oh -- it's a directory. We can't use it since hardlinked dirs are10:01
kraut+ * verboten. 10:01
krautrofl10:01
smb    quite possible that there will be collisions. This is a server bug, but10:01
smb    when the inodes in question are a directory (as is often the case) and10:01
krautdenglish for runaways10:01
smb    there is a collision with the root inode of the mount, the result is a10:01
smb    kernel panic on umount.10:02
krautam i the only one who hits that bug!?10:02
smbMaybe not, otherwise it would not have been fixed. But here, yes denke schon10:03
krautthat must be verboten! ;)10:04
smbVery much :)10:04
krauthmmm, i need the fsck a workaround10:04
krautaaah, i think i got it10:05
krautbrb, rebooting10:05
cooloneyapw: will the local "fdr binary-omap" command  run d-i/udeb stuff?10:06
cooloneyapw: because i can use my cross compile to build a kernel package10:06
cooloneybut it still failed in our PPA native builder10:06
ikepanhccooloney: is PPA supported ARM arch?10:07
apwcooloney, no it won't   fdr binary-arch does that10:07
apwcooloney, and even then you might need to touch /CurrentlyBuilding in your chroot10:08
cooloneyikepanhc: oh, yeah, it will send it to our ARM hardware builder because in our package arch=armel10:08
cooloneyapw: ok, this answer helps me a lot10:09
cooloneyso i can test it locally before i dput it to ppa for building10:09
apwikepanhc, in some PPAs it can be enabled, not generally10:09
cooloneythe ARM building will cost me 6 hrs to know the result10:09
apwcooloney do you know about sbuild ?10:10
apwthat uses qemu to emulate arm in an arm chroot, so you use the native compiler10:10
apwthat takes about 2 hours a build for me10:10
cooloneyapw: wow, cool man, i just heard the name of sbuild or pbuild10:13
cooloneyapw: is there any wiki about that?10:13
cooloneyi really wanna to setup such environment10:13
apwcooloney, not that i know about, i got pointed to it vaguly recently.  i installed 'ubuntu-dev-tools'10:13
krautsmb: fixed it with using the mount-option "noserverino". thanks for that info10:14
apwmk-sbuild --arch armel maverick10:14
apwthen that makes this special armel chroot10:14
apwthen you can make a the source package and build it with10:14
apwsbuild -d maverick-armel *.dsc10:14
smbkraut, Welcome. And the fix should get into one of the next updates10:14
apwit does take about 2x the time it takes to do a crosstools build, but it really uses the arm compilers etc10:15
cooloneyapw: ok, let me try that. how's your build machine configuration? i guess it is very powerful10:15
cooloneyand it still needs 2 hrs?10:15
krautsmb: that's fine10:15
apwits a 4x10:15
apwcooloney, you could do the build on emerald though10:15
cooloneyapw: but we might need ask for installing some package as root10:16
cooloneysudo apt-get install ubuntu-dev-tools10:16
cooloneyin emerald10:16
apwcooloney, that is possible10:16
apwwhat you got to compile on locally ?10:16
cooloneyapw: normally, i cross compile the kernel for arm arch such as fsl-imx51 and ti-omap410:18
cooloneyfdr clean && export $(dpkg-architecture -aarmel) && CROSS_COMPILE=arm-none-linux-gnueabi- fdr binary-omap410:19
cooloneyapw: with this command10:19
cooloneyit will generate a kernel package in the parent dir10:19
apwcooloney, yeah, but i've not found that works when you make the tools package etc, and as you found does not make the udebs10:19
apwi've used that form myself for most of lucid10:20
cooloneybut i uploaded my source package to PPA, it failed to build because of d-i/udeb10:20
cooloneyright10:20
cooloneyapw: agree, 10:20
cooloneyapw: so sbuild is the solution maybe, right?10:21
apwcirtianly it worked well for me, though its slower by some margin than crossbuilds, its some 3x the speed of a PPA for me10:22
apwand on emerald it would likely be faster yet10:22
cooloneyapw: ok, i will try it. at least it is much faster than PPA10:24
cooloneyapw: what's kind of CPU and memory do you have in your build machine running sbuild10:24
apwcooloney, emerald is on karmic and the tools don't exist10:30
amitksmb: going to linuxtag?10:31
smbamitk, Yep10:31
amitkregistered already?10:31
smbamitk, Err, doh! nope10:32
smbamitk, Is there actually need? I only see registration for those who want to exhibit10:33
amitksmb: dunno. I am thinking if I should go. Some interesting talks...10:34
smbamitk, Yeah, and its not too far from my place. :)10:34
smbamitk, The hotel question was open, which reminds me to ask again10:35
=== smb is now known as smb-afk
cooloneyapw: thanks a lot, building in sbuild now11:15
apwcooloney, awsome ... 11:15
apwcooloney, hope its less than 6 hours11:15
amitkcooloney: it's probably worth adding to kernelmaintenancestarter page for arm flavours11:16
cooloneyamitk: right, will do soon11:18
cooloneyapw: yeah, my machine is 4 core and 4G ram 1TB disk11:18
apwcooloney, so i'd guess more like 2 hours max11:18
apwwhich is a 3 builds a working day instead of one11:18
cooloneyapw: great, man. hehe11:21
ogradont forget that you build for lucid, not maverick ;)11:46
ogra(mk-sbuild --arch armel lucid)11:47
cooloneyogra: yeah, i am build for lucid11:49
cooloneyapw: did you see this before? building in sbuild stops at 'Unpack source', doesn't move on11:58
cooloneyhttp://pastebin.ubuntu.com/440341/11:58
apwcooloney, nope11:58
cooloneyapw: need i setup gpg key in sbuild?11:59
apwthat will take a while but not more than minutes11:59
apwi didn't no11:59
cooloneyok, 11:59
cooloneyapw: so weird. it stops there for ever12:05
apwthere should be a process doing something12:12
apwwhat does it seem to be doing12:12
cooloneydpkg-source is eating my 100% cpu from my 'top'12:14
Kanohi, how to DISABLE building perf tools?12:14
* cooloney reboots and try again.12:17
Kanohow about adding a ringbuffer patch?12:23
Kanohttp://intellinuxgraphics.org/h264.html12:23
apwKano, do_tools=false i think12:30
Kanowill try12:30
apwKano, check debian/rules/0-*12:30
apwyou can add that to your amd64.mk and i386.mk12:31
apwKano, the kernel components are in maverick already according to that page12:32
Kanohmm12:32
Kanobut for 2.6.34 rc5 you needed a patch12:33
Kanoand this does not fully apply now12:33
apwhrm, i see, missread the stupid page. i suspect its aimed to .35, and we'll get it then12:34
Kanobasically the rejects could be fixed12:36
Kanojust you have to change a bit more, a workaround was active in one file12:36
apwKano, its a pretty massive patch, not something we'd be that interested in worrying about till we get to our base release12:37
apwpgraner, we have a number of blueprints without priority, and none of us seems to have the touch to change them12:38
pgranerapw: nice12:38
Kanoit would be an interesting patch for the edgers ppa12:38
apwpgraner, any idea how we get the ability ?12:38
Kanoone thing i struggled last time was when i used12:39
pgranerapw: no, in the LP context blueprints are a black art... I'll give you a call in a few and we can walk thru them and I'll set12:39
Kanohttp://www.splitted-desktop.com/~gbeauchesne/libva/ironlake.patches/ubuntu.lucid/kernel/12:39
Kanothose patches are basically against lucid12:39
apwpgraner, this view http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.html has a good view into them12:39
Kanoi created the binary-headers too12:40
Kanobut12:40
apwKano, if X think they are of interest then there might be some point in doing them in edgers12:40
Kanowhy do they still need a patch?12:40
Kanolike12:40
Kanohttp://www.splitted-desktop.com/~gbeauchesne/libva/ironlake.patches/ubuntu.lucid/linux-libc-dev/12:41
Kanothis was not in the libc-dev12:41
apwKano, the split out headers are a subset and stuff not added in the correct way can go astray during stripping, indeed that is common with new stuff12:42
Kanothe same header is always shipped12:43
Kanohmm12:43
Kanomost likely the patch should be updated12:44
Kanoto patch directly the source12:44
Kanolooks a bit weird12:44
=== smb-afk is now known as smb
apwKeybuk, you about ?12:53
apwKeybuk, think i have a clean-ish patch to allow setting the kernel arguements, my debugging says its doing the right thing12:54
apwKeybuk, so what form do you want this to do testing12:55
ograapw, will it hand over console= options ? 12:58
apwogra, it hangs over literally everything on the command line12:58
apwhands12:58
apwno exceptions12:58
ogra(arm and mobile are eagerly waiting for a way to autospawn gettys on serial consoles via upstart, thats a requirement for it)12:59
ograthough its still not clear to me how to distinguish if you have multiple console= options, i wish the kernel would require enumeration for them13:00
ograapw, awesome :)13:00
apwhttp://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.html13:01
ogrageez, i didnt know devicetree was essential for maverick !13:01
ogra"mounting /proc and /sys automatically" oh sweet, we wouldnt need fstab anymore !13:03
Keybukapw: kernel in a ppa is always good13:04
abogani2cnd, apw: FIY I built lowlatency kernel on my PPA (https://launchpad.net/~abogani/+archive/broken) it is based on Lucid but for Maverick packaging is same. I can provide the patch (that is the contents of debian.lowlatency dir plus a little hack in debian/) or a git tree if you need. I hope that simplify your review work.13:17
pgranertgardner: ping13:32
tgardnerpgraner, yo13:32
apwabogani2, sure if you can point me at a git tree that would be great13:47
apwKeybuk, ack13:47
apwogasawara, i see your current tip is an abi bumper, but the abi is not bumpered13:47
apwogasawara, sorry not an abi bumper per-see, missing modules even13:49
abogani2apw: Sure but consider that the package in actual form don't include linux full source code copy so a fresh just cloned Maverick git tree could be deceivingly. Moreover should I use your ubuntu-debian.git as base? At the moment I have implemented, what seem to me, the Lucid way: so there are three directories debian/, debian.master/ and debian.lowlatency/.14:10
apwabogani2, don't worry about ubuntu-debian, i'll send you a pull request when thats ready to merge into there14:11
apwabogani2, but seeing the tree is very helpfil14:11
abogani2apw: Ok. Thanks.14:12
* abogani2 goes to prepare the git tree14:12
apwKeybuk, ok, the init argument handling is building in my green PPA: https://edge.launchpad.net/~apw/+archive/green/+packages14:17
apwKeybuk, and the union mount enabled kernel is still in purple: https://edge.launchpad.net/~apw/+archive/purple/+packages14:17
Keybukcool, can you mail me to remind me to test?14:18
cndapw: https://wiki.ubuntu.com/KernelTeam/KernelSimpleGuide?highlight=(request\-pull)14:24
apwKeybuk, email away14:31
pgranertgardner: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=56768114:37
ubot2Debian bug 567681 in btrfs-tools "please add -a to fsck.btrfs" [Wishlist,Open]14:37
cndKeybuk: do you know if we can remove the modalias for vga16fb now, or do we need to wait for some userspace changes?14:51
Keybukwell, you _can_14:51
Keybukthere will be consequences though14:51
Keybuka zillion screaming nvidia-glx users14:51
Keybukwe haven't done the bit that goes in its place14:51
cndKeybuk: ok, then we'll wait, thanks!15:05
cndcrimsun: will the hda powersave without popping fix be in maverick?15:05
cndjust want to double check15:05
=== jdstrand_ is now known as jdstrand
vanhoofif we had to guesstimate, when will 2.6.35 be released to the wild?15:21
cndvanhoof: I think kernel cycles average three months?15:22
cndso I would guess middle of august15:22
vanhoofcnd: cool15:22
vanhoofthank you15:22
bjfpgraner, just an fyi bug 586150 (comment #1)15:22
ubot2Launchpad bug 586150 in blueprint "The "Whiteboards" section of blueprints should be given more space (affects: 2) (heat: 12)" [Low,Triaged] https://launchpad.net/bugs/58615015:22
tgardnervanhoof, ogasawara estimated sometime in September15:27
vanhooftgardner: thanks15:28
JFocan I just say, I love it when i tell someone that they failed to respond on a bug and I expire it only to have them reopen it, fuss about it being closed, then go test the issue and tell me "oops, this is fixed, please close."15:39
JFomakes me crazy15:39
* tgardner wonders if jfo has noticed that half of all humans are below average15:39
JFoI have, and most of that half file kernel bugs it seems15:39
JFo:)15:40
JFocnd, wtf? re bug 58131215:43
ubot2Launchpad bug 581312 in linux (Ubuntu) "Unknown key fee[x] pressed with Dell Latitude XT2 (affects: 1) (heat: 20)" [Medium,Triaged] https://launchpad.net/bugs/58131215:43
cndJFo: ummm, what?15:44
JFodid you see the last comments15:44
cndyeah?15:44
cndJFo: what about them?15:46
JFoapparently nothing15:46
tgardnerlag, git log --pretty=oneline $*15:54
JFoamitk, you around?15:57
JFo<pitti> JFo, asac: someone added https://wiki.ubuntu.com/UbuntuARMTeam/ReleaseStatus/MaverickTasks?action=raw to maverick.cfg; should't that rather get into ubuntu-arm.cfg?15:57
JFo<pitti> it looks weird to distribute the ubuntu-arm WIs like that, but your call of course15:57
JFo^^ from #ubuntu-devel15:58
amitkJFo: shoot15:58
JFoamit, the above was what I wanted to show you15:58
smblag, To tell git the current top commit you could also use HEAD and HEAD~1 is the one before that and so on15:59
JFofrom pitti15:59
amitkJFo: that'd be Jamie filing new stuff15:59
ogasawaraapw: bah, forgot about missing modules when I built in fbcon16:00
JFoah16:00
ogasawaraapw: will get it fixed up16:00
smbogasawara, Heh, yeah. Probably want to do a ignore.modules instead of a modules.ignore...16:00
tgardnerlag, for example, 'git request-pull HEAD~1 git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git' assuming you have one commit in your local repo that you'd like to be pulled.16:00
lagOh okay16:01
ogasawarasmb: yah, I did the same for the last upload due to all the config tweaks16:01
lagThanks smb, tgardner16:01
vanhoofJFo: skype just told me about tomorrow ;)16:12
JFoheh16:13
=== kamal-away is now known as kamal
* bjf will brb16:53
kassahWhat's the best way to load a proposed kernel (I was requested to load 2.6.32.13 from proposed)16:59
kassahhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/51106616:59
ubot2Launchpad bug 511066 in linux (Ubuntu Lucid) (and 1 other project) "ModemManager: HP ev2210 Sierra MC5725 not detected (affects: 2) (heat: 18)" [Low,In progress]16:59
tgardnerkassah, 'wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.14-lucid/linux-image-2.6.32-02063214-generic_2.6.32-02063214_amd64.deb; sudo dpkg -i linux-image-2.6.32-02063214-generic_2.6.32-02063214_amd64.deb'17:03
kassahthanks =)17:04
ckingmanjo, you still around?17:06
manjocking, yeah17:06
manjocking, I think the problem is on my end 17:09
manjocking, let me restart mumble17:09
ckingmanjo, its at your end17:09
* bjf is back17:17
cndanyone have any ideas why when I run the following as root, it works, but when run by pm-utils when power is disconnected, it errors out with error 1:17:41
cndsetterm -blank 1 -powersave powerdown -powerdown 1 \17:41
cnd        < /dev/tty1 > /dev/tty1 2>&117:41
cndwhen run as root, I have to sudo su first, so maybe sudo is doing something extra?17:42
cndwhen pm-utils runs, it's running as root, no sudo17:42
cndit's driving me mad...17:43
jjohansencnd: environment variables?17:45
cndjjohansen: could be, I did a diff of the env output in each case17:45
cndnothing stood out as obvious17:45
tgardnercnd, you might ask kees, but its possible sudo is not granting the right CAPs17:45
cndtgardner: it seems like in this case sudo may have more privs than root somehow17:46
cndI'm going to strace it to see if I can find out exactly why it dies17:46
jjohansencnd: that can happen, a root process doesn't necessarily get all caps17:46
cndjjohansen: tgardner: strace FTW17:49
cndwrite(2, "setterm: $TERM is not defined.\n", 31setterm: $TERM is not defined.17:49
cndthough I had tried it without 2>&1 I thought, and I never saw this17:49
cndapw: yesterday you wondered if fdr binary-generic skipdbg=false would force generation of the ddeb without having to mess with touching /CurrentlyBuilding18:32
cndI can confirm that's correct18:32
* manjo heading out to get some lunch ... brb 1hr 18:46
jjohansen->lunch19:55
keeswhere are local references stored in .git ?  i.e. I have an upstream linux-2.6 tree that I want to have as a --reference for a new clone.  but if I forgot to do that during the clone, I can add it later and do a git gc --prune, but I can't figure out where to add it...20:06
tgardnerkees, I doubt it, you'll likely have to reclone20:06
keestgardner: nah, smb showed me magic at the last sprint20:07
tgardnerkees, perhaps its more hassle then its worth20:07
tgardnerdoh!20:07
keeswell, I have various topic branches now, so I want to manipulate the repo without throwing it away20:07
tgardnerpush you topic branches to different repo (like the linux-2.6 repo)20:08
tgardneryou can always delete them later20:08
keesah-ha, .git/objects/info/alternates20:09
keesokay, next up.... I have a remote, I've added a remote to it, how do I create a local branch for a remote master that isn't "origin"?20:10
tgardnergit checkout -b BRANCH origin/BRANCH20:11
tgardner'git branch -a' show all of the branches at remote repos20:12
keesI said "remote" twice there, meant "branch" first time.20:12
tgardnerI figured it out from context :)20:12
keessounds like I want  "git checkout -b LOCAL-BRANCH-NAME REMOTE/REMOTE-BRANCH-NAME20:12
tgardnerkees, exactly20:13
keescan I use "git log" to show other local branch logs?  (i.e. how do I find a commit id to cherry-pick without switching to the origin branch first?)20:18
ogasawarakees: you can do a `git log <branch name>`20:33
* ogasawara -> lunch20:35
keesah! I was trying too hard20:35
achiangkees: in git, just about every command works on a git identifier, whether it's a human readable name, or a sha120:51
keesachiang: seems like format-patch is an exception20:54
achiangkees: eh?20:56
* ogasawara goes to lunch for reals this time20:57
tgardnerkees, I think format-patch works on a single SHA1, or a range of IDs20:57
keesachiang: if I'm in a branch, and I want to use "format-patch" I can't specify an arbitrary sha120:57
keestgardner: yeah, my mental problems with git seem to revolve around the "scope" of branches20:57
keesI'm used to having a full working directory per branch (as with bzr)20:58
tgardnerkees, the syntax can be a bit dense20:58
achiangkees: interesting. i haven't used format-patch in a long time, not since i switched to stacked git20:58
maks_bzr is so bizarre20:58
maks_poor you kees 20:58
maks_format-patch <sha1sum>^..<sha1sum> kees 20:59
keesmaks_: ah-ha.20:59
keeswhat does "^" mean in that syntax?20:59
maks_the one previous20:59
maks_you can also use ~120:59
cndmpoirier: these two files (<flavour>.ignore and <flavour>.ignore.modules) tell the build process to ignore checking21:01
keesneat, that worked.21:01
keesso, it seems "scope" for git commands is really "all commits ever in any known branch".  only when one uses less specific arguments does it kick down using the current branch's view of commits.21:01
cndmpoirier: however, if you are just trying to build a kernel through fdr binary-omap, then you can add skipabi=true skipmodules=true to the command21:02
mpoiriersomething like:21:02
lifelesskees: I think its more 'reachable from reflog heads'21:02
lifelesskees: vs any commit21:02
cndmpoirier: I just realized I forgot to link to the files: http://kernel.ubuntu.com/git?p=cndougla/hedley.git;a=tree;f=debian.mvl-dove/abi/2.6.32-204.16hedley6/armel;h=736bf1ef045abfab6e0930d8031ebdfc5453bfee;hb=HEAD21:02
mpoirierfakeroot debian/rules binary-omap skipabi=true skipmodules=true ?21:02
tgardnermpoirier, 'echo 1 > debian.master/abi/2.6.34-4.11/armel/ignore'21:03
cndmpoirier: correct21:03
keeslifeless: ah, true, sounds right.  though I've never tried orphaning a commit and later tried to reach it21:03
achiangkees: note that format-patch is weird, in that you give it the sha1 of the commit *before* the one you really want21:03
achiangso that explains why you might be running into "scope" issues21:04
keesachiang: right, that bit I'm kind of used to now.  but this week I've tried to switch to using multiple topic branches so my existing workflows are slightly confused.  :)21:04
achiangif you're in master, and are trying to do a format-patch for a branch that has commits *after* master, then it looks like you can't simply specify a <since>21:05
achiangagain, stg ftw. ;)21:05
jjohansenachiang: curious, have you ever used guilt, and if so how do you find it compares to stg21:07
achiangjjohansen: i tried using guilt a long while ago and didn't quite like it as much as stg21:08
achianglet me try and remember why...21:08
jjohansenfair enough, I defaulted to it as its syntax was closer to quilt21:08
achiangjjohansen: i think my complaint with guilt was that it followed the git model *too* closely, in that it was a PITA to be working on a patch series and attempt to modify an earlier patch21:10
achiangbut that was about 1.5 years ago, so maybe it's improved a lot since21:11
jjohansenachiang: hrmm, no its just like quilt except better.  Just pop to the patch edit and refresh.  Better than quilt because any file under git control is automatically added, so no more quilt add/edit21:11
achiangjjohansen: yeah, ok. then i can't remember why i liked stg better (it has the same model btw)21:12
jjohansenI think there are a few things that stg probably handles better but, as I said I took a quick look at both an guilt was closer to quilt (which I used all the time)21:12
jjohansenright, its bascially the same21:13
achiangmaybe it was the mailer? is guilt's send-email wrapper nice/easy to use?21:13
achiangstg has a nice mail templating feature that i used heavily21:13
jjohansenah, that may be it, I have never gotten the mailer to work21:14
jjohansenand have to fallback to git send-email21:14
jjohansenof course I haven't tried it for a year21:14
achiangheh.21:14
jjohansenhrmm, looking at the current guilt there isn't even a mailer documented, though I am sure I tried playing with it in the past21:15
jjohansenperhaps it was one of the features that never got completed21:16
=== ayan is now known as ayan-afk
tormodis bug 585551 a udev or kernel bug, anyone?21:39
ubot2Launchpad bug 585551 in udev (Ubuntu) "mainline kernel makes udevd spin on device removal (inotify event) (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/58555121:39
mrecoh dear, since the last Ubuntu update my system randomly reboots21:40
mrecintel's crap graphicdriver is still not fixed and I'm getting glitches all over the screen randomly21:40
tormodmrec, update of what exactly?21:41
mrecsystemupdate there was not too much to update, is there any logfile available about system updates?21:41
tormoddpkg.log21:41
mreclibc was updated but not sure if that's the issue21:42
tormodmrec, you have lucid + proposed?21:43
mreconly lucid21:43
mreclibc was the most critical update probably I have the list here if it happens again I will report it21:44
phunge0achiang: hi, i've been having a WARNING in my linux-next kernel build22:09
phunge0"sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.0/slot'"22:09
phunge0googling showed a thread from a month ago http://lkml.org/lkml/2010/4/12/25922:09
phunge0but it doesn't look like anything was done about it22:09
achiangphunge0: yeah, i never really had a chance to debug that. :(22:09
achiangphunge0: i'm going to ask jesse to drop that patch, i don't have hardware or time to fix it22:10
phunge0i can help if you're interested, or maybe just revert the patch like you originally requested?22:10
achianghm22:10
achiangphunge0: can you pastebin lspci -vt for me please?22:10
phunge0achiang: http://pastebin.com/yECfYNZJ ... i'm on KVM, like the original submission22:12
achiangoh!22:12
achiangphunge0: you know, i didn't even see that eparis was using kvm the first time around22:12
phunge0interesting22:13
achiangthe fact that kvm is involved actually makes a lot more sense. i was *really* scratching my head initially about how on earth we could have gotten duplicate slot entries22:15
achiangphunge0: hm, weird. git grep sysfs_attribute_initialize returns nothing in my tree22:18
phunge0achiang: yeah, cool... my kvm setup is completely vanilla if you want to try to reproduce22:18
* achiang does a git remote update ; git rebase origin22:19
phunge0i know only a little about sysfs... sysfs_attr_init?22:19
achiangoh perhaps that's it22:19
achianghm22:20
phunge0# CONFIG_DEBUG_LOCK_ALLOC is not set22:20
phunge0it's a noop in my build, so i doubt that'd be it22:20
achiangi'm not sure that gregkh's email was correct. looking at the comment for sysfs_attr_init, it's talking about lockdep, which is completely unrelated to the warnings you're seeing22:20
phunge0yeah22:20
achiangphunge0: so you see that warning in the guest or the host?22:21
phunge0guest22:21
tormodwhy aren't the mainline daily builds, er, daily? :)22:35
JFobecause they build based on when there is an RC22:38
tormodanyway I hope yesterday's drm-next has what I need from today's missing daily22:39
tormodJFo, I think they are built more often than that?22:39
achiangphunge0: can you please pastebin: for i in /sys/devices/pci0000:00/* ; do ls -l $i ; done22:41
achiangin the guest22:41
phunge0achiang: http://pastebin.com/rb26vUMW22:46
phunge0and bus/pci/slots: http://pastebin.com/Se1TGyv722:48
achiangphunge0: sorry, one more pastebin please -- can you paste the entire dmesg from your guest so i can see the warnings?22:48
phunge0http://pastebin.com/Vc1h75Eu22:49
achiangphunge0: how do you feel about building kernels and testing patches?22:52
achiangphunge0: if it's too hard, don't worry about it, but if you're able, i'd like you to apply a debug patch for me22:52
phunge0achiang: i'm leaving work in around 20 minutes, gone until next tuesday :(22:54
achiangphunge0: how about if i send you an email and you can just report results when you get a chance?22:54
phunge0yeah absolutely22:54
achiangphunge0: address? you can /msg me if you want22:54

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