[01:26] <linuxR> hello, I discover total system freezes when working with eclipse (ubuntu 12.04 with all updates installed). can someone help me to analyze this? thanks
[07:50] <ppisati> moin
[07:56] <apw> ppisati, niu
[07:58]  * smb moans
[09:02] <linuxR> Hi. I experience system freezes in context of intel video and kernel 3.2.0-54-generic (kernel log: [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 00070000, was 16000000 freeze) ... is this problem being worked on? I think it possibly affects a large number of users
[09:17] <apw> linuxR, is there a bug filed?
[09:18] <apw> and what is the symptom ofther than the report in dmesg
[09:20] <linuxR> apw, the symptom is a complete system crash (not just X server)
[09:23] <linuxR> I think there's a number of bugs related to this: 1194329 , 1168467, http://ubuntuforums.org/showthread.php?t=2135522
[09:23] <apw> bug #1194329, bug #1168467
[09:23] <apw> OI ubot2`,
[09:24] <linuxR> it seems to be a kernel problem introduced with 3.2.0-40
[09:25] <apw> linuxR, is it easy to reproduce for you ?
[09:27] <linuxR> apw, yes. I just need to open a few files in "eclipse" and switch tabs between these files...and boom it goes
[09:27] <apw> linuxR, those errors in other bugs seems to be non-fatal, at least from a running point of view
[09:27] <apw> linuxR, so it is not clear that those error messages are relevant or not
[09:28] <apw> linuxR, therefore, as you have an easy way to reproduce it, then the right thing for you to do
[09:30] <apw> linuxR, is to file a bug from your system, and then we can get a proper bisection started for it
[09:30] <linuxR> okay, I will open a bug
[09:31] <linuxR> I'd be glad to provide further anaylsis when someone can guide me through
[09:31] <apw> get the bug filed, and then lets get a run of 3.2.0-40.64 and 3.2.0-41.65 to confirm the first one is good and second one is bad
[09:32] <apw> https://launchpad.net/ubuntu/precise/+source/linux/3.2.0-41.65
[09:32] <apw> https://launchpad.net/ubuntu/precise/+source/linux/3.2.0-40.64
[09:45] <linuxR> apw, can I just install all these kernels along each other? how can I select one for boot?
[09:49] <jpds> linuxR: In GRUB.
[09:55] <apw> linuxR, yes you can have many kernels installed they should all appear in grub menus
[09:59] <linuxR> can I just instal older kernels with apt?
[10:00] <linuxR> you referred to a source package?
[10:02] <smb> linuxR, you use "dpkg -i *.deb" with those
[10:03] <linuxR> smb, but then I'd have to configure/compile it myself?
[10:03] <smb> linuxR, And if you comment out the hidden grub variables in /etc/default/grub and run update-grub you will get a visible selection screen without having to press left-shift
[10:04] <smb> linuxR, apw did point to the lp page which has the source but also the build deb packages
[10:05] <apw> linuxR, as smb says, lower down on the pager are per build pages, which one you need depends on your machine
[10:05] <smb> You will need linux-headers...*all.deb, linux headers i386 or amd64 (depedns on what you got installed) the linux-image for that and linux-image-extra if that exists
[10:06] <linuxR> okay, will try that, thanks
[10:07] <smb> linuxR, Btw, the all headers is in the i386 build only
[10:09] <linuxR> would it not be a good idea to also try a current kernel (e.g. 3.8) and see if the problem was maybe fixed already?
[10:11] <apw> linuxR, you can do that if you wish indeed.  if we want to find the commit which broke it though (which is the easiest way to find out what fixed it later if it is fixed) is to prove the pair of kernels which bracket the breakage
[10:11] <apw> as then we can bisect to find the actual failing patch
[10:11] <apw> linuxR, when you have a bug, can we have the bug number please
[10:12] <ppisati> brb
[10:30] <linuxR> apw, the bug is: https://bugs.launchpad.net/ubuntu/+bug/1233086 
[10:30] <ubot2`> linuxR: Error: launchpad bug 1233086 not found
[10:31] <apw> linuxR, did you file that as a security issue or something?  as it seems to be 'hidden' (assuming you got the bug # right)
[10:31] <linuxR> apw, yes...this is security-relevant, isnt it?
[10:31] <linuxR> should I disclose it?
[10:31] <apw> linuxR, i thought your machine was crashing ?
[10:32] <linuxR> apw, thats correct. Thats why I thought this could possibly be exploited
[10:33] <apw> local only though, so not really any more exploitable than any other crasher or oops imo, but your call
[10:34] <apw> if its a security issue only the security team can see it
[10:34] <linuxR> I'll change that asap
[10:36] <linuxR> https://bugs.launchpad.net/ubuntu/+bug/1233086
[10:39] <apw> linuxR, ok i have put a summary of our discussion on IRC on there, and subscribed our defect analyst who can help with the bisection once you have a pair of kernels where it appeared
[10:40] <apw> linuxR, if you discover an old kernel which it does not appear in, then we have a regression so let me know if you find one
[10:42] <linuxR> apw, yes that would be the next steps to do. I'll give an update as soon as I have tested this with other kernels.
[12:18] <linuxR> apw, ok I'm ready to install and try the other kernels..but I have difficulties to determine the exact package name to install
[12:19] <linuxR> can you give me a hint?
[12:20] <linuxR> apt-cache search 3.2.0-40 yields 34 packages
[12:21] <linuxR> linux-image-3.2.0-40-generic. is that the correct one?
[12:26] <apw> linuxR, smb listed the exact ones to download 
[12:26] <smb> linuxR, You probably need 4. uname -m will tell you whether amd64 or i386, uname -r would tell you which flavour but very likely generic. Then
[12:27] <smb> i386 build: linux-headers-3.2.0-40_3.2.0-40.64_all.deb 
[12:28] <smb> linux-headers-3.2.0-40-<flavour>_3.2.0-40.64_<arch>.deb
[12:28] <smb> linux-image-3.2.0-40-<flavour>_3.2.0-40.64_<arch>.deb 
[12:28] <smb> linux-image-extra-3.2.0-40-<flavour>_3.2.0-40.64_<arch>.deb 
[12:31] <linuxR> okay, thanks. since I'm going to reboot now, I could trigger the freeze again. Is there any additional information I could get from this?
[12:49] <ppisati> apw: i was wrong, qemu doesn't emulate the virtualization extension, so we need real hw
[12:49] <ppisati> smb: ^
[12:50] <apw> ppisati, that is a bit of a shitter
[12:50] <smb> ppisati, Ok, but yeah would have been nice...
[12:50] <ppisati> apw: either calxeda ecx2000 or samsung exynos5
[12:50] <apw> ppisati, i guess we can use the 'fast' model
[12:53] <ppisati> apw: you mean the arm provided simulator?
[12:53] <ppisati> apw: could be, never tried
[12:55] <smb> henrix, would ext4 issues on online-resizefs related to set_flexbg_block_bitmap trigger any ringing bells on pending stable updates? (apparently in 3.8 but not 3.5 which maybe makes it SEP)
[12:57] <henrix> smb: i don't remember seeing anything related with that, but let me have a look
[12:57] <henrix> smb: do you have a link, sha1, ... ?
[12:57] <smb> henrix, I only saw some inode count overflow things
[12:57] <smb> henrix, https://bugs.launchpad.net/ubuntu/+bug/1233086
[12:58] <smb> err
[12:58] <smb> henrix, wrong number orry
[12:58] <smb> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075
[12:58] <henrix> smb: heh, i thought so :)
[12:59] <smb> henrix, Hm, though who knows maybe it is related to counts as the grow is large
[13:00] <henrix> smb: yeah, from < 3G to 2TB... that's a huge resize :)
[13:02] <smb> henrix, Apparently it did work in Q. I already asked to try raring release and S to narrow things a bit
[13:04] <linuxR> apw, smb : I could not find the additonal kernel in the grub boot menu, although the installation script reported that grub configuration would have been updated..ideas?
[13:05] <smb> linuxR, Did you look under "advanced options" or so?
[13:05] <apw> linuxR, what menu options _did_ you have
[13:05] <smb> The older kernels get sorted in there (the naming is a bit .. unhelpful)
[13:06] <henrix> smb: do you have any idea on the kernel version where this issue was seen?
[13:06] <linuxR> apw, just the current kernel (3.2.0-54-generic)
[13:06] <smb> henrix, Well, just "latest from today" for R
[13:07] <henrix> smb: ah, ok. i was looking at 3f8a6411fbada1fa482276591e037f3b1adcf55b but this is already in R for some time
[13:08] <linuxR> i'll ckeck again
[13:08] <smb> linuxR, The advanced menu does not show any kernel versions nitially
[13:08] <smb> just when selecting it
[13:09] <apw> linuxR, yeah "ubuntu" boots direct and "ubuntu advanced" is a menu
[13:09] <apw> it is most ... interesting semantics wise
[13:09] <linuxR> i'll check..thx
[14:29] <rtg> apw, pushed -rc3 rebase. thanks for the overlayfs fixes.
[14:30] <apw> rtg, np
[14:30] <caribou> apw: FYI, the mempolicy bug number is 1233175
[14:31] <caribou> apw: bug: #1233175
[14:31]  * apw pokes ubot2` in the eye
[14:31] <xnox> rtg: goldfish kernel now boot fine, had to fix up qemu =)
[14:31] <caribou> apw: :)
[14:31] <rtg> xnox, cool
[14:31] <xnox> rtg: (armhf that is, haven't started on x86 yet)
[14:32] <caribou> apw: one interesting fact about this one is that servers running lucid with similar workload *do* *not* show this behavior
[14:32] <apw> caribou, did you manage to repro it ?
[14:32] <caribou> apw: no, not yet
[14:32] <caribou> apw: but I was looking at Lucid's __mpol_put() and it is sensibly simpler
[14:33] <apw> caribou, t
[14:33] <apw> caribou, there is even less locking in lucid than in precise, i a supprised it is not worse
[14:34] <caribou> apw: nm, they're both the same :-/
[14:35] <apw> caribou, well there is a task lock round it in precise, which would likel change timing, perhaps it makes things more likely
[14:38] <ppisati> apw: it seems we need a license to get the RTSM
[14:38] <ppisati> apw: so no luck
[14:38] <diwic> Read The Sucking Manual ?
[14:39] <ppisati> Real-Time System Model
[14:39] <ppisati> "RTSMs are simulation models of ARM Hardware Platforms..."
[14:39] <ppisati> etcetc
[14:39] <diwic> ok
[14:53] <linuxR> apw, smb : I'm working on  3.2.0-40-generic now for some hours, have not been able to trigger the error again since
[14:54] <linuxR> still see the " [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy" message in kernel log..possibly unrelated to the freeze problem
[15:03]  * ppisati goes out for a bit
[15:05] <apw> linuxR, that is as waht i suspected might happen, so now you need to step forward to the next version and see if it breaks, and keeps doing that till it does,
[15:08] <riso64bit> hello
[15:11] <jsalisbury> linuxR, I can help you with the bisect.  I'm going to post some comments and kernels to test in the bug.
[15:17] <caribou> Is it possible to 'simulate' a NUMA architecture on a KVM virtual machine using non-NUMA hardware ?
[15:17] <apw> riso64bit, welcome
[15:18] <apw> caribou, hmm it might be, but not something i have ever tried, and you won't get the real effects clearly if you don't have a real numa under the hood
[15:18] <caribou> apw: I just want to exercise the numa-aware code using numactl
[15:19] <riso64bit> i have a problem whit the driver of touchpad on HPMini 210 & I have already open a ticket on launchpad (_https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188965) but Christopher M. Penalver (penalvch) write me to contact the Driver manteiner for help to fix the problem (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188965/comments/95).Yesterday i have sent the mail but i don't have received any 
[15:19] <riso64bit> response and so I don't now if i have made the right procedure.
[15:19] <apw> caribou, not sure is my best answer then :)  smb might have played so
[15:19] <riso64bit> sorry i'm not English
[15:19] <riso64bit> :D
[15:19] <caribou> apw: ok, I'll try to ping him, thanks
[15:20] <smb> apw, caribou Not exactly numa. Its possible to define the layout through libvirt cores/threads/cpu ...
[15:21] <apw> it might be enough to be usable for caribou's purposes then
[15:21] <caribou> smb: yep, I did that
[15:21] <caribou> ok, I'll dig that out, thanks
[15:21] <smb> Yeah, probably if two sockets automatically means NUMA like
[15:22] <apw> riso64bit, i'd not be expecting a response necessarily very quickly one doesn't even know if they are 'at work' any particular day
[15:23] <riso64bit> yes i know, but i don't know if i have made the right procedure :D
[15:25] <apw> riso64bit, there is little correct proceedure with upstream, other than donning a fire proof suit before emailing
[15:25] <smb> caribou, There seems to be -numa for kvm... Question is whether and if how libvirt would do things. But you should be able to look for the qemu process that gets started
[15:26] <caribou> smb: oh, thanks I'll check that out
[15:27] <riso64bit> ok, i will wait. 
[15:36] <smb> caribou, Hm, maybe if you hand tune the xml through virsh (see http://www.libvirt.org/formatdomain.html#elementsCPU)
[15:37] <caribou> smb: that looks good :<numa><cell... maybe what I'm after
[15:38] <caribou> smb: thanks
[16:43] <apw> ppisati, do you get any spinning irg/* processses on your omap4 with -generic
[16:48] <ppisati> apw: not that i recall
[16:48] <apw>    76 root     -51   0     0    0    0 S  24.8  0.0   1188:03 irq/88-48070000                                          
[16:48] <apw>    84 root     -51   0     0    0    0 R  23.1  0.0   1134:30 irq/151-twl6040                                          
[16:49] <apw> ppisati, ^
[16:50] <ppisati> apw: let me setup my board
[16:50] <apw> ppisati, i am going to try rebooting it to see if it is transient, i did get an L3 error over the weekend
[16:52] <apw> ppisati, yeah things look a lot better following a reboot, i wonder if the L3 error handler did not clean up right
[17:10] <apw> tjaalton, hey ... this 2 minutes to get dash thing with atoms and similar, are we expecting to do anything with ti
[17:11] <apw> tjaalton, bug #1222602
[17:19] <tjaalton> apw: still no word from upstream, but maybe the change could be reverted or make it so that for gen3 it forces the opengl version to 1.4
[17:20] <apw> tjaalton, either sounds appealing over where we are
[17:20] <tjaalton> heh, sure
[17:20] <apw> tjaalton, though i will say =1.4 does not make dash pretty, if appearing same day
[17:25] <tjaalton> with the workaround?
[17:26] <apw> tjaalton, yeah with the workaround the dash is not the right colours so teh gallback is not working quite right
[17:26] <Sarvatt> apw: can you run driconf and pastebinit the ~/.drirc it creates?
[17:27] <apw> Sarvatt, with or without the workaround
[17:27] <Sarvatt> doesn't matter
[17:27] <tjaalton> hmm ok
[17:27] <tjaalton> well force it to whatever it was before :)
[17:27] <apw> Floating point exception (core dumped)
[17:28] <apw> quality s/w
[17:28] <Sarvatt> hah
[17:28] <Sarvatt> apw: ah nevermind, they ripped out the options completely
[17:29] <apw> Sarvatt, Floating point exception (core dumped)
[17:29] <apw> arse
[17:29] <Sarvatt> tjaalton: thats pretty damn safe to just revert
[17:29] <apw> Sarvatt, http://paste.ubuntu.com/6176427/
[17:30] <Sarvatt> apw: sorry about that, I didn't see that they ripped out the options that forced it to 2.1 completely so they aren't in there to disable
[17:30] <apw> Sarvatt, heh
[17:34] <tjaalton> Sarvatt: ok then.. still would be good to know what upstream was thinking.. :/
[17:34]  * apw seculates ... la la la hasn't that shit h/w died yet ?
[17:34] <tjaalton> Sarvatt: was it idr?
[17:34] <Sarvatt> i915g supports it and we dont give a crap about i915 anymore, lets just do it
[17:35] <Sarvatt> whipping up a patch to revert it now, files got shuffled around a bit
[17:35] <tjaalton> well i guess it allows the hw to pass a few piglit tests more, even if they take an eternity to run :)
[17:36] <tjaalton> ^ motivation
[17:47] <Sarvatt> tjaalton: ok to push this to git? http://paste.ubuntu.com/6176506/
[17:48] <apw> Sarvatt, if you have some binaries to test, i am happy to do so
[17:48] <Sarvatt> sure thing, i'll throw it in a ppa
[17:49] <tjaalton> Sarvatt: yup go ahead
[17:51] <Sarvatt> oh nice, i already have a ppa named apw :)
[17:51] <apw> Sarvatt, :)
[17:51] <Sarvatt> apw: its uploading to https://launchpad.net/~sarvatt/+archive/apw now, should be about 45 minutes till its built
[17:52] <apw> Sarvatt, will watch out for it
[17:52] <apw> Sarvatt, 'maverick' packages ... an old one
[17:53] <Sarvatt> 148 weeks, wonder what it was about
[17:53] <Sarvatt> ahh right, actually sandybridge acceleration for 10.10 where it was disabled in the archive
[17:55] <Sarvatt> dang, 38 minute builder queue even at urgency=critical
[18:04] <apw> Sarvatt, i'll slurp it down and try a local build then
[18:04] <Sarvatt> apw: amd64 machine?
[18:05] <Sarvatt> if you have multiarch mesa installed thats gonna be a headache and dont bother
[18:05] <apw> Sarvatt, this is a 32 bit atom, so i think not
[18:05] <apw> Sarvatt, and by local i mean a builder build on my kernel builder
[18:30] <apw> Sarvatt, that FTBFS for me
[18:31] <tjaalton> log?
[18:32] <apw> tjaalton, http://paste.ubuntu.com/6176677/
[18:36] <apw> Sarvatt, doesn't that need like {} round the case 3: contents if you have variables in it
[19:04] <rkrishna> Hi, I am getting error "unable to handle kernel paging request" trying to install a video capture card, any ideas?
[20:53] <Sarvatt> apw: its built in the ppa, sorry about all that
[21:10] <linuxR> apw, jsalisbury: I tried to track down the error to a specific kernel version. I thought 3.4.42 was stable (working for multiple hours) ;tried 3.4.44 which crashed few minutes after boot, then tried 3.4.42 again which then also crashed almost instantly. Any ideas?
[21:55]  * rtg -> EOD