[12:48] <BenC> zul: ping
[01:43] <mikepj> Good to know about that UUID issue.  I had the same problem when installing on my server with 4 SATA disks.  Devices would switch names, etc.  Took me a few hours to figure it out and make the correct GRUB changes.
[02:55] <zul> BenC: pong
[03:01] <BenC> zul: xen on amd64 is failing to build...did you test it before you sent the config?
[03:02] <zul> yes I did 
[03:02] <zul> whats the error?
[03:05] <BenC> In file included from include/linux/mm.h:40,
[03:05] <BenC>                  from include/linux/suspend.h:11,                 from arch/x86_64/kernel/asm-offsets.c:12:
[03:05] <BenC> include2/asm/mach-xen/asm/pgtable.h:489: error: 'ptep' undeclared here (not in a function)
[03:05] <BenC> include2/asm/mach-xen/asm/pgtable.h:489: error: 'entry' undeclared here (not in a function)
[03:05] <BenC> include2/asm/mach-xen/asm/pgtable.h:489: error: expected identifier or '(' before 'if'
[03:05] <BenC> include2/asm/mach-xen/asm/pgtable.h:489: error: expected identifier or '(' before 'whi
[03:05] <BenC> and then some more
[03:06] <zul> crappers can you disable it for amd64 and send me the output
[03:09] <zul> sorry timed out
[09:01] <kraut> moin
[10:59] <AnAnt> bdmurray: Hello
[10:59] <AnAnt> bdmurray: what does "Triaged" mean ?
[10:59] <AnAnt> bdmurray: you are Brian Murray, right ?
[11:01] <soren> AnAnt: He is, but he's probably also very much asleep. :)
[11:02] <AnAnt> soren: ok, what does "Triaged" mean ?
[11:02] <soren> AnAnt: Do you mean in the traditional (medical) sense, the general Ubuntu sense or the kernel sense?
[11:03] <cjwatson> AnAnt: see https://lists.ubuntu.com/archives/ubuntu-bugsquad/2007-June/000559.html and thread
[11:04] <soren> AnAnt: Triaging is the process of going evaluating patients (especially after battles in war) evaluating which should be taken care of first, etc.
[11:04] <soren> AnAnt: In the general Ubuntu sense, it means "This bug has been looked at, verified, and should for all practical purposes be ready to be looked at by a developer".
[11:04] <AnAnt> soren: in the launchpad sense
[11:05] <soren> AnAnt: The kernel team has traditionally had slightly different procedures for bug management, so I'm not entirely sure if Triaged means something slightly different when it comes to kernel bugs.
[11:10] <AnAnt_> soren: thanks
[11:10] <AnAnt_> sorry, I got d/c 
[11:10] <AnAnt_> soren: regarding this bug: #103273
[11:11] <AnAnt_> soren: I just sent that it got partially solved by setting the option pci=noacpi
[11:11] <AnAnt_> soren: shall I provide any outputs (dmesg or whatever) when I passed pci=noacpi option?
[11:12] <soren> AnAnt_: I have no clue.
[11:12] <AnAnt_> k
[11:12] <AnAnt_> anyone got a clue ?
[11:15] <AnAnt_> ok, later then
[12:19] <Mithrandir> how can I force a driver to bind to a device?  I have a device I believe is supported by a driver, but I'd like to test before recompiling
[12:20] <infinity> You can echo the PCI ID to somewhere magic in /sys ..
[12:20] <Mithrandir> it's a USB device, though
[12:21] <infinity> They surely have IDs too... Of some sort. :)
[01:02] <cjwatson> find /sys -name new_id
[01:02] <cjwatson> you need the right syntax though
[01:03] <cjwatson> which I think is just "%x %x" % (vendor, product) for USB
[01:04] <cjwatson> (it's more complicated for PCI)
[01:12] <abogani> What is the best tool for manage a patch series on top fo git? stgit?
[02:34] <Mithrandir> hm, btsco needs the snd_bt_sco module to be loaded to be useful, but bluetooth devices aren't really plugged in like USB and such, so I don't think udev can get a uevent, reasonably.
[02:34] <Mithrandir> what's a good way to make sure snd_bt_sco gets loaded?
[02:43] <IntuitiveNipple> Mithrandir: I set it up so it is loaded when the --connect occurs
[02:44] <Mithrandir> IntuitiveNipple: where do you set that up?
[02:45] <IntuitiveNipple> I can't remember now; it was a while ago I set it up. I do recall having to trawl through a lot of Google search results until I found the correct mix of tips
[02:46] <IntuitiveNipple> The problem I had after getting it set-up was many apps wouldn't easily allow the selection of the ALSA device, and therefore they would insist on using the internal sound device
[06:31] <bdmurray> BenC: There is a bug a bugzilla.kernel.org that looks, uh, misplaced to me.  It is bug 7954 if you could have a peak that would be great.
[06:37] <BenC> bdmurray: ok, I'll check it out
[06:39] <bdmurray> BenC: It's about a MacBook Pro bug filed with Component Power-Processor which seems wrong and it should be an upstream bug of one of ours.
[10:15] <bdmurray> BenC: I'm having a hard time linking a linux-source-2.6.22 bug upstream.  The LP process is a bit confusing but I think there is not an appropriate upstream project for l-s-2.6.22.