[08:45] <emgent_> smb_tp: ping
[08:48] <smb_tp> emgent_, pong
[14:20] <Ng> is there a xen kernel for jaunty?
[14:36] <TheMuso> apw: Do you have those rebase script tweaks in a git repo yet? If so I should take a look at them as part of my getting linux-libc-dev for !x86/armel upoaded.
[14:52] <TheMuso> apw: Sorry, I'm on IRC for somewhat longer than I was just earlier.
[14:53] <TheMuso> apw: Never mind, I see the lpia upload. I'll pull that tree and have a look.
[15:11] <apw> TheMuso, yeah rebase-lpia should be the right one in the lpia tree
[15:13] <TheMuso> apw: Yeah got it, I'm going to use rebase/retag-lpia and change them for ports and use them as a base.
[15:17] <apw> TheMuso, cool.  if you need to ask anything about how its intended to work etc yell
[15:18] <TheMuso> apw: Thanks, but I think I'll be right.
[15:37] <praveen> is there any way for a thread to figure out if its is being traced by someone or not
[15:54] <TheMuso> c
[16:51] <TheMuso> apw, smb_tp, I am making progress. apw I have rebased based on your new script changes. Just need to make a few more changes before I'm willing to upload a git tree. I should have something ready tomorrow morning, given I'm not pulled away for discussions/meetings.
[16:52] <apw> TheMuso, that is awsome
[16:52] <smb_tp> TheMuso, Great
[16:55]  * lamont has a kvm/intrepid question...
[16:56] <lamont> so kvm host with winxp runninng inside it (so shoot me)... if the kvm window is in another workspace, it appears that (at least) when the windoze app is doing I/O, that it blocks because the window isn't in the foreground workspace...  how do I beat that into submission^W working anyway?
[16:56] <lamont> no libvirt involved here - that makes me cry somewhat
[16:58] <soren> lamont: JOOI... Compiz or no compiz?
[16:59] <lamont> metacity
[16:59] <lamont> metacity
[16:59] <soren> Could you try with compiz? Just for fun?
[16:59] <lamont> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
[17:00] <lamont> soren: that involves figuring out who to actually turn on compiz... and all of the pain that it causes
[17:00]  * soren has a half baked hypothesis about the cause of this
[17:00] <soren> lamont: just do "compiz --replace" in a terminal.
[17:00] <soren> lamont: And when you get bored with all the wobbliness, do "metacity --replace".
[17:01] <lamont> soren: the only really-missing bit from compiz for me is keyboardFocusPolicy == strict
[17:01] <lamont> which, uh, is documented in the source of metacity...
[17:01] <lamont>  :-)
[17:01] <lamont> and available via gconf-editor
[17:01] <lamont> well, that seems to have let it finish running
[17:02] <lamont> I'll give it a better test next time I boot the beatsy
[17:02] <lamont> beasty, even
[17:02]  * lamont likes the way compiz/metacity --replace hijacks the terminal window by not daemonizing.
[17:03] <lamont> well, maybe 'likes' isn't completely accurate
[17:03] <soren> It's a feature.
[17:04] <lamont> soren: for many bonus points and beers, port metacity-2.24.0/debian/patches/001_strict_focus.patch to compiz
[17:05] <lamont> Q: when does the newly created window get focus?  A: NEVER
[17:19] <lamont> soren: http://paste.ubuntu.com/113264/ explains _why_ switching to compiz didn't change anything...
[17:19] <lamont> in that it didn't switch
[19:06] <kennethr1> I think I'm getting a kernel panic on 8.10 via Wubi on Vista....I'm suspicious of the wireless...Broadcom BCM4311...how can I enable dumps/get  a backtrace?
[19:08] <oly562> im trying to load this webcam, can someone help me out? im pretty good with linux, and it shouldnt take too long, i just need some tips or clues ok? let me know what you want displayed from cmdline and i will provide any info that you may need. thanks!!
[19:09] <kennethr1> oly562: is it USB-attached?
[19:10] <kennethr1> oly562: did you try just plugging it in?
[19:10] <oly562> usb
[19:10] <oly562> 2.6.24-19-generic
[19:11] <oly562> Bus 005 Device 023: ID 041e:403d Creative Technology, Ltd WebCam Notebook Ultra
[19:12] <oly562> kennethr1: you good with linux mods and drivers? web cams specifically
[19:13] <kennethr1> oly562: what are you trying to do?
[19:18] <oly562> your kidding right kennethr1 lolol
[19:18] <oly562> nevermind dude. you should know by now
[19:18] <kennethr1> oly562: no, I mean what isn't working
[19:19] <kennethr1> oly562: are you trying to use skype? cheese? what?
[19:19] <kennethr1> what's the problem
[19:19] <oly562> cheese doesnt see it 
[19:20] <oly562> camorama neither
[19:20] <oly562> nor kopete
[19:20] <oly562> so forth
[19:20] <oly562> im trying to have my cam at least work locally
[19:20] <oly562> on linux of course
[19:21] <kennethr1> you're on 8.04?
[19:24] <oly562> yes
[19:24] <oly562> LTS
[19:31] <oly562> VF0070 is my model for cam
[19:36] <oly562> k so
[19:37] <oly562> kennethr1 really didnt have much info did he
[19:37] <oly562> lol
[19:55] <kennethr> How can I enable kernel panic dumps?
[20:42] <kennethr> How can I enable kernel panic dumps?
[21:41] <maco> hi kernel people. ive been looking at bug 272530 for a while, and it's turning out to be something that can be fixed on some machines using a bios update. on other machines, the most recent bios doesn't help. i'm guessing it's still a bios bug, just one that's being ignored by some manufacturers. should it be invalidated, or is there some way the kernel can work around the issue?
[21:41] <ubot3> Malone bug 272530 in linux "64-bit Intrepid automatic permanent reboot loop related to having exactly 4GB of memory" [High,Triaged] https://launchpad.net/bugs/272530
[21:45] <dtchen> it's very much still a bios bug. if enough info is provided, namely dmidecode, it could be warned during boot.
[21:53] <maco> dtchen: dmidecode? i dont know how to tell them to get that info
[21:53] <maco> dtchen: and when you say "warned on boot" do you mean throwing up a "you have a bios bug, so this won't work" message or finding a way to work around it?
[21:54] <dtchen> the former
[21:54] <dtchen> dmidecode is shipped by default
[21:54] <dtchen> in fact, some of the necessary info is already grabbed during boot; see /var/lib/acpi-support
[21:54] <maco> oh just "dmidecode > dmidecode.txt"?
[21:55] <dtchen> specifically, see /etc/acpi/start.d/10-save-dmidecode.sh
[23:35] <praveen_> hiiii....i tried to fork a child and then create several threads in the child made each one of them say ptrace_traceme. Then I watched thoses threads execute and i observed that all threads become zombie. But the output of the ps command showed parent alive. Can anybody explain this thing