[03:58] <AceLan> does anyone know how to generate the dmi info in the last part of the bug report # ex. in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585520 , dmi.bios.date: 02/13/2009 ...
[03:58] <ubot2`> Ubuntu bug 585520 in linux (Ubuntu) "Unable to resume from second consecutive suspend (affects: 2) (heat: 14)" [Medium,Triaged]
[04:18] <cooloney> AceLan: you mean, you wanna generate the dmi info from the dmesg.txt of that bug?
[04:19] <cooloney> AceLan: i don't think we can do that. i just know 'dmidecode'
[04:44] <AceLan> cooloney: yes, dmidecode don't have the same info as that shown on the bug report
[04:45] <AceLan> cooloney: I need dmi.bios.vendor: INSYDE and dmi.board.name: ZQ1B
[04:45] <AceLan> cooloney: do you know where can I get such info?
[04:54] <cooloney> AceLan: i think you can get that from dmidecode.
[04:55] <cooloney> BIOS Information Vendor: Intel Corp.
[04:55] <cooloney> that's mine
[04:55] <cooloney> Base Board Information -> Product Name: DG45ID
[04:56] <AceLan> cooloney: got it, thanks
[05:04] <cooloney> AceLan: no problem, man. i am still very sleepy due to the jetlag
[08:05] <devurandom_> hello
[08:06] <devurandom_> I have a problem in my 9.04 rootstocked ARM ubuntu-desktop image
[08:06] <devurandom_> no user but root is allowed to use networking
[08:06] <devurandom_> I tried it in several rootfilesystems with different network devices
[08:06] <devurandom_> so I suspect it is a kernel configuration matter
[08:07] <devurandom_> something in .config level that breaks permssion system
[08:08] <lag> devurandom_: Which board are you running it on?
[08:13] <jk-> devurandom_: how do you mean 'allowed to use networking'? what is failing?
[08:13] <lag> Morning jk- :_)
[08:13] <jk-> heya lag
[08:14] <lag> jk-: Did you use terminator to extinguish your decoration? 
[08:15] <jk-> lag: I have this in CompizConfig Settings Manager -> "Window Decorations" -> "Decoration Windows" = "(any) & !(class=Gnome-terminal)"
[08:15] <jk-> heh, snap
[08:16] <jk-> could probably simplify that to just "(!class=Gnome-terminal)"
[08:16] <jk-> err
[08:16] <jk-> "!(class=Gnome-terminal)"
[08:17] <lag> Okay - yeah, I've done that before when I made an invisible web browser :)
[08:17] <devurandom_> CONFIG_DNOTIFY=n
[08:17] <lag> Cheers 
[08:17] <devurandom_> lag: htcleo
[08:20] <devurandom_> jk-: non root can't ping
[08:21] <devurandom_> jk-: or use networking in any other way
[08:22] <jk-> devurandom_: what error does ping give?
[08:23] <devurandom_> permission denied
[08:23] <jk-> that's odd, as ping is setuid root
[08:24] <devurandom_> I've seen it in several rootfilesystems
[08:24] <lag> devurandom_: What is the result of: ls -l /bin/pin
[08:24] <lag> g
[08:24] <devurandom_> think I can't blame ubuntu arm
[08:25] <devurandom_> lag: I will check once I booted again. but it will not work with any problem. always some permission err
[08:25] <jk-> devurandom_: can you give us a little more info about how you're testing this? you're logged into a desktop session as a normal user, opened one terminal and 'ping foo.com' doesn't work, but sudo ping foo.com' does work?
[08:26] <devurandom_> jk-: exactly
[08:26] <devurandom_> on the tty
[08:26] <devurandom_> and same is reconstructible in gnome
[08:26] <devurandom_> $ firefox --- no joy
[08:26] <devurandom_> # firefox internet fun
[08:26] <jk-> devurandom_: ok, check the output of lag's command there
[08:27] <jk-> ls -l $(which ping)
[08:27] <lag> Oooooooooo
[08:27] <lag> :)
[08:27] <jk-> mm?
[08:28] <lag> ?
[08:28] <jk-> *suspense*
[08:28] <jk-> hey cking :)
[08:29] <cking> hiya
[08:29] <devurandom_> I'll check that in a minute.
[08:29] <lag> Morning cking
[08:30] <devurandom_> somebody got a fully known working with 9.04 ubuntu ARM .config ?
[08:31] <lag> For the kernel?
[08:31] <lag> Maverick or Lucid?
[08:31] <devurandom_> yeseh
[08:31] <devurandom_> lucid
[08:32] <lag> I have two
[08:32] <lag> One for OMAP3 and one for OMAP4
[08:32] <lag> Actually, I may be able to dig out an armel one too
[08:32] <devurandom_> I have a cortex-a8 device
[08:32] <lag> OMAP3, cool
[08:32] <devurandom_> so gimme the omap3
[08:32] <lag> k
[08:32] <devurandom_> tanks
[08:33] <devurandom_> want to look and see if something striking is in the diff vs my local config
[08:33] <devurandom_> thanks*
[08:35] <lag> np - give me a minute 
[08:35] <devurandom_> you have a beagle ? or some phone ?
[08:36] <lag> OMAP3: Beagle XM 
[08:36] <apw> isn't omap3 a standard build in maverick
[08:37] <jk-> devurandom_: this doesn't seem like a kernel config issue :/
[08:37] <devurandom_> I destroyed a beagle board with 12V on the supply line
[08:38] <devurandom_> jk-: how do you know ?
[08:38] <lag> Yep
[08:39] <lag> apw: -^
[08:39] <devurandom_> jk-: since I was spending two days trying to figure what inside my rootfs breaks apt to find out I had file locking disabled in the kernel I never exclude kernel problem
 isn't omap3 a standard build in maverick   <- maverick has any neon & vfp optimization ?
[08:40]  * apw has not idea about neon/vfp ... but it does have a config
[08:41] <lag> devurandom_: How big is your rootfs when bzipped? 
[08:41] <amitk> devurandom_: why are you on 9.04?
[08:41] <devurandom_> around 600M
[08:41] <devurandom_> amitk: because the rootstock tool is very broken
[08:41] <lag> Can you make it available to me? If so, I can test it for you
[08:42] <devurandom_> amitk: it will only succeed with 9.04 for me
[08:42] <lag> It will save you diffing configs, which can be laborious 
[08:42] <amitk> devurandom_: were you running 10.04 when runnning it?
[08:42] <devurandom_> lag: that would be marvellous
[08:42] <lag> devurandom_: np
[08:42] <devurandom_> amitk: no - I tried lucid rootfs in lucid and maveric rootfs in lucid. both fail
[08:42] <lag> I think 10.04 works fine though?
[08:43] <devurandom_> amitk: also lucid and maverick fail in the karmic
[08:43] <lag> devurandom_: Then you're doing something wrong
[08:43] <devurandom_> amitk: so I can only to karmic rootfs in karmic.
[08:43] <amitk> devurandom_: ogra would be interested in rootstock bugs
[08:43] <devurandom_> amitk: all of my bugs are documented on launchpad for many months.
[08:44] <devurandom_> amitk: and all in the changelog is a broken gui-
[08:44] <amitk> devurandom_: but have you tried the pre-built ubuntu images for omap?
[08:44] <devurandom_> amitk: I am aware of them but no
[08:44] <devurandom_> lag: as mentioned I documented all failures I got and all of them are reported
[08:44] <devurandom_> lag: and not marked fixed
[08:45] <lag> devurandom_: Thanks for reporting
[08:45] <lag> devurandom_: Where are the bugs?
[08:45] <devurandom_> lag: I did not update any
[08:46] <devurandom_> I was happy with the current situation of documentation launchpad as non of the stuff I've seen was marked to be solved
[08:47] <lag> devurandom_: Ah, I see. Would you mind pointing me to the bug inanycase? If they are still causing issues, I would like to either help, or gee the necessary people up.
[08:47] <devurandom_> lag: if you think it will still be helpful I can retry lucid rootstock from lucid host
[08:47] <devurandom_> I don't remember. all I know it was sth during qemu
[08:47] <lag> devurandom_: Are you uploading your rootfs to a place where I can access it?
[08:47] <devurandom_> download works
[08:47] <devurandom_> I think dependency trees are broken!
[08:48] <devurandom_> maybe the full desktop-image s are not sufficiently tested ?
[08:48] <amitk> devurandom_: lucid on lucid works for me
[08:48] <amitk> (for rootstock)
[08:48] <devurandom_> amitk: ubuntu-desktop ?
[08:48] <lag> Lucid rootfs and lucid kernel works for me
[08:48] <lag> And 
[08:48] <lag> Lucid rootfs with Maverick kernel also works for me
[08:48] <amitk> devurandom_: full desktop images have the problem of running out of memory - too little on beagleboard. 
[08:49] <amitk> Try the netinstall one
[08:49] <devurandom_> I am excited on here people are way more interested in rootstock status than in #ubuntu-arm chan
[08:49] <lag> devurandom_: That's a worrying factoid - the author is very busy in #ubuntu-arm
[08:49] <devurandom_> amitk: I don't have any target performance problems.
[08:50] <amitk> devurandom_: I'd suggest you first try the pre-built images : http://cdimage.ubuntu.com/ports/releases/lucid/release/ubuntu-10.04-netbook-armel+omap.img
[08:51] <amitk> (assumin you're after a beagle image)
[08:55] <devurandom_> lag: can you pastebin that config ?
[08:56]  * apw bounces to take a new kernel
[08:56] <devurandom_> maybe have a 2.6.32 one available ?
[08:57] <devurandom_> ping localhost
[08:57] <devurandom_> socket: Permission denied
[08:58] <lag> There is working everything in: http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/current/maverick-preinstalled-netbook-armel+omap.img.gz 
[08:59] <lag> dd bs=4092 if=<image> of=/dev/<sdcard>
[08:59] <lag> And help yourself to everything
[08:59] <lag> Working rootfs
[08:59] <devurandom_> is it an ext3 ?
[08:59] <lag> Working .config
[08:59] <lag> Yes
[08:59] <lag> No
[08:59] <lag> It is an entire SD card image
[08:59] <devurandom_> downloading
[09:00] <lag> VFS and EXT3
[09:00] <lag> You'll need an sd card with ~2GB
[09:01] <devurandom_> I work with .ext3 filesystem files I loop mount as /
[09:01] <devurandom_> no direct partitions on card for more flexibility
[09:02] <devurandom_> anyway I have to run
[09:02] <lag> You can loop mount it once on an SD card#
[09:02] <devurandom_> thank you guys a lot. I will let you know how things developed
[09:02] <lag> np
[09:05] <devurandom_> hold on
[09:05] <devurandom_> wait a sec
[09:05] <devurandom_> I don't need to try that
[09:05] <lag> devurandom_: We'll be here all day :)
[09:05] <devurandom_> I forgot to mention that I tried various rootfs
[09:05] <lag> There is a working kernel in there too
[09:06] <lag> There is working _everything_ for OMAP3
[09:06] <devurandom_> yea I can't bot a random omap kernel on my qualcomm SoC
[09:07] <lag> The requested .config is in there also
[09:07] <devurandom_> lag: do you have the config from that thing available ?
[09:07] <lag> Nope, I've just downloaded it though, so I can dig it out if you like?
[09:07] <devurandom_> ok I will take it from there then
[09:07] <devurandom_> taht would be nice as I have very slow link
[09:08] <lag> You know that it's our latest one though? i.e. Maverick
[09:09] <devurandom_> yea
[09:09] <devurandom_> wondering if it has neon mplayer
[09:10] <amitk> devurandom_: we don't yet support the qualcomm SoC
[09:10] <devurandom_> amitk: in that case it was nice to meet you ;)
[09:12] <lag> devurandom_: http://paste.ubuntu.com/469224/
[09:12] <lag> Not the latest, but it works
[09:12] <lag> devurandom_: Good luck
[09:13] <devurandom_> lag: thanks. but I need to be in the club to download it raw
[09:15] <lag> Club?
[09:16] <lag> http://paste.ubuntu.com/469224/plain/
[09:16] <lag> If that doesn't work for you send me your email address
[09:17] <lag> Or just highlight it and copy/paste 
[09:18] <devurandom_> I think I even have a launchpad account but I don't see the neccessity to login for a pastebin
[09:21] <lag> Either copy/paste the one you can see, or send me your email address
[12:52] <apw> ogasawara, morning ... early isn't it ?
[13:14] <lag> ikepanhc: ping
[13:15] <lag> Does anyone know where I can get the slide templates that ike used at the rally?
[13:20] <hrw> morning 
[13:20] <cking> lag, i've asked for them too
[13:20] <lag> You asked ike? 
[13:20] <hrw> are there any chances that ubuntu will get working 'apt-get source linux' one day?
[13:24] <cking> lag, email'd him this morning
[13:25] <lag> Are you going to use them at the summit? 
[13:25] <cking> lag, no, I just wanted to re-read it and stash it somewhere
[13:26] <lag> http://www.tuxresources.org/blog/wp-content/uploads/2006/10/1.png
[13:26] <lag> I might use that one :)
[13:26] <lag> Oooooooooooo: http://www.tuxresources.org/blog/wp-content/uploads/2006/10/4.png
[13:44] <th1> hi, I'm packaging a special kernel for use in a Xen environment. I need it to cause some extra modules (xenfs.ko and a couple others) to be added to the initramfs automagically somehow on the target system, how can I do this
[13:46] <tgardner> th1, /etc/initramfs-tools/modules
[13:46] <th1> tgardner, yes that's how I do it but I need it to happen automatically on a system when the kernel-image I'm making is installed
[13:47] <th1> ie. without the user editing that file
[13:48] <th1> I could do it in the postinst script of the kernel package but if I edit that file and then the user uninstalls my kernel package and switches back to a standard one, it's going to break
[13:57]  * vanhoof waves
[14:11] <th1> tgardner, I think I found what I needed by creating a hook like there is for lvm2..
[14:13] <tgardner> th1, in /etc/initramfs-tools/hooks ?
[14:13] <th1> in /usr/share/initramfs-tools/hooks 
[14:15] <th1> so I put that in my kernel image package and call manual_add_modules for the modules I need
[14:20] <tgardner> ogasawara, you should uncomment the backports entries in Maverick -meta before you upload Ubuntu-2.6.35.12.13
[14:21] <paultag> Hey kernel guys. After a quick exchange with cndougla ( howdy! ) I've decided to test the -M kernel. Is it safe to fetch the dsc and run a pbuild against Lucid? I have a driver regresson from 31-21 to 31-24, B43 issues on boot locking up initrd
[14:23] <cnd> paultag, I *think* you should be fine to build the kernel in lucid
[14:23] <cnd> but the toolchains are quite different now, so you never know
[14:23] <tgardner> paultag, there is already a kernel build for lucid in https://edge.launchpad.net/~kernel-ppa/+archive/ppa
[14:23] <paultag> tgardner: you've saved the day :)
[14:23] <paultag> cnd: I'd love to test this to see if it's an issue for 10.10, and if it can't get squashed before +1
[14:24] <paultag> I'll do my bit and homework :)
[14:24] <cnd> paultag, the other route you could try is the maverick kernel backport to lucid
[14:24] <cnd> tgardner would know more about that than I though
[14:25] <tgardner> cnd, which is just what I suggested, i.e.,  there is already a kernel built for lucid ...
[14:26] <paultag> swaping over now
[14:28] <cnd> oh, I thought that was in a different repo
[14:28] <cnd> nm then :)
[14:31] <paultag> Well, it booted, but it's a random chance thing ( I'm fairly sure it's a race condition ). Let me test a few times to get a nice sample pool
[14:31] <cnd> tgardner, there were some b43 fixes a few weeks ago
[14:31] <cnd> are they in lucid yet?
[14:32] <cnd> maybe apw or smb know?
[14:32] <apw> cnd, i don't think i know specificially ... if you have a reference to the fix i can find out
[14:32] <paultag> Opp! Still locked up. Two good boots, one failure
[14:33] <cnd> apw, I don't have a reference, I just remember you looking at a fix for b43 that made it actually work
[14:33] <cnd> something about disabling dma
[14:33] <cnd> cause it just doesn't work
[14:33] <apw> paultag, we a
[14:33] <apw> we have some boot hangs due to a unrelated graphics issue which is being worked on, so it might be that too
[14:34] <rsalveti> devurandom_: can you report the problems you're facing with rootstock? also let me know what version you're using
[14:34] <cnd> apw, he's hitting issues in lucid
[14:34] <cnd> and he's testing maverick right now
[14:34] <rsalveti> devurandom_: I'm maintaining it now, and fixing bugs everyday
[14:34] <apw> cnd that rings some kind of bell, i would have to defer to smb with such thin memory though ... think smb is off today, sounding like he was ill
[14:34] <apw> cnd right, i mean if you have boot hangs in maverick kernels it may not be the same hangs you have in lucid
[14:34] <paultag> apw: when I boot single user, it's always the last line -- and since it's single user I am not so sure it's a graphics thing
[14:34] <apw> as we know we have some in maverick which are all new
[14:35] <apw> paultag, good enough then
[14:35] <paultag> apw: it's present on current lucid to ppa kernel team <
[14:35] <paultag> erm, M
[14:35] <ikepanhc> lag: those slide at chinstrap.canonical.com:/home/ikepanhc
[14:36] <paultag> 2.6.32-24-generic to nightly, not present in 32-21
[14:36] <lag> ikepanhc: Did you make them?
[14:36] <paultag> Failure line off the initrd is :
[14:36] <paultag> b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16
[14:36] <paultag> (level, low) -> IRQ 16
[14:37] <ikepanhc> lag: which slide you ask?
[14:39] <paultag> Humm, I've just had about 8 good boots in a row. The issue looks to be harder to reproduce. This just screams Race Condition to me :/
[14:39] <lag> I'm after the templates that you used for your presentations whilst in Prague 
[14:41] <ikepanhc> you mean the template for presentation? I think they comes with lucid
[14:43] <lag> Oh okay
[14:44] <lag> ikepanhc: So it does
[14:44] <lag> ikepanhc: What's the time there/
[14:44] <lag> ?
[14:44] <ikepanhc> lag: ya, the name is GlossyUbuntu
[14:47] <paultag> cnd: OK. I'm going to reinstall from scratch. I'm going to try and reproduce with another driver to try and isolate. Are there any special steps I should take to aid in tracking it down?
[14:48] <ikepanhc> lag: oh, the time, it is 21:48 in Taiwan :)
[14:48] <cnd> after you reproduce we can look at debug steps
[14:48] <paultag> OK.
[14:48] <cnd> but there's nothing I would worry about for now
[14:49] <lag> ?
[14:54] <dcordes__> rsalveti: it is good to see rootstock is being fixed. I will retry a lucid rootfs soon and report any bugs found. I've been using the latest version from 2 weeks ago when I encountered the errors
[14:55] <dcordes__> amitk: may I ask if you are working for canonical ?
[14:56] <amitk> dcordes__: yes I am
[14:56] <rsalveti> dcordes__: cool, I'll try to release another version this week, and get it uploaded in maverick
[14:56] <jpds> 1/12
[15:01] <dcordes__> rsalveti: ok seems like I will ugprade to maverick on my workstation
[15:02] <dcordes__> amitk: I am very excited about all the ARM work done at canonical these days. you mentioned that qualcomm is not _yet_ supported and I have noticed that in fact quite som work is being done for the qualcomm SoCs. Is there some official documentation on the development process available?
[15:03] <amitk> dcordes__: we've carried the tree from android, but there is no ready-to-use image being created for qualcomm socs
[15:03] <dcordes__> amitk: I am very familiar with the msm7xxx msm7xxxA and qsd8xxxx (snapdragon) platforms and would like to help out
[15:04] <dcordes__> amitk: tree being kernel ?
[15:05] <amitk> dcordes__: right. You should talk to tgardner/rtg when he gets online. But we're didn't have a contract for qualcomm work like we did for TI, Freescale and Marvell.
[15:05] <amitk> s/we're/we/
[15:06] <dcordes__> amitk: I'm sure such things can also be achieved on community level :)
[15:06] <tgardner> dcordes__, qualcomm isn't gonna happen for Maverick. You might look into the ChromeOS project if that is the HW you're really interested in.
[15:07] <dcordes__> no thanks I'm not so anxious to promote all the google projects. enough people do.
[15:07] <paultag> cnd: It's slowly getting worse. I can't rule out hardware.
[15:07] <dcordes__> tgardner: that's why I am here
[15:09] <amitk> dcordes__: the rootfs will be usuable as-is, so you only need a kernel
[15:10] <cnd> apw, for the next three weeks (or until multitouch is off my back), could you or someone else handle my bug triaging responsibilities?
[15:11] <apw> cnd, we'll find someone yes
[15:11]  * apw gets his monkey tongs ready
[15:11]  * apw yanks that monkey off cnd's back
[15:12] <apw> JFo, that reminds me, seems you broke the links on the tagging page making them all 'OR' so that we had 50 in each category!  fixed it up
[15:12] <dcordes__> cnd: is this any tslib related ?
[15:12] <JFo> ?
[15:12]  * JFo looks
[15:13] <apw> JFo, the 'To Review' links we cleaned up and made nice and short, which unforuantly made them into 'any of these tags' searches ... so all of the links showed all bugs marked kernel-needs-review
[15:13] <apw> JFo, i added a stanza to say we want 'ALL' of the tags to each
[15:13] <JFo> ok, I can fix that
[15:14] <JFo> I know what i did
[15:14] <apw> already did after i noticed i had 54 in therm
[15:15] <cnd> apw, thanks!
[15:15] <cnd> dcordes__, tslib?
[15:16] <JFo> k
[15:16] <JFo> i see your fix
[15:18] <dcordes__> cnd: the multitouch worked on your back. is it related to touchscreen driver or tslib implementation ?
[15:18] <dcordes__> s/worked/work/
[15:23] <apw> JFo, some arsenal script is using https://wiki.ubuntu.com/KernelMainlineBuilds ... which is doubly out of date i think
[15:24] <JFo> indeed it is. i have an item to update some of the links as there is another that is old, but still gets you to the right place
[15:24] <apw> JFo, indeed, more a 'is this on your todo' than anything else
[15:24] <dcordes__> cnd: I am interested because I have a multitouch screen
[15:25] <dcordes__> I think many nice things could be done e.g. with mpx
[15:25] <JFo> cool :)
[15:25] <JFo> I have added it specifically
[15:32] <cnd> dcordes__, I haven't looked at tslib
[15:32] <cnd> I'm mostly focused on drivers and work to enable applications
[15:33] <dcordes__> cnd: are you using tslib to interface your drivers ?
[15:33] <cnd> no
[15:33] <cnd> I'm focusing on figuring out proper ways to interface with X
[15:34] <dcordes__> what options are there ?
[15:34] <dcordes__> ah a whole new approach
[15:34] <dcordes__> nice
[16:10] <paultag> cnd: JFo czajkowski and myself did a differential diagnosis. current theory is that it's the graphics card + fb issue
[16:11] <paultag> cnd: czajkowski has the same issue, and the only hardware in common is intel vga ( 945GME / GM965 )
[16:13] <JFo> apw, did we get any kind of fix in for the fb issue? my memory indicates no, but I could be wrong
[16:14] <JFo> actually, looks like you may have answered that already
 we have some boot hangs due to a unrelated graphics issue which is being worked on, so it might be that too
[16:15]  * apw is working on it at the moment
[16:16] <paultag> Is there anything you would like me to run on the hardware that can reproduce this?
[16:16] <paultag> ( to help identify anything you might need )
[16:16] <apw> if you are seeing the issue i am working on you should see panics associated with fb_release triggered by plymouthd
[16:16] <paultag> apw: will the kernel panic?
[16:17] <paultag> and will this present it'
[16:17] <apw> for the issue i am tracking, it commonly emits a panic yes, though often it continues
[16:17] <paultag> Humm
[16:17] <paultag> and will this present it's self even if I don't try and run Plymouth? 
[16:17] <paultag> ( read: remove splash from GRUB )
[16:18] <apw> nope, it would only be tickled by plymouth running, removing splash from the command line is not sufficient to stop it
[16:18] <apw> as plymouthd still opens the framebuffer and closes it even if it does not paint the splash
[16:18] <paultag> Ahha
[16:18] <paultag> apw: I'm not seeing a panic
[16:19] <apw> i see a variety of symptoms as it is a rave condidtion
[16:19] <apw> race
[16:19] <paultag> OK. Would you like me to document anything apw?
[16:19] <apw> mostly though its either a hard hang with blank screen or flashing a lot
[16:19] <paultag> apw: Hard hang
[16:19] <apw> then dropping to low res mode
[16:20] <apw> now the hard hang comes with a blank screen normally
[16:20] <paultag> apw: It does not change kernel display modes
[16:20] <paultag> apw: blinking cursor
[16:20] <paultag> unresponsive to keyboard input, REISUB or Ctrl+Alt+Del
[16:20] <apw> not sure i had a blinking cursor or not
[16:21] <paultag> apw: would you like anything documented and posted anywhere to aid in your work?
[16:21] <apw> if you cannot confirm the panic, i suspect you have a different issue
[16:21] <paultag> apw: There is no numlock or scrolllock LEDs, but the Caps Lock is not blinking
[16:23] <apw> thats not sounding 100% like my issue ... cirtainly mine is more random, not 100% hard lock
[16:24] <apw> if i had something which fixed it i'd suggest testing it, but i don't
[16:24] <paultag> apw: it's random
[16:24] <paultag> apw: it just always hardlocks
[16:24] <paultag> apw: e.g. no blinking screen, etc
[16:24] <apw> random and always are not really something you can put in one sentence are they ?
[16:24] <paultag> apw: sure they are
[16:24] <apw> i randomly always sneeze
[16:25] <apw> hrmmm
[16:25] <paultag> well, you could say, when I randomly sneeze, I always see spots
[16:25] <paultag> when I randomly crash, it always hard-hangs ( no other symptoms )
[16:25] <apw> do you ever get to the point where the machine is up long enough to look for an oops in the dmesg
[16:25] <apw> as the issue i am tickling is a boot only issue
[16:25] <paultag> apw: this is boot only
[16:26] <paultag> apw: in the first second after grub hands off execution
[16:26] <paultag> it's always in the initrd
[16:26] <apw> do you have a regular setup ?  no encryption etc ?
[16:27] <apw> as the driver at fault here doesn't load till we get into the main root for a normal setup
[16:27] <paultag> apw: I've wiped this four times in the last two days trying all setups. No encryption, present in all Lucid images I've tried
[16:27] <paultag> Hummm
[16:27] <apw> t
[16:27] <apw> that sounds like it rules my issue out
[16:27] <paultag> OK
[16:31] <paultag> thanks apw 
[16:43] <ogasawara> tgardner: you didn't put nouveau in ubuntu-maverick-lbm right?  ie I'm still gonna leave linux-backports-modules-nouveau-RELEASE_NAME-generic commented out in linux-meta.
[16:44] <tgardner> ogasawara, uh, right. nouveau is mainline in Maverick
[16:44] <ogasawara> tgardner: maybe I'll just delete that entry all together
[16:44] <tgardner> ogasawara, ack
[16:45] <sconklin> JFo: If I find a bug for which a patch is already in proposed, but isn't connected by having a buglink in the patch, is there any way I can set it up to automatically change to fix released when the SRU is released?
[16:47] <apw> crap the locking is all buggered in fbcon ... there is no locking whatsoever on the 'registered_fb' list ... so it can cause random panics if one ever goes away
[16:47] <apw> which is exactly what happens when drm starts up
[16:48] <ogasawara> JFo: we having a bug chat this morning?
[16:48] <JFo> we are if you like
[16:49] <JFo> I can cancel if needed
[16:49] <JFo> since we were all gone last week
[16:49] <ogasawara> JFo: I'm indifferent, whatever the group wants to do is fine with me
[16:49]  * apw abivalent
[16:49] <JFo> lets have it then and see what we can accomplish :)
[17:02] <ogasawara> JFo: my mumble is horked, I can't year you.
[17:02] <JFo> :-(
[17:02] <tgardner> ogasawara, well, get unhorked
[17:02] <JFo> heh
[17:02] <ogasawara> JFo: continue on without me while I try to get it fixed
[17:02] <JFo> ok
[17:04] <ogasawara> tgardner: you sound sick
[17:05] <tgardner> ogasawara, <sneeze>
[17:13] <paultag> OK, just an update cnd, apw: Issue not present in 9.10, I'm calling this a regression. Bug filed ( ask JFo asked ) #610124, #610126.
[17:15] <JFo> thanks paultag :)
[17:16] <paultag> no problem, thank you guys for putting up with me all day
[17:16] <paultag> I'll be here if you need anything more out of me. I'll leave 9.10 on here if I need to do anything more for you guys.
[17:17] <vanhoof> JFo: ping
[17:17] <vanhoof> JFo: you mentioned in an email a while back about having a few wifi/usb dongles
[17:17] <JFo> I do indeed
[17:17] <JFo> :)
[17:17] <vanhoof> JFo: I assume these are all external devices? ... do you have anything that can connect to the mobo?
[17:18] <JFo> these are external
[17:18] <vanhoof> kk I assumed so
[17:18] <JFo> pete may have some that connect to the mobo
[17:18] <JFo> as I had to swap mine out at the kernel sprint in january\
[17:18] <JFo> vanhoof, anything in particular you need?
[17:18] <vanhoof> JFo: just seeing what we have in hand to do some testing 
[17:19] <JFo> I see
[17:19] <JFo> I'll get with pete to see if we have any chips for mobo
[17:20] <JFo> and if so, what
[17:20] <vanhoof> JFo: that would be awesome
[17:20] <JFo> who loves ya baby? ;)
[17:20] <vanhoof> JFo: this is all in reference to that thread for usb/wifi recommendations we had last month
[17:20] <JFo> yeah, I remember
[17:20] <JFo> cool
[17:20] <JFo> I'll get you a list of what I have as well
[17:22] <vanhoof> JFo: that'd be cool
[17:22] <vanhoof> JFo: just cc'd you in the thread for frame of reference
[17:24] <cnd> paultag, sounds good :)
[17:25] <JFo> vanhoof, cool, thanks
[17:26] <JFo> I'll send back my list to that group of folks
[17:46] <JFo> so tgardner any ideas what days you paid for dinner?
[17:47] <JFo> I want to make sure my per diem is correct :)
[17:47] <tgardner> JFo, yeah, hang on.
[17:47] <JFo> k, thanks
[17:48] <apw> tgardner, lbm was turned off for maverick in -meta, did you handle that, or does someone need to do so?
[17:49] <JFo> think he pinged ogasawara earlier about that
[17:49] <ogasawara> apw: doing so now
[17:49] <tgardner> apw, I bugged ogasawara about it just this AM
[17:49] <JFo> man, I'm good ;)
[17:49] <apw> heh ... and the circle is closed ... :)
[17:50] <tgardner> JFo, I don't have you on any of the receipts for when I paid.
[17:50] <JFo> huh, ok
[17:50] <JFo> oh right, because that sushi place didn't take plastic
[17:51] <JFo> dang, what night was that?
[17:51] <JFo> :-/
[17:51] <tgardner> JFo, right, that was just per-diem
[17:51] <JFo> right
[17:51]  * JFo has to take better notes
[17:51] <tgardner> JFo, 7/20
[17:51] <JFo> ah, thanks
[17:52] <jjohansen> 7/21 was pizza after bowling
[17:52] <JFo> I didn't go
[17:53] <JFo> can't remember where we went that night
[17:53] <jjohansen> JFo: ah, I couldn't remember for sure
[17:53] <JFo> heh
[17:53] <JFo> yeah, you guys ditched the fat kid :-(
[17:53] <JFo> j/k
[17:53] <apw> JFo, you didn't go to place with the accordion didi you?  seem to remember you went somewhere like that
[17:53] <JFo> that was the last night
[17:53] <JFo> when we took 'the photo'
[17:54] <apw> yeah i think pete went there another time, and you went with him somewhere on bowling night right?
[17:54] <JFo> yeah
[17:54] <JFo> may have been the fat koala
[18:19] <cking> JFo, I'd like to see that photo. I heard it was quite amusing to say the least
[18:50] <apw> JFo, we need to get you a little book of calm
[18:54]  * tgardner lunches
[19:15] <paultag> JFo: Just an interesting note for you guys
[19:15] <paultag> JFo: I just tried installing arch to the box. I downloaded 2010.05 ( archlinux ), same exact error line with b43. Breathe easy, it's upstream, not Ubuntu diversions
[19:22] <JFo> apw, indeed we do
[19:23] <JFo> paultag, while not good news, at least we know it is universal
[19:23] <paultag> JFo: yessir, and at least it's not your guys's fault.
[19:23] <JFo> indeed :-D
[19:24] <paultag> I think I might just try and debootstrap it, and compile an old kernel
[19:24] <paultag> and test every few releases
[19:25] <apw> paultag, there are older .debs for mainline kernels in the mainline kernel archive
[19:25] <paultag> apw: Oh? I only saw the recent series in my apt-cache. Do I have to install the debs by hand and divert upgrades on it?
[19:26] <paultag> And are they "safe" with 10.04 ?
[19:26] <apw> they install in their own namespace, so they are unaffected by other kernel
[19:26] <paultag> Ah, even better
[19:26] <apw> safe is harder to say ... they are upstream as i comes
[19:27] <paultag> thanks for your help guys :)
[19:27] <paultag> thanks apw, I'll try it
[19:27] <apw> https://wiki.ubuntu.com/Kernel/MainlineBuilds
[19:27] <paultag> can't be worse then compiling your own kernel
[19:27] <apw> quicker for sure
[19:27] <JFo> oh yeah\
[19:27] <paultag> aye aye
[19:32] <ogasawara> sconklin: I just submitted a patch to upstream stable which should resolve bug 544740 assuming upstream stable accepts it
[19:32] <ubot2`> Launchpad bug 544740 in linux (Ubuntu Lucid) (and 1 other project) "fix for iSight cameras not being recognized (affects: 4) (heat: 24)" [Medium,In progress] https://launchpad.net/bugs/544740
[19:33] <ogasawara> sconklin: I tagged it 2.6.32.y, is there a different tag you guys are using to track bugs that will possible get fixed with future stable releases?
[19:35] <sconklin> ogasawara: I'm not aware of any tag that's being used, but there probably is one. I want to ask Stefan, and get it documented on the tags page. Thanks for the patch!
[19:40] <vanhoof> sconklin: did you hear back on that email you sent last week to intel-gfx?
[19:41] <sconklin> vanhoof: Manoj heard back from upstream. They rejected that patch, and are working on a real fix.
[19:42] <vanhoof> sconklin: this was the two liner?
[19:43] <sconklin> vanhoof: Yes. Manoj will be the interface person between OEM and the kernel team on this (and all kernel issues)
[19:43] <vanhoof> sconklin: https://patchwork.kernel.org/patch/109959/
[19:43] <vanhoof> looks like it was applied
[19:44] <sconklin> vanhoof: talk to Manoj about it, I haven't seen any of the emails that were exchanged with upstream about this
[19:44] <vanhoof> sconklin: k
[19:45] <sconklin> manjo:  ^^
[19:45] <manjo> vanhoof, I just emailed you 
[19:46] <vanhoof> manjo: right saw that ... thats the bug for failure to return from suspend
[19:46]  * vanhoof was referring to the two liner for the x201 w/ no graphics at all
[19:46]  * manjo so many intel video issues... 
[20:00]  * ogasawara lunch
[20:00] <JFo> sigh, now I'm sneezing... all I had before was a cough. :-/
[20:01]  * JFo hates rallyflu
[20:06] <ayan> ugh.  bummer.
[20:08] <jjohansen> -> Lunch
[21:42] <tgardner> ogasawara, http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=00f7ee15c69a78ba2551322b184b5b337dca2e4e is obsoleted by Linus' e7b96f28c58ca09f15f6c2e8ccbb889a30fab4f7
[21:44] <ogasawara> tgardner: ack, I'll replace it.