[01:40] <drbcladd> Upgrade to 12.04b on Alienware m17 with Corsair SSD as sda. Reboot to kernel panic. Tried booting daily build on CD, same panic. Best information I have: squashfs was logging; pagefault, null RIP message, kernel panic "not synching fatal exception in interrupt" then a line with pid and "comm: mod probe tainted G      D"
[01:41] <drbcladd> Posting in an effort to that disk to boot, sure, but also, what information can I give you when it doesn't even get to logging?
[02:02] <drbcladd> Well, good people, it is just about my bedtime; I will hang out here later and see if I can provide useful information for bug hunting. Thanks to the kernel team for their hard work.
[04:09] <GrueMaster> What ever happened to the 3 week SRU cadence?  I tested SRU kernels last week, the week before, now I am seeing yet another omap4 kernel SRU notification?
[04:10] <GrueMaster> Can we have some semblance of a scheduled release?
[04:48] <herton> GrueMaster, we are on the 3 week cadence, this week we will have new kernels prepared, nothing extra. Also there are kernels still from previous round that are pending or were not tested: a new maverick ti-omap4 with the fix for QA regression you identified (linux-ti-omap4 2.6.35-903.32, bug 942766, see the duplicate bug which was the update that you failed QA, fixed in this new one). And kernels from previous round still pending testing: linux
[04:48] <herton> -fsl-imx51  2.6.31-612.33 (bug 931913), linux-mvl-dove 2.6.32-423.42 (bug 932240). For more information on pending updates, see http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[04:48] <ubot2`> Launchpad bug 942766 in kernel-sru-workflow "linux-ti-omap4: 2.6.35-903.32 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/942766
[04:48] <ubot2`> Launchpad bug 931913 in kernel-sru-workflow "linux-fsl-imx51: 2.6.31-612.33 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/931913
[04:48] <ubot2`> Launchpad bug 932240 in kernel-sru-workflow "linux-mvl-dove: 2.6.32-423.42 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/932240
[04:50] <herton> And this is the schedule, https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock, we are on the SRU prep this week (new kernels)
[06:06] <GrueMaster> I see what appears to have happened.  Somewhere in the middle, I got side tracked with milestone testing.  Silly me.  
[06:07] <GrueMaster> Actually, most of the testing had been done, was just waiting for me to pass/fail.  Babbage was the only straggler, and it is running now.
[08:36] <rbasak> What would happen if I tried to boot precise userspace using a 2.6.32 kernel? Would it work? Is there any particular reason why it wouldn't?
[09:06] <smb> rbasak, Chances it does work are reasonably good. The major problem would be interface changes. One would think of drm, but also sysfs had the tendency to change at some point in an incompatible way
[09:07] <smb> But normally it is more problematic than going forward
[09:07] <smb> (like booting a precise kernel in lucid userspace)
[09:07] <smb> Because userspace tends to expect certain new features
[09:07] <rbasak> smb: thanks. drm won't be a problem as this would be headless. This is for hardware that isn't upstream and would require separate enablement work
[09:08] <rbasak> smb: I'll get them to try it :)
[09:08] <smb> rbasak, The only way to say with more certainity. :) 
[09:09] <rbasak> :-)
[09:09] <smb> I recently booted 2.6.38 on precise in a vm which seemed to work. Did not go further, though
[09:23] <apw> rbasak, i might expect it to work, but you get to keep all the pieces
[09:24] <rbasak> Understood :)
[09:43] <ppisati> smb: do you remember what's the script used to invalidate a tracking bug? i know it's part of kteam-tools but i don't remember the name off hand
[09:47] <smb> ppisati, Its so long ago, I would not know from my memory. I think I may even just have set the status to invalid which likely is wrong... hmmm
[09:48] <ppisati> smb: found
[09:49] <ppisati> smb: kteam-tools/stable/check-release-tracking-bugs
[09:49] <smb> "obviously"...
[09:56] <ppisati> smb: yeah... :)
[09:56] <ppisati> smb: i was AFK, could hear you but couldn't answer...
[09:57] <smb> ppisati, No worries, I am just generally ranting into unspecific directions... :-P
[09:59] <ppisati> smb: "ranting in the wind" that's a famous song...
[10:01]  * smb thought that was "blowing in the wind" ;)
[12:11]  * ppisati -> out for lunch
[12:12]  * henrix follows ppisati 
[13:48] <apw> :q
[13:49] <henrix> apw: wrong buffer
[14:20] <apw> sforshee, hey was there something for macbook brigtness in the -18 kernel ?
[14:21] <sforshee> apw, there's a new driver that gets screen brightness adjustable for some macbooks
[14:21] <apw> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748
[14:21] <ubot2`> Launchpad bug 947748 in gnome-settings-daemon "Brightness control not working after latest update" [Undecided,Confirmed]
[14:21] <apw> sforshee, then that is likely fallout
[14:23] <sforshee> apw, I'll follow up
[14:24] <tgardner> apw, grub2 just got uploaded with 20+ patches.
[14:24] <apw> tgardner, deep joy
[14:25] <tgardner> apw, I had the same revelation
[14:25] <jsalisbury> ##
[14:25] <jsalisbury> ## Kernel team meeting today @ 17:00 UTC
[14:25] <jsalisbury> ##
[14:28] <sforshee> apw, I don't think the brightness thing is a kernel problem. I'm seeing it on a macbook air that does not use the new driver (the module isn't even loaded). Can't adjust backlight using the buttons or settings, but I can adjust it through sysfs.
[14:29] <apw> sforshee, cool, can you point them at how to debug in the bug
[14:29] <sforshee> apw, ack
[14:29] <apw> seb128, ^^
[14:29] <Laney> fwiw with the latest kernel my macbook pro doesn't suspend when I shut the lid, but running sleep.sh does suspend it
[14:29] <Laney> what's the bug number?
[14:29] <seb128> sforshee, apw: thanks
[14:30] <seb128> Laney, bug #947748 is the one we discussed
[14:30] <ubot2`> Launchpad bug 947748 in gnome-settings-daemon "Brightness control not working after latest update" [Undecided,Confirmed] https://launchpad.net/bugs/947748
[14:30] <seb128> but it doesn't include suspend issues so far
[14:30] <Laney> ok, I wonder if those are linked
[14:30] <Laney> didn't check brightness
[14:31] <tgardner> Laney, I'm sure sforshee has a bug on that somewhere. I experienced the same issue.
[14:31] <seb128> sforshee, apw: g-s-d power code didn't change a lot, I would be a bit surprised if that's a g-s-d issue...
[14:31] <Laney> tgardner: ah OK
[14:31] <Laney> got a bit of a shock when returning home last night that the laptop was whirring away on the bed ...
[14:31] <apw> sforshee, isn't Laney's issue more likely the edp issue ?
[14:32] <tgardner> Laney, https://wiki.ubuntu.com/Kernel/MacEnablement
[14:32] <Laney> mine is a 7.1
[14:32] <sforshee> apw, could be
[14:32] <Laney> lid suspend always worked until now, but to be fair I hadn't rebooted for weeks so was probably on a rather old kernel before
[14:33] <sforshee> seb128, I'll reboot to the previous kernel and see if it works, but for this machine nothing should have really changed between kernels
[14:33] <seb128> sforshee, thanks
[14:33] <apw> Laney, there is an issue in which the internal edp is detected as external by g-s-d, and we do no suspend on lid if there is an 'external' monitory
[14:33] <Laney> sorry, I don't know what edp means :(
[14:34] <sforshee> embedded display port
[14:34] <Laney> ah
[14:34] <Laney> can I confirm this somehow?
[14:34] <sforshee> seb128, can't adjust brightness with -17 either, and I know it used to work with that kernel
[14:34] <seb128> sforshee, is the slider displayed in the ui?
[14:35] <seb128> sforshee, do you know how to query udev for "backlight" devices?
[14:35] <Laney> brightness works btw
[14:35] <seb128> the code basically does devices = g_udev_client_query_by_subsystem (client, "backlight");
[14:35] <sforshee> the slider appears briefly then goes away
[14:35] <apw> seb128, did udev change ?
[14:35] <seb128> apw, yes
[14:35] <sforshee> so someone else was having touchpad problems because udev wasn't done when the desktop started, wonder if that could be happening here as well
[14:36] <seb128> apw, but the change doesn't seem likely to create issues
[14:36] <seb128> "do not exit across a pending DM_COOKIE"
[14:36] <apw> seb128, well as sforshee said, booting the old kernel with this userspac is step one
[14:36] <apw> if that works, then its kernel, else its not
[14:37] <apw> and we will want to start downgrading udev, and g-s-d to see which of them it is
[14:37] <seb128> right
[14:37] <seb128> downgrading g-s-d next would be welcome
[14:38] <seb128> sforshee, apw: btw the current gnome-desktop3 includes the edp fixes from sforshee
[14:38] <seb128> i.e http://git.gnome.org/browse/gnome-desktop/commit/?id=11997d32313cd67f24cb26e18c562fa4b75ea36f
[14:38] <seb128> not sure if that's the issue you were looking at for Laney's suspend issue
[14:38] <Laney> I am testing -17
[14:39] <Laney> but you don't suspect a kernel problem so :-)
[14:40] <apw> Laney, i think they are saying if you have everything up to date squeeky new we might expect it fixe
[14:40] <Laney> oh ok
[14:40] <Laney> I dist-upgraded yesterday morning, so if it's since then then maybe
[14:44] <sforshee> seb128, I installed g-s-d 3.3.90-0ubuntu4 and now my backlight buttons work
[14:44] <seb128> sforshee, ok, great
[14:45] <sforshee> also the keyboard brightness indicator displays correctly
[14:45] <seb128> sforshee, is the slider in the power system settings ui showing as well?
[14:45] <sforshee> seb128, yes
[14:46] <seb128> sforshee, thanks for testing! and it's broken if you update gsd?
[14:47] <seb128> sforshee, can you get a G_MESSAGES_DEBUG=all gnome-settings-daemon --debug for both version?
[14:47] <seb128> sforshee, I would like to see what changed
[14:48] <sforshee> seb128, going back to 3.3.91-0ubuntu1 makes everything break again
[14:48] <sforshee> seb128, I'll get the debug output for you and put it on the bug
[14:49] <seb128> oh
[14:50] <seb128> sforshee, $ /usr/lib/gnome-settings-daemon/gsd-backlight-helper --get-brightness
[14:50] <seb128> sforshee, what does that return?
[14:51] <sforshee> seb128, it seems to be giving the correct values
[14:51] <seb128> weird :-(
[14:51] <seb128> there is basically 3 commits in the power code between those versions
[14:51] <seb128> http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0fc947c590ec40f492af16cef5e3de7775ba08ab
[14:51] <seb128> http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=305057ac831b357a03bb3f244059048551321b71
[14:51] <seb128> http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d361fcee80bbcf8cf2dd692eb91b05800b29f5fb
[14:52] <seb128> but I don't see any of those leading to issues
[14:52] <seb128> the only one that could make it bail out is the < 0 check
[14:52] <seb128> sforshee, what is you get the max value rather than the current one?
[14:52] <seb128> does the value seem correct?
[14:53] <seb128> --get-max...
[14:53] <sforshee> seb128, the value is correct
[14:53] <seb128> ok
[14:54] <seb128> dunno then... I will look at the debug log and the code
[14:54] <seb128> sforshee, thanks
[14:54] <sforshee> seb128, what's the best way to get g-s-d launched with the debugging you asked for?
[14:55] <seb128> sforshee, kill the running one and copy the command I gave
[14:55] <seb128> kill -9 `pidof g-s-d`; g-s-d --debug
[14:55] <seb128> if gnome-session is respawning it usually that will let you hijack it
[14:55] <seb128> export G_MESSAGES_DEBUG=all first though
[14:55] <seb128> that's needed for the logging to work
[14:57] <sforshee> yeah, it's the respawning that gets in the way
[15:07] <sforshee> seb128, just posted the g-s-d debug output to the bug
[15:07] <seb128> sforshee, thanks
[15:36]  * ogasawara back in 20
[16:35] <GrueMaster> herton: Not sure you saw my post last night after yours, I had lost track of last week due to milestone testing and a huge amount of other work I was doing (so in essence I am missing a week of sanity).  :P
[16:36] <Laney> I just checked with new everything and the suspend failure is still there, btw
[16:36] <herton> GrueMaster, ok, np
[16:36] <GrueMaster> At this time (barring the latest spin of SRU kernels) I believe I have tested everything to date.
[16:37] <GrueMaster> Also, when will we be dropping the imx51 kernels?  Lucid was only 18 months for arm, and the last of the buildds should have been replaced with Panda now afaik.
[16:38] <henrix> apw: here's the link: https://bugzilla.kernel.org/show_bug.cgi?id=22602
[16:38] <ubot2`> bugzilla.kernel.org bug 22602 in FAT/VFAT/MSDOS "Oops while unmounting an USB key with a FAT filesystem" [Normal,Assigned]
[16:41] <jsalisbury> apw: http://www.spinics.net/lists/linux-scsi/msg57577.html
[16:45] <jsalisbury> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/738876
[16:45] <ubot2`> Launchpad bug 738876 in linux "BUG: unable to handle kernel NULL pointer dereference at 00000000000000f0" [Medium,In progress]
[16:59] <sandjkirkland> I am having issues with oneiric to where the computer freezes and the monitor goes white, at random. 
[17:20] <davmor2> hey guys If I do a fresh install from the beta1 64bit desktop cd/usb it hard crashes the entire system starting the slide show for me on this system is there anything I can do to get some better logs to try and figure out what is causing it
[17:23] <apw> davmor2, if you boot it and don't install does it survive being used ?  you might be able to figure out how to trigger the issue there perhaps
[17:23] <apw> davmor2, i assume when you say hard crashes you have flash capslock, and you are unable to switch VTs
[17:25] <davmor2> apw: it runs fine from usb (I don't have a cd/dvd here)  and I've run the code for the slide show from the desktop to see if it is that, that is causing the crash and nothing but with out fail if I run the installer I get the crash
[17:26] <apw> davmor2, and the symptoms of the crash are?
[17:26] <davmor2> apw: And yes not sure about the flashy led but there it no way to access the tty's
[17:26] <apw> are you able to access the ttys from the live boot... i can't remember if its enabled
[17:26] <apw> davmor2, how long do you have from hitting 'GO' to when it breaks in the slide show?
[17:27] <davmor2> apw: so I hit the last continue button and then a few seconds pass,  the slideshow never starts and the system dies
[17:28] <apw> so that must be when it does the formatting of your disks right ?
[17:28] <apw> if it is crashing and you have a 'few seconds' you might be able to switch VT to whereever the kernel has its outptu going
[17:28] <apw> so that you can see it when the panic comes (assuming it is one)
[17:28] <davmor2> apw: I'm in millbank currently so I've run through it with ev to try and diagnose anything from ubiquity's side and nothing breaks it unless I do an install
[17:29] <apw> davmor2, ahh ok, well we'll be in tomorrow also so if we don't make progress here, ask my body about it
[17:29] <davmor2> apw: ah I'm back in wolvo tonight only down for today
[17:29] <apw> davmor2, anyhow one of the other VTs has the raw kernel output i beleieve, if you can find that and switch to it before the crash you might get some more info
[17:30] <davmor2> apw: Cool I'll try that tomorrow as I need the system today
[17:30] <apw> you can try and find it in the live boot i presume, and look for something which looks like the bottom of the dmesg output
[17:31] <apw> sandjkirkland, have you filed a bug for this issue?  do we know if the machine is completely dead, for example are you able to access the machine over the network when this occurs
[17:31] <apw> jsalisbury, bug #938894 us t
[17:31] <ubot2`> Launchpad bug 938894 in linux "BUG: unable to handle kernel paging request, __ticket_spin_lock+0x9/0x30 (dup-of: 922906)" [Medium,Incomplete] https://launchpad.net/bugs/938894
[17:31] <ubot2`> Launchpad bug 922906 in linux "BUG: unable to handle kernel NULL pointer dereference at 0000009c" [High,Confirmed] https://launchpad.net/bugs/922906
[17:31] <apw> jsalisbury, is the one which i am less sure is a duplicate of the ticket panic
[17:32] <davmor2> apw: the only thing I saw from tail on syslog was reference to an fb issue and at that piont if I flick back to the install it dies,  if I stay in the tty it seems to keep working
[17:32] <davmor2> apw: I'll try and get some more tomorrow for you :)
[17:33] <apw> davmor2, ok that might well be the hint we need i wonder if you might be able to install openssh-server into the live environ
[17:33] <apw> and login remotly before triggering the install phase, that might do it
[17:33] <apw> then you might get the end of the error before the machin
[17:33] <apw> dies
[17:34] <davmor2> apw: yeap I'll give it a bash tomorrow
[17:42] <diwic> tgardner, could you explain what you mean with "The 12.04 installer will not boot a non-PAE CPU"? I mean, my custom ISO *does* boot and install a non-pae kernel.
[17:43] <tgardner> diwic, I meant that the official  ISOs won't boot a non-PAE CPU.
[17:44] <diwic> tgardner, ok. Which is why I made a custom ISO.
[17:44] <diwic> tgardner, btw, it was also pointed out to me that the netboot iso/installer would support non-pae kernels.
[17:45] <diwic> tgardner, https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2012-February/013276.html
[17:47] <tgardner> diwic, hmm, that goes against what we decided at the TB meeting about non-PAE support. on the other hand, I don't care that much. non-PAE is going to be dropped for 12.10
[17:49] <jdstrand> jsalisbury, ogasawara: hi, fyi it doesn't seem bug 911059 is fixed after all
[17:49] <ubot2`> Launchpad bug 911059 in linux "Intel wireless randomly drops connection" [High,Fix released] https://launchpad.net/bugs/911059
[17:50] <jdstrand> should I file a new bug?
[17:50] <sandjkirkland> apw: sorry I was on another channel. When this happens I have to hard reboot. Its so random that sometimes I go days without issues and other times its 4 or 5 times in an hour
[17:51] <apw> jdstrand, i wonder if that patch is simply not enough ...
[17:51] <ogasawara> jdstrand: please do.  has the situation improved with the patch?
[17:51] <jdstrand> ogasawara: hard to say. I'd like to say 'maybe?' it doesn't happen super frequently-- just a few times a day
[17:52] <sandjkirkland> There isn't anything particular that I do that causes it. I can be on interent or libreoffice
[17:53] <tgardner> ogasawara, have you pointed jdstrand at the 3.3 compat-wireless bits ?
[17:53] <ogasawara> tgardner: oh yah, no I haven't
[17:53] <tgardner> ogasawara, might be a good chance for some testing on it
[17:55] <ogasawara> jdstrand: we've uploaded the linux-backports-modules-3.2.0 package which contains an updated compat-wireless stack from v3.3, you might want to give that a spin
[17:56] <ogasawara> jdstrand: https://launchpad.net/ubuntu/precise/+package/linux-backports-modules-cw-3.3-3.2.0-18-generic
[17:57] <tgardner> jdstrand, use linux-backports-modules-cw-3.3-precise-generic
[17:59] <jdstrand> ok
[17:59] <jdstrand> I filed 948235 just now
[17:59] <ogasawara> jono: you're the original bug reporter for bug 911059 - have you noticed any further drops since running with the applied fix?
[17:59] <ubot2`> Launchpad bug 911059 in linux "Intel wireless randomly drops connection" [High,Fix released] https://launchpad.net/bugs/911059
[18:02] <apw> anyone got an oneiric box, if so could they pasteme the output of: grep -r AT_EMPTY_PATH /usr/include
[18:02] <jdstrand> tgardner: after installing that package, is all I have to do rmmod iwlwifi ; modprobe iwlwifi?
[18:03] <tgardner> jdstrand, nah, you'd better reboot since the protocol stack modules are also different
[18:03] <jdstrand> ok
[18:04] <herton> apw, /usr/include/linux/fcntl.h:#define AT_EMPTY_PATH		0x1000	/* Allow empty relative pathname */
[18:09] <apw> herton, thanks ...
[18:18] <GrueMaster> sconklin: Ping.  I got the meter working.  On the Dove, only the processor draws from 12v, so the amp readings were very low compared to the panda, which has a single feed for everything attached (including the USB>Sata SSD).
[18:19] <GrueMaster> And I have it working on the dev board I need to test, with viable results.
[18:19] <sconklin> GrueMaster: ok, if it's low enough, you should switch the leads over to the 400 mA jack, if you haven't already
[18:20] <sconklin> glad to hear it's working
[18:20] <GrueMaster> No, on the test platform, I can peg it out at 1.5A using lamp and ab.
[18:21] <GrueMaster> It is going to be near impossible to get a decent set of readings for system wide testing, but this will at least give me core readings.
[18:21] <sconklin> GrueMaster: ok, good deal!
[18:22] <GrueMaster> Now to start honing my python skills and write some tests.
[18:24] <apw> bug 944347
[18:24] <ubot2`> Launchpad bug 944347 in grub2 "linux and initrd load very slowly on UEFI system" [Critical,Confirmed] https://launchpad.net/bugs/944347
[18:31] <jono> ogasawara, sorry, was on a call
[18:31] <jono> nope, works perfectly - thanks!
[18:36] <apw> ogasawara, (without looking at all) i wonder if that fix is iwlNNN specific in some way, and actually more of those are affected
[18:44] <ogasawara> apw: I was thinking the same
[18:45] <ogasawara> apw: although jdstand is using the same driver as jono
[18:45] <apw> ogasawara, erp
[18:45] <ogasawara> apw: but jdstand mentioned in his bug that he ran with the upstream 3.3 kernel for a day without issue
[18:46] <ogasawara> apw: so lbm might be promising in his case
[18:58] <tgardner> ogasawara, I have a i4965 that really began to suck from from v2.6.39-v3.2. I've been running v3.3-rc4 and up for several weeks with really good results.
[19:16] <jsalisbury> jono, do you have the following options still enabled: options iwlwifi 11n_disable=1 swcrypto=1
[19:23] <jono> jsalisbury, I don't think so, where would I add those?
[19:25] <jsalisbury> jono, You may have created a file in /etc/modprobe.d.  In that directory, can you run:
[19:25] <jsalisbury> grep 11n_disable *
[19:26] <jono> jsalisbury, nothing is returned
[19:27] <jsalisbury> jono, cool.  And you rebooted since adding that option manually?
[19:27] <jsalisbury> jono, with insmod
[19:27] <jono> jsalisbury, yep, lots of times
[19:27] <jsalisbury> jono, ok, thanks.
[20:23] <ohsix> herton: re: the 2.6.38-13 kernel pushed a little while ago, i haven't seen a corresponding -dbgsym package in a while, am i misunderstanding their use?
[20:24] <ohsix> i think it's in -proposed, dunno if dbgsym stuff matches
[20:24] <herton> ohsix, which one is missing, I see the latest ones at http://ddebs.ubuntu.com/pool/main/l/linux/
[20:25] <ohsix> 2.6.38-13.57
[20:25] <ohsix> -generic
[20:26] <herton> it's there: http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-2.6.38-13-generic-dbgsym_2.6.38-13.57_amd64.ddeb
[20:26] <herton> i386 also
[20:26] <ohsix> they're .56 apparently, numbers are a little out of sequence, don't know the implication
[20:27] <ohsix> hmm it's not being marked for upgrade
[20:28] <ohsix> ok i'll try and get to the bottom of it, something is weird for sure
[20:28] <ohsix> thanks
[20:30] <herton> np, it should update if you have linux-image-2.6.38-13-generic-dbgsym installed already, may be there is something else
[20:31] <ohsix> i don't know why the version of dbgsym i had installed was -56, the kernel i had wasn't
[21:42] <ohsix> herton: the ddebs.ubuntu server won't bluff to you if you add it as a package source and do regular updates? (about 10 times a week, updating the package sources) i still only see .56 as the only available version (this is on 10.04)
[21:45] <herton> ohsix, yes, it's not taking 13.57 even if you add ddeb natty-proposed archive, I think you should open a bug about it
[21:46]  * tgardner -> EOD
[21:47] <ohsix> against what, i'm a bit fuzzy on what's even happening, if it's on the ddebs server it should come in an update
[21:48] <herton> I think it's an archive problem
[21:48] <ohsix> it's all moot, i can check and see if it unfubars itself tomorrow; not enough time to fetch it today
[21:49] <ohsix> thanks again for the info
[21:50] <ohsix> all that .deb just to get vmlinux; it would be a huge boon just to package it by itself, and in a place that perf can find it :] (i've been told it might have been fixed to find it in the regular debug spot on newer versions, but i haven't checked)
[21:52] <ohsix> in something that's not a -dbgsym package that is, i realize they're just built with normal packages and contained all the stripped stuff; something in the main repo with a vmlinux and the modules separate
[22:21] <sandjkirkland> I am having issues with my computer freezing and monitor going white with oneiric. This does is so randomly it is impossible for a newbie as myself to determine the issue.
[22:21] <ohsix> intel gpu? sandybridge or ivybridge? -> gpu asplode