[03:54] <SlickT10> hello all: I have a unique problem, one that almost no one on any channel will respond to me about. Instead of reiterating it here, i have a question in launchpad: https://answers.launchpad.net/ubuntu/+question/81460 . At the advice of some that was here last time, I made it a bug and added info. I need to resolve this issue soon. I have expirence with embeded system work and I am not afraid to build things from scratch or even do mos
[03:54] <SlickT10> t the work, but I need some guidence where to go next. 
[03:57] <SlickT10> If nothing else, I would at least like to talk to one person that knows this part of the kernel, I would love to get a reference to someone that I can talk to directly
[03:57] <dtchen> i presume you've asked on the linux-usb mailing list? have you tried the 2.6.31-rc7 and daily mainline builds?
[03:57] <dtchen> err, 2.6.31-rc8*
[03:58] <dtchen> i.e., reproduce it in a vanilla kernel and take it upstream to bugzilla.kernel.org and lkml if necessary
[04:00] <SlickT10> Ive tried karmic
[04:01] <dtchen> i'm referring to http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31-rc8/ and http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ , respectively
[04:01] <SlickT10> no
[04:02] <SlickT10> that sounds like a good next step
[04:03] <SlickT10> i had a feeling this may go all the way back to the kernel, because it is the same behavior i got using pentoo
[04:03] <SlickT10> and backtrack 4 (a ubuntu derivative)
[04:07] <SlickT10> dtchen, thanks, this was the redirection I needed. I wasn't certain if I should take this upstream or not
[04:11] <dtchen> SlickT10: np
[04:38] <SlickT10> I was just talking to dtchen, but hes gone now. When booting up the rc8 kernel, it freezes on the audio driver init (I think). this keeps me from debugging the real problem. Is there a way to slow how fast the scrolling happens, or how do i skip a module?
[04:53] <SlickT10> Hmm, no answer?
[04:53] <SlickT10> no way to prevent sound from being initiated>
[04:53] <ScottK> !weekend | SlickT10
[04:53] <ubot3> SlickT10: It's a weekend.  Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question.  Please be patient, wait longer than you normally would, or try again during the working week.
[04:54] <ScottK> It's not actually the weekend, but it's nightime for pretty much all the kernel team.
[04:54] <SlickT10> hmm
[04:54] <SlickT10> Too bad :) I cant work on this during the day since Im at work then :)
[04:55] <SlickT10> thanks, going for reboot again
[05:18] <peepsalot> shortly after grub begins to load my kernel, I get a message "grep: /proc/cmdline: No such file or directory"
[05:18] <peepsalot> is this a bug?
[05:20] <peepsalot> once the system is booted, I can see that this file exists
[05:20] <peepsalot> hmm, looks like this maybe this is more of a grub than a kernel issue
[08:00] <eggonlea> hi ericm
[08:01] <ericm> hi eggonlea
[09:50] <nick[0]> on a ICH4-M laptop which enabling HPET through clocksource=hpet causes resume from S3 hangs, what can I do to reduce interrupts beyond NO_HZ=Y?
[09:50] <nick[0]> can lapic be used as a more efficient clocksource than acpi-pm?  Will acpi-pm use either the HPET or the lapic (which my BIOS disables...I haven't tried forcing it yet)
[09:53] <nick[0]> eh, did I need to identify to gain voice?
[10:51] <jk-> anyone seeing weirdness with signals on karmic?
[10:53] <jk-> i appear not to be able to kill processes on a different pty
[10:53] <jk-> seems like some processes aren't receiving SIGCHLD
[10:54] <jk-> .. when they don't have a pty
[10:54] <jk-> [jk@pororo ~]$ ssh briq true
[10:55] <jk-> <waits forever>
[10:56] <jk-> hmm, 'ssh -t briq true' also hangs, so it's not just when there's not pty
[11:45] <jk-> looks like this only happens for ssh sessions
[15:50] <rtg> ogra, would you follow up on bug #418265 ?
[15:50] <ubot3> Malone bug 418265 in linux-fsl-imx51 "Warning in ehci-hcd.c:911 on kernel 2.6.31-5-imx51" [High,Confirmed] https://launchpad.net/bugs/418265
[15:51] <ogra> rtg, can be closed, GrueMaster told me he will file a fresh bug that actually matches the discussion in there
[15:52] <ogra> the summary and description surely dont match the actual content anymore
[15:52] <rtg> ogra, invalid then?
[15:52] <ogra> yeah, 2.6.31-5-imx51 was never a valid kernel
[17:08] <lool> rtg: FYI UbuntuSpec: is just like Bug: but for ubuntu blueprints
[17:09] <rtg> lool, good to know. I'm not much of a wiki expert
[23:23] <Q-FUNK> ogasawara: I think that we just experienced the placebo syndrome. ;)
[23:24] <ogasawara> Q-FUNK: I'm soooo sorry about that
[23:24] <ogasawara> Q-FUNK: I just realized what happened right when you responded :(
[23:24] <Q-FUNK> it's ok
[23:25] <ogasawara> Q-FUNK: I actually have to ask one of the other kernel guys to kick off the build for me and I just spaced it and gave them the wrong commit the first time
[23:25] <Q-FUNK> by accident, we just might be confirming Ingo's doubts.
[23:25] <Q-FUNK> ah
[23:25] <ogasawara> Q-FUNK: yup, so it might work well in the end
[23:26] <Q-FUNK> ogasawara: hopefully :) we'd still have to narrow down the actual cause, after isolating the exact commit.
[23:26] <ogasawara> Q-FUNK: right
[23:27] <Q-FUNK> hopefully, Al Viro and Ingo Molnar will chip in and help us on this one.
[23:27] <ogasawara> Q-FUNK: I'd hope so