/srv/irclogs.ubuntu.com/2008/11/06/#ubuntu-kernel.txt

=== asac_ is now known as asac
BenCmjg59: well it stops if I kill acpid (and it happens even at the terminal without X running)00:36
BenCmjg59: Actually, I should have answered "no" since I get two actual keyboard events if acpid is running00:37
BenCmjg59: noticed by running showkeys00:38
cathyalHi03:24
cathyalis the ubuntu kernel based off the debian kernel03:24
TheMusocathyal: No.03:45
cathyalfigures03:47
=== rametux is now known as RameTux
=== rametux_ is now known as RameTux
CarlFKI can cause a kernel panic - what's the app I run to help with the bug report?06:25
=== thegodfather is now known as fabbione
=== rametux is now known as RameTux
=== rametux_ is now known as RameTux
=== rametux_ is now known as RameTux
=== Keybuk_ is now known as Keybuk
Kanohi, did you know about the new ndiswrapper problem: http://www.mail-archive.com/frugalware-git@frugalware.org/msg22366.html13:07
Kanoi see no fix for that in 8.17, or do i miss something?13:08
rtgKano: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=fb54a3e61f44d37b07426f2e7a86d7ca0a99e90a13:18
Kanook, thanks13:23
NCommandersmb_tp, thanks! (I saw your email)13:44
Kanortg: will you do a 2.6.28 test git soon?13:44
rtgKano: soon, being sometime in the next few weeks.13:46
=== rametux is now known as RameTux
CarlFK"kerneloops is a daemon that collects kernel crash information..."  does that include panic ?14:54
rtgan oops is a panic. 14:55
CarlFKneat.  it's magic. :)14:55
CarlFKI am guessing I have to do something?  kerneloops.org is not loading 14:56
rtgamitk is out kerneloops expert14:57
rtgs/out/our/14:57
amitkCarlFK: once you isntalled kerneloops, a gnome applet should be running in the background15:05
CarlFKamitk: what if I am runing on u-server?15:05
amitkCarlFK: no UI?15:05
CarlFKright15:05
CarlFKwell, no gui :)15:05
amitkCarlFK: ps aux | grep kerneloops 15:06
CarlFKif it is a huge problem running it without X, I can load it up - this box is just to hack on this 15:06
CarlFKps aux | grep kerneloops = nothing but the grep...15:06
amitkjust run it manually then15:07
amitkwith --nodaemon15:08
amitkif you want to know what it is doing15:08
CarlFKgah - "Connection to cp666 closed by remote host."15:11
amitkCarlFK: I guess it was designed mostly for desktop users.15:11
amitkcp666?15:11
CarlFKI am working with a memory leak, and it kills processes 15:11
CarlFKcompaq 666mhz 15:11
CarlFKhostname 15:11
amitkCarlFK: run it manually and let me know what happens.15:12
* amitk -> steps out for 30mins15:12
rtgamitk: what do we have to do to prep the Jaunty kernel to be  a good kerneloops citizen?15:44
amitkrtg: add something in the VERSION to identify it as Ubuntu15:52
amitkrtg: and info d-i and buildd folks about the same15:53
rtgamitk: lets make sure it gets done early, cause its gonna break some stuff, right?15:54
amitkrtg: right15:54
amitkrtg: who is preparing the tree? you on BenC ?15:54
amitks/on/or15:54
rtghaven't started yet. isn't pgraner keeping a list of UDS topics somewhere?15:55
BenCamitk, rtg: I'm doing the rebase for jaunty this weekend15:57
CarlFKamitk: as memory gets used, processes are being killed.  I bet kerneloops gets killed.  is there some way to prevent that?  (I am guessing best to disable the killing processes process...16:42
CarlFKhow can I set 80x50 to get more lines on the console ?16:45
nxvlhi!17:29
nxvlis there any way i can have my own branch in kernel.ubuntu.com?17:29
nxvland how can i create one17:29
NCommandernxvl, you need a kernel.ubuntu.com (aka zinc) account17:30
nxvloh17:30
amitkCarlFK: use sysctl to write '2' to /proc/sys/vm/overcommit_memory to turn off overcommit. That should keep OOM killer at bay.18:20
CarlFKamitk: given I have to keep rebooting the box, what's the kernel param to do it?18:30
amitkCarlFK: shove it into /etc/sysctl.conf18:30
CarlFKamitk: didn't help: juser@cp666:~$ cat /proc/sys/vm/overcommit_memory ; 218:41
CarlFKstill killed lots of processes before the panic 18:41
amitkCarlFK: how do you it kills processes?18:43
CarlFKamitk: on the console: "out of memory, kill process (123)..."18:44
CarlFKI am about to run it in a vm, so I should be abele get screen shots18:46
amitkCarlFK: is this a custom app leaking memory?18:56
CarlFKamitk: I think it is the vivi v4l2 driver (that is part of vanilla kernel)18:57
CarlFKthe app I use is the V4L2 sample: caputre.c 18:57
amitkCarlFK: ohh.. a kernel driver18:57
CarlFKyes18:57
NCommanderamitk, https://launchpad.net/bugs/290153 - do you know if anyone been working on this?18:57
amitkNCommander: not that I know of. Make sure ogasawara knows about it. She is our task master.19:00
amitkCarlFK: so running the capture app causes the oops?19:00
NCommanderogasawara, https://launchpad.net/bugs/290153 - mind taking a look, I know a few people who are having this one19:00
CarlFKamitk: yep19:01
CarlFKamitk: I am building up docs on it: http://linuxtv.org/v4lwiki/index.php/Test_Suite#memory_leak_219:01
amitkCarlFK: you might try running ulimit on the capture process to limit its memory19:02
amitkman bash -> grep ulimit19:02
CarlFKamitk: will that help fix the bug, or just prevent it?19:02
amitkCarlFK: prevent the capture process from exceeding its size. If it is the one leaking memory, it should crash first, not other processes.19:03
CarlFKamitk: given the memory isn't freed when the app exites, will ulimit help?19:04
amitkCarlFK: the app exits correctly?19:05
CarlFKamitk:  exit(EXIT_FAILURE);   line 54 http://linuxtv.org/hg/v4l-dvb/file/b45ffc93fb82/v4l2-apps/test/capture_example.c19:06
CarlFKif i run the app 8-12 times (depending on box) I get various flavors of crash that require a reboot 19:07
amitkCarlFK: can't get into it right now (9pm here). Could you please file a bug with all the info consolidated and how to reproduce it.19:08
CarlFKamitk: on lp, right?19:11
CarlFKwhat package?19:11
amitkCarlFK: yeah. File it against 'linux' now since you suspect the kernel is oopsing19:13
CarlFKamitk: I have a few screen shots of the console - wana see?19:13
CarlFKhttp://dev.personnelware.com/carl/a/qemu_2.png19:13
CarlFK0-4 are the whole sequence 19:14
CarlFKer, stops at 3.  4 is this chat window... opps.19:14
amitkCarlFK: I find it very surprising that turning off overcommit_memory still triggers OOM19:28
amitkCarlFK: what is the line you put in sysctl.conf?19:29
CarlFKfor that I ran sysctl19:33
CarlFKamitk: oh hell... I forgot to sudo 19:34
amitkCarlFK: you don't need sudo there. Just add vm.overcommit_memory = 2 to a new line in the file19:35
amitkand reboot19:35
CarlFKwell... takes a while for qemu to reboot19:36
CarlFKso I need to sudo for kerneloops --nodaemon ?19:36
CarlFKdo I... ?19:36
amitkCarlFK: you shouldn't need to. But no harm in it.19:38
CarlFKamitk: kerneloops --nodaemon means if the shell is killed,  kerneloops goes too, right?19:42
amitkCarlFK: yeah19:44
amitkCarlFK: kerneloops isn't really a solution to your current problem. If you are able to reproduce this in a VM, then see if you can get a serial console going there.19:47
CarlFKamitk: ok.  I have done it, but will take a while to figure that out, so get out of here while you have a chance :)19:48
amitkheh19:51
=== thegodfather is now known as fabbione
ogasawara_NCommander: thanks for the note about bug 29015320:35
CarlFKIs this the OOM killer, or something else? [  289.211607] Out of memory: kill process 3980 (sshd) score 2809 or a child [  289.215599] Killed process 3982 (bash)21:47
sorenCarlFK: Yes, that's the OOM killer doing its thing.21:55
CarlFKthanks.  21:55
sorenCarlFK: It sees you're out of memory and using a set of heuristics, it selects a process and kills it to free memory.21:56
CarlFKany idea how to turn it off?21:58
sorenStop running out of memory.21:58
CarlFKI am trying to gather info about a kernel panic, 21:58
CarlFKheh - good plan.21:58

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