[00:13] <jjohansen> hggdh: confirmed
[00:15] <hggdh> jjohansen: should I open a bug for that?
[00:16] <jjohansen> hggdh: no not yet, I'll poke at it or at the least poke smb when he comes on
[00:17] <hggdh> jjohansen: thank you
[00:30] <broder> so now that i've grabbed the stacktrace, is there anything i can do to help with the debugging of bug 784335?
[00:30] <ubot2> Launchpad bug 784335 in linux "Heavy network utilization with r8169 leads to kernel panic" [Undecided,Confirmed] https://launchpad.net/bugs/784335
[00:33] <jj-afk> back on later
[04:37] <bAdGigabit> Dose the current kernel support packet injection?
[04:37] <bAdGigabit> more specific. Will it support it for the ath9k drivers?
[04:49] <bAdGigabit> sorry, did anyone reply?
[05:05] <bAdGigabit> sorry, i kewp getting disconneted
[05:05] <bAdGigabit> any awnsers that i missed?
[08:28]  * apw yawns
[08:30] <jk-> hey apw & smb
[08:30] <apw> moin jk-
[08:31] <smb> morning jk- 
[09:04] <eagles0513875> morning apw :D 
[09:06] <valorie> hi all, since I upgraded to 11.04, my mic jack no longer works
[09:06] <valorie> I searched the bugs, but didn't find anyone else reporting this
[09:06] <valorie> what do i need to do to report a useful bug?
[09:08] <apw> eagles0513875, hi
[09:08] <eagles0513875> how goes it apw
[09:08] <apw> valorie, thinking
[09:09] <valorie> eagles0513875 suggested I ask here
[09:09] <apw> smb, can you remember what we file sound bugs against, alsa something something
[09:09] <eagles0513875> apw: it was my suggestion to have her ask here as we thought it might be a kernel issue
[09:09] <eagles0513875> me im kinda having a similar issue with usb webcam with mic and pulse audio
[09:09] <valorie> mic doesn't work either, but it never has
[09:09] <smb> apw, Something like that... could it be alsa-driver or so?
[09:09] <valorie> I think
[09:10] <apw> very likely a kernel issue, and reporting it against the right package is the key
[09:10] <apw> and before my first coffee i can't think what its called
[09:10] <eagles0513875> apw: should we have her try the proposed 38-9 kernel
[09:10] <valorie> I'll be around for another hour or so
[09:10] <awilkins> valorie, Do you know what sound hardware you're using?
[09:10]  * valorie serves coffee around the chan
[09:10] <apw> awilkins, i was just going to mention your fix
[09:11]  * awilkins grins
[09:11] <eagles0513875> im wondering if his fix woudl apply to usb webcams that have mics then again im not sure what that fix is 
[09:11] <valorie> not off the top of my head
[09:11] <awilkins> Probably not to a USB webcam with integrated mic
[09:11] <valorie> what's the command to find out?
[09:11] <eagles0513875> valorie: a simple lspci should tell ya 
[09:11] <eagles0513875> mines a Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
[09:11] <eagles0513875>  
[09:11] <eagles0513875> valorie: lspci on command line and find the line that says audio :D
[09:12] <eagles0513875> i think before it worked with my other motherboard which had a realtek audio chipset this has an intel one : (
[09:12] <apw> valorie, i think its "ubuntu-bug audio"
[09:12] <valorie> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
[09:12]  * apw thinks people have been chanigng things on us
[09:12] <valorie> 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
[09:12] <awilkins> Intel HDA... so that might be affected by that fix
[09:13] <awilkins> Intel HDA is an abstraction for a bunch of different chipsets from what I can gather
[09:13] <apw> awilkins, your change was to the codec side wasn't it ?  remember which one?
[09:13] <awilkins> AD1988
[09:13] <awilkins> valorie, Do us a   `dmesg | grep hda`
[09:13] <awilkins> And tell us what the line with hda_codec says
[09:14] <eagles0513875> valorie: did you check ur settings in the bios
[09:14] <eagles0513875> if you dont have it set to use hd you need to 
[09:15] <valorie> http://paste.ubuntu.com/612193
[09:15] <valorie> no line with hda_codec
[09:15] <valorie> how do I check the setting in the bios?
[09:16] <valorie> I've done that before, but years ago
[09:16] <awilkins> valorie, You'd have to play that by ear - reboot, watch your power up messages for the key for "setup", and hunt around in your menus
[09:16] <eagles0513875> ya 
[09:16] <awilkins> BIOS setup usually requires you to make an affirmative choice to save settings also
[09:17] <eagles0513875> i checked my bios and i dont have any settings in mine 
[09:17] <eagles0513875> this is hopefully a temp motherboard i have 
[09:17] <eagles0513875> till i rma my higher end motherboard
[09:17] <awilkins> But there are too many nonstandard variants for us to walk you through it, probably in the "PCI devices" area
[09:17] <eagles0513875> actually im thinking my issue is more with skype itself
[09:17] <valorie> well, this is my laptop/work/main computer
[09:17] <eagles0513875> cuz i use mumble 
[09:17] <eagles0513875> and my mic works just fine :( 
[09:18] <valorie> oh weird
[09:18] <eagles0513875> ya
[09:18] <eagles0513875> i know 
[09:18] <valorie> well, skype used to work
[09:18] <eagles0513875> i know 
[09:18] <valorie> now the mic doesn't
[09:18] <eagles0513875> valorie: sme issue
[09:18] <eagles0513875> same*
[09:18] <valorie> but I don't remember if that was a different lappy or this one
[09:18] <eagles0513875> apw: who would we need to contact to report this as skype is in the ubuntu partner repo
[09:18] <valorie> BUT: soundrecorder doesn't work either
[09:18] <valorie> eagles0513875: HA!
[09:18] <valorie> like Microsoft will care
[09:18] <eagles0513875> the funny thing
[09:19] <eagles0513875> the older static libs on the skype site work just fine 
[09:19] <eagles0513875> even the version in 10.10 worked
[09:19]  * eagles0513875 needs to develop an alternative to skype before it gets destroyed
[09:19] <awilkins> Skype works just fine on pulse now
[09:19] <valorie> skype hasn't worked for me for at least the last 3 versions of kubuntu
[09:19] <eagles0513875> awilkins: i have no mic input 
[09:19] <valorie> but I've not had a problems with the headphones for a long, long time
[09:19] <eagles0513875> it works fine but no mic
[09:20] <eagles0513875> awilkins: how did you manage to get it to work
[09:20] <valorie> jack worked until upgrade, and then it didn't
[09:20] <awilkins> eagles0513875, Neither did I - previously suffered from #593018, then from #776964
[09:21] <eagles0513875> skype says to go into the pulseaudio settings and i have no idea where those are
[09:21] <valorie> veromix will do it
[09:21] <awilkins> valorie, I had the same thing - but before I had to flip-flop the input selector to get the mic working, but then it stopped
[09:21] <eagles0513875> awilkins: its saying i have to use the local mixer to adjust settings but kmix doesnt have my cam mic listed
[09:21] <valorie> or pavucontrol
[09:22] <valorie> eagles0513875: does alsamixer have it listed?
[09:22] <awilkins> eagles0513875, Well, it sounds like the driver for your cam mic isn't working, or isn't present
[09:22] <eagles0513875> in kmix my logitech quick cam is listed
[09:22] <valorie> sec
[09:22] <awilkins> valorie, Since your hardware previously worked, more chance of working out what's wrong
[09:24] <eagles0513875> skype is bugged 
[09:24] <eagles0513875> i installed pavucontrol and mic is picking up sound there 
[09:24] <eagles0513875> skype for some reason isnt
[09:25] <awilkins> Which version of Skype? I'm presuming latest
[09:25] <awilkins> Specifically, I have 2.2 beta and it works fine with GNOME / Pulseaudio.
[09:26] <awilkins> If you can record sound from your mic, eagles0513875, it's not really a kernel problem, and I would suggest you'd have more luck in a channel devoted to userland software.
[09:26] <eagles0513875> ya
[09:26] <eagles0513875> awilkins: version of skype taht is in the partner repo
[09:27] <awilkins> eagles0513875, AFAIK that's the same as the one straight from the skype website. Mine says 2.2.0.25 in it's "About" box
[09:27] <eagles0513875> ya
[09:27] <eagles0513875> might uninstall it 
[09:28] <eagles0513875> and use the static package from the site
[09:29] <valorie> yay, you got your sound working though!
[09:29] <awilkins> eagles0513875, Try cleaning out it's settings first, move the ~/.Skype folder out of the way, start it up, and try a test call
[09:29] <valorie> I don't have time to restart tonight, but tomorrow when I start up, I'll look in the bios and see if I find anything suspicious
[09:30] <awilkins> valorie, The other tool I found useful was  http://www.alsa-project.org/main/index.php/HDA_Analyzer
[09:30] <awilkins> valorie, That lets you mess directly with the codec parameters
[09:31] <awilkins> valorie, In my case, my mic input pin was not set up right - it needed it's VREF setting to be 80, but the driver wasn't initializing it correctly
[09:31] <awilkins> See : https://bugs.launchpad.net/ubuntu/natty/+source/linux/+bug/776964
[09:31] <ubot2> Launchpad bug 776964 in linux "p5n32e-plus HDA Nvidia AD1988B microphone input not working" [Low,In progress]
[09:32] <eagles0513875> awilkins: still nothing 
[09:32] <eagles0513875> i dont have time to hack at this right now
[09:32] <awilkins> valorie, We've not really discovered what your sound hardware is yet - HDA Intel hides a bunch of implementations and your dmesg didn't tell us what it was either
[09:33] <awilkins> That tool will probably be more informative, at least
[09:33] <valorie> any way to dig deeper?
[09:33] <awilkins> http://www.alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA
[09:33] <valorie> oh, hda analyzer
[09:33] <valorie> which is a script to run
[09:33] <awilkins> Yes, you have to run it as root
[09:33]  * eagles0513875 wants my original motherboard back so badly
[09:33] <awilkins> sudo python run.py
[09:33] <valorie> not sure I can make heads or tails of it
[09:33] <eagles0513875> my original motherboard works so much better then this one 
[09:34] <eagles0513875> would probably require a linux reinstall though :( 
[09:34] <valorie> I'm a writer, not a devel
[09:34] <awilkins> valorie, It just gives you direct access to all those little switches that you see in a recording studio
[09:34] <awilkins> valorie, Instead of one big volume knob
[09:35] <eagles0513875> awilkins: usually i stick with the nvidia nforce chipsets 
[09:35] <eagles0513875> those have realtek which i have never had any issues with 
[09:35] <eagles0513875> not to mention i can use fully my 5.1 atm down to 2.1 with this motherboard
[09:35] <awilkins> eagles0513875, I have an nforce, but my sound is an Analog Devices
[09:36] <eagles0513875> would love to take advantage of the spdif the other motherboard has
[09:39] <awilkins> valorie, If you have HDAAnalyzer running, what's the name on the first AUD_OUT device?
[09:41] <apw> awilkins, this thing should be packaged and installed by default
[09:42] <awilkins> apw, The HDAAnalyzer thing downloads components of itself, but I suppose you could install the bootstrap script. I would guess that
[09:42] <apw> i think i would be happier if someone packaged the bits
[09:42] <apw> as its a bit scarey to download some random stuff and run it as root
[09:42] <awilkins> I would guess that HDA Intel is probably responsible for quite a few bugs because of the myriad of implementations
[09:43] <awilkins> But the actual implementation inside seems to hide well
[09:44] <awilkins> lspci for me does not reflect that the codec is an AD1988B, neither does HDAAnalyzer either, to be true
[09:44] <awilkins> Apart from some of the node names
[09:44] <diwic> for HDAanalyzer, just download snd-hda-tools from ppa:diwic/ppa and run "sudo hda_analyzer"
[09:45] <awilkins> dmesg reports it, but valorie doesn't seem to have that so maybe there is an inconsistent level of logging in the various codec implementations in the drivers
[09:45] <valorie> oh, rather that wgetting it?
[09:45] <valorie> I was opening the /proc/asound/card0/ and looking at it
[09:45] <diwic> valorie, yeah, I packaged it and a few other hda tools up
[09:45] <diwic> (i e if you were asking me)
[09:46] <awilkins> valorie, The first line of /proc/asound/card0/codec#0 seems to be the information we seek
[09:46] <awilkins> At least, in my case
[09:47] <valorie> Codec: IDT 92HD71B7X
[09:47] <awilkins> On the plus side, that's marvellously specific
[09:47] <awilkins> On the downside, it's not the thing we have recently fixed
[09:48] <valorie> snd-tools is installing
[09:48] <awilkins> So it worked in Maverick but not Natty?
[09:48] <valorie> yes
[09:48] <valorie> ok, what do you need from that analyzer?
[09:49] <awilkins> valorie, I can't think of anything specific... but what you can do is try to find your Mic input pin
[09:49] <awilkins> So you should have a bunch of PIN nodes
[09:49] <valorie> in node editor, or text dump?
[09:49] <awilkins> Node editor
[09:49] <awilkins> On the left in the tree there are a bunch of PIN nodes
[09:50] <valorie> oooh
[09:50] <awilkins> If you look in the Config default section on the right, you will see some description of each node
[09:50] <awilkins> Find the one your Mic is plugged into
[09:50] <valorie> Press Detect
[09:50] <valorie> Headphone Drive
[09:50] <valorie> Output
[09:50] <valorie> first pin
[09:50] <awilkins> I found the "Jack color" and "Jack location" bits helpful locating it
[09:51] <valorie> mic jack is pink!
[09:51] <awilkins> e.g. mine is PIN 0x17  Jack type : Mic  Jack location : Ext Jack location2 : Rear
[09:51] <awilkins> That's the one
[09:51] <awilkins> What's it's Wiget control section say?
[09:52] <valorie> boxes are all unchecked
[09:52] <valorie> VREF HIZ below that
[09:52] <awilkins> Ok, check "IN" and change the VREF to 80
[09:52] <valorie> done
[09:53] <valorie> I think that's the jack for an external mic
[09:53] <awilkins> Now open Sound recorder or something with a VU meter (  `pavumeter --record` ) and try it out
[09:53] <valorie> let me get one
[09:53] <valorie> or I guess I can use my headphones
[09:53] <awilkins> Ah, what' the input for the Mic you are actually using
[09:53] <awilkins> That one was probably not initialized if you weren't using it on purpose
[09:54] <awilkins> Esp. if it has "input sense"
[09:54] <valorie> I was trying to get the internal mic working
[09:54] <awilkins> Probably another pin
[09:54] <valorie> Press Detect
[09:54] <valorie> Input
[09:54] <valorie> VREF_HIZ
[09:54] <valorie> VREF_50
[09:54] <valorie> VREF_GRD
[09:54] <valorie> VREF_80
[09:54] <valorie> but it would be cool to get this one working too
[09:55] <apw> internal mics are sometimes on the same plug as the external and connected when the jack is not
[09:55] <awilkins> True, you might want to try that VU meter anyway
[09:55] <valorie> did, and nothing
[09:56] <valorie> just dead
[09:56] <valorie> ok, another pin
[09:56] <diwic> valorie, btw, regardless if you get somewhere or not, will you file a bug (unless you already did) for it, e g "using ubuntu-bug audio"?
[09:56] <diwic> thanks!
[09:57] <awilkins> Pins are just the start, alas, the whole chain of things has to work.... I found the thing that draws an SVG diagram of your codec useful
[09:57] <valorie> Jack connection: Fixed
[09:57] <valorie> Jack type:       Mic
[09:57] <diwic> awilkins, codecgraph is also packaged in snd-hda-tools
[09:57] <valorie> Jack location:   Ext
[09:57] <valorie> Jack location2:  Top
[09:57] <valorie> Jack connector:  Digital
[09:57] <valorie> Jack color:      Black
[09:57] <valorie> No presence
[09:57] <valorie> is another
[09:57] <awilkins> And I was already reasonably familiar with the control set on my codec because I had to monkey around with the selectors to get it to work with Maverick
[09:57] <valorie> well, I will file one, but I wanted decent details
[09:57] <valorie> "it doesn't work" isn't very helpful
[09:57] <awilkins> valorie, That one is probably an audio out
[09:58] <valorie> Stereo
[09:58] <valorie> Output Amplifier
[09:58] <valorie> you're right
[09:58] <awilkins> You want ones that have the PIN cap "Input"
[09:58] <diwic> valorie, that's great although "ubuntu-bug audio" will include some relevant files that can help us analyze the problem
[09:58] <apw> diwic, do you use hda analyser ?
[09:59] <diwic> apw, sometimes, yes
[09:59] <apw> diwic, next time we are in the same place, you have to show us how to interterpret its output
[09:59] <valorie> Jack connection: Jack
[09:59] <valorie> Jack type:       HP Out
[09:59] <valorie> Jack location:   Ext
[09:59] <valorie> Jack location2:  Front
[09:59] <valorie> Jack connector:  1/8
[09:59] <awilkins> Headphones out
[09:59] <valorie> Jack color:      Green
[09:59] <valorie> is headphones
[10:00] <valorie> Headphone Drive
[10:00] <valorie> Output
[10:00] <diwic> apw, maybe it's time for another audio triaging session 
[10:00] <valorie> widget control has nothing selected
[10:00] <diwic> apw, I saw JFo wanted more of that as well
[10:00] <awilkins> valorie, Paste the contents of your /proc/asound/card0/codec#0 file to the pastebin
[10:00] <apw> diwic, yeah i'd like to listen in on one again, there is more tooling now than i remember
[10:01] <diwic> apw, we could do one hda driver specific 
[10:01] <apw> yeah, as that is our primary pain point
[10:01] <valorie> http://paste.ubuntu.com/612205
[10:01] <awilkins> valorie, I think node 0x18 is your baby
[10:02] <awilkins> valorie, Select node 0x18 and check the VREF value
[10:02] <valorie> Jack connection: Fixed
[10:02] <valorie> Jack type:       Mic
[10:02] <valorie> Jack location:   Ext
[10:02] <valorie> Jack location2:  Top
[10:02] <valorie> Jack connector:  Digital
[10:02] <valorie> Jack color:      Black
[10:02] <valorie> No presence
[10:02] <valorie> there is none
[10:02] <valorie> in is checked
[10:02] <valorie> but no vref value
[10:03] <awilkins> Hmm, from this file, node 0x18 should be "Internal Mic Capture Volume"
[10:03] <awilkins> But no VREF
[10:03] <valorie> yes, that's the name
[10:03] <awilkins> Bah
[10:03] <valorie> but no vref
[10:03] <diwic> awilkins, digital mics usually don't have VREF_80 and that stuff because the connection between the dmic and the codec is digital
[10:03] <valorie> maybe it never DID work
[10:04] <valorie> sec, gotta take the old dog outside
[10:04] <awilkins> diwic, Thanks... I'm just an amateur
[10:04] <diwic> awilkins, and we need more helpful amateurs :-) and help them become more qualified
[10:05] <awilkins> Gah, I had that codec grapher somewhere
[10:06] <valorie> blind, deaf, and when he's gotta go, he's gotta go
[10:06] <apw> diwic, if you haven't met awilkins hes definatly a potential contributer on the debugging audio side
[10:06] <diwic> nice! 
[10:07]  * diwic shakes hands with awilkins 
[10:07]  * awilkins shakes hands back
[10:07] <apw> awilkins, meet diwic our sound expert
[10:08] <diwic> awilkins, the codecgraph utility is packaged and ready in the snd-hda-tools package in ppa:diwic/ppa 
[10:09] <awilkins> diwic, Yup, installed
[10:09] <diwic> (or ppa:diwic/maverick for 10.10)
[10:09] <diwic> awilkins, so what I would do in this case is to take the codec a ride through hda-emu and see if the automuting does what it should
[10:10] <diwic> auto-switching between int and ext mic
[10:10] <diwic> valorie, when you posted that codec file, was anything plugged into the mic?
[10:10] <diwic> awilkins, potentially try a newer alsa-driver as well
[10:10] <valorie> hmm
[10:11] <valorie> I don't think so
[10:11] <valorie> I plugged in to test
[10:11] <awilkins> I think the relevant nodes are ...  nodes   0x18 (the mic pin)  0x1c (audio selector)  and 0x12  (audio input)
[10:11] <valorie> and then just now, plugged in earphones to test
[10:11] <valorie> earphones are really why I'm here
[10:12] <valorie> as it is unknown whether or not the mic ever worked
[10:12] <valorie> laptop isn't that old, but
[10:12] <valorie> don't know
[10:12] <diwic> awilkins, hmm, I /think/ it is 0x18 - 0x1d - 0x13 because that's stream 0, but better double-check in hda-emu
[10:13] <valorie> so the headphones textdump is at http://paste.ubuntu.com/612209
[10:13] <awilkins> diwic, What's the significance of dotty lines over solid ones - I was tending to follow solid ones when I was debugging my own issue
[10:14] <diwic> awilkins, dotty lines are generally unconnected but could potentially be connected if one changes that in the driver or hda-emu
[10:15] <diwic> awilkins, or in hda-analyzer I mean
[10:15] <valorie> and here is the codec#0 with definitely nothing plugged in: http://paste.ubuntu.com/612210
[10:16] <diwic> awilkins, ok so it is 0x18 - 0x1c - 0x12 actually
[10:17] <diwic> valorie, you don't happen to have an ATI controller, do you? 
[10:17] <valorie> yes
[10:17] <diwic> valorie, you might be suffering from bug 741825 then 
[10:17] <ubot2> Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825
[10:18] <valorie> gah!
[10:19] <diwic> valorie, and if so the recommended solution is https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules as we think this was finally fixed a few days ago 
[10:19] <awilkins> If your first one was plugged and your second one was not, then I would concur
[10:19] <valorie> 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
[10:19] <awilkins> Because they are identical
[10:19] <diwic> apw, we should just see some more testing of this fix and then make it into a Natty SRU
[10:20] <diwic> apw, I think it needs two different commits to fix
[10:20] <apw> diwic, big and ugly ?
[10:21] <diwic> apw, no, but potentially affecting a lot of machines, that's my only hesitation...but in this case I think it's worth it
[10:21] <valorie> ok, installing
[10:21] <valorie> and for this, I will restart
[10:24] <jussi> o/
[10:25] <jussi> I just had a major crash of the whole system, ended up with this: http://wstaw.org/m/2011/05/24/2011-05-24_11-37-17_362_Oulu.jpg
[10:25] <jussi> any help ?
[10:25] <diwic> apw, i e affecting all ATI HDA machines
[10:26] <jussi> is there anything else I can get now (after a restart) that would help diagnose this? 
[10:29] <apw> jussi, hmmm another cpuidle_idle_call explosion
[10:29] <apw> what kernel is that?
[10:29] <jussi> jussi@squirrel:~$ uname -a
[10:29] <jussi> Linux squirrel 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
[10:31] <diwic> ok I'll be away for lunch for a while, see you later!
[10:32] <jussi> apw: Im aroundish with this PC for the next ~4 hours. If there is anything else you need, please ask. Ill go file a bug in the meantime. 
[10:37] <eagles0513875> jussi: did you have your whole system lock up on u and freeze nastily
[10:38] <eagles0513875> when you maximize konsole or certain other apps?
[10:38] <jussi> eagles0513875: no. 
[10:38] <eagles0513875> ok just checking cuz that is a super  nasty bug which boils down to an nvidia driver issue
[10:39] <jussi> eagles0513875: given I dont have nvidia...
[10:39] <eagles0513875> ahh 
[10:39]  * eagles0513875 retreats to the amarok channel
[10:40] <jussi> bug 787442
[10:40] <ubot2> Launchpad bug 787442 in linux "Complete machine crash (kernel panic?) " [Undecided,New] https://launchpad.net/bugs/787442
[10:40] <jussi> apw: ^^
[10:42] <eagles0513875> jussi: i was having those with atheros wifi card in my netbook
[10:42] <valorie> here goes nothing, restarting.....
[10:43] <eagles0513875> gd luck valorie
[10:43] <apw> jussi, you had a photo, could you attach that pls
[10:44] <jussi> apw: its attached - first attachment.
[10:44] <apw> stupid launchpad, hiding the important one
[10:44] <jussi> heh
[10:46] <apw> jussi, i've updated the subject.  if this is reproducible you could try the -propsoed kernel which as a heap of stable updates (-9
[10:46] <jussi> apw: I havent managed to reproduce :/
[10:47] <apw> i think i've seen 3 reports of something ismilar, one was put in my hands at UDS, but nothing common about them
[10:47] <eagles0513875> apw: there was my issue with kernel panicing and my atheros wifi card which is fixed in proposed
[10:48] <jussi> apw: I had this bug earlier: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775432 - I put it in someones hands at UDS. 
[10:48] <ubot2> Launchpad bug 775432 in linux "rtl8169 kernel panic" [Undecided,Confirmed]
[10:49] <valorie> thank you SO MUCH! 
[10:49] <valorie> I now have earphones again
[10:49] <valorie> if you give me that bug report, I'll comment on it if necessary
[10:50] <apw> jussi, that one is definatly different
[10:50] <jussi> apw: yeah. 
[10:50] <jussi> apw: it was your hands (and Leann's) that I put it into iirc
[10:51] <jussi> Anywya, If I manage to reproduce, Ill let you know. 
[10:51] <apw> jussi, quite likely :)  i had a lot of machines put in my hands over the week its hard to keep anything striaght
[10:51] <jussi> apw: :)
[10:51] <smb> jj-afk, hggdh FYI: I am able to reproduce the maverick ec2 fail locally. The "close blk" is normal though. It seems to be a very early lockup though. As I see 100% cpu usage but no dmesg output at all.
[10:53] <awilkins> valorie, bug 741825
[10:53] <ubot2> Launchpad bug 741825 in alsa-driver "ATI controllers [1002:4383] and [1002:4383] (rev 40): Intermittent record and jack sense failure" [Undecided,Incomplete] https://launchpad.net/bugs/741825
[11:01] <valorie> also, my mic seems to work now
[11:01] <valorie> at least the volume meter is showing activity
[11:01] <valorie> \o/
[11:04] <valorie> and SKYPE WORKS TOO!
[11:04] <valorie> y'all are miracle workers
[11:05] <apw> valorie, one of the many advantages of open source ... one can fix it
[11:06] <valorie> kub. packagers are working on some free alternatives
[11:06] <valorie> I hope we come up with something as good
[11:06] <valorie> or better
[11:09] <eagles0513875> awilkins: could ur fix possibly fix my issue with my webcam mic if it fixed it for valorie
[11:13] <awilkins> eagles0513875, An integrated webcam mic would be a USB driver problem
[11:14] <eagles0513875> ok
[11:14] <awilkins> eagles0513875, Mine didn't fix valories, she had a jack sensing issue, and my issue was a codec initialization issue
[11:14] <eagles0513875> ahh ok
[11:14] <eagles0513875> i guess ill have to take a look at the bios
[11:14] <awilkins> valorie has been fixed by another patch though
[11:14] <eagles0513875> ok 
[11:15] <awilkins> I think if you can actually record sound from that mic it's not so much a kernel problem
[11:15] <eagles0513875> ok
[11:15] <eagles0513875> software as in skype issue 
[11:17] <awilkins> eagles0513875, Don't know - you might consider trying a GNOME session (or Unity) to see if it works there
[11:17] <awilkins> eagles0513875, I don't know enough about KDE / phonon / whatever to speculate
[11:17] <eagles0513875> ok no worries
[12:37] <diwic> what am I doing wrong if I try to boot from a live Natty USB stick and get the error "Unable to find a medium containing a live file system"?
[12:38] <diwic> and dropped to a busybox shell
[12:42] <diwic> ok; switched usb slot, that helped
[13:32] <htorque> hello everyone! are there known boot problems with oneiric and intel hd graphics? my boot 'fails' 4 out of 5 times (i can ssh into the machine).
[13:32] <htorque> i sometimes see the plymouth text theme (kms problem?), but most of the time it's just a black screen with a blinking cursor. not happening with nvidia on the same notebook.
[14:25] <apw> htorque, nothing known, i use the kernel on my systems here and haven't seen that myself
[14:26] <apw> but i am not using oneiric userspace with them
[14:27] <htorque> apw, thanks. the only weird thing i noticed when ssh'd into the machine, was the short output of lsmod: http://paste.ubuntu.com/612274/
[14:27] <apw> htorque, does lsmod complete ?
[14:28] <htorque> i got a new prompt, so i guess yes (i didn't check the return value)
[14:29] <apw> a prompt is enough for me
[14:29] <apw> so i'd say we're only half booted
[14:32] <htorque> apw, would you say that looks like a kernel issue? i would then try to bisect
[14:33] <apw> very hard to say, i would try with the last natty kerenl on your userspace
[14:33] <apw> and see if the problem is resolved, if so then kernel it is
[14:33] <htorque> apw, thanks, will do.
[14:35] <dmarkey> hmm.. is there a known issue where xen network/block modules arent automatically modprobe'd
[14:35] <dmarkey> in 11.04
[14:39] <apw> dmarkey, in the virtual kernel ?
[14:40] <smb> dmarkey, Hm, not really aware of that. Seemed to have worked for me at least...
[14:40] <smb> (virtual kernel)
[14:41] <dmarkey> i'm using the pae kernel
[14:42] <smb> dmarkey, as domU (just to be sure)
[14:42] <dmarkey> Yes :)
[14:42] <dmarkey> i'll install the virtual kerne
[14:43] <htorque> apw: also happening with the natty kernel
[14:43] <apw> htorque, and you didn't have this i assume on natty itself?  so that implies it is something else
[14:43] <smb> dmarkey, I have not tried generic-pae but at least with the virtual I don't remember any problems when starting an instance
[14:44] <apw> given you have almost nothing running/loaded, i am worried about upstart
[14:44] <htorque> apw: no, natty was working fine
[14:49] <htorque> apw: "init: udev-fallback-graphics main process (...) terminated with status 1" - could this be the cause?
[14:49] <apw> yep, that could easily be the cuase
[14:50] <apw> as things wait for that to complete before starting X
[14:50] <htorque> i just wonder why this doesn't happen with nouveau
[14:50] <dmarkey> smb: do you have a installer initrd with the -virtual kernel
[14:51] <apw> htorque, well that one only does something if the drm driver doesn't load
[14:51] <apw> so its possible its telling you that the drm driver didn't load
[14:51] <apw> and that behaves different for each
[14:51] <apw> now why that has stopped working as normal is another question
[14:52] <apw> from your lsmod you also don't have much of anything else loaded, so it could be a udev issue
[14:52] <smb> dmarkey, not really. I sort of cheat and start of the cloud images (ripping the cloud out) most of the time.
[14:53] <dmarkey> i see. is I assu,e its udev thats dropping the ball here?
[14:53] <dmarkey> assume*
[14:54] <smb> dmarkey, those would be at http://uec-images.ubuntu.com/ (but probably won't help you). Hm, a sec
[14:57] <htorque> apw: "udevd: error binding udev control socket" sounds serious - had to use a camera to capture it, not sure if i get something similar in the nouveau case (it's just scrolling away too fast)
[14:57] <dmarkey> hmm.. how are these bootstrapped?
[14:58] <smb> dmarkey, ah wait. At least for virtual those are built-in... I guess not for the other flavours. So you probably need to add them to /etc/modules
[14:59] <dmarkey> but will that make it into the initrd?
[15:01] <smb> dmarkey, Right, modules, for generic-pae and built-in for virtual. Let me check...
[15:02] <smb> dmarkey, Maybe /etc/initramfs-tools/modules is better
[15:02] <dmarkey> but the modules are in my initrd at the min.. the problem is they're not getting modprobed!
[15:03] <smb> dmarkey, At least the comment in initramfs-tools/modules says that they should get loaded if listed there
[15:03] <dmarkey> ah i see
[15:36] <htorque> apw: it boots fine with natty's udev
[15:36] <apw> htorque, sounds like the place to file a bug then
[15:36] <apw> can you pasge the number here as well
[15:37] <htorque> apw: yeah, thanks! will do.
[15:38]  * ogasawara back in 20
[15:39] <htorque> hm, that's similar to the messages i see: bug 712026 -> comment #14 by smoser
[15:39] <ubot2> Launchpad bug 712026 in udev "cloud-init.conf never runs, instance not reachable via ssh" [High,Fix released] https://launchpad.net/bugs/712026
[15:41] <apw> htorque, that is a very different bug, could you file a new one, and indicate in smosers one that there is a separate bug
[15:46] <apw> htorque, is this a real machine or a VM for you
[15:46] <htorque> apw: real machine
[16:09] <htorque> apw: bug 787610 (sorry, took some time)
[16:09] <ubot2> Launchpad bug 787610 in udev "System fails to boot with Intel HD graphics" [Undecided,New] https://launchpad.net/bugs/787610
[16:32] <hggdh> smb: ping -- maverick ec2
[16:32] <smb> hggdh, pong, yes broken
[16:32] <JFo> heh
[16:32] <JFo> quickest conversation ever
[16:32] <hggdh> smb: will we regen the whole thing? In other words, should we keep on and test maverick on hardware?
[16:33] <hggdh> JFo: but I insist ;-)
[16:33] <JFo> heh, of course :)
[16:35] <smb> hggdh, I'd probably go on while I try to find what broke it
[16:35] <hggdh> smb: roj
[16:35] <smb> hggdh, Maybe start with 32bit to see if it breaks real hw too
[16:36] <hggdh> smb: heh. Nothing like beating on a piece of hot iron. Will do
[16:37] <smb> hggdh, I saw the same hang with the current master-next so at least not fixed in there. 
[16:37] <hggdh> things get more exciting, I see
[16:38] <smb> hggdh, Now I am trying to bisect or make crash work for me...
[16:42] <herton> smb, ogasawara: bjf told me about Finalise() vim for kernel changelog, where it comes from?
[16:42] <smb> herton, IT some vim file magic
[16:42] <herton> I was using dch on my test builds, but seems more practical to use this directly in vi
[16:43] <ogasawara> herton: smb taught me that bit of magic
[16:43] <smb> Though it needed enabling tings sometimes. If it works for you there is even more magic that came from apw to make it a two keystroke
[16:43] <ogasawara> yah, I've got a vim shortcut for it
[16:44] <smb> herton, can send you the relevant vimrc thing
[16:45] <herton> smb: yes please do
[16:45] <apw> yeah i use a couple of bindings
[16:46] <apw> to those vim functions, which are only loaded when the file is called changelog
[16:52] <smb> herton, file is on the way
[16:53] <herton> received here, thanks, will try it
[16:56] <herton> where you define Finalise(), is it from some plugin like package?
[17:00] <herton> ok seems to come from /usr/share/vim/vimcurrent/ftplugin/debchangelog.vim, just wonder why it didn't find it
[17:01] <smb> herton, As I wrote there is also the plugin enable switch. I remember this had to be turned on at some point
[17:01] <smb> So enable filetype plugins and the file must be named changelog
[17:02] <smb> otherwise it is not there
[17:07] <herton> smb: it is what filetype plugin on is supposed to do right? will figure this out later, lunch here, bbl
[17:08] <ppisati> don't we have the meeting in an hour? i think i didn't see brad email
[17:09] <JFo> yep, we do
[17:09] <apw> sconklin, bjf, FYI the lts-backport-natty is now up to date, and should be included in the matrix
[17:09] <bjf> apw, thanks, we were talking about it just a little while ago
[17:09] <apw> i talked to cjw and we don't need to do anything other than get it copied to -proposed 
[17:10] <apw> no process is required.  so i've pulled it forward and uploaded it to ckt PPA, hopefully I did it right :)
[17:10] <bjf> ppetraki, you are correct and i'd completely forgotten about it
[17:10] <apw> the brnaches are all pushed into lucid repo as normal
[17:10] <apw> branch and tag even
[17:10] <bjf> apw, i'll bet you didn't add a tracking bug :-)
[17:10] <JFo> we have a seeming conflict with some app dev board?
[17:10] <JFo> bjf ^^
[17:11] <ppetraki> bjf, what am I right about? (happens alot)
[17:11] <JFo> at 5 in the -meeting room that is
[17:11] <bjf> JFo, looking
[17:11] <JFo> k
[17:11] <JFo> bjf, I'm looking at http://www.ubuntu-news.org/calendars/fridge/
[17:11] <JFo> just FYI
[17:11] <apw> bjf, heh nope, though when i uploaded it i was building it to get it into universe for a MIR, which is not required, so i forgive me ... feel free to blow it up and replace it
[17:12] <bjf> apw, we appreciate any and all help, np
[17:12] <smb> bjf, sconklin Btw, I had been questioned about "when goes lucid from proposed to updates". As the calendar shows this week prep for next cycle I was not really able to answer. ;)
[17:12] <apw> yeah been wondering of those 'yellow' things had been updated since the 2w to 3w transition
[17:12] <sconklin> smb: it is out of our hands.
[17:13] <bjf> smb, basically, qa is behind schedule so we're not sure
[17:13] <bjf> ppetraki, about the meeting
[17:14] <smb> Ah. Somehow I had the illusion for lucid it was done.
[17:14] <JFo> ppetraki, he meant that for ppisati 
[17:14] <JFo> :)
[17:15]  * JFo directs traffic
[17:15] <bjf> JFo, i see what you are talking about, any thoughts on who i talk to about it
[17:15] <JFo> no idea
[17:15] <ppetraki> I figured :)
[17:15] <JFo> one sec...
[17:15] <bjf> ppetraki, sorrry for the noise :-)
[17:15] <ppetraki> np
[17:15] <JFo> bjf, looks like allison
[17:15] <JFo> as per https://wiki.ubuntu.com/AppReviewBoard/Agenda
[17:16] <bjf> JFo, thanks, i'll ping her
[17:16] <JFo> k
[17:16]  * JFo is fully caffeinated today. imagine what I coulod accomplish on Jolt Cola ;)
[17:16] <JFo> could*
[17:16] <JFo> I still wouldn't be able to spell all of the time
[17:18] <smb> JFo, Imagine all the trippple keypressses. :)
[17:19] <JFo> heh
[17:19] <JFo> then you could call me JittersFo
[17:20] <smb> JFo, Or "Zip" (If you ever played Fallout 3 ;))
[17:21] <JFo> heh, I do
[17:21] <bjf> JFo, they are moving, thanks for the heads up
[17:21] <JFo> bjf, my pleasure
[17:22] <bjf> ppisati, am going to be looking for you for ARM status from now on, you are on the agenda
[17:22] <JFo> be ready, we hate slow meetings ;-)
[17:22] <bjf> ppisati, i can let it go this time, but be ready next time
[17:22] <ppisati> bjf: ack
[17:24] <apw> bjf, am i on the hook for anything today
[17:24] <bjf> apw, NO! but i can find something if you like :-)
[17:24] <bjf> apw, or if ogasawara would like me to
[17:25] <apw> heh, that'll be just fine, i assume its at now +00:35
[17:25] <JFo> smb, do I need an EC2 item vor my metrics in the meeting?
[17:25] <JFo> for*
[17:26] <bjf> ##
[17:26] <bjf> ## Kernel team meeting in 34 minutes
[17:26] <bjf> ##
[17:26] <smb> JFo, Hm do we do special metrics for any arm stuff?
[17:27] <JFo> I did have items for them in case they were needed
[17:27] <bjf> smb, you are on the hook for one agenda item
[17:27] <JFo> I don't put them unless you guys tell me to
[17:28] <smb> JFo, Yeah, I am not sure (maybe yet) I need one... I'll come and whine whenever I find out I do
[17:28] <JFo> sounds good
[17:28] <JFo> I'll leave it off for now
[17:28] <smb> bjf, Guess I should look at it then...
[17:28] <bjf> jfo, ogasawara, sconklin smb all have agenda items, just a heads-up
[17:28] <smb> ta
[17:53] <JFo> I'm ready
[17:54] <apw> sconklin, did i see you applied both vesafb patches?  i think i was expecting only the first to apply to older releases
[17:55] <sconklin> apw: well, I've deleted the email now, but I thought that the 0/0 listed all the series. Probably my mistake
[17:55] <apw> I am proposing the first patch for Oneiric, Natty, Maverick, and Lucid
[17:55] <apw> as a clear bug fix.  The second sounds like something we could apply in
[17:55] <apw> Oneiric only and see what falls out.
[17:55] <sconklin> They all applied. Whether that's correct or not is a reasonable question
[17:55] <sconklin> I'll redo it after the meeting
[17:56] <apw> sconklin, ack, the risk for the older releases is too high imo
[17:56] <apw> for the small gain its likely to give
[17:56] <sconklin> apw: ack, I trust that judgement
[17:57] <sconklin> at least it's just a one patch reset unless something else has been pushed ;-)
[17:57] <dmarkey> Anyway, i'm going to file a ticket for this xen-blkfront not being modprobe'd
[18:00] <sconklin> apw: all fixed, thanks for letting me know
[18:08] <JFo> wow, my typing skills fail
[18:09]  * ppisati -> gym
[18:10] <jjohansen> ogasawara: agree with doing config review at the sprint, I don't think there are any critically big changes to come out of it
[18:11] <ogasawara> jjohansen: cool, I'll mark your work item as done then :)
[18:11] <jjohansen> hehe :)
[18:11] <ogasawara> jjohansen: and add an item to our agenda for the rally
[18:11] <jjohansen> thanks
[18:14] <JFo> <-need food, back soon
[18:40] <jjohansen> ogasawara, apw, rtg: actually there was one config that I thought worth discussing now.  CONFIG_HZ
[18:40] <jjohansen> for our i386 and ppc kernels it is 250, but for our amd64 kernels it is 100.  I think desktop should be 250
[18:40] <apw> jjohansen, ok whats your reasoning .... (i tend to agree but)
[18:41] <ogasawara> jjohansen: hrm, I thought bjf had sent a patch for that.
[18:41] <jjohansen> apw: well for desktop we would like a better latency, 250 is a nice compromise between 100 and 1000
[18:41] <bjf> ogasawara, no, i bumped the number of cpus
[18:41] <ogasawara> ah, I stand corrected
[18:41] <jjohansen> it also what we settled on for the i386 desktop
[18:42] <apw> jjohansen, i tend to agree its odd they are not consistant
[18:42] <jjohansen> apw: I don't have any figures, I could go and generate some, but that is one difference that really stood out
[18:42] <apw> i think we moved cause NO_HZ was supposed to make the number meaningless anyhow
[18:43] <jjohansen> apw: no NO_HZ is only for tickless sleep
[18:44] <jjohansen> apw: hrm, no I stand corrected, from the current Kconfig
[18:44] <jjohansen>          This option enables a tickless system: timer interrupts will
[18:44] <jjohansen>           only trigger on an as-needed basis both when the system is
[18:44] <jjohansen>           busy and when the system is idle.
[18:45] <jjohansen> so it for busy as well, now I don't remember that change happening
[18:45] <apw> which should mean a higer HZ is cheaper, but cking's number says not ... hrm
[18:45] <apw> i am inclined to agree that without numbers that they should be consistant, 250 desktop, 100 server
[18:45] <apw> and work from there
[18:46] <jjohansen> apw: I think we should add a work item to generate some numbers and review at the sprint
[18:46] <apw> jjohansen, ack, you got time to do the work, or should i finger cking as he is off :)
[18:47] <JFo> heh
[18:47] <jjohansen> apw: since I brought it up, I'll take it as part of my prep for the config review
[18:47] <JFo> also, it would be awesome if you guys could spare me some skills training at platform
[18:47] <JFo> I'm trying to narrow some stuff we could work on in a few blocks
[18:48] <JFo> will send e-mail once I have more written down
[18:48] <JFo> going to see about getting some of graphics/sound/hardware enablement time as well
[19:02] <bjf> ogasawara, should i pull the config review from the meeting agenda until post Rally ?
[19:02] <ogasawara> bjf: sure
[19:05] <apw> jjohansen, if you have time thats great else just assign it to [canonical-kernel-team] and it'll stay on my radar
[19:06] <jjohansen> apw: lets assign it to me for now and if I don't get to it with in the next week or two we will reevaluate
[19:06] <apw> jjohansen, works for me
[19:29]  * apw wanders off to get some dinner ... laters
[19:38] <JFo> ogasawara, are you aware of a change like the one described in bug 787671 ?
[19:38] <ubot2> Launchpad bug 787671 in linux "Starting with 2.6.39, EBS volumes start at /dev/xvde" [Undecided,New] https://launchpad.net/bugs/787671
[19:38] <JFo> seems like something that should be easy to confirm if I had the requisite volumes :)
[19:39] <JFo> and where would I look to determine if there was a change? obviously git log would help, but anything  more than that?
[19:39] <manjo> how do I determine which upstream tree I cloned my tree from ? 
[19:40] <manjo> thanks found it 
[19:40] <JFo> what was it manjo 
[19:40] <JFo> ?
[19:40] <manjo> .git/config has the info 
[19:41] <JFo> cool, thanks
[19:42]  * JFo grabs oneiric branch while he is thinking about it
[19:51] <ogasawara> JFo: I'm not aware of changes, maybe smb or jjohansen could confirm?
[19:54] <jjohansen> JFo: I haven't follow the ebs volume changes to closely this last kernel, but there were xen patches that went into to 2.6.39, I have a look
[19:54] <JFo> yeah, I initially thought of smb, but after hours for him. :)
[19:55] <JFo> k, thanks jjohansen 
[19:58] <JFo> my oneiric branch fetch is taking longer than I thought
[20:04] <jjohansen> JFo: so there is a patch that affects the xen-blkfront driver device id numbering, I haven't looked at it to much but I suspect it is the cause
[20:04] <bjf> kees, is there a way (other than uploading a package) to see if my upload rights have been granted in LP?
[20:04] <JFo> jjohansen, ok, thanks
[20:05] <kees> bjf: that's an excellent question. I don't know where that information is held, actually. I'll see if cjwatson knows.
[20:09] <kees> bjf: looks like you still don't have it. who else on the team has those rights, just so I can compare?
[20:09] <bjf> ogasawara, 
[20:09] <bjf> kees, ogasawara would have them
[20:10] <kees> all these irc nick vs LP nicks ;)
[20:10] <kees> yeah, I see her perms, so it looks like whoever needs to do that hasn't done it.
[20:11] <bjf> kees, thanks for checking
[20:11] <kees> https://launchpad.net/~ubuntu-kernel-uploaders/+members  is it just this list?
[20:12] <kees> bjf: who from the DMB is supposed to update that?
[20:12] <bjf> kees, that looks like the right list, i don't know who is supposed to update it
[20:13] <kees> (for reference, lp:~ubuntu-archive/ubuntu-archive-tools/trunk/ has edit_acl.py which I'm using as "./edit_acl.py query -p brad-figg" and "./edit_acl.py query -p leannogasawara")
[20:15] <kees> bjf: maco says she has added you now.
[20:15] <kees> and the edit_acl.py output seems to agree
[20:16] <bjf> kees, i just popped onto the list
[20:16] <bjf> kees, you want to remove me from ubuntu-drivers ?
[20:16] <kees> bjf: sure, let's try that again....
[20:17] <kees> bjf: okay, I've deactivated you there. can you still do bug task nominations?
[20:18] <bjf> kees, I'll give it a twirl and get back to you if i have any problems, thanks for the help
[20:18] <kees> bjf: okay, cool. thanks for testing! :)
[20:25] <avinashhm> Hi friends , i am trying to compile ubuntu kernel .. got the sources via 'apt-get source linux-image-$(uname -r)' .. i don't want to use fakeroot to compile ... want to use general make with some configs .. was looking on info to build which config .. any pointers will help 
[20:28] <bjf> avinashhm, https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel documents how we suggest you do it
[20:29] <bjf> avinashhm, if you want to find another way, google is your friend :-)
[20:29] <hggdh> smb: maverick i386 is OK on KVM
[20:30] <avinashhm> bjf, sure ... ;-) .. i ll go over the link .. thanks buddy ..
[20:41] <JFo> jjohansen, was the one you were thinking it was the "xen-blkfront: handle Xen major numbers other than XENVBD" one?
[20:42] <avinashhm> Hi bjf , just curious ... i need only info abt the config used ... is it 'i386_defconfig' ? which is used for regular ubuntu ...(arch/x86/configs/i386_defconfig ?
[20:48] <manjo> ogasawara, who is looking at Ubuntu delta this cycle ? 
[20:49] <ogasawara> manjo: it's been farmed to different individuals
[20:49] <ogasawara> manjo: anything in particular you're interested in?
[20:49] <bjf> avinashhm, cp /boot/config-`uname -r` /usr/src/linux/.config
[20:49] <manjo> ogasawara, omnibook module needs a refresh its been oopsing since natty
[20:49] <ogasawara> manjo: we've disabled it
[20:50] <manjo> ogasawara, ok.. looks like the project is dead ... 
[20:50] <ogasawara> manjo: discussed it at UDS and decided to turn it off and see who screams
[20:50] <manjo> ogasawara, Satellite and Tecra and some HP users 
[20:50] <manjo> ie tohsiba & HP 
[20:50] <manjo> toshiba rather 
[20:51] <mjg59> It's really not the right interface for any modern hardware
[20:52] <manjo> sure its a crappy module 
[20:54] <manjo> ogasawara, we introduced it in karmic coz some people requested it ... good to know we got rid of it 
[20:56] <jjohansen> JFo: yep
[20:56] <JFo> cool, found it here https://patchwork.kernel.org/patch/567891/
[20:56] <JFo> no idea what all is going on, but I understand a large part of it
[20:57] <JFo> going to look at it a bit tomorrow, my brain is almost fried for today
[20:58] <avinashhm> bjf, thanks very much
[20:58] <bjf> avinashhm, you may not want to actually copy it where i indicated, but it shows you where to find it
[20:59] <avinashhm> bjf, correct ... i downloaded src ~/git/ .. i ll copy to this root ..
[20:59] <kees> hmpf, how do I fix the "Author" when working on git patches?
[21:01] <sforshee> kees, git commit --author="..."
[21:01] <ogasawara> kees: git commit --author ?
[21:01] <kees> what if I'm working on a rebase?
[21:03] <ogasawara> kees: hrm, could you use rebase -i, mark the commit as an 'edit', and then use git commit --author ?
[21:04] <kees> ah! good, yes
[21:05] <kees> ogasawara: yes! it worked. :) git commit --amend --author ...; git rebase --continue sweet
[21:05] <ogasawara> kees: nice
[21:15] <sconklin> http://lwn.net/Articles/444336/ Interesting argument against prefetch
[21:16]  * JFo takes notes
[21:20] <JFo> stepping away for a bit. I need to run an errand
[21:22]  * jjohansen steps away for some lunch
[22:11]  * herton --> eod
[22:55] <jjohansen> hallyn: have you seen https://lkml.org/lkml/2011/5/24/502
[23:01] <hallyn> no
[23:05] <hallyn> jjohansen: have you pursued it?
[23:06] <jjohansen> hallyn: just to the apparmor, first poke level, /me is planning to get back to it later tonight
[23:06] <jjohansen> I want to finish up with some other stuff first
[23:06] <hallyn> jjohansen: ok, thanks
[23:08] <hallyn> i dunno, but 'cred' is NULL at cap_capable() too.  THis looks like memory corruption
[23:22] <jjohansen> hallyn: yeah I wasn't sure what was going on there, I want to try replicating myself
[23:22] <hallyn> ditto
[23:23] <hallyn> bbl
[23:23] <hallyn> thanks for the tip