[08:36]  * apw yawns
[08:39] <abogani> apw: Good morning!
[08:48] <apw> gah 11 minutes before launchpad goes, if one needs anything
[08:48] <apw> abogani, moin!
[08:52] <AnAnt> Hello, could the kernel patch noted by crimsun on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414795 be applied in maverick ?
[08:52] <ubot2> Launchpad bug 414795 in pulseaudio (Ubuntu) (and 1 other project) "PC beep no longer works in Karmic alpha4 (affects: 4) (heat: 30)" [Undecided,Invalid]
[08:56] <akgraner> apw ping
[08:57] <apw> akgraner, hi
[08:57] <akgraner> apw - I tried the kernel you asked me too - no overheating
[08:58] <apw> akgraner, exceelent, i'll tell bisect 'good' then and get you another one ...
[08:58] <akgraner> okie dokie - I didn't try using wireless as that didn't seem to be an option with the one you gave me
[08:59] <apw> akgraner, hrm odd
[08:59] <akgraner> broadcom
[08:59] <apw> AHH you need the indep headers too, i'll make sure they are in the next oe
[08:59] <apw> one
[09:00] <apw> akgraner, building ...
[09:00] <akgraner> okie dokie - I leave for Ohio in like 12 hours - but will test what I can before I leave
[09:02] <apw> AnAnt, to get that on the dev teams radar it should be emailed to kernel-team email list requesting its consideration for maverick
[09:03] <AnAnt> apw: thanks
[09:05] <apw> AnAnt, i'd refer you to the FAQ question on 'how can get requesti a patch be included in the ubuntu kernel?" but there doesn't seem to be one!
[09:08] <apw> AnAnt, there is: https://wiki.ubuntu.com/Kernel/FAQ/DevHowToPatch
[09:11] <AnAnt> apw: thanks, according to  Kernel/Dev/KernelPatches , I should refer to upstream thread that discussed the patch, but I know nothing about it
[09:12] <apw> if you don't know, leave it out, ensure the bug is linked to as dtchen says stuff in there those considering wil lcare about
[09:14] <AnAnt> linked to ?
[09:16] <apw> the email contains the bug number or a web link to the bug
[09:17] <AnAnt> ah, ok
[09:47]  * cooloney just installed daily-live iso of maverick on his inspiron 1012, but found kernel doesn't find the Network Wired controller
[09:48] <cking> cooloney, what wifi chipset do you have?
[09:48] <cooloney> so there is no network on my laptop
[09:48] <AnAnt> apw: thanks again
[09:48] <cooloney> cking: wifi controller is in my lspci list
[09:49] <apw> cooloney, no wired controller did you say?  which one is it normally
[09:49] <cooloney> but failed to find the wire network controller in my lspci
[09:49] <cooloney> apw: no wired controller
[09:49] <apw> right, but there is one, what one _was_ it before it wasn't there
[09:51] <cooloney> apw: i have to search in the google, hold on
[09:51] <apw> cooloney, 1012 is a new mini10 yes
[09:51] <cking> isn't that broadcom wl?
[09:51] <apw> cking, can you hear me ?
[09:54] <apw> akgraner, ok am pushing a 'bisect2' kernel to the same place, will be there in about 10 mins
[09:55] <akgraner> apw - thanks!
[09:55] <apw> akgraner, late there isn't it ?
[09:55] <akgraner> early almost 5am
[09:55]  * cking wonders if akgraner ever sleeps
[09:55] <apw> akgraner, sorry any time before 6 is late not early
[09:55] <cking> time is relative ya know
[09:56] <apw> akgraner, you getting up at 4 now ?
[09:56] <akgraner> cking, I do :-) but I won't be here this weekend so I have lots of notes and to do lists to leave for *everyone* :-)
[09:57] <akgraner> apw, yep something like that - kids are back in school and Becca had to be at school by 0645 the last 2 weeks for drivers ed
[09:57] <cooloney> cking: /winxp/15
[09:57] <apw> akgraner, just say no
[09:57] <cking> cooloney, eh?
[09:57] <apw> cooloney, that doesn't sound like the name of a controller to me
[09:58] <cooloney> sorry, &_&
[09:58] <amitk> akgraner: 5am, eeeeeks! I haven't seen that time on my clock ever unless I've stayed up all night
[09:58] <akgraner> plus I wanted to be up early to test the kernels from apw before I head to OLF in case something weird happens - since my computer will be with me
[09:58]  * cking thought time between midnight and 6am did not exist
[09:59] <apw> akgraner, just make sure you download the offiical good kernel that was the latest good one, and keep it as a .deb on your machine
[09:59] <jjohansen> no no its the time between 6am - 8am that doesn't exist
[09:59] <cooloney> apw and cking, lspci http://pastebin.ubuntu.com/490836/
[09:59] <apw> jjohansen, you can talk
[09:59] <akgraner> apw will do :-)
[09:59] <jjohansen> who me :)
[10:00] <cooloney> apw and cking, dmesg -> http://pastebin.ubuntu.com/490838/
[10:00] <apw> cooloney, its not there, as you said, but that doesn't help
[10:01] <apw> cooloney, this is a dell mini 10v new version yes ?
[10:01] <apw> if so then its likely its an rtl8139
[10:02] <cooloney> 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
[10:02] <cooloney> apw: i guess this is my missing wired ethernet controller
[10:03] <apw> oh, a differnet one than normal ... hrm
[10:03] <cooloney> apw: let me boot into lucid live-cd and check the lspci
[10:10] <apw> akgraner, push complete
[10:13] <akgraner> apw awesome same place as before?
[10:13] <apw> akgraner, yeah, bisec2
[10:13] <apw> bisect2
[10:14] <akgraner> looking now  - downloading now :-)
[10:14] <akgraner> do I need both header files
[10:15] <apw> the second one may help wireless work as you have bcmwl
[10:15] <akgraner> so the one that says all? or just the i386?
[10:16] <apw> i'd get an install all three bisect2 .debs
[10:16] <akgraner> roger that
[10:16] <akgraner> everything is downloading now
[10:17] <akgraner> give me just a few and I'll reboot and see what happens 
[10:17] <apw> akgraner, no rush as and when you get a chance
[10:17] <akgraner> apw if I don't do it now - when the sun comes up  - something shiny will go by and you'll have to remind me :-)
[10:23] <cooloney> apw and cking, so weird. in lucid live cd, wired ethernet still missed
[10:26] <cking> cooloney, were you running lucid on this before you installed maverick?
[10:26] <cooloney> cking: yes, ethernet works fine before
[10:26] <cking> most curious
[10:26] <cooloney> after i installed maverick today, it's missing
[10:27] <cking> cooloney, I suggest unplugging the power, taking out the battery, completely powering it off and retry
[10:27] <apw> cooloney, cnd has one of those machines, might want to ask him if his net is ok
[10:28] <cking> cooloney, are you booting with the ethernet cable already connected or not?
[10:29] <slacker_nl> for those who want/need to know: the generic kernel in -proposed on lucid works for me :)
[10:32] <akgraner> apw, this one will be listed as 32-23 as well correct?
[10:33] <akgraner> I installed it and selected it but still no wireless - will boot back into the new kernel and try connecting wired this time brb
[10:34] <apw> akgraner, yeah same name
[10:37] <cooloney> cking: let me try your method
[10:37] <cooloney> apw: cnd has a final product, mine is an engineering sample
[10:37] <apw> ahh
[10:37] <cking> bound to work then ;-)
[10:38] <cking> got the latest BIOS on it?
[10:38] <cooloney> cking: i think so, if it still fails, i will check the BIOS 
[10:40] <apw> and chceek its not disabled in the bios all of a suddent
[10:46] <cooloney> cking and apw, nice, i got my wired controller back after uninstalling the battery
[10:46] <apw> !
[10:46] <apw> on maverick ?
[10:46] <cooloney> reboot again with external power supply
[10:46] <cooloney> apw: yeah, maverick
[11:17] <akgraner> apw, my machine is about 61 degrees Celsius with the new kernel - with 22 it hovers around 48 but 61 is better than 90
[11:18] <apw> hrm, not convinced that means its good or not
[11:18] <apw> akgraner, ^^
[11:18] <akgraner> had to boot back into 22 to get back online though  - so now I am back to 48 
[11:18] <apw> could you run while :; do :; done in a terminal window and see what it does
[11:18] <apw> i suspect that one may be bad
[11:21] <akgraner> apw okie dokie brb
[11:32] <akgraner> apw, I ran that command at got into the 70's before I stopped it
[11:33] <apw> akgraner, so that sounds like a bad kernel to me then
[11:33] <akgraner> yep I believe you are correct
[11:33] <akgraner> I rebooted back into 22 for now
[11:33] <apw> yep, told the bisect its bad
[11:34]  * apw builds akgraner another kernel
[11:34] <akgraner> apw, thanks!
[12:29] <apw> akgraner, ok uploading a third kernel now ... about 10 mins to run
[12:35] <ilmari> mjg59: bah, the acpi battery units fix doesn't apply to the maverick kernel due to it updating the battery info asynchronously :(
[12:38] <mjg59> ilmari: Shouldn't be a difficult backport
[12:51] <akgraner> apw okie dokie
[12:59] <apw> ilmari, the async patch was pretty small, so i'd be supprised if its hard to apply
[13:00] <apw> whats the fix for
[13:00] <ilmari> apw: changing battery capacity units
[13:00] <apw> ilmari, got a pointer to the patch ?
[13:00] <ilmari> https://patchwork.kernel.org/patch/119791/
[13:01] <ilmari> apw: it adds an argument to the acpi_battery_update function, which is what is being called asynchronously
[13:01] <apw> ahh a pain indeed
[13:01] <ilmari> easiest would probably be to create another async function that calls it with that argument
[13:01] <apw> ilmari, patchworks seems to be dead
[13:01] <ilmari> WFM
[13:02] <apw> Internal Server Error
[13:02] <ilmari> s/argument/argument set/
[13:02] <apw> yep
[13:02] <pgraner> apw, you narrowing down akgraner's problem?
[13:02] <ilmari> the patch link fails, but the mbox link works
[13:02] <apw> pgraner, slowly but shurly, she is testing a third bisect point
[13:03] <ilmari> hm, it seems to be intermittent
[13:03] <ilmari> apw: try again
[13:03] <pgraner> apw, how many patches are you down to now?
[13:03] <apw> pgraner, still loads
[13:04] <pgraner> apw, yikes
[13:04] <apw> 80 or so i'd guess, but we started at about 400 so we're getting there
[13:05] <apw> poke her to report her testing on this one :)
[13:05] <pgraner> apw, she's testing it now
[13:05] <pgraner> apw, I have to keep telling her the dpkg incantation to install the bits... 
[13:05] <apw> heheh
[13:06]  * pgraner feels like a scratched cd
[13:06] <akgraner> the up arrow key is a beautiful thing 
[13:06]  * pgraner is trying to be hip and updated... so I used that instead of a broken record
[13:10] <apw> pgraner, heh should be a 'looped mp3' surley
[13:11]  * apw cannot see any patches in the good->bad range that make any sense as the cause ... lets hope the bad is right
[13:12] <pgraner> apw, yea, its got to be something obscure
[13:12]  * ilmari will have a go at porting the acpi battery patch later (but not today)
[13:13] <apw> ilmari, may be easier to pop the async patch, apply it and fix that one as it goes on
[13:15] <akgraner> apw, installed and ran a script based on the command you gave me earlier - it got up to 74 degrees in less than 5 mins
[13:16] <apw> akgraner, and if you run it now on the -22 known good one ?
[13:17] <akgraner> let me find out brb
[13:24] <akgraner> apw, with the script it is hitting 75 with the script running on -22
[13:24] <apw> so ... its likely this and the previous 'bad' was actually a good
[13:24] <apw> to confirm that you could go to your latest kernel which is deffo bad and doing the same test
[13:25] <apw> akgraner, ^^
[13:25] <akgraner> yep - I think it's -25
[13:25] <akgraner> will do that now
[13:26] <apw> thanks, if we are 'bad'ing when we should be 'good'ing we'll be here forever
[13:29] <akgraner> apw with the latest kernel - I hit the 70's with the script in less than 10 seconds
[13:29] <apw> ok ... so thats the test then 70 in seconds == bad, 70 in 5 mins == good
[13:30] <apw> so i've reversed the previous bad to a good, and will get you a new kernel shortly
[13:30] <akgraner> so do I start timing with 22 and go forward when I get the new kernel?
[13:31] <apw> well we know -22 is 5 mins, and we know that the previous time we said 5 mins was bad, so i've redone the bisect changing that to a good result
[13:31] <apw> the next kernel just need to know if its 5 mins or 10s to 70
[13:31] <apw> the former == good, latter == bad
[13:32] <akgraner> roger that
[13:34] <cnd> cooloney, I've had a few odd issues with ethernet in maverick
[13:35] <cnd> the driver would die I think
[13:35] <cnd> oops in /var/log/messages
[13:35] <cnd> but I don't usually use ethernet, so I don't know how often it occurs
[13:36] <cking> cnd, I've seen the ethernet disappear on early prototype machines like cooloney did. complete power off seemed to help for some unknown reason
[14:11] <apw> akgraner, ok bisect4 is on its way up
[14:11] <apw> let me know how she fairs for you
[14:16] <apw> akgraner, its up and ready
[14:41] <akgraner> apw ok will do
[14:41] <akgraner> I have to step out for an hour or so but will let you know as soon as I get back
[15:17]  * apw pops out for a late lunch
[15:18] <apw> ahh scratch that
[15:28] <diwic> bjf, so long story short, after a small discussion with JFo, we decided to put us both up for holding the triage session this Saturday, but if you wan't me to hold it, I can do that
[15:29] <bjf> diwic, i had no plans for doing it and was hoping to do other things. how much time is involved
[15:31] <diwic> bjf, the actual session for sound is one hour
[15:32] <diwic> JFo, do I have to prepare some Lernid stuff, and if so, how do I do that?
[15:32] <diwic> I've never used Lernid
[15:37] <diwic> bjf, so if I were to hold the session, and I assume I am :-) , you got an email of what I'm going to talk about
[15:48] <bjf> diwic, i've got nothing, i have pretty much just ignored the summit completely
[15:49] <diwic> bjf, okay. I'll hold it. Let's see if anyone shows up. Do you think what's in that email is a good outline of what people would like to hear on a triage session?
[15:52] <JFo> diwic, no
[15:52] <JFo> lernid is just a tool that folks can use to watch the class
[15:52] <JFo> diwic, even if it seems no one is watching, the show should still be done since we keep a log of the class so that people can look later
[15:53] <diwic> JFo, okay, I'll just spare the work needed to create slides then
[15:53] <JFo> yeah, unless you already have something, I'd just chat about sound
[15:53] <diwic> JFo, I have an outline of what I want to talk about, hopefully bjf is reviewing it right now.
[15:53] <JFo> cool
[15:55] <bjf> diwic: that's a pretty good list, if you threw that together in 10 minutes i've very impressed
[15:55] <bjf> diwic: looks really good to mi
[15:55] <bjf> s/mi/me/
[15:56] <diwic> bjf, no, that was not in 10 minutes. I did that a few weeks ago or something when I thought about sound troubleshooting in general (w r t wiki pages and ubuntu-bug audio)  
[15:56] <bjf> diwic: regardless it's a very good list
[15:57] <diwic> bjf, great. Then I have something to talk about, at least :-)
[16:45] <ogasawara> tgardner: just saw your email about broadcom in staging-next
[16:45] <ogasawara> tgardner: think that's something we want to get into Maverick?
[16:49] <tgardner> ogasawara, If we do I think it'll come back via compat-wireless
[17:01] <JFo> who is dealing with mvl issues now? bug 634161
[17:01] <ubot2> Launchpad bug 634161 in linux-mvl-dove (Ubuntu) "Unable to handle kernel paging request at virtual address 0ce003be (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/634161
[17:01] <bjf> JFo: ericm
[17:02] <JFo> looks to be the same issue as seen on omap
[17:02] <JFo> thanks bjf
[17:13] <algspd> hi
[17:13] <algspd> need help with i915
[17:14] <algspd> anyone?
[17:21] <JFo> algspd, describe the problem and someone may be able to help
[17:21] <JFo> we can't answer as to whether we can help until we know that
[17:22] <algspd> Ok, If I try to boot on LVMS kernel freezes while booting, if I boot on VGA everything is ok and X starts, and if I boot without kms on LVMS and using vesa driver it boots on LVMS
[17:23] <algspd> the problem is that i want to boot with kms on laptop screen (LVMS)
[17:24] <JFo> hmmm
[17:24] <JFo> algspd, have you filed a bug on this?
[17:25] <algspd> no, i think's not a bug but a missconfiguration or a hardware particularity
[17:26] <JFo> I understand, but it is best if we have a bug for this sort of thing so that we can fix the issue for all users of i915 that may be affected.
[17:27] <JFo> that and so we can have a central place for environment information to look at
[17:27] <JFo> while digging into the problem
[17:27] <algspd> ok where to post the bug?
[17:27] <JFo> do you have a Launchpad account?
[17:28] <JFo> on https://launchpad.net/ ?
[17:28] <JFo> if so it is a simple thing to file the bug using 'ubuntu-bug linux' from the terminal window
[17:32] <JFo> <-lunch
[17:34] <bjf> ogasawara: git://kernel.ubuntu.com/bradf/ubuntu-linux mvl-dove
[17:34] <bjf> ogasawara: git://kernel.ubuntu.com/bradf/ubuntu-lucid mvl-dove
[17:39] <algspd> If I try to boot on LVMS kernel freezes while booting, if I boot on VGA everything is ok and X starts, and if I boot without kms on LVMS and using vesa driver it boots on LVMS. The problem is that i want to boot with kms on laptop screen (LVMS).  I switch interface with "video=LVDS-1:d" as kernel param.
[17:39] <algspd> can anyone help?
[17:43] <ogasawara> bjf: looks good to me
[17:43] <bjf> ogasawara: thanks
[17:57] <JFo> guess my instructions weren't clear enough
[18:00]  * cking reboots
[18:07] <manjo> ogasawara, in case we have driver issues with WD HDDs you think you can make room for fixes after 16th ?
[18:07] <ogasawara> manjo: just replying to your email
[18:07] <manjo> ok
[18:08] <ogasawara> manjo: but in short, there's not going to be a large window for any changes beyond kernel freeze
[18:08] <manjo> bah
[18:09]  * manjo can't bribe leann with beer anymore 
[18:12] <pgraner> ogasawara, http://lwn.net/Articles/404248/
[18:12] <pgraner> ogasawara, something we can pkg up for maverick?
[18:13] <bjf> pgraner: heh, rtg already mentioned it on the mailing list
[18:13] <pgraner> bjf, ah, I'm behind on mailing lists today... on the phone all AM
[18:13] <cking> apw, commit a321cedb12904114e2ba5041a3673ca24deb09c9 seems to be the offending patch - on Lucid TjMax was 85, but now with this patch my model 0xf cpu is defaulting to TjMax as 100
[18:13] <ogasawara> pgraner: heh, I asked tgardner about it and if we did get it for Maverick, he suspects it'll come via compat-wireless
[18:14] <ogasawara> [08:45:39] <ogasawara> tgardner: just saw your email about broadcom in staging-next
[18:14] <ogasawara> [08:45:58] <ogasawara> tgardner: think that's something we want to get into Maverick?
[18:14] <ogasawara> [08:49:41] <tgardner> ogasawara, If we do I think it'll come back via compat-wireless
[18:14] <ogasawara> pgraner: ^^
[18:15] <pgraner> ogasawara, ack
[18:57] <JFo> pgraner, have you seen this? http://uds.ubuntu.com/tracks/
[19:12] <pgraner> JFo, yep why?
[19:19] <JFo> just wondered
[19:32] <pgraner> ogasawara, ping
[19:32] <ogasawara> pgraner: pong
[19:32] <pgraner> ogasawara, where do you stash the kernel release mgr notes?
[19:32] <pgraner> ogasawara, wiki search is failing me
[19:33] <ogasawara> pgraner: https://wiki.ubuntu.com/Kernel/Handbook/ReleaseManagement
[19:33] <pgraner> ogasawara, thank you
[19:33] <JFo> I always forget the Handbook bit
[19:35] <pgraner> ogasawara, we prolly need to add a section about how to get things in the release notes
[19:36] <ogasawara> pgraner: ack
[19:36] <pgraner> ogasawara, by adding a release note task and subscribing ubuntu-release-notes and adding some rough example text
[19:36] <ogasawara> pgraner: I'll get a blurb crafted and added
[19:37] <pgraner> ogasawara, coolio not sure where it should go in there, thx
[19:44]  * ogasawara lunch
[19:51] <ck> is there any way that I can help out the ubuntu kernel team in terms of development work? I was clicking around the websites and I am pretty confused by the ways in which we can help out in development work.
[19:55] <apw> ck we are alwats 
[19:55] <apw> alwat
[19:55] <apw> always keen for help.  we do most of the devleopment side on the mailing list
[19:56] <ck> hey apw thanks for the reply..
[19:56] <jjohansen> ck: it pretty wide open, choose something you are interested in, and start sending patches, and discussing
[19:56] <ck> oh so its pretty much free and easy? which means I do not need to get into any offical team or such?
[19:57] <jjohansen> ck, no official team needed, but it is good to subscribe to the mailing list
[19:57] <jjohansen> otherwise all your mails will have to be moderated
[19:59] <ck> ok thanks jjohansen, I shall do that tomorrow
[19:59] <ck> you said something about "choose something you are interested in", does that mean I should be surfing around Launchpad?
[20:00] <jjohansen> ck: well you can if you are interested in bugs
[20:00] <apw> yeah remember a distro kernel is mostly an integration and publishing exercise, the meat of the work is bug related
[20:00] <jjohansen> ck: basically, just find bits and pieces you are interested in, maybe you want a specific patch from upstream in, maybe you like hacking audio
[20:01] <jjohansen> so, you target those areas, perhaps work with upstream, or just bring missing bits to our attention
[20:02] <jjohansen> as apw said most of the distro kernel work is integration and bug work, but you don't have to do that
[20:02] <jjohansen> if you are doing this on your time, have fun with it, pick things that interest you
[20:02] <jjohansen> or things you want to learn about
[20:03] <jjohansen> there will never be a shortage of items looking for attention
[20:03] <ck> thats true.. we can never have a perfect OS
[20:03] <ck> alright seems like I should sign up for the mailing list and hang around this channel more often
[20:04] <ck> thanks jjohansen and apw!
[20:35]  * jjohansen steps away for a bit
[21:12] <pgraner> ogasawara,  tagging for release notes already described in https://wiki.ubuntu.com/RCBugTargetting
[21:36] <ogasawara> pgraner: I'll just have the Release Manager notes auto include the release notes section of RCBugTargetting
[21:36] <pgraner> ogasawara, rock on
[23:17] <kriebly> Hi there, I was wondering if I need to be concerned about "CVE-2010-2960 keyctl_session_to_parent NULL deref system crash" with Ubuntu 10.4/Lucid's linux-image-2.6.32-24-server (amd64)
[23:17] <ubot2> kriebly: The keyctl_session_to_parent function in security/keys/keyctl.c in the Linux kernel 2.6.35.4 and earlier expects that a certain parent session keyring exists, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a KEYCTL_SESSION_TO_PARENT argument to the keyctl function. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-2960)
[23:18] <kriebly> I didn't find any discussion in the list archive or irc logs :)
[23:19] <kees> kriebly: it has not been fixed it; it is planned for the next security update
[23:19] <kriebly> thanks kees. Do you know when that update is coming out?
[23:21] <kees> kriebly: I haven't talked to smb about it, but probably last next week.
[23:22] <kriebly> okay. late next week. Thanks for the info!