/srv/irclogs.ubuntu.com/2008/11/24/#ubuntu-kernel.txt

ciberBOBhey guys just need some link or recommendations for initiatives in the development of the Linux kernel and contribute something to the community02:33
ciberBOBnot is channel for disscusion for kernel developer ?02:34
* abogani waves08:57
aboganismb_tp: Please remember to pull from my git tree to obtain PREEMPT_RT support update for Hardy.08:57
smb_tpabogani, I will do. :) Thanks for the reminder08:58
aboganismb_tp: Sorry to bother more and more. :-)08:58
smb_tpabogani, Hey, no problem. You had the work with it.08:59
aboganiAre there some plan to change build system for kernel flavours (obviously generic/server excluded) ? Will it remain "out" (as did in Intrepid) or return to "in" (as did in hardy)?09:04
aboganiPerhaps BenC know it ^^^09:06
smb_tpabogani, I frankly don't know at the moment. Ben might know. Or amitk, did you catch discussions about that ^^^09:13
amitksmb_tp: abogani: change build system for what again10:40
amitk?10:40
smb_tpamitk, If I understood correctly the question was about -rt flavour10:41
amitksmb_tp: -rt flavour integrated into the Ubuntu kernel?10:42
smb_tpamitk, Into the build. But I think the intention was there to have a separate tree like lpia and ports. But I am not remembering well10:43
apwamitk, just was trying to edit the config lists in the a1 jaunty kernel and got the following error from armel11:22
apwAbout to configure armel config.iop32x11:22
apwmake[1]: Entering directory `/home/apw/git2/ubuntu-jaunty'11:22
apw/home/apw/git2/ubuntu-jaunty/Makefile:449: /home/apw/git2/ubuntu-jaunty/arch/armel/Makefile: No such file or directory11:22
apwmake[2]: *** No rule to make target `/home/apw/git2/ubuntu-jaunty/arch/armel/Makefile'.  Stop.11:22
apwmake[1]: *** [sub-make] Error 211:22
apwmake[1]: Leaving directory `/home/apw/git2/ubuntu-jaunty'11:22
apwmake: *** [editconfigs] Error 211:22
amitkapw: this is with 'debian/rules updateconfigs'?11:25
apwd/r editconfigs11:25
amitkapw: hmm.. not sure if editconfigs can work on a different arch11:28
amitkapw: I know why now...11:30
amitkit should work... patch coming up11:30
apwamitk, cool ... will give it a try11:35
apw(when it appears)11:35
amitkapw: pushed..11:39
apwamitk, got it, seems to work just fine for me ... thanks11:45
amitknp11:46
apwbetter warn BenC that the jaunty tree has commits on top of it12:21
amitkBenC: ^12:23
BenCapw, amitk: Got it, thanks12:40
BenCamitk: have you compiled the current tree on armel to make sure things are good?13:05
amitkBenC: another trivial change to getabis pushed.13:07
amitkBenC: I haven't. I can kickstart a build now.13:07
BenCamitk: thanks, I want to upload today and I just need to make sure armel will build13:25
mkrufkysmb_tp: hello.  I have some additional sms1xxx changesets that I merged into a separate branch.  These changes depend on the ones pending from last week.  Would you prefer that I generate a pull request against the last changeset in my last request, or should I just generate a whole new one with all pending changes altogether?14:06
mkrufky...and yes, I have LP's created, etc... some of the LP's are private bugs for the Belmont project ....  the fixes can go both to Belmont and Hardy14:07
smb_tpmkrufky, since I did not get to those yet, I would prefer one new one with everything together. 14:08
mkrufkyok, i will send that right now14:08
mkrufkythanks in advance :-)14:08
smb_tpmkrufky, Ah, ok. Could you probably open dummy ones for the private bugs. I know it is a bit tedious but then the references to those can be publicly be followed14:09
BenCA list of modules that I had to disable in jaunty kernel has been sent to kernel-team@ if any gets that forward porting feeling14:09
apwsmb_tp, just found and interesting work around for my dell studio 15 hang, which fits with your suspicion of cpu concurrency issues14:10
mkrufkysmb_tp: I can just make the bug public -- there isnt actually any private info in there ....  you should just ignore the pull request to mfrey INSIDE the bug report though14:10
BenCIf you're not sure what that feeling feels like, it's a cross between a burning and slight tingling in the area of your brain where common sense takes place14:10
apwa script to disable all but one cpu for the suspend cycle sort it out14:10
rtgapw: https://bugs.launchpad.net/bugs/30015914:12
smb_tpmkrufky, Hm, I should be able to ignore that. rtg what do you think of that?14:13
apwrtg that one looks 'fun' too, but i think the issue is actually: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/276943/14:14
mkrufkyi just say to ignore because my belmont pull requests are in separate branches against his git tree14:14
rtgsmb_tp: if there is nothing proprietary in the bug, then just make it public.14:14
mkrufkyi been using separate branches for belmont vs hardy mainstream, so that u guys can just pull / merge without any issue14:14
mkrufkyyeah i will do that14:15
rtgapw: I just noticed that other folks have come up with the same work-wround.14:15
smb_tpmkrufky, Ok, great. Maybe you could refresh my memory with a mail to kernel-team if you are ready. ;-)14:15
apwits alll a bit frightening, stupid userland s/w accessing h/w, ouch14:15
mkrufkysmb_tp: yes, will send that mail in a few minutes14:16
smb_tpmkrufky, Cool, thanks. :)14:16
rtgoff-lining is actually a normal part of suspend, but its also almost the last thing that happens before calling ACPI to suspend.14:16
apwyeah the key seems to be not-onlining them again for 10s14:17
apwso that X has woken up and posted the h/w before they arrive14:17
apwif this suggested bodge patch is right it may be that we are loading irq handlers and not waiting for all cpu's to get with the program before dri interrupts start raining in ... its possible an rcu grace period wait in the dri driver would fix it14:18
rtgapw: sounds like it could be lieb's VT race.14:19
apwi thought the bug there was that the switch didn't occur correctly, in that overlapping vt switches could get lost14:19
apwthis is definatly some kind of parallel hardware init problem14:19
rtgapw: I think it can manifest itself in a variety of ways. I assume you can reach your laptop over the network when its gets wedged on resume?14:21
apwnope, when it wedges its _hard_ gone14:22
rtgapw: well, then that isn't the VT lock.14:23
apwby suspending from a text console, i can resume correctly to there, and wait long enough for wireless to come back up14:23
apwthen login from my 'tv' system, but when i switch to X she dies, and the cpu is pegged14:23
apwthe network connection then times out14:24
BenCapw: even after waiting some time after resume?14:24
apwyeah ... its the switch back to X which takes the machine out14:24
apwand this workaround seems to demonstrate its lack of smp locking somewhere14:25
BenCapw: what xorg driver?14:25
apwthe bug may well be in X dri drivers, or the real kernel dri drivers, its not clear14:25
apwintel xorg driver, i915 dri module14:25
apwother people are reporting it in other dri modules, so its likely a systemic failure across the family14:30
mkrufkyemail sent, smb_tp14:32
smb_tpmkrufky, ok. got it and put on todo list14:32
mkrufkythanks14:32
apwrtg this linux backports module (intrepid) seems to crap out if the directory above the build is dirty?  is that reasonable?15:29
rtgapw: no, its not reasonable, but it happens. it doesn't match correctly if there are old .deb files from a [previous version.15:30
apwat least i am not going mad15:30
rtgI've fixed many of the packages.15:30
rtgapw: since I'm working on Intrepid LBM today, I'll get that fixed.15:31
apwsounds good, thanks15:31
apwits the imagelist=$(cat .... bit which seems to die15:31
rtgthats the one.15:32
rtgrm -f ../*.deb and it should be OK.15:32
apwyeah will do that for now, to confirm my lbm patch actually builds15:32
rtgapw: I'm about to do a complete update from upstream.15:33
apwof the wireless yes?15:33
rtgfor wireless, are you adding some new driver?15:33
apwyeah we talked about it last week, its a backport of some nic driver15:33
rtgapw: I had a vague memory of that (which should be OK)15:34
apwas its put in there now it would be independant of your changes15:34
rtgr8169, right?15:34
apwjust trying to confirm i did it right by building it which is challenging at best15:34
apwyeah thats the one15:34
amitkrtg: I think the intrepid kernel has the same problem, IIRC15:34
amitkrtg: imagelist one, I mean15:34
rtgnot too surprising.15:35
rtgit goes back as far as dapper15:35
apwits taken me sometime to work out what i needed in my chroots to get it building, and then a while to build them15:35
BenCapw: in buildscripts git there is a shell script that will create schroot compatible tarballs for chroots, complete with all the build requirements for the kernel16:29
BenCapw: if you want to just complete your current chroot's, there's a listing of the extra packages needed in there as well16:30
apwnice16:31
apwthanks BenC 16:31
BenCnp16:38
* BenC needs more coffee16:38
apwthe markets are up 9.2% ... hmmm16:38
amitkapw: for how long?17:03
amitkBenC: I got a build failure on ARM. will investigate now. Should I pull in cjwatson's patches as well?17:05
BenCamitk: I already pulled them and pushed17:05
amitkBenC: ok. I'll rebase and fix configs.17:06
* amitk is going to setup cross-compilation now. Qemu builds are painful17:08
BenCamitk: does qemu take advantage of multicore?17:10
amitkBenC: it does have a -smp option. I have it set to 3. It improves things a bit.17:12
apwamitk, heh they are closed, so at least until tommorrow morning17:14
apwamitk, are we going to have some kind of cross-compile porter?17:14
amitkapw: I'll post instructions to setup a cross-compile toolchain. And then we can ask IS to do it on a fast porter machine. Ideally I would like Ubuntu to provide a cross-compiler package so that it is automatic.17:18
apwthat sound perfect17:18
BenCamitk: best bet is to talk to doko...debian used to (may still?) have a cross-compile toolchain package, so it might not be too hard to do17:23
=== mcasadevall is now known as NCommander
kirklandsmb_tp: ping, regarding https://bugs.edge.launchpad.net/ubuntu/+source/iscsitarget/+bug/27862518:04
kirklandsmb_tp: i merged a new iscsitarget package for jaunty, but this problem remains18:05
kirklandsmb_tp: it seems that the kernel module code contained in the source of the new package fixes the "can't unload modules" problem18:05
kirklandsmb_tp: is this module code something that can be merged into the kernel modules code?  what's the rules/policy/process for doing so?  can you help?18:06
smb_tpkirkland, yeah there was some proc (or sysfs) change18:06
kirklandsmb_tp: cool, you're on top of it?18:06
smb_tpkirkland, I am not that familliar with why it isn't in the kernel. There was a guy involved who is the maintainer of the package. Maybe he is more up to it18:06
kirklandsmb_tp: so what is in the kernel, iscsitarget wise?18:07
kirklandsmb_tp: seems we ship an iscsci_trgt.ko18:07
kirklandsmb_tp: is that from upstream?18:07
kirklandsmb_tp: do they publish some additional code that's not upstream yet?  (i don't get it)18:08
smb_tpkirkland, In Intrepid its in the kernel because lum went in there18:08
smb_tpkirkland, I think the kernel itself has nothing of it18:08
kirklandsmb_tp: so lum includes module code that's not in the kernel.org kernel?18:08
smb_tpkirkland, yes18:08
kirklandsmb_tp: cool, and what's the process for getting that code update?18:09
kirklandsmb_tp: ie, could we import the "working" iscsi_tgrt code from this package?18:09
smb_tpkirkland, For Intrepid that is basically what I did.18:09
smb_tpkirkland, There is a BOM file with the location of the original download18:09
smb_tpkirkland, IIRC iscsitarget.sf.net18:10
kirklandsmb_tp: cool, so will you be doing the same for Jaunty, at some point?18:10
smb_tpkirkland, since there is a bit stacking on my queue and my memory isn't sometime lacking it would be good to add a pointer via kernel-team mailing list ;-)18:12
kirklandsmb_tp: okay, cool.  what's that address, please?18:13
rtgkirkland: we'll have to for Jaunty since iscsitarget FTBS18:13
kirklandrtg: thanks18:13
smb_tprtg, Are you on it18:13
smb_tp?18:13
kirklandrtg: right now, package upgrades of iscsitarget will fail too, because it can't unload the modules on the initscript "stop"18:13
rtgyeah - we'll get there eventually.18:13
smb_tpkirkland, Oh just for general "reminders" kernel-team at lists.ubuntu.com :)18:16
s0ullighthi guys18:16
BenCjust about to boot the jaunty kernel...18:24
BenCWARNING: I'm getting ready to do a force push18:26
smb_tpBenC, Did you pull the uvcvideo patch?18:30
BenCsmb_tp: yeah, just did a pull to make sure I have everything18:31
smb_tpBenC, Cool. pfew :)18:31
s0u[]ightwhat kernel is this new release using atm?18:32
NCommanderhey BenC 18:33
rtgsconklin: did you get that? My nick isn't registered, so I never know if private chats work18:38
BenCNCommander: yo18:40
NCommanderBenC, how goes 2.6.28?18:40
sconklinrtg: yeah, I got it18:41
calcBenC: i think you found a perpetual energy machine in your stove :-\19:02
rtgsmb_tp: speaking of iscsitarget, did you build test the Intrepid commit? http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=8c09ecb39475e13bc86dc6df3c7fa787abc34aae19:13
NCommandercalc, BenC's cooking can't be that bad19:14
smb_tprtg, At least I always wanted it. I am not sure anymore... 19:14
rtghuh?19:15
smb_tprtg, I might suffer from too many nested interrupts. I thought I had test build it might be just an intention that got dropped19:18
rtgsmb_tp: well, reverting it allows the compile to continue. I'll figure it out later this afternoon.19:19
smb_tprtg, Hm, found some debs with a matching git with iscsitarget on ronne. 19:19
smb_tprtg, but that was 9.18...19:20
rtgsmb_tp:  probably some header that changed.19:20
smb_tprtg, maybe. if you don't get to it maybe send me an email with the build log19:22
rtgsmb_tp: don't sweat it. I'll get it figured out after lunch.19:23
smb_tprtg, no worries. :) enjoy.19:23
rtgsconklin: you can work around that build failure by reverting the last commit to ubuntu/iscsitarget19:23
smb_tprtg, I am off after one more mail19:23
sconklinrtg: ok, thanks. 19:24
lamonthow do I get kvm to _NOT_ stop doing stuff when I iconify the window?19:27
lamontbecause I'd like to set the machine to doing a task and then not have the window occupying realestate until I want to go look at it....19:28
amitkcross compiling is sooo much more bearable...19:30
amitkrtg: I've fixed armel configs and all four flavours compile now. Pushed fixes to jaunty. Could you inform BenC when he gets back?20:51
rtgamitk: sure, I'll even do some test building.20:52
amitkrtg: thanks. Good night...20:53

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