[00:44] <bjf> ogasawara: you ever build lbm by hand?
[07:04] <diwic> According to ubuntu-kernel's meeting minutes, I have at least one "work item". How do I find out what that work item is?
[07:07] <RAOF> diwic: Check out http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.html
[07:11] <diwic> RAOF, thanks
[08:30] <lacostej> Anyone does know how to bring attention to a regression with a patch ? See bug #86820. I've nominated it for Maverick in launchpad but that was probably not the right thing to do...
[08:34] <diwic> lacostej, if there is a patch in 2.6.36, you have tested it and it works okay, you might want to send a pull request on the ubuntu-kernel mailing list
[08:34] <lacostej> I've backported it to 2.6.32 and I use it everyday
[08:34] <diwic> lacostej, https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
[08:35] <lacostej> I can upgrade to 10.10 beta, and try backporting it to 2.6.35 as well if needed
[08:59] <lacostej> diwic: I mailed the list. I am not subscribed so I hope it will go through.
[09:00] <diwic> lacostej, nothing showed up yet, it's likely moderated
[09:01] <lacostej> ok. I will stick here for a while then :)
[09:46] <apw> lacostej, it is indeed moderated for non-members ... spam overload elsewise
[09:47] <lacostej> apw should I register and re-send or just wait for the moderation to happen ?
[09:47] <apw> lacostej, it should appear shortly
[09:47] <lacostej> ah yes. it did in the archive
[09:48] <lacostej> mmm it got truncated in the web archive. The patch isn't there
[09:48] <apw> lacostej, subject ?
[09:48] <lacostej> https://lists.ubuntu.com/archives/kernel-team/2010-September/012634.html
[09:48] <lacostej> "[Maverick] [pull request] Input: i8042 - reset keyboard controller	wehen resuming from S2R"
[09:48] <apw> who knows where the actual email is
[09:49] <lacostej> apw: in my sent box ;)
[09:50] <apw> heh arrived finally ... you'd think there were 100s of people on the list
[09:52] <jjohansen> good night *
[09:53] <lacostej> apw: does my mail contain the patch ? 
[09:53] <lacostej> because the web version doesn't
[09:53] <apw> yep all there
[09:53] <lacostej> good
[09:53] <apw> though its not a pull request :)  its the patch 
[09:53] <lacostej> thanks for the help
[09:54] <apw> all i did was tell it you wern't a spammer
[09:54] <lacostej> that's all that was required :)
[09:55] <lacostej> yea it's not a pull request, but the upstream commit id is in the mail. I guess they can cherry pick the patch if needed. Not sure how they would do that. maybe a format-patch + patch or a merge. I don't have great git skills
[09:56] <apw> the contents of the email is just fine, i'd have put [PATCH] on it not [pull request] just cause its just a patch.  you did the right things putting the upstream id in there etc
[09:56] <apw> everything someone needs to find and apply the original themselves is in there so its good
[09:59] <apw> lacostej, done the admin on the bug, the fix will get tracked on the mailing list now
[09:59] <lacostej> great
[11:34] <cking> apw, http://kernel.ubuntu.com/~cking/dust.jpg
[13:45] <apw> cking, we didi change how we work out if you have CPU internal sensors in 2.6.35, using cpuid instread of a hard coded list
[13:45] <apw> so it is entirly possible it is different
[13:45] <apw> sensors command may twll you where they are coming from 
[13:46]  * cking looks
[13:56] <apw> cking, does sensors say 'owt ?
[13:57] <cking> no
[13:57] <cking> apw, sensors
[13:57] <cking> coretemp-isa-0000
[13:57] <cking> Adapter: ISA adapter
[13:57] <cking> Core 0:      +61.0°C  (high = +100.0°C, crit = +100.0°C)  
[13:57] <cking> coretemp-isa-0001
[13:57] <cking> Adapter: ISA adapter
[13:57] <cking> Core 1:      +61.0°C  (high = +100.0°C, crit = +100.0°C)  
[13:58] <apw> i wonder if you had those before, worth checking in lucid next time you are forced to reboot
[13:58] <apw> 61 is still jolly hot
[13:58] <cking> I assume ISA adapter refers to the fact that sensors is getting info from the lower 64K I/O port 
[13:59] <apw> yeah i'd been assuming something similar
[13:59] <apw> time for a temperature gague on the air coming out :)
[13:59] <cking> 61 is better than the 91 degrees I saw before cleaning out the dust puppies
[13:59] <apw> heheh
[13:59] <apw> mad
[14:03] <apw> jk-, what was the symptoms on your battery failure
[14:03] <jk-> apw: flashing amber battery light
[14:04] <jk-> (inc. in BIOS)
[14:04] <mjg59> Doesn't coretemp read from an msr?
[14:04] <apw> jk-, i have also killed a battery recently on a dell, just wondered if it sounded similar
[14:04] <apw> but it sounds like different symptom
[14:04] <apw> mjg59, yeah, i suspect the isa one is 'under' the CPU
[14:04] <jk-> yeah, I was suspicious it was caused by an upgrade
[14:05] <jk-> but I think that's just coincidence
[14:05] <jk-> more likely caused by the warranty expiring :D
[14:05] <apw> heh yeah
[14:22] <AnAnt> Hello, how can I enable CONFIG_SND_HDA_INPUT_BEEP_MODE ? I read that it is runtime configurable via sysfs 
[14:27] <AnAnt> sudo sh -c "echo 1 > /sys/module/snd_hda_intel/parameters/beep_mode"
[14:27] <AnAnt> sh: cannot create /sys/module/snd_hda_intel/parameters/beep_mode: Permission denied
[14:30] <abogani> AnAnt: Could you try as root effective user?
[14:30] <mjg59> apw: Does /sys/module/snd_hda_intel/parameters/beep_mode exist?
[14:32] <apw> AnAnt, ^^
[14:45] <mjg59> apw: Whoops, sorry
[14:51] <apw> :)
[15:14] <AnAnt> mjg59: yes it does exist
[15:14] <AnAnt> mjg59: funny, is that it did get written to
[15:14] <AnAnt> that's is the contents of the file:
[15:15] <AnAnt> 1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[15:15] <AnAnt> I dunno what are all those values, shouldn't it just be 0 or 1 or 2 ?
[15:21] <apw> bjf[afk], poke
[15:21] <bjf> ouch
[15:22] <bjf> apw, how can i be of no use to you today?
[15:23] <ogasawara> bjf: did you get your answer about building lbm?
[15:23] <apw> bjf, wanted to chat about the CD create scripts
[15:23] <apw> mumble ?
[15:24] <bjf> apw, give me a sec, got to straighten out a 9 yr old
[15:24] <apw> bjf, np 
[15:24] <bjf> ogasawara: talk to you about it in a bit maybe
[15:29] <JFo> bjf, or sconklin will we be doing an upload to -proposed sometime soon? QA is asking.
[15:29] <bjf> JFo: did one last week
[15:29] <sconklin> ^^
[15:29] <JFo> k
[15:29] <bjf> JFo: why is qa asking? do they want to test it?
[15:30] <sconklin> bjf: good one ;-)
[15:30] <JFo> yep
[15:30] <JFo> they are wanting to do a run on the planned testing
[15:30] <bjf> JFo: as long as you're talking to them about it, it would be nice if we could see some results
[15:30] <JFo> ok
[15:30] <bjf> JFo: we've been asking about that for a while
[15:31] <JFo> yeah, I've asked
[15:31] <sconklin> This is an especially good one to test, as it's a lot of changes
[15:31] <bjf> JFo: the one that is there now is a very good candidate
[15:31] <JFo> will let you know what the result is
[15:31] <JFo> cool
[15:32] <sconklin> JFo: Do you think that they can actually test any of the bugs that should be closed by this one?
[15:32] <JFo> not sure: 
 JFo, I can point you to how they would look, but I don't have current results for kernels... there was stuff missing in checkbox as well to link packages to tests
