[00:58]  * jjohansen steps away for a bit
[02:20] <sdhasu> !ops
[02:20] <ubot2> Help! lamont, zul, T-Bone, mdz, or jdub
[02:23] <sdhasu> !ops
[02:23] <sdhasu> ban me
[02:23] <ubot2> Help! lamont, zul, T-Bone, mdz, or jdub
[06:39] <eruditehermit> anyone around?
[09:06] <awilkins> Hi there, have just fixed a kernel bug and had a few questions
[09:06] <awilkins> Is there a way to get Soyuz to build a kernel image to a PPA?
[09:06] <apw> awilkins, you can upload modified kernles to PPAs yes
[09:07] <apw> awilkins, if you need a quick test kernel it may be quicker to do a manual build, as that only builds fewer flavours
[09:07] <awilkins> apw, Can you just upload debs, or do you need to upload source differences?
[09:07] <awilkins> apw, I've got it built and running
[09:07] <apw> awilkins, PPAs are identicle to the main archives
[09:07] <apw> so you can upload source packages there too
[09:08] <apw> awilkins, whats the bug, anything interesting?
[09:08] <awilkins> bug #776964 
[09:08] <ubot2> Launchpad bug 776964 in alsa-driver "p5n32e-plus HDA Nvidia AD1988B microphone input not working" [Undecided,Confirmed] https://launchpad.net/bugs/776964
[09:10] <apw> awilkins, if you just want some semi-official kernels with the patch i can spin some and shove those on people and link them to the bug
[09:12] <apw> awilkins, is that of use ?
[09:12] <awilkins> apw, I've got the amd64 one built here, but that would be useful to the other chap in the comment thread, I think. I'm not sure how many people have noticed this one... we can't be the only three people running Ubuntu on that motherboard though, and from the code, the bug may affect anyone with a AD1988 variant
[09:12] <apw> awilkins, well the norm is to get testing on the bug ... for which i can provide kernels, and then push the patch into the kernel if it fixes things
[09:12] <apw> i see you say the patch is accepted by alsa upstream?  got a link to that
[09:13] <awilkins> apw, I just got a mail from Takashi Iwai, not sure he's pushed his tree yet though
[09:13] <apw> arggg bug trackers which need a login to _look_ at bugs ... no thanks you
[09:13] <apw> awilkins, can you forward me the patch you sent him
[09:14] <apw> and i can spin with the right patch then
[09:14] <awilkins> Done
[09:15] <awilkins> A variant of this problem has affected the kernel for several releases, but until now it was workaroundable
[09:15] <apw> awilkins, well its good to get it fixed if its broken
[09:15] <awilkins> That provoked me into actually looking at it... nothing like breaking something to make a geek try to fix it
[09:16] <awilkins> bug #593018 Is the older variant of this bug that has a workaround
[09:16] <ubot2> Launchpad bug 593018 in alsa-driver "nvidi p5n32e-plus Analog Devices AD1988B soundmax microphone only works after switching to another input setting and back" [Undecided,Confirmed] https://launchpad.net/bugs/593018
[09:17] <awilkins> It only worked by coincidence, reading the code from Maverick, it has a similar logic fault (comparing a type constant to an array index instead of the type value)
[09:18] <awilkins> I don't know the policy for what constitutes an SRU worthy thing though
[09:19] <apw> awilkins, small obvious and fixing a real user problem, generally those are valid
[09:19] <apw> if they come via stable all the better, and if we get lots of testing we can help that happen too
[09:21] <awilkins> I pulled the alsa-driver bzr branches for maverick and natty - they were useful for reference, do they actually get used to make the builds, because I get the impression the git repositories are the real sources?
[09:22] <apw> awilkins, our master source is our git tree also, we make source packages from that and upload them
[09:24] <awilkins> apw, Link to actual patch on mailing list http://thread.gmane.org/gmane.linux.alsa.devel/85204  # just in case that's helpful
[09:25] <apw> awilkins, indeed so
[09:26] <apw> awilkins, where are you testing, which release
[09:27] <awilkins> apw, I'm on natty, testing on my normal working machine. I patched the tip of git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
[09:28] <apw> awilkins, cool
[09:30] <awilkins> apw, maverick and lucid would need a slightly different patch
[09:32] <apw> awilkins, we can worry about those later
[09:45] <apw> awilkins, if you feel inclined you could port the patch and attach it to the bug for those releases
[09:46] <awilkins> apw, :-)   Also think this bug is replicated in some of the other patch-panel modules
[09:46] <awilkins> There are quite a number of "my mike doesn't work" bugs in Launchpad, I was trolling through them to see which ones were AD1988 related
[09:50] <apw> awilkins, good plan, once the test kernels are there we can perhaps get some testing on those other ones and pull the duplicates in
[10:18] <awilkins> apw, Bah,  I take it back, this is not the same problem as #593018, the code looks all right in <= maverick, on inspection.
[10:19] <apw> awilkins, well thats good to know anyhow
[10:19] <apw> awilkins, ok test kernels are in the bug
[10:28] <awilkins> As expected, nothing has exploded and my mic still works.
[10:30] <apw> indeedd, hopfully some of the other testers will chime in
[13:06] <LinkRage> here it says: 'NMI: PCI system error (SERR) for reason %02x' in traps.c (http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=blob;f=arch/x86/kernel/traps.c)
[13:06] <LinkRage> how do I find what's the reason (%02x)
[13:06] <LinkRage> in my case dmesg shows a5, sometimes b5 for %02x e.g.: NMI: PCI system error (SERR) for reason a5 on CPU 0
[13:36] <apw> awilkins, could you comment in your own bug that you tested my kernels, that helps with the processing
[13:52] <apw> LinkRage, at first glance (without looking) i'd say they sound like bus produces numbers, ie intel defines them
[13:54] <apw> SERR#
[13:54] <apw> System Error is for reporting address parity errors, data parity errors during a Special Cycle, or any other fatal system error. SERR# is shared among all PCI devices and is driven only as an open drain signal (it is driven low or tri-stated by PCI devices, but never driven high). It is activated synchronously to CLK, but when released will float high asynchronously through a pull-up resistor.
[13:54] <apw> LinkRage, ^^ seems to imply a hardware error being reported
[13:54] <LinkRage> looks like
[13:54] <LinkRage> well I'm testing now...
[13:55] <LinkRage> the issue is caused by brand new (tested) pci sound card
[13:56] <LinkRage> I think I fixed it by disabled ECC error detection, PCI error detection and disallowed plug & play OS to touch the BIOS settings
[13:56] <LinkRage> now I'm booting ubuntu again to see what happens
[13:57] <apw> well disabling error detextion on PCI likely will get rid of the SERR reports, but they are telling you something bad is occuring
[14:01] <LinkRage> hm, I guess you're right
[14:01] <LinkRage> I'm also thinking of removing all the other PCI component (HW raids etc - it old server from 2002)
[14:10] <_ruben> server with soundcard? :P
[14:12] <LinkRage> yep, I'm going to give it to my father, since he's desktop is even older :)
[14:13] <LinkRage> ubuntu worked fine this time, now I enabled ECC and PCI detection, but left the plug & play OS: Disabled in BIOS, so let's see...
[14:16] <LinkRage> huh, PCI error checking is causing the issue when enabled
[14:16] <apw> that makes sense as SERR is a PCI thing
[14:16] <LinkRage> :)
[14:17] <mjg59> LinkRage: More likely that something else is causing it, but you only notice when you have PCI error checking turned on
[14:17] <LinkRage> I have 2 options here - either remove all the pci raid stuff, and try again, or disable error checking, I've no clue about third option :)
[14:17] <LinkRage> mjg59, good point
[14:18] <apw> its not likely things are going to work well with that disabled, its trying to tell you something, something urgent enough that an NMI is warrented
[14:19] <apw> kees, about?  need to talk to you about a possible bug in Yama
[14:19] <LinkRage> well, I'll remove all the other PCI devices since I'm not sure if they are in so working condition
[14:19] <LinkRage> thanks for your advices btw :)
[14:50]  * apw bounces to test a kernel
[14:58] <kees> apw: sure, what's up?
[14:58] <apw> kees, hiay, the yama path check
[14:58] <apw> it uses generic_permissions()
[14:59] <apw> which in turn uses i_uid etc and those do not seem to be guarenteed valid
[14:59] <apw> in the case where the filesystem supplies a permissions() op
[14:59] <apw> i'll email you the patch i think yama needs
[15:00] <apw> kees, ok dropped you a dirty copy ... see what you think
[15:01] <kees> apw: ah, interesting, perhaps this is the origin of 729338 ?
[15:01] <apw> bug #729338
[15:01] <ubot2> Launchpad bug 729338 in linux "yama hardlink restriction misbehaves under aufs" [Undecided,New] https://launchpad.net/bugs/729338
[15:01] <kees> I had been stratching my head over that one
[15:01] <apw> kees, heh that likely is so, as its under overlayfs which tickles the same issue
[15:02] <apw> i have a kernel here with aufs in and the patch so i could test
[15:04] <kees> apw: why doesn't generic_permission do the i_op->permission check itself?
[15:04] <apw> thats not what its for
[15:04] <apw> generic_foo in general are for use as implementations when you don't have a foo op
[15:05] <apw> if you wern't a security op i'd expect you to be using inode_permissions
[15:05] <apw> but that in itself calls security which sounds loop tastic
[15:05] <apw> kees, ^^
[15:06] <apw> kees, testing aufs for the same issue now
[15:09] <apw> kees, is the hardlink stuff new in oneiric ?
[15:10] <apw> kees, ok the same test case does not tickle aufs, but the error is the same
[15:10] <apw> in your report as to what i was seeing in mine
[15:12] <apw> kees, ahh ok managed to reproduce on aufs at least
[15:15] <kees> apw: no, hardlink restrictions have always existed in Yama
[15:15] <apw> odd that we've not seen th
[15:15] <apw> this more often, or indeed that it only afffects the one case not all that affects overlayfs
[15:16] <kees> not a lot of people use stacked FSes
[15:16] <kees> Yama was first in 10.10
[15:16] <apw> kees, we use them all the time on all liveCDs
[15:16] <kees> right, but with very few hardlinks :)
[15:16] <kees> anyway, was the aufs issue the same thing? I wasn't clear on what you had said
[15:17] <apw> kees will know shortly
[15:17] <apw> have to reboot to confirm
[15:21] <apw> kees, ok so this does not fix the aufs interaction
[15:22] <apw> kees, the debug i have is useful however
[15:22] <kees> apw: geh, bummer.
[15:22] <apw> kees, i may as well have a look at it while i ma in the zone
[16:19] <esmaeil> hi how can i install gcc 3.4 in ubuntu 11.04
[16:21] <hallyn> Does anyone here closely follow netdev@?  I'm trying to figure out if the patch whose discussion appears to end here http://kerneltrap.org/mailarchive/linux-netdev/2010/5/6/6276530  ever got picked back up in a new form
[17:28] <apw> hallyn, tim would be your man, but he is away
[17:30] <hallyn> apw: ok, thanks.
[17:44] <JFo> <-food time, back soon