[01:03] <jcrigby> anyone here know how to do binutils version specific (assembler actually) flags in kernel build?
[03:38] <faranda> hi there...
[03:39] <faranda> I have running a hardy (ubuntu 8.04) with kernel 2.6.36
[03:39] <faranda> I have problem with apparmor
[03:39] <faranda> I build a deb package from source apparmor-2.1+1075
[03:39] <faranda> the problem is in the init script
[03:39] <faranda> when I run init script, show me the message :    Loading AppArmor profiles - failed, Do you have the correct privileges?:
[03:39] <faranda> when I run apparmor_status, show me the message :    apparmor module is loaded.  You do not have enough privilege to read the profile set.
[03:41] <faranda> in kernel 2.6.36, apparmor is not a module
[05:16] <cactaur> Hi everyone. When upgrading to Maverick, I had a problem with the kernel not being able to find the root filesystem. When I filed a bug on launchpad, one of the triagers told me to test the mainline kernels to see if it's still an issue. I've been following the instructions on the Kernel/MainlineBuild wiki page, but when I try to install the linux-image package, it fails because it  says it can't create initrd. I was wondering if someone coul
[13:10] <vish> apw: hi, i tested your kernel for Bug #652934 , and it works fine.. no problems
[13:10] <ubot2> Launchpad bug 652934 in linux (Ubuntu) "[RV515] Guest session causes screen to flicker violently and session is unusable (affects: 2) (heat: 16)" [Medium,Confirmed] https://launchpad.net/bugs/652934
[13:11] <vish> apw: and thanks..  :)
[14:13] <tgardner> apw, all is good? or did I manage to wreck the repo for you last night?
[14:15] <apw> tgardner, you managed to lose a couple of things somehow but they are back now
[14:15] <apw> tgardner, the version built ok and is being consumed ok
[14:16] <tgardner> apw, hmm, I was worried about that, but couldn't actually spot them. what did I lose?
[14:17] <apw> a couple of changes i had made to commentary to categorise patches, nothing i couldn't recover from my local master
[14:17] <apw> (stuff to make the next fold down easier)
[14:17] <tgardner> apw, so, they were on master but not on master-next?
[14:19] <apw> tgardner, that is possible.  i wouldn't worry about it am going to change where i do things to prevent this occuring again
[14:20] <tgardner> apw, ack
[15:00] <komputes> JFo: ping
[15:01] <komputes> JFo: Can you let me know if any other info is needed to triage https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596080
[15:01] <ubot2> Launchpad bug 596080 in linux (Ubuntu) "dell latitude e6510 screen stays black from suspend (affects: 15) (heat: 80)" [Undecided,Incomplete]
[15:01] <komputes> JFo: we found a workaround boot parameter, any chance of making it work out of the box when when this hardware is detected?
[16:00] <ogasawara> bjf, sconklin: either of you started in on the Hardy rebase?  If not, I'll start it.
[16:00] <sconklin> ogasawara: no
[16:00] <sconklin> not me
[16:01] <bjf> ogasawara, i've not, was about to package up maverick
[16:01] <ogasawara> bjf, sconklin: cool, I'll start hardy then.
[16:01] <ogasawara> sconklin: want me to also get lucid and karmic packaged up?
[16:02] <sconklin> ogasawara: sure, why would I turn that down?
[16:02] <ogasawara> heh
[17:53] <tgardner> apw, bug #683775
[17:53] <ubot2> Launchpad bug 683775 in linux (Ubuntu) "Natty Alpha 1, i915 has blank screen after boot (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/683775
[18:04] <ogasawara> JFo: did you still need to chat with me?  /me never saw an email.
[18:06] <JFo> I think my question was a bit premature ogasawara. I am still reading the source on the KernelBugList script before I ask you anything about it :)
[18:06] <JFo> so I didn't send the email
[18:06] <ogasawara> JFo: ok cool
[18:06] <JFo> until I can better phrase it :)
[18:07] <ogasawara> JFo: I have to admit that script is quite a hack so might be hard to follow
[18:07] <JFo> heh
[18:07] <JFo> well, combine that then with my limited python knowledge and you can understand my delay :-D
[18:07]  * JFo is learning though
[18:08] <ogasawara> JFo: I could probably try to add some comments to it which might help
[18:09] <ogasawara> JFo: just point me to the copy you are using
[18:09] <JFo> nah, this is actually forcing me to learn the way ythings work
[18:09] <ogasawara> JFo: ok
[18:09] <JFo> which I think is better for me
[18:09] <JFo> :)
[18:09] <JFo> don't worry about it
[18:10] <JFo> I am getting it 
[18:13] <ogasawara> bjf: I like that checklist.  we do need to throw it into a wiki or something...
[18:14] <bjf> ogasawara, i'd really like it to be a web form page with a storage backend (me *HATE* wiki)
[18:14] <JFo> <-lunch
[18:14] <JFo> brb
[18:15] <bjf> ogasawara, you know, someone that is going to take 3 months off with nothing better to do could probably do that in her spare time :-)
[18:16] <ogasawara> heh
[18:19] <ogasawara> bjf, sconklin: hardy test builds are underway, am going to start on Dapper in the mean time.
[18:19] <bjf> ogasawara, cool!
[18:19] <sconklin> yay
[18:24] <tgardner> apw, do you still have the Ubuntu-2.6.37-6.17 tag in your tree? It does not appear to be in the repo.
[18:36] <apw> tgardner, will check
[18:37] <tgardner> apw, am also thinking the regression is because of the built-in AGP
[18:37] <apw> tgardner, ok i've pushed
[18:37] <apw> tgardner, could be
[18:37] <apw> tgardner, but why does your machine fail and my idneticle one work
[18:37] <apw> with the same kernel bits
[18:37] <tgardner> apw, I'm spinning a kernel without CONFIG_AGP=y
[18:38] <tgardner> apw, um, dunno. but I _do_ think its a race condition.
[18:40] <apw> tgardner, ok have to move locations ...
[18:40] <tgardner> apw, you headed home?
[18:40] <apw> tgardner, let me know how the AGP thing works out
[18:41] <apw> tgardner, am going out for dinner with the guys here then home
[18:41] <apw> will check in when i get there
[18:41] <tgardner> apw, I'll update the bug report
[18:41] <tgardner> shall I subscribe you?
[18:41] <apw> please do subscribe me
[18:41] <apw> tgardner, will scratch my mini to try and reproduce what you have from todays dailies too
[18:42] <tgardner> apw, done
[18:42] <apw> jjohansen, get that one reported too, gpu hangs rock
[18:43] <jjohansen> apw: will do
[18:49] <JFo> bjf, these examples in the lpltk are great... thanks :-)
[18:50] <JFo> <- finally had a chance to look at them
[18:50] <bjf> JFo, cool, my plan is, if i have to explain something to someone, i'm going to explain it in an example
[18:50] <JFo> definitely works for me
[18:51] <JFo> I can apply these immediately in my new scripts
[19:04] <JFo> bjf I just remembered a question I had wanted to ask a while back. Why do we skip processing of regression- bugs in the new-process -new script?
[19:04] <JFo> you may have told me, but I forgot
[19:04] <JFo> :-/
[19:05] <bjf> JFo, don't know
[19:05] <JFo> oh
[19:06] <JFo> :)
[19:06] <JFo> heh
[19:06] <JFo> ok
[19:06] <bjf> JFo, that script is full of rules that i don't understand why they are the way they are
[19:06] <bjf> JFo, remember it predates me
[19:06] <JFo> right
[19:06] <JFo> I couldn't remember if that was something we consciously added or not
[19:07]  * JFo is writing up some items for us to chat about concerning the arsenal scripts.
[19:07] <JFo> not stuff that you have to do
[19:07] <bjf> JFo, not that i remember now, though maybe at the time we/i had a reason to do so
[19:07] <JFo> just things I wanted you and I to talk about before too long
[19:07] <JFo> heh
[19:07] <JFo> no problem
[19:07]  * JFo isn't worried about it
[19:12] <alex88> hi.. natty live cd in synaptic says that has kernel 2.6.37-5.14 but i've downloaded source and after compiling it says 2.6.37-rc2.. modules will work on livecd kernel?
[19:13] <tgardner> alex88, cat /proc/version_signature
[19:13] <alex88> on live cd?
[19:13] <tgardner> yep, after booting
[19:14] <alex88> oh.. i don't have it running.. i'm compiling kernel.. i'll try in few secs...
[19:28] <GrueMaster> apw: I have done some preliminary testing of linux-linaro-omap on my beagleXM and have not seen any major issues.  System boots as normal, no crashes, and no changes in support from what I can see so far.
[19:33]  * tgardner --> lunch
[19:34]  * cking --> calling it a day
[19:35] <JFo> enjoy cking 
[19:37] <cking> I always enjoy :-)
[19:37] <JFo> :-D
[19:41] <alex88> btw, the alpha1 that's near will be rc4?
[19:41] <alex88> *2.6.37-rc4
[19:44] <pgraner> JFo, how are we standing on bugs with patches?
[19:46] <JFo> pgraner, so far I am working out how to handle them appropriately on a case by case basis so that I can document the process (more for me than anything else)
[19:46] <JFo> I am going through them this week to weed out the ones incorrectly set as having a patch
[19:46] <JFo> and removing them
[19:47] <JFo> plus I was just drafting an e-mail for apw with a list of questions that should help the majority of the process
[19:47] <JFo> I suspect it will take a bit to answer as it involves manipulating the patches themselves
[19:47] <JFo> magical runes and all
[19:47] <JFo> I'll CC you on it
[19:50] <pgraner> JFo, ok, I suspect most are not worthwhile or obsolete at this point. ATM I'm not so much concerned with process as clearing them out, perhaps giving each team member some that they can churn out would get you there faster. Then work out process with a new fresh patch when they start coming in?
[19:50] <JFo> I agree.
[19:50] <JFo> ok. I can do that then
[19:51] <pgraner> JFo, ack
[19:51] <alex88> tgardner: /proc/version_signature is correct 2.6.37-rc2.. why inserting module from that kernel source gives "disagrees about version of symbol module_layout" ?
[19:54] <alex88> need to use the same source and running kernel??
[20:00] <JFo> bjf, what tag are you guys using on your SRU bugs? I want to get them on the list
[20:00]  * JFo has a moment of clarity and looks on the Tagging page
[20:00] <bjf> JFo, i just (yesterday) started using "kernel-tracking-bug" and there's one more ...
[20:00] <JFo> ok
[20:04] <bjf> JFo, also "stable-reverted-<release>" and "stable-reapply-<release>"
[20:04] <JFo> ok
[20:04] <JFo> do you just want the ones from natty on the list for those or whatever is tagged?
[20:06] <tgardner> alex88, it should say something like 'Ubuntu 2.6.37-7.19-generic'. any modules you're trying to load must have been built against the kernel you have booted.
[20:06] <JFo> bjf, that was a dumb question
[20:06] <JFo> let me rephrase
[20:06] <JFo> will there be a time that there are any of those last two on versions earlier than Maverick?
[20:07] <JFo> I see 6 reverted for maverick now
[20:07] <bjf> JFo, Lucid
[20:07] <JFo> ok
[20:07] <JFo> so only lucid and maverick for now
[20:07] <JFo> cool
[20:07] <alex88> tgardner: it's 2.6.37-5.14 and 2.6.37-rc2.. I've compiled kernel when running maverick kernel, so older, rebuild filesystem.squashfs with included the recompiled modules but it seem that has the old one.. how can i do a think like this? Should i recompile with 2.6.37-rc2 running?
[20:08] <tgardner> alex88, what is it you're trying to do?
[20:09] <alex88> tgardner: i have to replace ahci module with recompiled one to add support to my hdd controller and use it
[20:09] <tgardner> alex88, you're gonna be better off rebuilding the whole kernel after updating the module source.
[20:10] <alex88> i've extracted the squashfs, and replaced /lib/modules/2.6.37-5-generic/kernel/drivers/ata/ahci.ko with my own
[20:10] <alex88> i've tried to follow the guide on ubuntu doc but i had errors in initrd.. Btw, i have the whole kernel compiled and debs.. what should i do?
[20:11] <tgardner> external modules have to be built against the kernel headers using exactly the same version of gcc and binutils
[20:11] <alex88> oh... otherwise i'll get that error right?
[20:12] <tgardner> right, your modules won't load
[20:12] <alex88> but, i've replaced the ahci.ko, why is it loading correctly (but it seems not patched)? and he can't insmod the same file?
[20:13] <tgardner> I haven't the faintest idea
[20:14] <alex88> ok :) thanks for helping
[20:47]  * jjohansen lunch
[21:46] <JFo> bbiab
[22:30] <apw> jjohansen, did rtg let you know how his testing went?
[22:31] <jjohansen> apw: he said the -6 worked for him and he was going to try head with a patch, but I didn't here anything after that
[22:32] <apw> jjohansen, thanks ;)
[22:33] <jjohansen> apw: mine is very much a different issue, it seems it almost always a gpu hang being reported
[22:34] <vish> apw: hi.. did you notice the comment regarding RV515 flickering with the kernel you had prepared?  is there anything else that needs to be done for the bug?
[22:44] <vish> apw: err, rather the flickering is /fixed/ with your kernel..
[23:07] <apw> vish that is good information but unless we can square the circle with the original bug and fix that too we are in a hole
[23:21] <chrismsnz> JFo: Looks like martin peterson has started commiting code for that bug - including backports
[23:21] <chrismsnz> (the stex scsi corruption bug)
[23:22] <chrismsnz> i can see it in his working copies: http://git.kernel.org/?p=linux/kernel/git/mkp/linux-2.6-mkp.git;a=summary - see for-stable-2.6.3x.y heads
[23:28] <JFo> chrismsnz, excellent! :)
[23:28] <chrismsnz> I've updated the bug with the patches if you want to check it out
[23:28] <chrismsnz> https://bugs.launchpad.net/linux/+bug/586897
[23:28] <ubot2> Launchpad bug 586897 in linux-2.6 (Debian) (and 2 other projects) "stex driver (Promise SuperTrak 8350/4650,etc) produces drastic I/O errors/corruption with 10.04 or later (affects: 3) (heat: 18)" [Unknown,Confirmed]
[23:31] <chrismsnz> unfortunately I can't test it anymore, we put the server into production running 9.10 :-O
[23:32] <JFo> :-(