[01:55] <shawn1> Hello
[01:57] <shawn1> My kernel doesn't seem to be allowing me to use a multi-gpu card (GTX295).  It will only detect one core.  I checked lspci and that should show two entries for the GTX 295, but it only shows one.  I did lspci -A intel-conf2, though, and found "00:08.0 Non-VGA unclassified device: Device aebc:75c5 (rev 40)".  That item didn't show up on any of the other lspci detection lists.
[02:00] <ohsix> do you get any messages about pci routing in dmesg? there's a few methods you can try if the bios doesn't set things up right
[06:54] <unixpro1970> Shawn2, some gtx295 cards are 1 core while others are 2 core.
[06:54] <unixpro1970> The single core gtx295 came later
[10:38] <pip> !ciao
[10:38] <ubot2`> Factoid 'ciao' not found
[10:38] <pip> !list
[10:38] <ubot2`> This is not a file sharing channel (or network); be sure to read the channel topic. If you're looking for information about me, type « /msg ubottu !bot ». If you're looking for a channel, see « /msg ubottu !alis ».
[10:58] <abdo> Hello guys
[10:58] <abdo> one of my servers had a kernel panic
[10:59] <abdo> I can collect "linux-image-2.6.35-26.0.crash.gz" file from /var/crash
[10:59] <abdo> I tried to use:
[11:01] <abdo> gdb vmlinuz-2.6.35-26-server linux-image-2.6.35-26.0.crash
[11:01] <abdo> and got:
[11:01] <abdo> /tmp/linux-image-2.6.35-26.0.crash" is not a core dump: File format not recognized
[11:01] <abdo> can any one help me and put me on the right path? thanks in advance.
[12:32]  * ppisati -> starvation avoidance
[13:00] <rbasak> I'm trying to cross compile an armhf kernel out of the git source for bisecting purposes. Is this easiest way? I found instructions for using xdeb but they break when when xdeb 404s on http://ports.ubuntu.com/ubuntu-ports/pool/main/z/zlib/lib32z1_1.2.3.4.dfsg-3ubuntu3_armel.deb. And the instructions at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel don't cover cross compiling. Some help, please?
[13:01] <ppisati> rbasak: export $(dpkg-architecture -aarmel); export CROSS_COMPILE=arm-linux-gnueabi-
[13:01] <ppisati> rbasak: fakeroot debian/rules clean binary-omap4
[13:01] <ppisati> rbasak: to get an armhf kernel, substitute "-aarmel" with "-aarmhf"
[13:02] <ppisati> rbasak: yep, i should update those instructions
[13:02] <rbasak> awesome, thanks!
[13:02] <rbasak> I have an automated test rig now. I should be able to do an automatic bisection
[13:03] <ppisati> rbasak: btw, what are you looking for with your bisection?
[13:03] <rbasak> right now, the random panics. but I also wanted to have an arrangement ready to do it in the future
[13:04] <ppisati> rbasak: random panic???
[13:04] <rbasak> the installer fails randomly right now
[13:04] <rbasak> I had some logs saved from friday, hang on
[13:05] <rbasak> ppisati: eg. http://paste.ubuntu.com/819098/
[13:07] <ppisati> rbasak: well, that's with the previous kernel
[13:08] <ppisati> rbasak: but the panic looks strange'
[13:08] <rbasak> ppisati: ah yes - I take it the installer hasn't been updated with the latest kernel yet
[13:09] <ppisati> rbasak: tell me if it's reproducible with the new one
[13:12] <rbasak> ppisati: I'd love a script to give me a working uImage and uInitrd out of the latest kernel. How would I do that?
[13:12] <rbasak> I'm not yet very familiar with the tooling around the kernel builds
[13:14] <ppisati> rbasak: uImage is definitely inside the .deb, so you can get it easily
[13:14] <ppisati> rbasak: while initrd IIRC is built at install time
[13:14] <rbasak> what about the installer initrd? that's the one I'm after
[13:14] <ppisati> rbasak: so probably the easiest way is to insall the kernel somewhere and get the two files
[13:14] <rbasak> If the uImage is in there I can extract that part, thanks
[13:14] <rbasak> Is the installer uInitrd the same as an installed machine's uInitrd?
[13:15] <rbasak> The one you gave me for the test the other day didn't work
[13:15] <ppisati> rbasak: don't know, you should ask the #arm guys (ogra's angels)
[13:15] <rbasak> OK I'll take it to #ubuntu-arm
[13:29] <abdo> Can any one help me on my question?
[13:37] <rbasak> ppisati: make: *** No rule to make target `binary-omap4'.  Stop.
[13:37] <rbasak> ppisati: this is debian/rules out of ubuntu-precise.git, right?
[13:42] <ppisati> rbasak: did you checkout the omap4 branch first? and did you clean?
[13:43] <rbasak> ah, there's an omap4 branch? :-)
[13:43] <ppisati> rbasak: git checkout ti-omap4
[13:43] <rbasak> ppisati: now working, thanks :)
[13:44] <ppisati> rbasak: tell me how it goes
[13:44] <rbasak> will do!
[14:12] <ppisati> a bug in Incoplete status will vanish after 60days of no activity, right?
[14:12] <ppisati> *Incomplete
[14:30] <herton> ppisati, for Ubuntu I think that's correct, there are more details: https://help.launchpad.net/Bugs/Expiry (assuming this is uptodate)
[15:27] <ppisati> why bug 732628 is still showing up in linux-ti-omap4?
[15:27] <ubot2`> Launchpad bug 732628 in linux-ti-omap4 "TOCTOU in mount.ecryptfs_private" [Low,Fix committed] https://launchpad.net/bugs/732628
[15:31]  * ogasawara back in 20
[16:05] <jsalisbury> ogasawara, A possible regression with ath9k devices in 3.2.0-12: bug 923512 and 923605
[16:05] <ubot2`> Launchpad bug 923512 in linux "ath9k wireless stopped working after kernel upgrade to 3.2.0-12" [High,Incomplete] https://launchpad.net/bugs/923512
[16:05] <ubot2`> Launchpad bug 923605 in linux "Wireless network card unable to connect to router with 3.2.0-12 kernel (dup-of: 923512)" [Undecided,Incomplete] https://launchpad.net/bugs/923605
[16:09] <jsalisbury> ogasawara, I can bisect between the two kernels to identify the bad commit.
[16:12] <ogasawara> jsalisbury: ok thanks.  the only thing that would come to mind is something in the 3.2.2 stable update...
[16:12] <ogasawara> jsalisbury: everything else would seem unrelated
[16:15] <ogasawara> jsalisbury: you'll want to find out specifically what version them mean when they say "working fine with the previous kernel version". do they mean 3.2.0-11.19 or an Oneiric kernel or ...
[16:23] <jsalisbury> ogasawara, ahh, right.  thanks.
[17:00] <smb> tgardner-afk, Not sure whether someone fixed something under our back or it makes a difference between bare metal and kvm-vm or is just random, but right now an cobbler install of precise-amd64 did work (with the usual whining about unloadable modules)
[17:15] <ogasawara> diwic: is there a specific tag you want us to use to flag audio bugs which are likely due to the the new jack detection patches?  or do you want us to just ping you with the bug #'s?
[17:15] <ogasawara> eg bug 923316
[17:15] <ubot2`> Launchpad bug 923316 in linux "[regression] Speakers are not muted while plugin the headphone " [Undecided,Confirmed] https://launchpad.net/bugs/923316
[17:16] <ogasawara> bug 923409
[17:16] <ubot2`> Launchpad bug 923409 in linux "No sound" [Undecided,Confirmed] https://launchpad.net/bugs/923409
[17:19] <ogasawara> jsalisbury: ^^ just fyi, you'll want to keep an eye out for any audio regressions as of 3.2.0-11.19 due to the new jack detection patches
[17:35]  * ppisati disappears for a bit...
[17:51] <diwic> ogasawara, ouch :-( 
[17:52] <diwic> ogasawara, I guess pinging me or assigning bugs to me will be best, thanks
[17:53] <ogasawara> diwic: ack, will do
[18:01] <jsalisbury> ogasawara, I'll keep an eye out, thanks
[18:38] <vanhoof> ogasawara: been otp for a bit, but tgardner let me know you found the prob already w/ cw-3.2, happy to test things out here for ya
[18:39] <ogasawara> vanhoof: perfect, I'm just getting the bug filed etc.  Will get a patch thrown together and have you test.
[18:39] <vanhoof> ogasawara: for reference: http://paste.ubuntu.com/822889/
[18:56]  * tgardner -> lunch
[20:00] <jwi> jsalisbury: i think bug 923094 is just about shipping that specific module in /debian.master/d-i
[20:00] <ubot2`> Launchpad bug 923094 in linux "Debian Installer kernel (PowerPC) is missing therm_adt746x module" [Medium,Incomplete] https://launchpad.net/bugs/923094
[20:15] <ogasawara> vanhoof: bug 923900, http://people.canonical.com/~ogasawara/lp923900/
[20:15] <ubot2`> Launchpad bug 923900 in linux-backports-modules-3.0.0 "Enable iwlwifi drivers for compat-wireless v3.2 backports" [Medium,Triaged] https://launchpad.net/bugs/923900
[20:16] <vanhoof> ogasawara: thanks
[20:16] <vanhoof> will give it a go
[20:21] <jsalisbury> jwi, right
[20:27] <vanhoof> ogasawara: looks good, gonna do some testing now w/ new(er) cards
[20:27] <vanhoof> ogasawara: http://paste.ubuntu.com/823004/
[20:27] <vanhoof> ogasawara: thank you :D
[21:39] <smagoun> A question on kernel ABI numbers. The ABI numbers need to be unique within a particular topic branch, but not globally - correct? So for example if you have a topic branch foo with ABI base 3.2-100, and another topic branch bar with ABI base 3.2-100, would there be package collisions if packages from each branch were in the same archive? (Not that this is good form)
[21:41] <tgardner> smagoun, they need to be unique within an archive since all of the binary packages share the same directory.
[21:45] <smagoun> tgardner: So we'd potentially wind up with linux-image-3.2.0-100-foo and linux-image-3.2.0-100-bar? Which isn't useful if you're trying to keep the two separate. Is that correct?
[21:48] <tgardner> smagoun, it might be confusing if the binaries are unrelated ('cause its the form we have right now, e.g., linux-image-3.2.12-virtual and linux-image-3.2.12-generic)
[21:50] <tgardner> note that I didn't get those example version numbers quite correct. it should have been linux-image-3.2.0-12-generic, etc
[21:50] <smagoun> tgardner: makes sense. Is there a 'safe' ABI base that thirdparties can adopt as an ABI base if they want to avoid collisions with Ubuntu kernels for the forseeable future (say through 14.04)? -2000, for example?
[21:51] <tgardner> smagoun, yeah, anything 3 digits with a unique flavour name is likely gonna be OK
[21:52] <smagoun> tgardner: thanks. Is 4 digits off-limits, or just more typing than 3 digits and therefore less desirable?
[21:52] <tgardner> smagoun, checkout how we've named the ti-omap4 stuff: https://launchpad.net/ubuntu/+source/linux-ti-omap4. 4 digits is fine (I mis-spoke)
[21:53]  * smagoun looks
[21:53] <smagoun> tgardner: Is there a specific reason for the jump in ABI between 3.0 and 3.2? I see 3.0.0-1205.10 in 11.10, and 3.2.0-1405.7 in 12.04
[21:55] <tgardner> smagoun, since the kernel version is embedded in the package name there really wasn't a need to also rev the ABI series, but it might reduce confusion. I dunno... 
[21:56] <smagoun> understood, thanks
[21:56] <tgardner> so, no, I don't think there was a specific reason
[21:56]  * tgardner is EOD
[23:03] <hallyn> hm, is bug 923900 why my laptop lost 
[23:03] <ubot2`> Launchpad bug 923900 in linux-backports-modules-3.0.0 "Enable iwlwifi drivers for compat-wireless v3.2 backports" [Medium,Triaged] https://launchpad.net/bugs/923900
[23:03] <hallyn> wireless with latest update?
[23:04] <hallyn> probably not...~.