[01:09] <r3pek> hey!
[01:09] <r3pek> any dev around?
[01:11] <IntuitiveNipple> >/dev/null :)
[01:12] <r3pek> :P
[01:13] <IntuitiveNipple> sorry... I couldn't resist :)
[01:15] <S0me1> hi
[01:15] <S0me1> Can  i ask?
[01:20] <bdmurray> S0me1: ask what?
[01:39] <S0me1> why ubuntu developers fix winmodem issue on some laptops such as Dell XPS?
[01:40] <mjg59> I don't understand the question?
[01:40] <mjg59> Oh, you mean the hsfmodem drivers?
[01:41] <mjg59> We don't have permission to distribute those. Dell do.
[01:44] <S0me1> mjg59: Dell is sleeping :)
[01:45] <mjg59> I suspect that questions about those may have to go to Dell. I'm not sure what the support situation is in that respect.
[01:45] <S0me1> but that's mean if you have permission you can do it !!
[01:45] <mjg59> We don't have permission. 
[01:45] <mjg59> So we can't
[01:45] <S0me1> :) OK
[01:46] <S0me1> I am sure ubuntu kernel they can fix this issue , but there is a policy from DELL
[01:47] <mjg59> No, we can't
[01:47] <mjg59> The copyright holder (Linuxant, not Dell) have not granted us a license
[01:50] <S0me1> mjg59: have ubuntu team try get granted license from Linuxant 4 ubuntu users?
[01:50] <S0me1> why not try ask them ?
[01:50] <mjg59> I did, a year ago
[01:51] <S0me1> and what they said?
[01:53] <mjg59> I never got a reply
[01:53] <S0me1> sorry for my question ... but this very important for me I tried find-out solution ... this is why i am asking you
[01:53] <mjg59> But given that they charge money for it, I suspect we'd never be able to distribute it for free
[01:54] <IntuitiveNipple> S0me1: I found the Linuxant drivers mess up the snd-hda-intel and report a shed-load of unhandled events, so I dropped them
[01:55] <S0me1> I see ... I think they never want work with you in this issue ... 
[01:57] <S0me1> anyway guys ... nice chatting with you 
[01:57] <S0me1> nice to meet you :)
[03:17] <lamont> 	kernel-wedge copy-modules 2.6.22-11 hppa64 2.6.22-11-hppa64
[03:17] <lamont> missing module serpent
[03:17] <lamont> http://launchpadlibrarian.net/9335614/buildlog_ubuntu-gutsy-hppa.linux-source-2.6.22_2.6.22-11.33_FAILEDTOBUILD.txt.gz
[03:17] <lamont> OTOH, that was a build in the data center...
[03:18] <lamont> is there going to be another kernel upload this week, I wonder?
[03:19] <fabbione> isn't there a -12 already ?
[03:19] <fabbione> oh no
[03:19] <fabbione> never mind
[03:55] <defendguin> ubuntu just pushed out an update to the synaptics package and now the side scroll on my touchpad doesn't function 
[03:55] <defendguin> gutsy of course
[04:18] <mjg59> defendguin: system/preferences/mouse
[04:21] <defendguin> ha i didn't even think to look and see if it had been disabled 
[04:21] <defendguin> sorry mat
[04:23] <defendguin> wow and tap to click wasnt working either   i certainly hope that isn't supposed to be the default behavior after the update
[08:51] <john> anyone there
[11:21] <kraut> moin
[12:53] <Nafallo> what did I do when I got that irq x: nobody cared again?
[12:56] <zul> use irqpoll
[12:59] <Nafallo> thanks zul
[01:48] <BenC> pkl_, amitk, rtg, kylem: getting ready to do another kernel upload. Any last minute patches you guys know of that need to be in?
[01:49] <BenC> lamont: did you check on the hppa ftbfs? I noticed it, but didn't look into it
[01:55] <kylem> BenC, nyetski on my end.
[01:55] <amitk> mjg59: ping for the usb-autosuspend-disable patch
[01:56] <amitk> BenC: nada
[01:56] <BenC> kylem: good morning...any comment on bug #119976?
[01:56] <ubotu> Launchpad bug 119976 in linux-source-2.6.22 "All the task previous are killed after resumed from S3 on Santa Rosa with Crestline" [High,Confirmed]  https://launchpad.net/bugs/119976
[01:56] <ogra> amitk, ooohhh is that like "dont unload my usb disk if / is on it during suspend" ?
[01:56] <kylem> if it only happens on the sdv and not on the production hw, i don't know what we can do
[01:58] <BenC> kylem: it almost doesn't sound like a kernel bug to me either
[01:58] <BenC> sounds like xorg crashing
[01:58] <kylem> yeah.
[01:58] <amitk> ogra: not really. It is mainly to avoid breaking a _lot_ of usb peripherals (scanners, printers, etc.) that don't deal with USB autosuspend very well.
[02:00] <kylem> my 965 box suspended and resumed at least 10 times in a row last night running gears, so i really don't see what the probelm is...
[02:00] <BenC> kylem: ok, can you comment on the bug, and maybe punt it over to xorg?
[02:01] <amitk> ogra: is it becoming common to have / on a usb disk?
[02:02] <BenC> amitk: there's a class of system where the built-in driver is a 2g usb flash
[02:02] <BenC> s/driver/drive/
[02:06] <ogra> amitk, well, its the case for me on the classmate 
[02:07] <ogra> and i guess it will become common in the embedded world as well 
[02:10] <amitk> ogra: how is classmate dealing with it currently?
[02:10] <ogra> not at all, i had to disable suspend
[02:11] <ogra> you can suspend/resume fine ... up to the first disk access :)
[02:20] <amitk> ogra: a proper fix would probably require collating VFS mount information with USB disk information to make suspend decision...
[02:21] <ogra> well, a kernel option to just suppress the unloading would suffice for a start :)
[02:21] <ogra> indeed nifty autodetection etc would be cooler :)
[02:22] <amitk> but that would still leave usb disks with / on them un-suspendable
[02:26] <ogra> hmm
[02:28] <lamont> BenC: hppa ftbfs: module "serpent" went *poof*  No clue what that module is, or if I even care if it is there...
[02:28] <BenC> lamont: I can add a modules.ignore for that
[02:29] <lamont> BenC: sounds good to me
[02:29] <amitk> ogra: /sys/module/usbcore/parameters/autosuspend doesn't work? Or something like ./devices/pci0000:00/0000:00:1d.7/usb4/power/autosuspend?
[02:29] <BenC> lamont: config CRYPTO_SERPENT
[02:29] <ogra> it didnt in feisty, i didnt try with gutsy yet .... 
[02:29] <lamont> heh - I was half way guessing that would be a crypto module
[02:30] <lamont> it was either that or an I/O card
[02:30] <BenC> ogra: remember feisty didn't have that mod param...maybe it'll work for gutsy with that
[02:31] <ogra> BenC, i'll try it later today
[02:31] <BenC> lamont: hmm, the config option doesn't have any deps...no idea why it went missing
[02:31] <BenC> might be better to re-enable it
[02:31] <lamont> re-enabled is fine too
[02:31] <lamont> I got it: let's do both. :)
[02:31] <lamont> that way if there's another, it'll at least build
[02:32] <lamont> or does the modules check dump all of them before barfing?  as opposed to just the first one
[02:32] <amitk> ogra: aahaa.. you tried this on feisty.
[02:32] <BenC> lamont: it dumps all
[02:32] <ogra> amitk, yeah, until recently i had no working gutsy image 
[02:32] <BenC> lamont: plus modules.ignore is a list of modules, not a blanket ignore of failures
[02:32] <lamont> cool.  IIRC it does hppa32 before hppa64, and abi before modules, so that should be the  only issue in the build
[02:32] <lamont> oh
[02:33] <lamont> yeah - renable sounds good.
[02:33] <lamont> do you have an hppa box to play with?
[02:34] <BenC> lamont: was enabled in hppa32, re-enabled in hppa64, and updateconfigs leaves it intact
[02:34] <BenC> so this should be good for hppa to get built today
[02:34] <lamont> cool
[02:36] <lamont> atm linux-source-2.6.22 will fall into a pool of ~340 packages at the same pri in queue-mangler
[02:36] <lamont> hrm.. that reminds me... need to get some stuff pushed from universe
[02:41] <rtg> BenC: the only thing I might have is sky2 fixes.
[02:42] <BenC> rtg: ok
[02:42] <rtg> BenC: still waiting on Stephan. I'll bug him this morning.
[02:42] <BenC> reminder, we have a kernel team meeting at 1600 UTC
[02:43] <zul> yippe skippe
[02:52] <mjg59> amitk: Ok, will dig that out
[03:02] <tepsipakki> hey, I've filed a but against the gutsy kernel since it (?) claims that the flashdisk in my camera is corrupt, but the same happens with feisty kernel. Should I reassign it to another package?
[03:03] <tepsipakki> it works in feisty proper
[03:09] <tepsipakki> bug 134477 if interested :)
[03:09] <ubotu> Launchpad bug 134477 in linux-source-2.6.22 "reports corrupt filesystem on flash-media, fine on feisty" [High,Confirmed]  https://launchpad.net/bugs/134477
[03:17] <soren> tepsipakki: "the same happens in feisty" vs. "fine on feisty"?
[03:18] <tepsipakki> soren: with feisty kernel on gutsy
[03:18] <tepsipakki> but a real feisty installation is ok
[03:19] <soren> tepsipakki: Ah, ok.
[03:19] <tepsipakki> so I'm wondering if it's a kernel bug at all, but somewhere else
[03:19] <tepsipakki> my wife is pissed off because I can't get the pictures from it :)
[03:20] <BenC> tepsipakki: if the difference between working and not working is userspace, then blame userspace :)
[03:21] <BenC> tepsipakki: where do you see that it is corrupted? dmesg, gnome pop-up?
[03:21] <tepsipakki> dmesg, it doesn't get mounted
[03:21] <BenC> tepsipakki: can you mount it and see the files in a terminal?
[03:22] <tepsipakki> no, not even fdisk works..
[03:22] <BenC> tepsipakki: what filesystem?
[03:22] <tepsipakki> fat16
[03:22] <tepsipakki> I don't have it handy atm
[03:22] <rtg> tepsipakki: Is it the same media? Perhaps flash is going bad....
[03:22] <tepsipakki> but in 4h or so..
[03:23] <BenC> tepsipakki: have you tried formatting it?
[03:23] <tepsipakki> rtg: same media yes, bought after last Christmas
[03:23] <tepsipakki> BenC: yes, worked fine on feisty
[03:24] <rtg> tepsipakki: If the problem can be reproduced with another part, then it might really be a bug. Otherwise I suspect a HW failure.
[03:24] <Lure> BenC: is it worthwhile to milestone bug 136257? - restart/reboot does not work on some HP laptops
[03:24] <ubotu> Launchpad bug 136257 in linux-source-2.6.22 "regression: restart system does not work on HP nw8240" [Medium,Triaged]  https://launchpad.net/bugs/136257
[03:24] <tepsipakki> rtg: hmm, correct. I don't have another microsd-card available, though I could buy one
[03:25] <rtg> tepsipakki: The reason I say that it might be HW failure is that SD failures do not appear to be widespread. 
[03:26] <BenC> Lure: yes, please, and see about testing reboot=b reboot=w reboot=h on the machine
[03:26] <BenC> try each one separately
[03:26] <Lure> BenC: ok, will do
[03:26] <BenC> Lure: will need output of "sudo dmidecode > dmidecode.txt" as well
[03:27] <tepsipakki> rtg: would that cover the fact that it works on feisty?
[03:28] <soren> tepsipakki: You've seen it work in Feisty after you've seen it fail on Gutsy?
[03:28] <tepsipakki> soren: yes
[03:29] <tepsipakki> I've reproduced the problem on three gutsy installations, but on my office workstation (feisty) it keeps working :/
[03:31] <zul> BenC: about your email what about bugs that are in 2.6.20 that are still in gutsy (ie: pci ids, etc)
[03:33] <BenC> zul: add a target for 2.6.22 and milestone it for beta
[03:37] <mjg59> BenC: Hi - did you see my message about msi and mmconfig?
[03:37] <BenC> mjg59: no, missed that. What's up?
[03:38] <mjg59> BenC: The patches we applied to feisty to alter the msi and mmconfig defaults seem to be missing
[03:42] <mjg59> BenC: Was that deliberate?
[03:48] <BenC> mjg59: I asked kyle about it and I forget what he said
[03:48] <BenC> kylem: msi patches ^^ ?
[03:48] <mjg59> BenC: Would it be possible to get the list of patches in feisty that aren't in gutsy?
[03:49] <BenC> tepsipakki: I/O errors are indicative of bad media
[03:49] <mjg59> BenC: Or a broken driver, but yeah
[03:49] <kylem> they should be reapplied.. they weren't in the diff you sent me to bash into gutsy.
[03:50] <BenC> right, but if it used to work in feisty, and now doesn't work on feisty kernel, then I suspect hw
[03:50] <tepsipakki> BenC: right, I'll buy a new card (ExtremeIII this time, and bigger) and test with that
[03:50] <mjg59> tepsipakki: This was SD, or compact flash?
[03:50] <tepsipakki> mjg59: SD
[03:50] <mjg59> Ok. No clue, then.
[03:52] <tepsipakki> BenC: also, it does work on a real feisty install (not just kernel+gutsy)
[03:53] <BenC> tepsipakki: see, that makes no sense to me
[03:53] <BenC> feisty with gutsy userspace should not make this sort of things appear
[03:53] <tepsipakki> BenC: hopefully we'll be a whole lot wiser later today :)
[03:54] <BenC> tepsipakki: test a feisty and gutsy livecd if you can please
[03:55] <tepsipakki> BenC: sure will
[03:55] <BenC> tepsipakki: thanks
[04:03] <tepsipakki> hmm, dailies are oversized (even dvd)
[04:03] <mjg59> Grab a CD daily and burn it to a dvd?
[04:03] <tepsipakki> oh, haven't done that yet :)
[04:13] <zul> BenC: okie dokie
[04:16] <BenC> rtg, pkl_, kylem: btw, activity reports were due for this morning :)
[04:17] <pkl_> BenC: I'm kinda busy at the moment :)
[04:17] <pkl_> BenC: I'll do a quick activity report
[04:18] <rtg> BenC: Gusty debian/control-scripts/* ?
[04:19] <BenC> rtg: working on it now
[04:21] <amitk> mjg59: were you trying to get the isight camera working on gutsy?
[04:22] <mjg59> amitk: Yeah, ought to work fine now
[04:22] <amitk> bug #131222
[04:22] <ubotu> Launchpad bug 131222 in ubuntu "isight does not work in ubuntu gutsy - Video for Linux 2 (v4l2): Could not get buffers from device '/dev/video0'." [Undecided,New]  https://launchpad.net/bugs/131222
[04:22] <mjg59> Oh, there's a gstreamer update needed if you want to use gstreamer
[04:22] <mjg59> I uploaded it but managed to bodge the package somehow. I blame its clean target
[04:23] <mjg59> I'll redo that at some stage
[04:23] <amitk> mjg59: so we will have that for gutsy beta then?
[04:35] <mjg59> amitk: Should do, yes
[04:46] <Lure> BenC: reboot=b work for bug 136257
[04:46] <ubotu> Launchpad bug 136257 in linux-source-2.6.22 "regression: restart system does not work on HP nw8240" [Medium,Triaged]  https://launchpad.net/bugs/136257
[04:46] <BenC> Lure: ok, with dmidecode we can force it for that specific machine
[04:46] <BenC> machine type
[04:46] <Lure> BenC: dmidecode is attached to bug
[04:46] <BenC> Lure: thanks
[04:47] <Lure> BenC: thank you! ;-)
[04:58] <mjg59> Wait. We used to have reboot=b for all HPs.
[04:58] <mjg59> What happened to that?
[05:00] <mjg59> In fact, we still do
[05:00] <mjg59> Lure: Your dmi tables are broken
[05:01] <Lure> mjg59: how can I fix them?
[05:01] <mjg59> Lure: Try updating your bios
[05:01] <Lure> oh shit, this requires windows again :-(
[05:01] <mjg59> Well, the alternative is to just always boot with reboot=b
[05:02] <mjg59> There's not enough information in your DMI tables to identify your system
[05:02] <Lure> mjg59: how can dmi table get corrupted, if I do not change bios?
[05:02] <Lure> mjg59: interesting...
[05:02] <mjg59> No clue
[05:08] <bdmurray> BenC: Is there time to look at the cherry-pick tagged bug reports before Beta?
[05:08] <BenC> bdmurray: should be
[05:08] <BenC> bdmurray: do you have a quick link?
[05:09] <bdmurray> https://launchpad.net/ubuntu/+bugs?field.tag=cherry-pick
[05:09] <bdmurray> It is a short url even. ;)
[05:09] <BenC> bdmurray: thanks
[05:10] <bdmurray> There are also some kernel-oops tagged bugs for 2.6.22 - https://launchpad.net/ubuntu/+bugs?field.tag=kernel-oops
[05:49] <BenC> bdmurray: cherry-pick list done, except one report
[05:49] <BenC> bdmurray: any chance I could get you to add a list of tags we're using for the kernel to our bug triage page?
[05:51] <BenC> kylem: pushed all my changes to ubuntu-gutsy, she's all yours...thanks
[05:51] <BenC> kylem: abi's are all ready, just needs a insertchanges when all the patches are in
[05:51] <bdmurray> BenC: What is happening with usb autosuspend?
[05:51] <bdmurray> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/85488/comments/442
[05:52] <ubotu> Launchpad bug 85488 in sane-backends "some usb_devices fault if usb_suspend enabled" [Medium,Confirmed]  
[05:52] <BenC> bdmurray: there's a blacklist of devices that disable auto-suspend
[05:52] <BenC> bdmurray: people are supposed to provide usb ven/dev id's for devices that need them
[05:52] <bdmurray> BenC: It looks like gregkh just commit a patch to disable autosupsend though
[05:53] <bdmurray> If I am reading that right.
[05:53] <BenC> bdmurray: probably misreading it, autosuspend is a config option you can disable already
[05:53] <bdmurray> http://git.kernel.org/?p=linux/kernel/git/gregkh/usb-2.6.git;a=commit;h=7d2c592609a7da950b458403f1936d382f38ff9c
[05:54] <BenC> and in gutsy you can add a module option to disable it as well
[05:54] <BenC> bdmurray: ok, let's toss that one into cherry-pick
[05:54] <mjg59> BenC: No, the default upstream is to disable autosuspend for everything other than hubs
[05:55] <zul> we already have that for 2.6.22
[05:55] <BenC> mjg59: right, just read the commit
[05:56] <zul> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-gutsy.git;a=commit;h=db90e7a15cb4a160610b4e58576f25539ca216e7
[05:56] <BenC> zul: doesn't look like we had it
[05:56] <zul> BenC: ^^ same commit
[05:56] <BenC> +
[05:56] <BenC> +       /* By default, disable autosuspend for all non-hubs */
[05:56] <BenC> +#ifdef CONFIG_USB_SUSPEND
[05:56] <BenC> +       if (udev->descriptor.bDeviceClass != USB_CLASS_HUB)
[05:56] <BenC> +               udev->autosuspend_delay = -1;
[05:56] <BenC> +#endif
[05:56] <BenC> we were missing that it seems
[05:57] <zul> ah yeah..
[05:57] <zul> i see now
[05:57] <BenC> not the same commit
[05:57] <kylem> BenC, ok doke
[05:57] <zul> BenC: same commit message though ;)
[05:58] <BenC> zul: doesn't look like it to me :)
[05:58] <zul> maybe i should lay off the crack pipe then
[05:58] <BenC> as849 vs. as965
[05:58] <BenC> bdmurray: patch cherry-picked
[05:58] <bdmurray> So I could comment on 85488 saying that auto-suspend for USB devices will be disabled for everything except hubs.
[05:59] <maks_> meeting?
[05:59] <BenC> bdmurray: yes, and fixed-committed for 2.6.22
[05:59] <BenC> yep
[06:27] <zul> whoops it looks like xen needs to be added to amd64 lum as well
[06:44] <dholbach> rtg: I assigned bug 139323 to the kernel team because I thought that you guys would be the most knowledgeable about that package
[06:44] <ubotu> Launchpad bug 139323 in libieee1284 "please sync from debian libieee1284  (0.2.10-8)" [Undecided,New]  https://launchpad.net/bugs/139323
[06:44] <dholbach> so I'd just need somebody who'd ACK that sync request if it's ok
[06:44] <rtg> dholbach: It looks harmless, but its way outside the kernel.
[06:45] <dholbach> rtg: the people who get those sponsoring bugs assigned are usually not the 'bug contacts' but people who might have a clue
[06:45] <ogra> are there any known bugs with usb dvb cards ? i had an oops last night with a Hanftek DVB-T card last night (kept dmesg if its not known yet) seems usbcore is stuck sice that happended (havent rebooted yet)
[06:45] <dholbach> rtg: I simply can't deal with all the sponsoring bugs that come in, so I need to assign them to people
[06:45] <rtg> dholbach: Well, I don't count as someone who has a clue about this one :)
[06:46] <dholbach> rtg: I thought that somebody in the kernel team might :)
[06:47] <dholbach> so all I need from somebody of you guys is a "OK, look good" and I won't pester you with this one any more :)
[06:47] <rtg> dholbach: OK, I'll update the LP report.
[06:47] <dholbach> thanks a lot rtg, I'll pass it on to ubuntu-archive then
[06:50] <ogra> ah, nm, found bug 115284 ... seems to be my issue
[06:50] <ubotu> Launchpad bug 115284 in linux-source-2.6.22 "USB DVB-T Tuner causes Kernel Oops" [Medium,Triaged]  https://launchpad.net/bugs/115284
[07:04] <tepsipakki> rtg: with a new SD card I still get errors, so it's not that
[07:04] <tepsipakki> next I'll test feisty&gutsy live-cd's
[07:09] <zul> stupid power
[07:33] <Lure> mjg59: new bios does not fix the reboot problem, I have added new dmidecode to the bug
[07:50] <BenC> Lure: bug# again?
[07:51] <Lure> BenC: bug 136257 - it looks like root cause is that "Product Name" is empty in dmidecode...
[07:51] <ubotu> Launchpad bug 136257 in linux-source-2.6.22 "regression: restart system does not work on HP nw8240" [Medium,Triaged]  https://launchpad.net/bugs/136257
[07:54] <BenC> Lure: ok
[07:54] <Lure> BenC: not sure how this can happen to dmi table though...
[07:54] <BenC> Lure: vendor mistake
[08:07] <tepsipakki> ok, feisty live-cd is ok, but gutsy is still broken
[08:08] <Lure> BenC: funny as it is, this laptop was properly reporting product name as seen in old bug 63123
[08:08] <ubotu> Launchpad bug 63123 in linux-source-2.6.20 "battery info & fans do not work after hibernate (HP nw8240)" [Medium,Incomplete]  https://launchpad.net/bugs/63123
[08:16] <tepsipakki> hmm, on the other hand.. I don't get anything on the gutsy dmesg, maybe because the desktop is generally unusable on the daily live-cd
[08:32] <tepsipakki> BenC: so, testing the gutsy live-cd failed, because it can't modprobe anything, they just hang
[08:33] <tepsipakki> I got the desktop to load eventually
[09:51] <xhaker> woops
[09:52] <xhaker> bear with me
[09:58] <xhaker> s/10/11
[09:58] <xhaker> it was s/26/33 before
[09:58] <xhaker> nitpicking :D
[09:58] <Nafallo> ooh
[09:58] <Nafallo> oki ;-)
[09:59] <xhaker> so who here knows Robert Moore?
[09:59] <mjg59> At Intel?
[09:59] <xhaker> yes
[09:59] <mjg59> He's not very involved in the Linux side of things
[09:59] <mjg59> More just the core ACPI code
[09:59] <xhaker> yes
[09:59] <xhaker> that's why i'm trying to find him
[10:00] <mjg59> He still occasionally pops up on the linux-acpi list
[10:00] <xhaker> i've read about the beta kernel milestone and etc
[10:00] <xhaker> mjg59, you probably don't remember this.. but i was trying to fix an acpi bug, present since 2.6.21, with acpi and batteries
[10:01] <xhaker> i've made a patch that you looked into.. but it's awesomely small and kindoff hard to document
[10:01] <xhaker> i've found another bug report upstream about it
[10:02] <xhaker> http://bugzilla.kernel.org/show_bug.cgi?id=8810
[10:02] <ubotu> bugzilla.kernel.org bug 8810 in ACPICA-Core "Laptop needs acpi_serialize to works - HP Pavillion dv8230us" [Normal,Reopened]  
[10:02] <xhaker> could you please look into the last two comments there
[10:02] <Nafallo> oooh
[10:02] <Nafallo> ubotu is finally here :-D
[10:02] <xhaker> i know mjg59 is the laptops guy
[10:02] <xhaker> but you can look too Nafallo  :)
[10:02] <Nafallo> xhaker: naah. can't :-P.
[10:03] <xhaker> mjg59, this other bug seems to be a duplicate http://bugzilla.kernel.org/show_bug.cgi?id=8171
[10:03] <ubotu> bugzilla.kernel.org bug 8171 in ACPICA-Core "acpi_serialize locks system during boot" [Blocking,Assigned]  
[10:03] <xhaker> but moore claims to be preparing a patch
[10:04] <xhaker> i've set this bug to high on launchpad.. this affects thinkpads too i think.
[10:04] <xhaker> reading robert moore's comments make me think my patch is not that crazy
[10:05] <mjg59> xhaker: No, returning AE_OK there isn't the right thing to do. The execution failed.
[10:06] <xhaker> mjg59, yes, you might be right. i'd love to see robert's patch, could he have commit it yet?
[10:07] <xhaker> i'd set this bug to critical if i was brave enough
[10:07] <mjg59> xhaker: If it's committed, it'll be in the acpi git tree
[10:09] <mjg59> it's on git.kernel.org
[10:19] <xhaker> mjg59, no related commit there.. crossing fingers for robert to free the patch
[11:16] <bdmurray> mjg59: bug 74683 seems to be fix released now is that right?
[11:16] <ubotu> Launchpad bug 74683 in acpi-support "incorrect dependencies for acpi-support" [Low,Fix committed]  https://launchpad.net/bugs/74683
[11:22] <mjg59> bdmurray: Yup
[11:25] <bdmurray> mjg59: Okay, also looking at bug 77212 it looks like it could use a bit more love.
[11:26] <ubotu> Launchpad bug 77212 in acpi-support "No screen upon resume from suspend to ram (Fujitsu Lifebook S7020)" [Medium,Triaged]  https://launchpad.net/bugs/77212
[11:38] <elmo> oh, come on, seriously - the order of my sound cards is non-deterministic in feisty :-/
[11:53] <jwest-> any gdb gurus
[12:04] <gnomefreak> guru == knows how to use it?
[12:07] <BenC> elmo: there's some magic with id= for each module you can use to force it
[12:08] <elmo> BenC: I wish I didn't have to, but then I guess not many people have > 1 soundcard
[12:08] <BenC> elmo: mostly the media guys
[12:09] <BenC> wish the alsa/gnome stuff had a better way of configuring it in the UI
[12:13] <JanC> all peripheral devices should just have a built-in unique ID  ;)
[12:15] <BenC> ieee1394 does :)
[12:18] <mjg59> Where did the rtl8180 driver go?
[12:19] <mjg59> We only have rtl8187, which is the USB model
[12:24] <BenC> for some reason I was thinking rtl818x was both
[12:24] <mjg59> I think rtl818x as a project is both, but we only have the 8187 portion
[12:25] <mjg59> There's no mention of pci in the set we have