[01:22] <Rocket2DMn> hey guys, had a quick question.  Bug 332170 is talking about a message printed during boot and seems to be related to a problem some people are having with their systems performing poorly.
[01:22] <ubot3> Malone bug 332170 in linux "[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset" [Undecided,Confirmed] https://launchpad.net/bugs/332170
[01:22] <Rocket2DMn> I see the message "cpufreq: No nForce2 chipset" also, but don't experience extra slowness, though I've always used ondemand for cpufreq
[01:44] <mjg59> The message is harmless
[01:49] <Rocket2DMn> thanks mjg59 , i'll let them know
[01:50] <mjg59> Should really be KERN_INFO rather than KERN_ERR though
[01:51] <Rocket2DMn> where do you see that it is ERR?
[01:51] <mjg59> The sourcecode
[01:51] <mjg59> I'll send a patch upstream
[01:51] <Rocket2DMn> ah, if it was INFO would it be printed to the screen?
[01:51] <mjg59> No
[01:52] <Rocket2DMn> Ok, so you want me to change the bug to something saying that message should be KERN_INFO instead of KERN_ERR
[01:52] <Rocket2DMn> ?
[01:54] <mjg59> Feel free
[01:54] <mjg59> The slowness is because p4-clockmod is binding and getting used with the ondemand governor
[01:54]  * Rocket2DMn nods
[01:54] <Rocket2DMn> is it just adapting then and will improve?
[01:55] <mjg59> I've told Scott how to fix that
[01:56] <Rocket2DMn> fix which? the printing or the slowness?
[01:57] <mjg59> The slowness
[01:57] <Rocket2DMn> Ok, so what we really have is two bugs in cpufreq then?  One for slowness and one for changing STD_ERR to STD_INFO ?
[01:59] <mjg59> Fix slowness:
[02:00] <mjg59> sed -i s/1000000/10000001/ arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
[02:01] <Rocket2DMn> I don't have the kernel source code, you are changing a value of 1 million to 1 million + 1?
[02:02] <Rocket2DMn> Well, I'll take your word for it :)  Shall I include that in the report, or do you know if there is another report open for the slowness problem?
[02:04] <Rocket2DMn> i thikn i see it
[02:04] <Rocket2DMn> bug 332017
[02:04] <ubot3> Malone bug 332017 in linux "Significant performance regression in 2.6.28-8.24 due to p4-clockmod" [High,Fix committed] https://launchpad.net/bugs/332017
[02:04] <mjg59> No, one million to ten million and one
[02:07] <Rocket2DMn> ah, I didn't read close enough, sorry.  Is the Scott in the bug I just listed the same Scott you mentioned earlier?
[02:07] <Rocket2DMn> Scott James Remnant
[02:07] <mjg59> Yes
[02:08] <Rocket2DMn> Ok, great!  I'll just have this bug I started with be used to fix the KERN_ERR issue.
[02:08] <Rocket2DMn> Thank you for your help mjg59 
[02:10] <mjg59> Rocket2DMn: Patch just got accepted upstream, so it'll be fixed in 2.6.30. The fix can be backported easily.
[02:10] <Rocket2DMn> for the slowness?
[02:11] <mjg59> For the message
[02:11] <mjg59> I'm chatting with the cpufreq maintainer about the slowness issue
[02:11] <Rocket2DMn> Ah, i just marked as triaged, guess I'll change to Fix Committed.  Thanks for the update
[02:11] <mjg59> Well, it's not committed to the Ubuntu kernel
[02:11] <mjg59> So I don't know that fix ommitted is correct
[02:11] <Rocket2DMn> that would be Fix Released
[02:12] <Rocket2DMn> last time i checked anyway
[02:12] <mjg59> I've lost track of how launchpad stuff is triaged nowadays
[02:12] <Rocket2DMn> https://wiki.ubuntu.com/Bugs/Status
[02:12] <Rocket2DMn> For us, Committed means its committed anywhere, even upstream
[02:16] <Rocket2DMn> Hey you wouldn't happen to have a link to an upstream bug report or a commit page would you?
[02:25] <mjg59> Nope, it hasn't been pushed yet
[02:26] <Rocket2DMn> heh ok, back to Triaged we go.  That's all I have, thank you again for your time mjg59 .
[02:28] <mjg59> No problem
[02:28] <mjg59> It should turn up in the cpufreq git tree shortly
[02:37] <Shanix_> hi all, I am getting the error -> kernel: [365385.583926] python[943]: segfault at 8908ec93 ip b7c50c8c sp bf843430 error 4 in libgobject-2.0.so.0.1800.2[b7c46000+3c000]
[02:37] <Shanix_> is there anyway that I can fix it by add/remove certain package??
[02:41] <mjg59> It's not a kernel problem - the kernel is just reporting that one of your applications crashed
[03:28] <Shanix_> mjg59, I see. Thanks.
[04:21] <TimStarling> I isolated a kernel bug a week ago, it's totally ubuntu's fault, not related to upstream, it's a regression and it's easy to fix
[04:22] <TimStarling> I put a comment on the bug report and emailed the person who committed the bug
[04:22] <TimStarling> but still no response
[04:22] <TimStarling> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/297213
[04:22] <ubot3> Malone bug 297213 in linux "Intrepid: Missing hdaps_ec kernel module" [Medium,New] 
[04:23] <TimStarling> is there anyone here willing to look at it?
[13:26] <TimStarling> quiet channel
[13:31] <iulian> It's weekend.
[13:42] <TimStarling> you mean you people have a life outside ubuntu?
[13:46] <LLStarks> morning
[13:50] <TimStarling> morning
[13:51] <TimStarling> iulian: I'll take that as a yes
[14:05] <LLStarks> what's up with the ubuntu kernel naming scheme?
[15:04] <maxb> LLStarks: What do you mean?
[15:05] <LLStarks> 2.6.28-8 = 2.6.28.6
[15:05] <LLStarks> right?
[15:10] <maxb> LLStarks: the -8 is the ABI number
[15:10] <LLStarks> what does that mean?
[15:11] <maxb> It means that that number will be incremented by the Ubuntu packagers to signify that kernel modules must be rebuilt
[15:12] <LLStarks> but surely the kernel that gets packaged is based off of a point release, isn't it?
[15:12] <marius_> hello, I posted a bug report with a patch. i wounder if I did everything right: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/330259
[15:12] <ubot3> Malone bug 330259 in linux-meta "Problematic volume control keys and mute key of several notebooks + Patch" [Undecided,In progress] 
[15:13] <LLStarks> what version is the current jaunty kernel based on?
[15:16] <marius_> is there anything else to be done by me ?
[15:16] <LLStarks> what is the difference between 2.6.28-8 and 2.6.28.6?
[15:20] <marius_> nobody here who can answer my question?
[15:21] <maxb> LLStarks: the key thing to understand is that the .6 and -8 are telling you about totally separate concepts
[15:21]  * LLStarks is n00b. Explain to me like you would a child.
[15:22] <maxb> The ABI number, which always comes after a hyphen, serves one purpose only: to designate the compatibility (or not, as the case may be) of the built kernel with particular builds of modules
[15:23] <maxb> The point release number designates the number of the upstream point release.
[15:23] <maxb> A point release may *or may not* cause an ABI bump
[15:23] <maxb> Conversely, and ABI bump may be required for reasons other than a point release
[15:23] <maxb> (i.e. an Ubuntu-specific change)
[15:24] <maxb> s/and/an/
[15:24] <LLStarks> does -8 imply a point release has occurred?
[15:24] <maxb> No
[15:25] <maxb> the ABI number implies nothing whatsoever about point releases
[15:25] <maxb> (Though it would be somewhat unusual for 7 ABI bumps to have occurred without a single point release happenning)
[15:25] <maxb> (7, because it starts at 1)
[15:26] <LLStarks> so. when i roll a 20-sided kernel +5 charisma and kms support, what i am getting?
[15:26] <LLStarks> *kernel for
[15:26] <maxb> To discover which point releases have been integrated into an Ubuntu kernel, you must inspect the package changelog
[15:26] <LLStarks> **am i
[15:27] <LLStarks> why is it like that? shouldn't such things like a point release be readily reflected?
[15:27] <maxb> No
[15:29] <maxb> The fact that you need to rebuild your kernel modules is a more significant event than the upstream stable branch happening to release
[15:29] <LLStarks> i see.
[15:29] <maxb> Information on which point releases are included is always available in the package changelog
[15:31] <LLStarks> how can i tell which ABI i'm rolling when i use kernelcheck?
[15:32] <maxb> I've not encountered kernelcheck, what is it?
[15:33] <LLStarks> dot dot dot.
[15:33] <LLStarks> http://kcheck.sourceforge.net/
[15:33] <IntuitiveNipple> LLStarks: We now build upstream kernels and provide them in the archives
[15:34] <LLStarks> i saw.
[15:34] <LLStarks> no kms though.
[15:34]  * LLStarks gives angry glare
[15:34] <IntuitiveNipple> not yet, give it time!
[15:34] <IntuitiveNipple> That'll come for Karmic
[15:35] <LLStarks> can't you just enable i915.modeset?
[15:36] <IntuitiveNipple> You'd have to ask Andy. So far as I'm aware they are being built with the Ubuntu configs... but... I've not actually looked closely at that :)
[15:36] <maxb> LLStarks: I'm not entirely certain I understand your question, but assuming you mean "When I build my own kernel by non-Ubuntu means, which Ubuntu ABI am I getting?", the answer is "Quite possibly none of them, if you're building your own kernel, build your own modules too."
[15:38] <IntuitiveNipple> You can get the abi with "make kernelversion" or "make kernelrelease"
[15:39] <LLStarks> what folder?
[15:42] <IntuitiveNipple> the root of the kernel source
[15:42] <IntuitiveNipple> that's part of the standard kernel Makefile
[15:42] <IntuitiveNipple> "kernelrelease" only works after "make prepare"
[15:42] <TimStarling> can I repeat my question from yesterday?
[15:43] <IntuitiveNipple> TimStarling: I saw it... not had time to do anything though
[15:43] <TimStarling> ok
[15:43] <marius_> I also got a question you got time for me ?
[15:44] <TimStarling> so should I keep asking people until someone gives in and does it?
[15:45] <IntuitiveNipple> TimStarling: I seem to recall several months ago, something similar happened with another module. Can't remember which one, though :s
[15:45] <TimStarling> seems kind of silly that a module can just go missing like that
[15:46] <IntuitiveNipple> There could have been a good reason... some (in)compatibility issue that wasn't logged in the changelog
[15:46] <TimStarling> true
[15:47] <maxb> I have noticed a trivial bug in the lbm prepare-compat-wireless.sh script - a missing $ sign on a shell variable expansion. Is there someone around who could just apply that trivial change?
[15:47] <TimStarling> that's why I emailled Ben Collins first
[15:49] <TimStarling> I've had this laptop for almost a year now, and ubuntu has slowly been supporting more and more components in it
[15:50] <IntuitiveNipple> Looking at the commit diff you reference, I'm almost sure I've dealt with that previously.
[15:51] <TimStarling> the hard drive has had a bit of corruption and I've been wondering if it's about to go, that's what made me think of hdaps
[15:55] <TimStarling> if you need me to help test it, I'll be around
[16:05] <IntuitiveNipple> ha.. found it! https://lists.ubuntu.com/archives/kernel-team/2008-September/003171.html
[16:06] <IntuitiveNipple> Tim-away: Looks like the same forgetfulness as happened Gutsy > Hardy
[16:32] <IntuitiveNipple> maxb: {WT} ?
[16:37] <maxb> yes
[16:37] <maxb> I guess I could send a patch to the kernel team, but it's a single character :-)
[16:37] <IntuitiveNipple> ok
[16:38] <IntuitiveNipple> they all count :D
[20:38] <maco> hi amber
[20:38] <maco> are you going to try to help with the bug jamming
[20:38] <maco> ?
[20:40] <maco> er...wrong channel