[13:29] <sconklin2> cking: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613381
[13:29] <ubot2> Launchpad bug 613381 in linux (Ubuntu Maverick) (and 2 other projects) "S3 resume hang when PCI Express wakeups don't clear the PM1 PCI_WAKE_DISABLE bit (affects: 1) (heat: 44)" [Undecided,Fix committed]
[13:31] <cking> sconklin, different BIOS. I will re-check with original H/W and BIOS to see if it's not a BIOS regression.
[13:31] <sconklin> cking: ok, just trying to keep you posted
[13:32] <cking> sconklin, thanks, I was eyeballing it two mins a go :-)
[13:32] <jk-> cking: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668413 - looks like ACPI is reporting incorrect temperature values
[13:32] <ubot2> Launchpad bug 668413 in linux (Ubuntu) "Fan malfunction on Lenovo 3000 N100. (affects: 1) (heat: 10)" [Undecided,New]
[13:32] <jk-> does the fwts cover any of this?
[13:32] <cking> jk-, this is not an ACPI issue. I have this machine
[13:33] <jk-> cking: oh!
[13:33] <cking> jk-, http://smackerelofopinion.blogspot.com/2010/09/sensors-reporting-hot-cpu-in-maverick.html
[13:33] <cking> I will add this info into the bug
[13:34] <jk-> cking: ok, thanks
[13:35] <jk-> seems to be intermittent though, would TjMax be changing?
[13:36] <cking> jk-, ok, it's an older kernel and older BIOS, so my blog is not relevant.
[13:49] <cking> jk-, I updated that bug.
[13:49] <jk-> cking: awesome, thanks
[13:50] <cking> np
[14:04] <JFo> you rock cking... hey, aren't you supposed to be on a plane? :-P 
[14:04]  * JFo covers his head for the beating
[14:05] <cking> :-)
[14:13] <m4t> hey, has anyone else seen strange boot failures with 10.10 x86 + kernel-package 12.036?
[14:13] <m4t> identical code + kernel-package produces bootable kernels in a 10.04 debootstrap chroot
[14:28] <apw> m4t, 12.036 ?
[16:06] <LLStarks> hi, does anyone here know whether the ubuntu kernel pulls from the iwlwifi-2.6 git?
[16:45] <m4t> apw yes 12.036
[16:46] <m4t> https://launchpad.net/ubuntu/+archive/primary/+files/kernel-package_12.036_all.deb
[16:46] <m4t> the same .deb produces bootable kernels inside a lucid deboostrap
[16:46] <m4t> but not on maverick itself
[16:46] <m4t> did some odd default cflag change or the like, between releases?
[16:53] <m4t> this seems a really odd problem to me, i'd like to figure out what's causing it. the kernels compiled in maverick with that kernel-package just hang on boot. so from my limited perspective it seems like it might be a code generation issue, or perhaps some part of the process is stripping things out of the kernel
[16:54] <m4t> CONFIG_HANG_INDEFINITELY is not set
[17:34] <apw> m4t, whats the full version number of the busted version ?
[17:44] <LLStarks> apw, i may have a solution for the iwl3945 throughput issues that have been present since hardy.
[17:45] <apw> LLStarks, solutions are always welcome ... what you do ... by an ath9k ? :)
[17:45] <LLStarks> nope.
[17:45] <LLStarks> http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi-2.6.git;a=commit;h=0d8e0e28a27779f480adb6674ca5fc29879a2080
[17:45] <LLStarks> this commit and the ones immediately after it are said to fix the miserable speeds
[17:46] <LLStarks> i was rather surprised that these changes aren't included in the 2.6.37 natty kernels
[17:46] <apw> LLStarks, sounds good, if you can confirm that we'd be interesting
[17:47] <LLStarks> we have one confirmation and i may have also, if only for a few minutes.
[17:47] <apw> LLStarks, well the natty kernels would have them if upstream has them
[17:47] <apw> i assume from your link they are in the wifi tree
[17:47] <LLStarks> yes
[17:47] <LLStarks> but not in linus' master for some reason
[17:48] <apw> yeah, perhaps waiting for -rc2 to merge yet
[17:49] <LLStarks> is there any way to compile iwl3945 by itself without a 4 hour roll?
[17:49] <LLStarks> *iwl3945 plus the 80211 stuff
[17:50] <LLStarks> splicing into compat-wireless is hit-or-miss
[17:51] <apw> LLStarks, well if you have a build directory, you can drop the build stamp _only_ from the debian/stamps directory and it will incrementally build the updated files only
[17:52] <LLStarks> debian packaging... yuck. i just want a .ko
[17:55] <LLStarks> apw, is it possible to clone a kernel git and then upload it to launchpad for compilation?
[17:55] <LLStarks> *upload to a launchpad ppa
[17:56] <apw> LLStarks, one of ours?  yep, fakeroot debian/rules clean; then package it
[18:03] <m4t> apw these are vanilla; 2.6.35.7, 2.6.35.8, 2.6.36 all hang at the same place during boot, when compiled on 10.10/x86 with kernel-package 12.036
[18:03] <m4t> with both gcc-4.4 and gcc-4.5
[18:04] <m4t> identical kernel-package+kernel source+kernel config boot fine, when compiled inside lucid chroot
[18:05] <m4t> i'm trying a generic linux_2.6.35-22.35 build with dpkg-buildpackage -b now, to see if the same issue is there
[18:07] <apw> m4t do thes ones in the mainline archive boot ?
[18:07] <m4t> yep 2.6.36 from natty boots fine
[18:08] <m4t> as do the generic maverick kernels
[18:10] <m4t> with nousb acpi=off pnpbios=off, the broken kernel hangs at ps2 keyboard initialization
[18:10] <m4t> otherwise, it hangs when first ehci device comes up
[19:34] <kees> so, what's the magic to push to my own natty repo on zinc? I swear I'm doing what I did for maverick, but git is erroring out
[19:35] <kees> I have the repo set up on zinc
[19:35] <kees> I have a natty branch locally
[19:35] <kees> I can't push
[19:35] <kees>  ! [remote rejected] natty -> master (branch is currently checked out)
[19:35] <ubot2> kees: Error: I am only a bot, please don't think I'm intelligent :)
[19:44] <kees> tgardner: got a moment to help me with this?
[19:45] <tgardner> kees, you likely didn't clone it as a bare repo
[19:45] <kees> tgardner: http://paste.ubuntu.com/526538/
[19:46] <kees> the remote is cloned per https://wiki.ubuntu.com/KernelTeam/KernelSimpleGuide
[19:46] <tgardner> kees, set 'bare=tru' in config
[19:46] <tgardner> true*
[19:46] <kees> tgardner: on zinc or local?
[19:46] <tgardner> on zinc
[19:47] <kees> weird. that used to work. so the wiki is wrong?
[19:48] <tgardner> kees, looks like it. I'll fix it
[19:48] <kees> tgardner: okay, thanks
[19:48] <kees> yup, that push worked now
[19:50] <tgardner> kees, wiki updated
[19:51] <kees> tgardner: sweet, thanks. now I can do my pull requests. :)