/srv/irclogs.ubuntu.com/2010/06/22/#ubuntu-kernel.txt

psusiI've noticed that Ubuntu kernels use a lot more memory than mainline ppa builds... I've compared the output of free and ps aux on both and can see no substantial difference in the rss total in ps, but free -m reports 545mb more used ram under the Ubuntu kernel01:32
psusiare there some reporting files in /sys or /proc somewhere I can't find to get more information on kernel memory usage?01:32
jjohansenpsusi: /proc/slab/01:35
psusijjohansen, no such dir...01:35
jjohansenerr make that /proc/slabinfo01:35
psusiahh ;)01:35
psusinope, not there either01:35
jjohansenwhat kernel?01:36
psusi2.6.35-rc3+01:36
jjohansenhrmm, ubuntu or mainline01:36
psusimainline currently01:36
jjohansenI think its a config option01:36
psusiI built it with the config file taken from the current maverick kernel01:37
jjohansenpsusi: can you open a bug, and report the disparity01:37
psusiyea... I intend do, was just hoping for some advice on getting more info that could be helpful for the report01:37
jjohansenhrmm, okay I'll have a look once my maverick install is done01:37
jjohansen/proc/slabinfo should be there01:38
psusiI was just looking in the kernel documentation and found slabinfo.c...01:38
psusiseems useful... going to check ubuntu kernel...01:41
psusioh great... NOW it ISN'T hogging memory....01:44
psusiman it sure takes ages for the build farm to build the kernel... 3 hours and still going... iirc it takes me about an hour...02:11
=== ericm-Zzz is now known as ericm
keesogasawara, JFo: this bug report isn't very great, but I don't know what to say beyond what I've put here: 597075.  any ideas to help me debug this?03:04
ogasawarakees: hrm, removing quiet and splash help show anything like a panic?03:06
ogasawarakees: can you attach lspci from when you boot 2.6.34?03:07
=== jjohansen is now known as jjohansen-afk
psusijesus... the build farm is coming up on 5 hours compiling the kernel... what is it, a pentium-133? heh...03:54
keesogasawara: yeah, no panic, nothing.  on a normal boot, the framebuffer loads, clears the screen and nothing else ever happens.  if I break=top, I get an initramfs prompt and it hangs.04:40
keesogasawara: I've done a full apport-collect on that bug now.04:41
=== ricotz_ is now known as ricotz
* smb waves good morning to .*08:18
jk-smb! just the guy...08:18
ckingmorning smb08:18
jk-do you have an ETA for the alsa backports to hit -proposed ?08:18
smbjk-, Uh oh... :)08:18
jk-:)08:19
smbwhich ones that did not?08:19
jk-oh, an update has gone up?08:19
* jk- looks08:19
smbjk-, should be in proposed as you whished. :)08:20
smbIF you talking of Lucid of course08:20
smblinux-backports-modules-2.6.32 | 2.6.32-23.16 | lucid-proposed | source08:22
jk-smb: yep, Lucid08:22
jk-thanks :)08:22
smbjk-, NP. Actually the ALSA stuff was in -23.15 but it seems in minorly messed up and did not include the whole changelog since updates. :/08:24
slytherinOn powerpc, power management in gnome-power-manager does not work correctly without loading pmu_battery module. What can be done to make it work out of box?08:25
smbslytherin, Hm, is there any bus information / IDs that could be used in module alias definitions08:29
slytherinsmb: I don't know. I only know for sure this bug is affecting a lot of people and is open since karmic.08:29
smbThe usual way in the kernel would be to have something like this but that might be better answered by someone who actually is doing work on ppc08:31
slytherinbug 458004 has relevant info. I can do necessary testing on my ibook. But I don't know enough to try kernel changes myself.08:32
ubot2Launchpad bug 458004 in linux (Ubuntu) (and 1 other project) "gnome-power-manger does not work in karmic ppc (affects: 2) (heat: 27)" [Medium,Triaged] https://launchpad.net/bugs/45800408:32
krautmoin08:43
amitklag: nice overview of the suspend/resume debugging! :)08:49
amitklag: did you discuss this with upstream?08:49
lagamitk: Thank you08:49
lagamitk: I believe it has. It has been passed to Matt? @ -mm08:50
cooloneylag: your email is quite helpful, since i also got suspend/resume on fsl-imx5108:52
apwsmb, morning08:57
smbapw, morning08:59
slytherinsmb: Can you please take a look at the bug and comment on what the next step should be?09:00
* apw suspects it would be easier for him to do that if slytherin included bug #nnnn so that ubbotu could do her thing09:00
smbits above09:01
smbbut i cannot really comment on ppc09:01
slytherinShould I bug TheMuso then?09:03
apwslytherin, i would say its a lack of a module alias, but presumably there is a simple work around of adding modules to /etc/modules09:04
slytherinapw: There is. But users want power management to work out of box.09:05
slytherinSpecifically on laptops (ibook/powerbook etc).09:05
apwapple really should help the community to keep their laptops working shouldn't they09:06
slytherinThey did till OS X 10.5. Now there is no powerpc support.09:07
apwslytherin, thats apple for you, don't care about their customers once the kit is a year old09:08
slytherinAnyway, what I was looking for is what is the best way to make it work out of box in Ubuntu. Sine we already know which module is needed, what is the next step.09:08
apwslytherin, you need to work out what feature of the platform indicates that that module is needed09:09
apwthe module in the kernel has no load triggers.  there is no 'if this h/w exists you should load'09:09
slytherinHow do I go about that. As per comment in bug 458004, "To make DeviceKit see the battery, pmu_battery kernel module needs to be  loaded."09:11
ubot2Launchpad bug 458004 in linux (Ubuntu) (and 1 other project) "gnome-power-manger does not work in karmic ppc (affects: 2) (heat: 27)" [Medium,Triaged] https://launchpad.net/bugs/45800409:11
smbI was trying look a bit at the whole thing, but my problem is that I don't see a pmu_battery module at all on the only ppc machine I can access (ppc64 though). There are battery modules but also have no alias . The only other mchanism other that matchin dmi information09:15
smbwhich ppc does not have, would be bus ids, which batteries usually also not have09:15
smbSo probably some devicekit magic might be reasonable09:15
slytherinsmb: What kind of magic?09:26
smbslytherin, Well, find out that the machine you are running is a ppc. The problem is, and that should be answered by someone who really understand ppc. How do you decide which battery module should be loaded and when. As I saw on that ppc64 machine there is no pmu_battery modules provided (at least not for Karmic). So what should be loaded then. And when. 09:28
smbAnd when not09:28
slytherinI can't say I understand ppc. I will check if anyone in Debian knows what to do.09:29
apwslytherin, normally such a module has aliases to load based on the machine type, so you would need to find a computer readable identifier for the machine which has this, the equivalent of dmi-decode on x8609:30
apwyou can then tie the module to that existance.  you can tell if there is such a thing by 1) trying dmidecode, 2) looking at the udev logs to see if it fired an event for the device09:30
apwfor the battery09:30
slytherinWill it be sufficient to check difference between udev log when module is loaded vs not loaded.09:33
apwslytherin, nope, the event would have fired if it exists09:33
apwslytherin, the way auto loading works is that the kernel detects things in the machine and triggers uevents, those go to udev which tries to match modules to them and autoload them09:34
slytherinhmm09:34
apwto be loaded a module has to advertise it understands something, some h/w attribute so that the udev triggers it09:34
apwnow the module you want loaded doesn't do that so udev will never load it whether there is a trigger or not09:35
slytherinOk.09:35
apwso you need to look a tthe udev log and see what h/w triggers appeared and see if there is one for the specific machine type or better for the battery09:35
apwslytherin, i would advise adding the udev log to the bug09:36
slytherinDoing that right now. Please note that I have already loaded the module.09:37
jk-slytherin: and maybe poke around in /proc/device-tree to see if there's a directory that describes the battery ?09:37
slytherinjk-: http://paste.ubuntu.com/453282/09:44
slytherinapw: Added udev log to the bug.09:44
apwjk-, any idea what this means: MODALIAS=ssb:v4243id0812rev0509:48
apwslytherin, its probabally not very convienient, but it would be helpful if the log didn't have the battery autoloaded09:50
slytherinapw: Ok. Let me reboot without the module.09:50
=== ogra_ is now known as ogra
slytherinapw: Attached the udev log without module loaded. If there is any more info needed, let me know.10:01
* slytherin will be out for some time10:03
apwjk-, is there a machine identifier in of ?10:08
=== smb is now known as smb-afk
jk-apw: it should be in /proc/device-tree/model11:29
jk-it should contain something like PowerBook5,211:30
jk-IIRC11:30
=== smb-afk is now known as smb
BenCwow, you guys have a ToS for IRC now14:34
=== sconklin-gone is now known as sconklin
bjfmoin all14:53
JFomoin bjf14:59
JFoapw, this looks potentially important: bug 59625714:59
ubot2Launchpad bug 596257 in linux (Ubuntu) "MAJOR CRASH POSSIBLE: sysrq remains active with 2.6.35 (affects: 3) (heat: 18)" [Undecided,Confirmed] https://launchpad.net/bugs/59625714:59
JFohmm, they reference the patch that apparently fixes it15:03
simarBug 569122 . Please help regarding the triaging  ... Logs can help ..15:46
ubot2Launchpad bug 569122 in linux (Ubuntu) "Resuming from hibernation fails (video garbage with nouveau, no progress/hibernation with nvidia-current) (affects: 2) (dups: 1) (heat: 68)" [Medium,Confirmed] https://launchpad.net/bugs/56912215:46
tseliotmjg59: what would be the right place to look at if my dell laptop's Print key behaves like SysRq when I press "Alt+Print"?15:57
mjg59showkey on the console is the easiest15:59
tseliotright, I was thinking in terms of code16:01
tseliotmjg59: it gives me code 56 and 99, which is not SysRq16:06
tseliotshowkey -k, that is16:07
=== ericm_ is now known as ericm-Zzz
=== jjohansen-afk is now known as jjohansen
JFoogasawara, do you want me to tag config request bugs with a kconfig tag?16:22
JFoI saw that you did that on one16:22
* bjf is meeting the rest of the pdx mafia downtown, will be back online in a bit16:22
ogasawaraJFo: that's what I'd been using in the past16:24
JFocool16:24
JFoI can add that to the tagging wiki16:24
ogasawaraJFo: sounds good16:24
JFo:)16:24
tazzi have a x86_64 i5 processor, would it be possible for me to compile a i386 kernel ? 16:35
JFotgardner, what were the packages we wanted to add to bug metrics for the team meeting?16:50
JFoomap and what?16:50
* JFo forgets16:50
tgardnerti-omap4 ?16:50
tgardnerJFo, ^^16:50
JFoyeah, I have that one, wasn't there another?16:50
tgardnerJFo, was it in the notes from last week IRC meeting?16:51
JFothink it was in e-mail, but I can't find it now16:51
tgardner'cause I'm not really remembering what you're talking about16:51
JFoheh16:51
JFoyou were telling the guys you wanted a status during the meeting for 2 projects16:52
JFoand I only remember the one16:52
JFoI'm sure it was an e-mail you sent out16:52
tgardnerJFo, just looked through the notes. nothing is jumping out at me16:57
JFoah well16:57
JFoI'll add the omap and maybe someone will remember during the meeting for next week16:57
simarhello17:09
* bjf is back17:15
jjohansenbe back in 517:15
gnomefreaki have 2 bugs that seem to be the same (same error code and same problem) except they are not on the same version of kernel, one is 2.6.32-22 and the other is -2317:17
gnomefreakdoes that sound like the same? i can give bug numbers if you like17:17
gnomefreaksee bug 596557 and bug 59629317:22
ubot2Launchpad bug 596557 in grub2 (Ubuntu) "package linux-image-2.6.32-22-generic 2.6.32-22.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/59655717:22
ubot2Launchpad bug 596293 in grub2 (Ubuntu) "package linux-image-2.6.32-23-generic-pae 2.6.32-23.37 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 127 (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/59629317:22
manjocking, around ? 17:23
ckingmanjo, yep17:23
ckingwassup?17:24
manjocking, at the plugfest 17:24
ogragnomefreak, these are users that followed very likely the ubuntugeek blog and broke their /etc/default/grub file by copy pasting 17:24
ogragnomefreak, we have 100s of duplicates of that bug17:24
manjocking, you said you were able to boot iso on virtual box 17:24
manjowas that the one with the modified grub ?17:24
gnomefreakogra: ok thanks if i run into them i will mark them. Do you have a master bug #?17:24
ograthanks to the blog software ubuntugeek uses which replaces quotes qith double backticks17:24
JFodid the team meeting time change?17:24
bjfJFo, no why?17:25
ckingmanjo, I was mistaken - my UEFI flag got flipped back to non-UEFI17:25
JFojust looked odd to me17:25
JFomaybe I just had too much coffee this AM17:25
JFo:)17:25
bjfJFo, 35 minutes from now17:25
JFohmmm17:25
manjocking, ok so we don't know yet if the new isos work... ok so I will make copies of the livecd iso and hand those out17:26
ogragnomefreak, not from the top of my head, there is a guy (Jean-Baptiste Lallement) who did the collecting of these bugs for the last few weeks. i guess he has a master17:26
JFothe calendar shows it an hour and 35 from now bjf17:26
JFoso it did look funny to me17:26
gnomefreakogra: thanks17:26
JFowhoops17:26
JFonevermind bjf17:26
JFofigured out what it was17:27
ckingmanjo, well, may be worth trying it with one first before handing out a load17:27
manjocking, yeah I have tried the livecd at home 17:27
JFobjf, the KTeam cal hadn't loaded, so I was seeing the call on the Eng Cal17:27
manjothis is based on the iso that was prior last weekend 17:27
JFoheh17:27
manjoso last Thursday etc 17:27
ogasawaramanjo: any progress with the new firewire stack bits?  will it make Alpha 2?17:29
manjoogasawara, I sent out the patch to the ukml ... 17:29
ogasawaramanjo: right, just curious if it's been applied and uploaded17:30
manjotgardner, ^^ ?17:30
ogasawaramanjo: I assume the second work item "add basic tests to kernel-qa to test new firewire stack." will slip to Alpha3?17:30
manjoogasawara, yeah unfortunately I am out this week.. so next week I will be able to add some 17:31
ckingmanjo, looks like you may need to "wing it" a bit then17:31
ogasawaramanjo: the tests aren't A2 release critical so I'll reset it to the A3 milestone17:32
manjoogasawara, sure 17:33
manjoogasawara, tests are not even part of the OS so its ok to slip I think 17:33
ogasawaramanjo: ack17:33
manjocking, intel just asked me if I have any server isos17:34
manjocking, :) 17:34
ckingnot today17:34
ckingmanjo, suppose it's not out of the question is it?17:35
manjocking, yeah they wanted us to show case the cloud stuff... 17:35
manjocking there is another plugfest in October 13-15 Taipei17:35
ckingmanjo, nothing like being put on the spot17:35
ckingNow that sounds like a good opportunity17:36
manjocking, we should get someone out there for that one with maverick desktop & servers17:36
manjocking, 2.2TB HDD looks like a big new thing that EFI supports and there is seagate & WD here with 2.2 drivers 17:36
manjodrives17:36
ckingmanjo, agree - want to forward the details of the Taipei plugfest to hugh and me?17:37
manjocking, will do17:37
ckingcheers17:37
bjf##17:43
bjf## Kernel team meeting in 20 minutes17:43
bjf##17:43
bjf##17:56
bjf## Kernel team meeting in 5 minutes17:56
bjf##17:56
manjobjf, I won't make it to the meeting 18:03
=== sconklin is now known as sconklin-lunch
slangasekapw: hi, I have a stack of issues with the ti-omap4 kernel packages that I'm trying to unwind; the first is that I can't clone git from the documented URL :)18:32
tgardnerslangasek, git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git18:35
slangasektgardner, apw: so here are the main lintian problems that I'm concerned about in the ti-omap4 package:18:38
slangasekW: linux-image-2.6.34-900-omap4: postrm-does-not-purge-debconf18:38
slangasekW: linux-image-2.6.34-900-omap4: missing-debconf-dependency-for-preinst18:38
slangasekthere's also a lot of changelog noise which probably just needs some tuning to whatever script generates those18:38
slangasekthe postrm stuff ought to be fixable by making sure the maint script has a #DEBHELPER# token in it18:39
slangasekassuming you're using debhelper in debian/rules... which I hope you are :)18:40
slangasekthe lintian warning wouldn't be there if you're not using debconf18:41
apwslangasek, ok thanks .... hrm18:42
slangasekapw: debian/control-scripts/preinst - inherited from kernel-package, blaaah18:43
apwsee we get to blame debian :)18:44
slangasekheh18:45
apwi see all the debian kernels have the same warnings ... whee18:48
* apw cries at how slow lintian is on a kernle package18:49
slangasekick18:49
apwproduce some output dammit18:52
apwno really i'd love to know your oppinion on my package, today18:54
ckingpatience is a virtual, apparently, but I've never gotten around to prove it.18:55
apwFINALLY18:55
apwslangasek, is there a way to say some warnings are wrong?18:55
apwW: linux source: native-package-with-dash-version18:55
apwW: linux source: changelog-should-mention-nmu18:55
apwits not clear we can avoid either of those18:56
apwW: linux-image-2.6.35-5-generic: windows-devel-file-in-package lib/firmware/2.6.35-5-generic/korg/k1212.dsp18:56
apwor indeed that one18:56
slangasekapw: yes, lintian overrides - I agree those should be overridden18:57
slangasekI think the lintian manpage documents how to declare overrides18:57
apwslangasek, yep found it, will get those added and get the others on the list to squash18:59
JFobjf, you want that ftraceable bugs item on the arsenal BP?19:01
bjfJFo, we were maintaining a wiki page with arsenal todo items on it, that's where it should go so we don't loose track of it19:02
JFok19:03
* JFo goes to look for the page19:03
JFohmmm, bjf do you have the link handy?19:04
JFoI apparently don't have it bookmarked and my wiki search fu is weak today19:04
bjfJFo, damn, i just knew you were going to ask... now i've got to go hunt for it :-)19:04
JFoheh19:04
bjfHA! too easy ... http://wiki.canonical.com/Kernel/Arsenal19:05
JFonice19:06
JFohmmm19:06
JFobjf, you big kidder19:07
JFoI suppose that means you want me to create it :-P19:07
bjfJFo, just a sec19:07
JFok19:07
JFo:)19:07
bjfhttps://wiki.ubuntu.com/Kernel/Arsenal19:07
bjfuser error19:08
JFocool19:08
* tgardner lunches19:08
JFocnd, do you think it would be possible for you to give me some ideas on what bugs you want to see in the 'ftraceable bugs'?19:13
JFoI suspect this is something where you want us to identify them and then ask them to do a specific set of commands19:13
JFoto provide the output to the bug19:13
apwslangasek, i am not seeing any whinges about our changelog format, have you an example19:20
slangasekapw: in the ti-omap4 package: W: linux-image-2.6.34-900-omap4: debian-changelog-line-too-long line 3119:24
apwslangasek, thanks19:25
JFoapw, do you see a use-case for mainline -server kernel builds?19:36
JFosomeone is asking about them in a bug19:37
apwi don't know of any, do they have one?19:37
tgardnerabout the only differenxces are HZ and def scheduler and I/O settings19:37
JFoit made me wonder if it were something worthwhile for us to build as an unsupported test case for server users19:38
shadeslayerhi,can someone look at 59304119:39
shadeslayerbug 59304119:39
ubot2Launchpad bug 593041 in linux (Ubuntu) "New 2.6.35 kernel keeps toggling bluetooth radio (affects: 1) (heat: 6)" [Undecided,Triaged] https://launchpad.net/bugs/59304119:39
shadeslayerits getting worse with each kernel upgrade :P19:39
jjohansenwhat is the magic url for opening bugs again?19:39
JFo+filebug iirc jjohansen 19:40
* JFo checks19:40
ogasawarajjohansen: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+filebug19:40
tgardnerhttps://bugs.edge.launchpad.net/ubuntu/+filebug19:40
jjohansenthanks19:40
* JFo ticks a point19:40
JFo;)19:40
jjohansen-> rebooting and then switching venues19:52
apw$ lintian linux_2.6.35-5.7.dsc19:56
apwN: 2 tags overridden (2 warnings)19:56
apw$19:57
apwbetter me think19:57
tgardnerogasawara, Maverick git URLs in LP bugs become invalid the next time you rebase20:20
tgardnerhttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/594382/comments/820:21
ubot2Launchpad bug 594382 in linux (Ubuntu Maverick) (and 1 other project) "Wake up daisy chain activation failed on omap3 (affects: 1) (heat: 8)" [Critical,Fix committed]20:21
ogasawaratgardner: bah, you're right20:22
tgardnerogasawara, that particular commit also has a bogus buglink, I emailed you about it.20:23
ogasawaratgardner: I'll fix that up20:24
=== sconklin-lunch is now known as sconklin
AzelphurHi, i keep getting an issue with my pc which i think is to do with kernel usb support, my keyboard/mouse will randomly start going very slowly, keystrokes arrive very slowly and often in the wrong order or not at all, mouse position seems to update twice a second, i tried replugging my keyboard, it took 3 minutes to be powered up again20:54
Azelphuri can only solve the issue by restarting my pc, restarting X does not solve it20:54
Azelphurand it happens seemingly at random20:55
Azelphurrunning 10.04 64bit20:55
ogasawaratgardner: was trying to schroot into maverick-armel on tangerine, but get the following error21:05
ogasawaratgardner: $ schroot -c maverick-armel21:05
ogasawarammap: Operation not permitted21:05
ogasawaratgardner: no hurry on needing to get it fixed, was just testing if I could use the chroot to do a test build21:06
* ogasawara lunch21:08
tgardnerogasawara, ack, looking into it21:14
keesogasawara: your mmap_min_addr is too high.  install qemu-kvm-extras-static21:16
tgardnerkees, rtg@tangerine:~$ dpkg -l|grep qemu21:17
tgardnerii  qemu-kvm-extras-static          0.12.3+noroms-0ubuntu9            static QEMU user mode emulation binaries21:17
keeshm, check /etc/sysctl.d/ ?  do you have 30-qemu-kvm-extras-static.conf ?21:17
tgardnerkees, yep21:18
tgardnervm.mmap_min_addr = 409721:18
keeswhat does   cat /proc/sys/vm/mmap_min_addr 21:18
keessay?21:18
tgardner6553621:19
keessounds like qemu-kvm-extras-static's packaging doesn't reload sysctl correctly.21:19
keessudo service procps start    shoudl fix it21:19
tgardner409721:19
keesnow the schroot should work21:20
tgardnerkees, success!21:20
kees\o/21:20
tgardnerkees, so, basically you need a reboot after installing qemu-kvm-extras-static.21:20
keesno, qemu-kvm-extras-static needs to call "start procps" in its postinst21:21
tgardnerkees, I saw this on one other machine after a fresh install, so I think you're right21:21
keestgardner: open a bug, should be a really easy fix for hallyn :)21:22
tgardnerkees, doing so as we speak21:22
tgardnerkees, its got this:21:23
tgardner# apply /etc/sysctl.d settings21:23
tgardnerif [ "$1" = configure ]; then21:23
tgardner    invoke-rc.d procps start21:23
tgardnerfi21:23
keesinvoke-rc.d is wrong.  :)21:25
tgardnerkees, so, change it to 'service procps start' ?21:25
keesthe whole line should be "start procps"   (upstart fully broke invoke-rc.d, which was always wrong, iiuc)21:25
keesyeah, "service procps start" is more portable (to Debian) than just "start procs" but both will worki.21:26
tgardnerogasawara, tangerine armel schroot issue fixed thanks to kees21:39
bguthroIs anyone here particularly versed on the i915 driver?21:39
bguthroI've got a Dell Latitude E6410, that when switched to an external VGA display at the BIOS, will come up properly...but if left to its own devices, never displays on the LVDS connector21:40
slangasekkees: nooooooooo21:41
keesslangasek: ?21:41
bguthrolspci looks like its the "Ironlake" chip, referred to in drivers/gpu/drm/i91521:41
keesslangasek: but invoke-rc.d doesn't work...21:42
keesO_o21:42
keestgardner: everything I said about invoke-rc.d is wrong.21:42
keestgardner: something is still wrong in the qemu-... package though21:43
tgardnerI'm getting that. how come?21:43
keesit looks like invoke-rc.d still works, and slangasek is trying to reach across the table here to hurt me21:43
slangasektgardner: invoke-rc.d is still the only suitable interface for use in maintainer scripts.  Keybuk doesn't want this to be the interface for upstart jobs, but hasn't implemented its replacement yet21:43
keestgardner: but something still didn't actually fire procps after qemu... installed.21:43
slangasekif there are any cases where invoke-rc.d currently fails, we should fix that instead of calling a different command21:44
tgardnerkees, exactly21:44
keesslangasek: this has been a problem in other packages (wine) too.21:46
slangasektgardner: was there any output in the dpkg log?21:46
slangasekthen we shall fix it! :)21:46
tgardnerslangasek, where is the dpkg log?21:47
slangasektgardner: /var/log/dpkg.log21:47
tgardnernm21:47
slangasekactually, /var/log/apt/term.log is more useful21:47
tgardnerkees, slangasek:21:48
tgardnerSelecting previously deselected package qemu-kvm-extras-static.^M21:48
tgardnerUnpacking qemu-kvm-extras-static (from .../qemu-kvm-extras-static_0.12.3+noroms-0ubuntu9_amd64.deb) ...^M21:48
tgardnerProcessing triggers for man-db ...^M21:48
tgardnerProcessing triggers for ureadahead ...^M21:48
tgardnerSetting up binfmt-support (1.2.18) ...^M21:48
tgardner * Enabling additional executable binary formats binfmt-support^M21:48
tgardner   ...done.^M21:48
tgardner^M21:48
tgardnerSetting up qemu-kvm-extras-static (0.12.3+noroms-0ubuntu9) ...^M21:48
tgardnerupdate-binfmts: warning: /var/lib/binfmts/arm does not exist; nothing to do! ^M21:48
tgardnerprocps stop/waiting^M21:48
tgardner^M21:48
tgardnerLog ended: 2010-06-19  15:11:2021:49
tgardnerI see that procps _was_ restarted21:49
* kees scratches his head21:49
* kees tries to reproduce locally21:50
* slangasek nods21:51
keesworked correctly for me.  :(21:52
tgardnerkees, me too. huh. the failure was on a 64 CPU machine. timing?21:53
keesO_o uhm21:53
tgardnerkees, I can try it on that machine.21:53
keesbasically, installing and purging qemu-kvm-extras-static each time it should change /proc/sys/vm/mmap_min_addr21:54
tgardnerkees, dang, it worked that time. I purged and restored /proc/sys/vm/mmap_min_addr to 64K, then reinstalled.21:56
keestgardner: purging should restore mmap_min_addr on it's own (due to /etc/sysctl.d/10-zeropage.conf)21:57
tgardnerkees, I didn't actually check first21:58
slangasekand there's a bug in the postrm, purge will fail if the procps package has been uninstalled :)21:59
tgardnerkees, slangasek: well, I'm gonna let you wizards deal with it. Its EOD for me.22:00
keesif procps has been uninstalled I won't debug that system.  :)22:00
keestgardner: cool, thanks.  weirdness.22:01
tgardnerkees, non-sequitur, I think it should be YAMAC (Yet Another Mandantory Access Control) LVM22:01
keesit's not a MAC!  :)  It's a NAC.   NAKed Access Control system22:02
tgardnermaybe this attempt will get some traction22:02
kamaljjohansen: ping22:20
jjohansenkamal: pong22:21
kamalis the atop patch being considered for lucid kernel, or just maverick?  (I have it working in lucid with just one tiny change)22:21
jjohansenmaverick22:21
jjohansenit isn't something we will sru22:22
kamalthat was my guess (but was easier for me to test / play with in lucid :)   ok, I'll check applying it to maverick.22:22
jjohansenyeah, completely understood.  I had considered that too22:23
bjfJFo, around?23:18
stentenFor bug reports, what subsystem are Oopses under? kernel-core?23:43
ogasawarastenten: if you're not sure which subsystem the oops is coming from I'd use kernel-uncat23:46
ogasawarastenten: we review those weekly and it'll then get shuffled to the right category23:46
stentenogasawara: ok, thanks!23:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!