/srv/irclogs.ubuntu.com/2010/06/23/#ubuntu-kernel.txt

JFobjf, am now00:23
bjfJFo, no big deal, someone was pointing out a Launchpad oddity00:23
JFoah00:23
bjfJFo, just emailed some links to you00:24
JFosweet00:25
* JFo looks00:25
bjfthe "current series" is 2.6.3100:25
bjfi'd never looked at any of those pages00:25
JFoyeah, we need to change the development focus :)01:07
=== ericm-Zzz is now known as ericm
MTecknologyjussi: You ever get that figured out?03:36
=== bjf is now known as bjf[afk]
=== sconklin is now known as sconklin-gone
=== bjf is now known as bjf[afk]
=== lifeless_ is now known as lifeless
* amitk waves08:05
* cooloney waves back to amitk 08:07
om26eris there any technical name for gpu-switching? (for finding related bugs upstream)09:00
apwom26er, not sure i even know what you mean by gpu-switching09:07
om26erapw, there are system with two graphics card. e.g alienware m11x09:09
apwi would call those dual-gpu something like that09:09
=== cnd is now known as cnd-vac
ograapw, do you know if anyone is on top of bug 595949 ?09:23
ubot2Launchpad bug 595949 in linux-meta-ti-omap (Ubuntu Maverick) (and 1 other project) "linux-meta-ti-omap depends on the wrong binary kernel in maverick (affects: 1) (heat: 8)" [Critical,New] https://launchpad.net/bugs/59594909:23
apwogra, not sure, will look09:56
apwachaemenes, wondering why you need to turn off that option?10:23
achaemenesapw: I'm doing some security research, and writing a rootkit for 8.04 - however from 2.6.24-19 to 2.6.24-28, that option has been enabled - as is happening with most kernels in most distros - however i have to keep it disabled because my work hasn't yet finished, but I'd like to be on the latest 8.04 kernel while developing it10:26
achaemenesonce it's complete, I'll have to write an anti-rootkit for it10:27
achaemenesand after that, again a rootkit that does not modify syscall tables at all, and again an anti-rootkit for that... etc. 10:27
* achaemenes git clones10:32
apwachaemenes, if you have a local linux-2.6 tree you can --reference that, as we are pretty close to mainline10:33
achaemenesahh thanks, good to know10:34
lagHas anyone build the Lucid ti-omap branch recently?10:55
lagbuilt*10:55
ogralag, i guess smb since there were security updates in lucid10:56
lagThanks ogra10:56
apwi built it i believe to when testing the debian commonisation changes10:59
achaemenesi hear make-kpkg is now the "old way" :)11:17
achaemenesman i felt old after reading that11:17
arunachaemenes,  what's the new way to build kernels?11:19
ograapw, hmm, dont we end up with clashing binaries now for linux-omap ? 11:27
ograsince the old one still exists in the archive11:28
achaemenesarun - i was just reading the ubuntu page which is where i read that comment: https://help.ubuntu.com/community/Kernel/Compile#Alternate Build Method: The Old-Fashioned Debian Way11:34
achaemenesapw - is that the best page i should be reading for doing what i'm doing?11:37
apwachaemenes, i would normally build from the git tree11:39
apwgit checkout -b foo <tag>11:40
apwthen use a chroot to build it11:40
achaemenessince the clone, all ive done is "git checkout Ubuntu-2.6.24-28.71                     "11:40
apwfakeroot debian/rules clean; fakeroot debian/rules binary-generic11:40
apw(both inside the chroot)11:40
achaemenesand i am guessing debian/config/i386/condif.server shoud be == /boot/config-`uname -r`11:41
apwyep the config fragments used to make the configs are in debian/config11:43
achaemeneshmmm, this is odd: /usr/src/ubuntu-hardy is not clean, please run 'make mrproper'11:44
achaemenesif i mrproper, all the goodies will disappear11:44
apwtry rmdir include/config11:44
achaemeneshmm, no such directory - I'll just post a complete log of what I've done in case I'm doing something silly (/me prepares pastebin)11:45
achaemeneshttp://pastebin.com/kTNmSsY011:47
achaemenesand there is no include/config or include/config*11:47
apwwhat does git ls-files -o show11:48
achaemenesno output at all11:49
apwachaemenes, oh you have .config11:52
apwyou don't put the .config in the top level11:52
achaemenesapw - oh? they how will it know what to build?11:52
apwit will build the flavour config for the flavour that you speciified11:53
apwbinary-server for the server config11:53
achaemenesohhhh11:53
achaemenesof course!11:53
achaemenesduh11:53
apwrm .config and it'll work i suspect11:53
achaemenesthankyou apw - you've been increadably helpful - and yet - that was it!11:53
achaemenesi didnt even think twice on that11:54
achaemenesapw will you be making it (or interested in) ruxcon? :)11:55
apwheh don't think i'll be there11:55
apwsome of our security people might though11:55
amitkcooloney: lag: so TI-omap4 is based on 2.6.33 or 34?12:09
* amitk thinks it is .34, based on the renamed package12:09
ograamitk, .3412:09
* ogra will start building hand-rolled test images today for omap412:10
ograso you can try it if you have omap4 HW12:10
amitkok, I got confused by some commits I saw from lucid in there12:10
lagVERSION = 212:10
lagPATCHLEVEL = 612:10
lagSUBLEVEL = 3412:10
lagEXTRAVERSION =12:10
lagNAME = Sheep on Meth12:10
lag:)12:10
amitkogra: no OMAP4 HW here12:10
lagWho names these things?12:10
lag:)12:10
ogratime you get some 12:10
apwogra, the linux-image-omap meta packages are updated in maverick12:11
apwlag, thats linus himself12:11
lagapw: Maybe he needs to stay off the stuff himself 12:11
apwlag, very likely :)12:12
=== cking is now known as cking-afk
lag/12:12
thangam_arunHello All12:30
thangam_aruni am building kernel on Ubuntu-8.1012:31
thangam_arunbut at the end i am getting two .deb files(image, kernel-header)12:32
thangam_arunBut i want to build debug kernel 12:32
thangam_arunhow do i get that .deb file ??12:32
thangam_arunlinux-headers-2.6.27-17-core2_2.6.27-17.46_i386.deb linux-image-2.6.27-17-core2_2.6.27-17.46_i386.deb 12:32
thangam_arunthese are tow files i got, after compionilat12:33
thangam_arun*compilation12:33
thangam_arunsudo CONCURRENCY_LEVEL=2 NOEXTRAS=1 skipabi=true skipmodule=true fakeroot debian.master/rules binary-core212:33
thangam_arunthe above one is used for kernel compilation 12:34
thangam_arunCan you please some one help to get "debug" kernel .deb file 12:34
thangam_aruni am witing for reply ??12:37
smbthangam_arun, If you are looking for the package that contains the unstripped binaries, try adding a skipdbg=false to you cmd line12:44
thangam_arunsmb: Okay12:45
thangam_arunsmb: wht about "binary-debs" ??12:45
thangam_arunsmb, Any idea?12:46
smbNo I am trying to understand what exactly you mean with binary-debs.12:47
smbAs an argument12:47
smbor as something else12:47
thangam_arunokay12:47
smbThat was sort of a question on my side. :)12:48
smbAs targets I usually use only binary-<flavour> or binary or binary-arch12:48
thangam_arunoh ok12:49
smbI mean, you got a linux-image apparently, which would be the binary kernel package.12:49
thangam_arunyes that correct12:49
smbYou might want to make a run with either binary-indep or binary-header which creates the common headefr package12:50
thangam_arunis that enough for debugging purpose ?12:50
bguthroHello,12:51
smbDepends on how you debug. If you add printk's or use special debugging options you might not need the debug package. That only help to disassemble stuff or find symbols or profile12:51
smbthangam_arun, But otherwise that should be enough12:52
thangam_arunin this build i have configured "debug" in the "kernel hacking" section12:52
bguthroI'm attempting to chase down an Intel i915 problem in lucid - nothing displayed on an E6410... I've tried up to the mainline builds of 2.6.35-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid - and now wanted to try the Intel-drm development branch from kernel.org...but wanted to know if there was some build patch that I can apply over the top, to get the deb build system...12:53
bguthroI assume this is one of kees trees here: http://kernel.ubuntu.com/git?p=kees/linux-2.6.git;a=summary - but didn't know if there was a patch I should be using, to apply on top of a different devel branch: http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=summary12:55
smbthangam_arun, Hm, I cannot say from my head what exactly that enables. Generally the build has bdebugging informationenabled but strips things for the normal packages12:56
smbbullgard4, It looks like something from kees and maybe you will find useful things under mainline-build in git://kernel.ubuntu.com/ubuntu/kteam-tools.git but apw may have better info or even written a wikke 12:58
thangam_arunsmb, okay12:58
thangam_arunsmb, let me experiment and see12:58
smbthangam_arun, best way to go. :)12:59
thangam_arunsmb, bwt when i gave binary-debs building extra modules, i do not know why :)13:00
apwbguthro, don't we already build the drm-intel branch in the mainline builds ?13:00
smbthangam_arun, Ugh, I fail to parse that last sentence. o_O13:01
apwhttp://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/13:01
apw thangam_arun which ones extra do you get ?  .udebs perhaps ?13:01
bguthroExcellent. I missed that. Thanks - saves me some time!13:01
thangam_arunsmb, when i pass "binary-debs" option for compliation, it is compiling new modules 13:02
bguthroIs there a git tree somewhere that this is generated from that I could dig into, if I have to debug this LVDS issue?13:03
apwbguthro, nope.  but the scheme is simple, checkout the debian* directories from lucid/master into your mainline tree, update the configs and buil13:03
apwbuild .. thats is what the mainline builds do13:04
bguthroapw, sounds like a plan. Thanks a lot13:04
smbthangam_arun, Hm, ok. Maybe the udeb packages?13:04
thangam_arunsmb, might be. waiting for build to complete13:05
=== cking-afk is now known as cking
achaemenesapw - i forgot to ask, say i want to amend the "binary-server" - which config file do i change?13:32
achaemenesdebian/config/i386/config.server maps to binary-server? or there is more magic to it?13:33
apwi think you change debian/config/i386/config:CONFIG_DEBUG_RODATA=y13:38
apwand usually run debian/rules updateconfigs afterwards13:38
achaemenesright, and all the other configs in there are regened13:44
achaemeneshmmm, no 13:46
achaemenesgit status shows only that file to have changed13:46
apwthats good, that means your change stuck13:46
achaemenesis there an inheritance model with those files then?13:47
apwyeah the config is common to the others13:47
achaemenesahh ok now i get it13:47
ccheneyapw: i need kernels please... ;-)14:32
=== sconklin-gone is now known as sconklin
ccheneyapw: aka is there a status update yet? :)14:33
ccheneytgardner, or do you happen to know?14:34
tgardnerccheney, eh? know about what?14:45
ccheneytgardner, oh sorry i didn't explain what i am asking about, i need ppa test kernels (or however they will be provided) for rc's between 2.6.32 and 2.6.33 to track down the cause of bug 58886114:46
ubot2Launchpad bug 588861 in linux (Ubuntu Maverick) (and 4 other projects) ""pad block corrupted" error when trying to register an image with 2.6.34 kernel (affects: 1) (heat: 12)" [High,Triaged] https://launchpad.net/bugs/58886114:46
ccheneytgardner, its a blocker for UEC14:46
tgardnerccheney, uh, hang on while I figure it out14:46
ccheneytgardner, jjohansen was looking into it but said he might not have time to get to them and so you or andy might end up generating them14:46
ccheneyits becoming more urgent as i'm pretty sure your kernel alpha 2 freeze window is rapidly approaching :)14:47
tgardnerccheney, well, I'm pretty sure you're releasing A2 with a Lucid kernel14:48
ccheneytgardner, yea i think at this point we will probably need to do that14:48
ccheneyeven if we find the kernel it broke in it might not be obvious how to fix it14:48
tgardnerccheney, this is the -virtual flavour, right?14:49
ccheney-server14:51
ccheneyi tested using the ppa mainline kernels where it was seen as well14:51
ccheneythe error happens on the walrus server not inside a kvm instance14:51
tgardnerccheney, what is a walrus server?14:52
ccheneyits the part of eucalyptus that stores images for use by instances14:52
ccheneytgardner, so basically i try to add a lucid image to the uec machine to be used by instances that want to use it and when doing so it gives me the pad block corrupted error14:53
tgardnerccheney, so you want a -server flavour built from sources somewhere between 2.6.32.15.5 and 2.6.33 ?14:55
ccheneyyes -server if possible but for testing it can be even mainline like at http://kernel.ubuntu.com/~kernel-ppa/mainline/ as it shows the same issue14:55
ccheneywhichever is easier on you guys14:56
tgardnerccheney, damn, I had apw clean up all those daily builds just last week.14:59
tgardnerccheney, I'll start reproducing the 2.6.33-rcX builds to see if we can narrow it down14:59
ccheneytgardner, sorry we didn't get to it sooner I was out on paternal leave for the past 2 weeks and got assigned the bug on last Friday, from what I recall they were already gone at that time.15:01
pgranerJFo: can you get this on one of our lists? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/44904315:07
ubot2Launchpad bug 449043 in linux (Ubuntu) "Suspend/resume failing with Audigy2 PCMCIA attached (affects: 5) (dups: 1) (heat: 30)" [Undecided,Triaged]15:08
JFopgraner, yessir15:08
tgardnerccheney, http://kernel.ubuntu.com/~rtg/2.6.33/linux-image-2.6.33-rc1_2.6.33-rc1-1_amd64.deb15:45
=== bjf[afk] is now known as bjf
ccheneythanks15:51
tgardnerccheney, -rc2 is building, but I suspect you'll find that -rc1 doesn't work. -rc1 is where most of the new changes appear15:52
ccheneyok thanks15:52
tgardnerI'll bisect between 2.6.32 and 2.6.33-rc1 if that is the case15:53
* ccheney hopes he didn't corrupt his setup, might have to reinstall maverick before testing15:53
ccheneyok will try to get this tested asap, my euca-* commands aren't working at the moment, going to see if rebooting helps, otherwise may be another hour before i can test to do a full reinstall15:54
ccheneywow that deb is giant :)15:56
tgardnerccheney, its probably not stripped. I build using the Kbuild deb-pkg target15:57
ccheneyoh ok15:57
tgardnerit'll make bisection a lot quicker15:57
smbsconklin, Hi Steve, be careful with that last SRU. I was under the impression it was invalid15:57
JFoapw, you around?15:58
JFolooks like we need to do some updating to https://edge.launchpad.net/linux/15:59
tgardnerJFo, wow, I've never seen that page16:02
JFoheh16:02
JFobjf pointed it out to me yesterday16:02
JFoalong with this one https://edge.launchpad.net/linux/2.6.3116:03
JFobut there doesn't appear to be a corresponding .35 page16:03
JFoor anything later than that for that matter16:04
ogasawaraJFo: is that the project to allow setting upstream bug watches?16:04
JFoogasawara, I think so, but I am not sure16:04
JFoit is owned by us though16:05
JFoogasawara, we can change these pages yes?16:06
JFosince it is showing .31 as the dev effort :)16:06
ogasawaraJFo: not sure if we can or if we have to ask the launchpad team to help16:06
sconklinsmb: you mean only the one from Manoj, right? If so, I agree and it is not in my branch16:06
JFohmmm16:06
ogasawaraJFo: right, definitely out of date16:06
JFoheh16:06
* JFo tries something16:06
smbsconklin, Right I was referring to that. It sounded like that was next on your list when quickly reading over that16:07
JFoogasawara, want me to try changing it to .35?16:07
bjfJFo, there was a page were you could register a new "series"16:07
JFoI think I have the power16:07
ogasawaraJFo: sure16:07
bjfJFo, but I didn't play with it16:07
JFohmmm16:07
sconklinsmb: no, I couldn't tell what was needed and it looked incomplete so I was going to leave it alone16:07
smbsconklin, Ok, right. Taht was one were apw and myself have looked at and did not find real eviddence why it should be broken. And I think manjo wanted to test it again and I don't remember feddback there.16:08
* JFo waits for LP to refresh16:08
JFoogasawara, look at it now16:09
ccheneytgardner, it tells me unknown command recordfail16:09
JFoI changed it to trunk16:09
JFoas dev seried16:09
ccheneytgardner, at grub when trying to boot your kernel16:09
JFoerr series16:09
ogasawaraJFo: cool16:09
bjfJFo, on https://launchpad.net/linux/ there is a link "Register a series"16:10
smbbjf, sconklin I am currently listening to a training session. But we can get together after that when you want to. (to sort out questions)16:10
* ccheney wonders if something he did when he removed the old kernels and installed the new one messed up grub somehow16:10
bjfsmb, wfm16:10
ogasawaraJFo: and it is indeed the project that was set up that allows setting the upstream bug watches16:10
JFocool, I thought it must be16:10
=== ericm is now known as ericm-Zzz
ogasawaraJFo: I opened a bug with an upstream bug watch and followed the links back to that page16:11
JFocool :)16:11
tgardnerccheney, you can still boot older kernels? you though you might have borked you UEC enviro.16:12
tgardnerthought*16:12
ccheneytgardner, well i didn't know i had borked grub, but yea it seems to not boot any kernel now for some reason and i see insmod messages in the grub config, which seem somehow wrong as well16:12
* ccheney looks at his other systems grub config file16:12
jamincI'm currently experiencing Bug #593650, as part of the troubleshooting I've tested a few kernel builds from the mainline PPA.  Each of the builds I've tested so far (.35-rc3 and .34) appear to correct the crash issue, but each appear to be interact badly with libvirtd managed VMs... suggestions?16:13
ubot2Launchpad bug 593650 in linux (Ubuntu) "periodic kernel crash and system reboot (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/59365016:13
tgardnerccheney, well, make sure you have a stable boot environment first.16:13
ccheneyhmm i bet the insmod stuff has to do with grub2, i don't know that much about the newer version16:13
JFoogasawara, I find it interesting that https://edge.launchpad.net/linux/trunk shows incomplete info16:16
JFolooks like there may be a bzr branch somewhere that isn't up to date or something16:16
ccheneyhmm yea it booted back up fine under 2.6.35-4-server, will try the test kernel again to see what is going on16:16
ogasawaraJFo: yah was wondering why it was only showing through 2.6.32-rc816:17
JFoogasawara, is this ours ~vcs-imports/linux/trunk ?16:17
ogasawaraJFo: no idea, I'm not sure where the trunk actually lives16:18
JFohmmm16:18
JFoogasawara, looks like it is here https://code.edge.launchpad.net/~vcs-imports/linux/trunk16:19
ccheneytgardner, hmm yea just the test kernel fails with 'recordfail' related error message, the server kernel works, tested it a second time16:19
* ccheney looks to see what the cause of that would be16:19
ogasawaraJFo: interestingly, the recent revisions notes looks accurate (ie 2.6.35-rc3)16:19
JFoyeah, was just looking at that16:20
tgardnerccheney, shit, must be the way the kernels are packaged. are you running update-initramfs ?16:20
ogasawaraJFo: Ah, "This branch is an import of the HEAD branch of the Git repository at git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git."16:20
ogasawaraJFo: so it seems to generate from mainline which is good16:20
ccheneytgardner, not manually, but i can if needed16:20
tgardnerccheney, give that a try16:20
tgardner'update-initramfs -u' after 'dpkg -i'16:21
JFoogasawara, wonder why the other data is wrong then16:21
ogasawaraJFo: but I can't explain why it's then displaying out of date16:21
JFohmmm16:21
JFolet me think on it a minute16:21
JFoI may have an idea why16:21
ccheneyrunning: update-initramfs -k all -c  to see if it helps16:21
ccheneyjust running that didn't seem to help16:23
ccheneymaybe i should run it verbose to see if it is having problems? it didn't return any errors when i ran it though16:23
tgardnerccheney, lemme build a 2.6.32.15 kernel just to make sure its a packaging issue.16:24
ogasawaraJFo: maybe has to do with the milestones? https://edge.launchpad.net/linux/+milestones16:24
ccheneytgardner, ok16:24
JFocould be16:24
ogasawaraJFo: as those look to only go up through 2.6.32-rc816:24
JFohmmm16:24
JFothat has to be it16:24
JFoso ogasawara it looks like it pulls those from registered series16:25
JFoI registered https://edge.launchpad.net/linux/2.6.3516:25
JFobut it has no milestones16:25
JFowonder where those were coming from before16:25
ogasawaraJFo: "Milestones belong to a series and can be created from the series page by a project owner or series release manager."16:26
JFohmmm, but I am sure no one from upstream was creating these in LP16:27
jamincany ideas on what would cause mainline kernel builds to somehow cause libvirt managed VM disk image files to be non-writable?16:27
JFoor rather, reasonably sure16:27
ogasawaraJFo: I think the project ower is actually the ubuntu-kernel-team16:27
JFoyeah, that makes sense due to us owning the pages/branch/etc16:27
ogasawaraJFo: so I think you need administrative rights with the ubuntu-kernel-team to then create the milestones for a series16:28
JFohmmm16:28
JFolooks like I have that type of permission16:28
JFoif I hit create milestone16:28
JFoit gives me a dialog where I can enter the info16:28
JFolooking at this page https://edge.launchpad.net/linux/2.6.3416:29
JFotoward the bottom16:29
JFoyou have it too I bet16:29
ogasawaraJFo: I don't have that magic16:29
ogasawaraJFo: you'r special16:29
JFooooh16:29
* JFo feels powerful16:29
JFo:P16:29
JFowell, if you feel it is worthwhile, I can look up the milestones for .34 and .35 and add them I guess16:30
JFonot sure what the benefit is though16:30
ogasawaraJFo: not sure who actually looks at that page16:30
JFosame here16:30
JFoor if it has some impact on anything in bugs16:30
ogasawaraJFo: and it seems annoying you'd have to go and set the milestone for each -rc kernel that comes out16:31
JFoyep, we are thinking the same16:31
ogasawaraJFo: maybe just set 2.6.35-rc1, 2.6.35-rc2, and 2.6.35-rc3 and call it done16:31
JFoso maybe I just do it for the kernels we determine to use for a release16:31
JFosounds fine16:32
ogasawaraJFo: yah, I wouldn't bother with 2.6.33 or 2.6.3416:32
JFoyeah16:32
JFok16:32
JFowill do16:32
JFoogasawara, is there a good place to find release dates for RC?16:34
ogasawaraJFo: hrm, just a sec and let me see if I can find you something16:35
JFoooh, I may have found something16:35
ogasawaraJFo: shoot, I thought the kernel version map might have it16:36
JFoI found an RSS feed for releases16:36
ogasawarabut doesn't :(16:36
JFolemme check16:36
JFoogasawara, I found http://www.kernel.org/kdist/rss.xml16:36
JFoit shows release dates :-)16:36
JFoJune 11 was RC3 yes?16:36
ogasawaraJFo: yep that sounds right16:37
JFoRC2 June 6?16:37
* JFo is so handy16:37
JFowait a sec...16:37
ogasawaraJFo: you have the git tree cloned locally?16:37
JFoogasawara, I do16:38
ogasawaraJFo: git show v2.6.35-rc316:38
smbbjf, sconklin Ok, I am finished over there16:38
bjfsmb, just be a sec, getting mumble setup for today16:38
macoJFo: that rss feed doesnt look like it agrees with you...16:38
JFoogasawara, sweet16:38
ogasawaraJFo: wash, rinse, repeat for the others16:39
JFoogasawara, :-P16:39
JFomaco, how so?16:39
macoJFo: that rss feed is showing rc2&3 on the 11th16:39
maco(you sound more likely to be right)16:39
JFoI don't see that16:40
JFooh no, that is git6 of RC216:40
JFoI looked back for the RC2 release16:40
macooh16:40
macoum ok. im confused. i dont see june 6 anywhere on there16:41
jamincalright, this just more and more strange... with the current stable lucid kernel (2.6.32-22-generic) I'm able to start VMs backed by a qcow2 file using libvirt just fine... the same VM with a mainline kernel fails to start via libvirt... however, changing ownership of the qcow2 file to root:root fixes the problem... anyone have ideas as to why?16:49
JFomainline:2.6.35-rc22010-06-0616:49
JFomaco ^ that is from that RSS16:50
JFoogasawara, odd that now it still isn't showing up16:51
* JFo tries something16:51
ogasawaraJFo: maybe refreshes hourly or something16:51
JFothink I figured it out16:52
JFoone sec16:52
JFoah well, I'll look back in on it later 16:55
tgardnerccheney, http://kernel.ubuntu.com/~rtg/2.6.33/linux-image-2.6.32.15_2.6.32.15-2_amd64.deb17:01
ccheneytgardner, thanks17:06
ogasawarajjohansen: do you think we'll have the apparmor maverick update before Fri?17:23
jjohansenogasawara: yeah sorry, the testing took a little longer than I planned, I am working on the cleaned up rebase for you now17:24
ogasawarajjohansen: sweet, thanks17:24
tgardnerapw, mumble me when you get around17:27
ccheneytgardner, 32.15 didn't work either, was that the test to see if it was the packaging issue?17:32
tgardnerccheney, yep, so I've gotta figure out what the hell I'm doing wrong.17:32
ccheneytgardner, ok, not sure what is causing it, i haven't seen that kind of error before17:32
ccheneytgardner, when i remove recordfail i get a little further17:34
ccheneyit says the following:17:34
ccheneyKernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)17:35
ccheneythe system uses lvm17:35
tgardnerccheney, hmm, thats definitely an initramfs issue, or perhaps teh default config doesn't build in the right drivers17:36
ccheneyoh17:36
ccheneytgardner, http://pastebin.com/6GMaie6T not sure if that is useful for you to see, but it does look normal to me at least like the other grub entries that work17:40
maks_tgardner: no17:49
maks_aboves message means that it is a bootloader issue.17:49
maks_aboves is a linux-2.6 message when it can't mount root.17:49
maks_this means it never got the initramfs.17:49
tgardnermaks_, well, its still a apackaging issue in the way I was building. I used the internal kpg-deb target17:49
maks_well i didn't see the kernel commandline17:50
maks_it may well be that the initramfs wasn't passed at all.17:50
tgardnermaks_, likely, thats why I suggested it was an initramfs issue. its the normal culprit when you can't mount the root FS.17:51
maks_no that is not an initramfs issue itself :P17:52
maks_as it wasn't loaded ;)17:52
tgardnersemantics17:53
maks_ccheney: in http://pastebin.com/6GMaie6T  why do you have toplevel dir entries?17:53
maks_just use the stuff in /boot/17:54
maks_hmm don't see a faulty entry although if those symlinks exists17:56
maks_ccheney: does ls -l /initrd.img-2.6.32.15 really exist?17:56
ccheneymaks_, i didn't modify that, its the way maverick does it17:56
ccheneymaks_, maybe its buggy?17:56
ccheneyall i did to it was run update-grub2 to make sure it was up to date17:57
ccheneyafter installing 32.15 for some reason it didn't even appear in the boot list until i did that17:57
maks_can you please anser the ls17:57
maks_hmm i might have an outdated grub2 here in Squeeze, but I see /boot/ everywhere.17:57
ccheneymaks_, hmm let me see something17:58
ccheneyit might make sense, looking17:58
ccheneymaks_, yea since i am using lvm / is the non lvm boot dir17:59
ccheneyso that should be sane17:59
ccheneyhttp://pastebin.com/jm6trFQv17:59
ccheneyhttp://pastebin.com/a5JpZZVT17:59
ccheneythose are my fdisk -l output and lvscan output17:59
maks_ls -l  /initrd.img-2.6.32.15 # or you land on fucking ignore18:00
ccheneythere is no  /initrd.img-2.6.32.15 on my root filesystem but that isn't what grub2 is looking at when it boots (or shouldn't be anyway) since it is lvm18:01
ccheneyi can create a link to it but it won't work unless grub2 magically reads lvm volumes now, will verify18:01
ccheneymaks_, and note the other kernels also work fine without any symlink there18:02
maks_hmm so it sees /boot as /, okay fun never saw that yet.18:03
maks_and the ls -l /boot//initrd.img-2.6.32.15 exists ?18:03
ccheneystill did not work with the same error as expected18:04
ccheneyyes18:04
ccheneyi also regenerated the 33-rc1 initramfs before tgardner sent me a 32.15 to test with, regenerating it did not help at least for the 33-rc1 kernel he sent me18:05
maks_what's it's size, compared to the others?18:05
maks_(have to run so will read later)18:06
tgardnerjjohansen, what else besides 'fdr binary-server AUTOBUILD=1 no_dumpfile=1' ? I'm getting errors when its generating the package, 'dh_installdeb: package linux-image-2.6.32-23-ref-server is not in control info'18:06
ccheneymaks_, much larger from what i recall, iirc he thought it was not stripped18:06
ccheneysystem just finished booting, looking now18:06
jjohansentgardner: hrmm I don't recall ever seeing that18:06
ccheneymaks_, the two that don't work are over 85MB, and the one that does is 11MB for the initrd18:07
jjohansentgardner: what you have looks good to me, I haven't done it for a while, maybe something in the updated build infrastructe?18:07
jjohansenI have just kicked off a build to see what I get18:08
* ccheney wonders if initramfs/initrd can get too big to work18:08
tgardnerjjohansen, shit, I didn't want to have to _think_ about this.18:08
tgardnerccheney, how do I replicate what you have for a testbed?18:19
ccheneytgardner, i installed maverick alpha 1 and then installed your image (i did a few things in between but no package upgrades)18:20
tgardnerccheney, no, I meant how do I replicate what you're doing with UEC ?18:20
tgardnerisn't that is whats failing?18:21
ccheneytgardner, oh i see18:21
ccheneyyea, i can email you the script i am running18:21
tgardnerccheney, I don't know jack shit about UEC, so make it an installation guide for idiots.18:22
ccheneyok18:22
ccheneytgardner, ok i wrote it up, if you have any questions let me know18:28
ccheneytgardner, it should be fairly straight forward, the test doesn't really need any knowledge of UEC beyond getting through the install steps I referenced in the email18:29
ccheneytgardner, and to see if the issue is happening you grep under /var/log/eucalyptus after running the script for the 'pad block corrupted' message as noted in the bug report18:29
tgardnerccheney, ack18:30
ckingtgardner, emerald isn't too happy, it's kinda stuck on some builds18:59
tgardnercking, emerald.mills ?19:00
ckingyep19:00
jjohansenyeah, for me too19:01
tgardneroops in dmesg19:01
ckingyep, looks kinda wrong to me19:01
tgardnercking, jjohansen: I'm installing ogasawara's latest kernel, rebooting in a sec19:03
ckingcool19:03
jjohansentgardner: thanks19:03
tgardnercking, jjohansen: maybe its this: http://launchpadlibrarian.net/50396107/qemu-kvm_0.12.3%2Bnoroms-0ubuntu9_0.12.3%2Bnoroms-0ubuntu9.1.diff.gz19:07
jjohansenccheney: ^19:09
=== JanC_ is now known as JanC
tgardnerjjohansen, no, I meant that the mem leak in qemu might be why processes stall on emerald after awhile19:11
ckingseems to happen a lot now we do a load of QEMU assisted builds19:12
jjohansentgardner: yeah, I hadn't looked at it yet when I did that and just assumed was for the ccheney conversation, and tab completion had gotten you :)19:12
JFopgraner, I find the last comment here disturbing: bug 36573919:17
ubot2Launchpad bug 365739 in linux (Ubuntu) "Loud cracking sound before suspend to RAM (affects: 1) (heat: 16)" [Undecided,Fix released] https://launchpad.net/bugs/36573919:17
JFosorry, wrong bug19:18
JFobug 59259819:18
ubot2Launchpad bug 592598 in linux (Ubuntu) "dell latitude 2110: speakers work; headphones don't work (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/59259819:18
JFopgraner, ^^19:18
* tgardner lunches19:29
jjohansen-> lunch19:43
apwtgardner, been laid flat by my head ... will try and catch you after your lunch19:44
tgardnerapw, no problem, I've about gotthe local mainline build stuff figured out. I'm gonna add some notes to the README in the giot repo19:56
ckingthis day is never gonna end20:16
* ogasawara lunch20:35
tgardnerccheney, http://kernel.ubuntu.com/~rtg/mainline/v2.6.33-rc1-maverick/21:11
ccheneytgardner, thanks21:11
tgardnerccheney, if -rc1 works for you, then watch at http://kernel.ubuntu.com/~rtg/mainline/ for the next one to appear in about an hour21:13
ccheneyit booted mostly ok, some alsa backtrace, testing now21:15
ccheneytgardner, looks like the problem is there in 33rc121:18
ccheneytgardner, i'm seeing some of the errors already, I have it run the test 10 times but it definitely looks like it was in rc1 already21:18
tgardnerccheney, ok, I'll start bisecting between 2.6.32.15 and 2.6.33-rc121:19
ccheneyok21:19
ccheneytgardner, it finished and failed all 10 tries21:32
tgardnerccheney, k21:33
=== kentb is now known as kentb_out
bguthroI have what I'm sure will come across as a stupid question but here goes... I'm used to developing outside of a .deb environment...so I am still getting used to this build system. How can I do an incremental build, without rebuilding the entire tree? I start by doing DEB_BUILD_OPTIONS=parallel=4 AUTOBUILD=1 NOEXTRAS=1 skipabi=true skipmodule=true fakeroot debian/rules binary-generic - but then subsequent executions of that do not seem to build the22:04
bguthro tree, only install it...22:04
bguthroIf I'm working on just 1 module - what is the best way to do iterative work?22:05
jjohansenbguthro: when developing and doing incremental builds, I actually build outside of the .deb env22:06
jjohansenbguthro: once done with that I will move patches inside the deb22:06
jjohansenits just faster, and no overhead of packaging up the kernel into .debs etc either22:07
bguthrojjohansen: so you have the tree, and just do a "make modules", "make install" ?22:07
jjohansenbasically22:08
bguthrook, thanks.22:08
jjohansenyou need to make the kernel first and install it22:08
bguthroclearly22:08
jjohansenthen you can just install the modules to that kernel22:08
bguthroand a depmod -a...22:08
jjohansenyeah22:08
bguthrook, thanks22:08
jjohansenthe you need update-initramfs, and update-grub22:09
keesogasawara: my hangs are i915 related.  yay22:18
ogasawarakees: yuck22:18
keesogasawara: I have to blacklist both i915 and intel_agp.  though that really doesn't help because as soon as udev start on the real root, it loads them anyway and hangs the system.  and if I blacklist them in both initramfs and real root, X still tries to load them.  *stabby*22:19
ogasawaraheh, stabby22:19
ogasawarakees: you said this started with 2.6.35-rc1?22:22
keesogasawara: yup.22:22
apwbguthro, you can remove the build stamp from the debian/stamps directory then it will only incrementally build22:35
=== sconklin is now known as sconklin-gone
ogasawarabah, stupid disconnect.  kees, did you see my above msgs?22:43
kees21:22 < ogasawara> kees: you said this started with 2.6.35-rc1?22:45
kees21:22 < kees> ogasawara: yup.22:45
keesogasawara: that's all I saw22:45
ogasawara[14:40:21] <ogasawara> kees: was browsing through rafael's regression list http://lkml.org/lkml/2010/6/20/143 but I'm not seeing anything noted there similar to what you're seeing22:45
ogasawara[14:40:34] <ogasawara> kees: ogasawara@emiko:~/linux-2.6$ git log --pretty=oneline v2.6.34..v2.6.35-rc1 -- drivers/gpu/drm/i915 | wc -l22:45
ogasawara[14:40:34] <ogasawara> 7122:45
ogasawara[14:40:54] <ogasawara> kees: If I started building bisect kernels, could you test?22:45
keesogasawara: yup, totally22:45
ogasawarakees: amd64?22:53
keesogasawara: yuppers22:54
keesogasawara: if you show me how to do the bisect while keeping a sane debian/ directory, I can do it :)22:55
ogasawarakees: was going to sorta try and see if I could just bisect amongst those 71 commits first22:55
ogasawarakees: I don't think there's a sane way to do that though22:56
ogasawarakees: using 'git bisect' at least22:56
ogasawarakees: I wanted to avoid having to bisect all of 2.6.34..2.6.35-rc122:57
ogasawarakees: I started doing the following on tangerine . . . git bisect start v2.6.35-rc1 v2.6.34 -- drivers/gpu/drm/i91523:05
ogasawarakees: I think the debian directory is still ok, but we'll see how long that lasts23:05
ogasawaranm, it's hosed23:07
=== kamal is now known as kamal-away
ogasawarakees: http://kernel.ubuntu.com/git?p=ubuntu/kteam-tools.git;a=blob;f=mainline-build/README;h=448b7308f357764e812a607033d717ce7625962f;hb=HEAD23:18
ogasawarakees: I think I can use those instructions, will let you know23:19
keesogasawara: hunh.  okay23:23
=== bjf is now known as bjf[afk]

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