[15:32] <JFo> :-/
 JFo, yeah, it's just the code changes weren't done last week... I'm looking for a future upload to see that what tracks uploads really works properly :/
[15:34] <JFo> they are rolling out an updated checkbox to test
[15:34] <JFo> he will retest the kernel in -proposed
[15:35] <JFo> and I'll let you know the results of the testing
[15:35] <sconklin> JFo: it'll likely be a couple of weeks at least before we get a new proposed.
[15:35] <JFo> no problem
[15:35] <JFo> he is going to run the tests on the one there again
[15:35] <sconklin> and that's only if this one has no issues
[15:35] <JFo> yep
[16:42]  * tgardner packs for wireless mini-summit
[17:37] <ogra> tgardner, could you hold back with the omap4 upload until tomorrow, we need to build an image for TI with the new kernel and couldnt build any since beta due to the kernel vs meta skew on omap4
[17:38] <bjf> ogasawara: i'm trying to build ubuntu-lucid-lbm in a lucid-amd64 chroot ...
[17:39] <bjf> ogasawara: i did an "fdr clean" and then an "dpkg-buildpackage -b -rfakeroot -uc -us"...
[17:39] <ogasawara> bjf: the corresponding linux-headers are also installed right?
[17:39] <bjf> ogasawara: this seems to have gotten through compatwireless and alsa but is dieing on wwan-drivers with: ccache: failed to create /root/.ccache (Permission denied)
[17:40] <bjf> ogasawara: yes and i modified the debian/changelog to match the headers :-)
[17:40] <bjf> ogasawara: i went backwards one abi
[17:41] <tgardner> ogra, there is an omap4 currently building with some packaging fixes. I'll hold off until next week unless you hassle me about it.
[17:42] <ogra> tgardner, well, just because you said in your mail you'd upload immediately after that built 
[17:42] <ogasawara> bjf: hrm, not sure about the Permission denied error.  when I built my test debs for the maverick, I did 'fdr clean' followed by 'fdr binary-arch'
[17:42] <ogra> if you planned to hold back longer anyway, i wont complain
[17:42] <bjf> ogasawara: will give that a try
[17:42] <tgardner> ogra, will do. apw ^^
[17:42] <ogra> tgardner, and i know about the current build, eagerly waiting for it :)
[17:43] <bjf> ogasawara: same error, will retry it clean
[17:43] <diwic_dinner> fdr?
[17:43] <bjf> diwic_dinner: an alias for "fakeroot debian/rules"
[17:43] <diwic_dinner> aha
[17:44] <tgardner> bjf, why is there a ccache in there? perhaps something in your environment is scrogged?
[17:45] <apw> tgardner, its nearly complete as far as i can tell.. i assume i did push everything so you had something to base your pull into
[17:45] <bjf> tgardner: don't know what to tell you
[17:45] <tgardner> apw, yep, it all looked corect
[17:45] <apw> good ... so are you asking if you should wait ?
[17:46] <tgardner> bjf, is it clean, clean ?
[17:46] <ogra> apw, btw, see -devel ... if we would not try to strip translations from the linux package that might speed up building ;)
[17:46] <ogra> especially on arm
[17:47] <bjf> tgardner: yes, fresh clone
[17:47] <bjf> tgardner: going to try again on tangerine in case it's my chroot somehow
[18:05] <manjo> cking, yo!
[18:06] <cking> manjo, hi
[18:06] <manjo> cking, sorry I missed this mornings chat on mumble
[18:07] <cking> what time does that mumble session start for you?
[18:08] <manjo> cking, heh 8am :)
[18:08] <cking> oh, zzz time then :-)
[18:09] <manjo> heh
[18:09] <manjo> no I forgot about it 
[18:09] <manjo> cking can you hear me on mumble ? 
[18:09] <cking> no, my audio is off (again!)
[18:09] <manjo> ah
[18:39] <gbledsoe> greetings all - do we have members of the kernel team on presently?  
[18:43] <JFo> gbledsoe, always
[18:43] <bjf> ogasawara: i was able to build the maverick lbm on tangerine but not the lucid lbm
[18:43] <JFo> :)
[18:44] <bjf> ogasawara: still pounding my head against it
[18:44] <gbledsoe> thanks JFo
[18:44] <JFo> gbledsoe, my pleasure
[18:44] <gbledsoe> I had a couple quick questions and hope I won't take up too much of anybody's time 
[18:45] <JFo> ask away gbledsoe 
[18:45] <ogasawara> bjf: hrm, I'll see if I can get lucid lbm to build.
[18:45] <JFo> if anyone is available and knows, they will answer
[18:45] <gbledsoe> I run a number of freeswitch servers that see a pretty good load (15 mb/s in rtp traffic, 100 calls apiece or so)
[18:45] <gbledsoe> so the server kernel has always given us quite a bit lower load
[18:46] <gbledsoe> I tested the upgrade from 8.04 to 10.04 and found that the server kernel has gone away?
[18:46] <gbledsoe> now it appears (on x86) to be a pointer to generic pae
[18:46] <gbledsoe> which uses 250 Hz clock and cfq schedular
[18:46] <gbledsoe> under load, this produces about 4x the load average for us
[18:47] <gbledsoe> so is this a permanent?  and has anyone complained about this at all?
[18:48] <gbledsoe> and what are the chances of resurrecting the x86 server kernel?  :-D
[18:49] <apw> gbledsoe, yep that is deliberate and permenant.  server class h/w normally is 64bit now, so why not use that kernel
[18:49] <apw> noone complained about it at the UDS sessions when it was discussed, nor really complained when it was announced close to a year back now
[18:50] <gbledsoe> in my experience 64 bit kernel has more bugs because it has traditionally seen less use - I've been bitten a number of times
[18:50] <gbledsoe> so I should pay closer attention in the future, aye?  :-)
[18:50] <apw> now that 32bit and 64bit arch support is merged, that is less likely and server side its the one we test now as its the only one
[18:51]  * apw runs 64 bit on everything that will run it
[18:51] <gbledsoe> ok, well that answers my question, thank you
[18:51] <apw> heh you cirtainly need to realise we are on a 6 month cycle and everything can change every six months
[18:51] <apw> gbledsoe, you can even run the 64bit kernel on 32 bit userspace in theory as a test
[18:52] <gbledsoe> true
[18:52] <apw> though you have to force the kernel to install
[18:56]  * cking calls it a day
[19:22] <ogasawara> bjf: on tangerine it doesn't look like the header files are installed in the lucid chroots?  but I just tested building lucid lbm on a local box and it passed after I installed linux-headers-server (already had linux-headers-generic installed)
[19:23] <bjf> ogasawara: ok, just rebuilt my lucid chroot locally, will install the headers and try again
[19:23] <bjf> ogasawara: thanks for looking
[19:23] <ogasawara> bjf: np
[19:23] <ogasawara> bjf: I was going to test on emerald, but it seems to be down for me at least
[19:24] <ogasawara> bjf: do you have sudo permissions on tangerine?
[19:24] <bjf> ogasawara: yes
[19:24] <ogasawara> bjf: to install the headers in the lucid chroot
[19:24] <ogasawara> bjf: I can then test it there to make sure it's working
[19:24] <bjf> ogasawara: ok, heading there now to install
[19:32] <bjf> ogasawara: i've installed the headers on tangerine and started my own test build, working better than before
[19:33] <bjf> ogasawara: i had installed the headers on my local build system but didn't on tangerine
[19:33] <bjf> ogasawara: in the past I've usually run into build-dependency issues which pointed at the headers, this time it was trying to build alsa and dying
[19:33] <bjf> ogasawara: anyway, its working better now, will see if everything builds
[19:34] <ogasawara> bjf: cool, let me know
[19:41] <bjf> ogasawara: ok, the build on tangerine worked just fine
[19:42] <ogasawara> bjf: nice
[20:10] <bjf> ogasawara: would you mind ack'ing my lucid lbm pull request?
[20:11] <ogasawara> bjf: sure
[20:34] <akgraner> apw can and will do - thanks - I leave for Ohio LinuxFest tomorrow afternoon  - I'll do my best to get back to you by this evening or early my time tomorrow
[20:42] <apw> akgraner, thanks
[22:07] <ilmari> any chance of getting https://patchwork.kernel.org/patch/119791/ into maverick?
[22:07] <ilmari> "Update battery information on notification 0x81" - fixes erroneous battery reading when unplugging A/C power on newer thinkpads
[22:56]  * jjohansen heads out to do some errands
[23:23] <bjf[afk]> JFo: where is your "buglist" that generates the top 50 list? i'm looking in your home dir on cranberry
[23:45] <[reed]> mjg59: ping?