/srv/irclogs.ubuntu.com/2006/03/02/#ubuntu-kernel.txt

=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #ubuntu-kernel
bluefoxicyHi01:23
bluefoxicythis may be a stupid question01:23
bluefoxicybut should running mplayer on a half-corrupted wmv file cause it to stop, complain it died01:24
bluefoxicyand then if you hit "OK" so it exits OR kill -9 it01:24
bluefoxicythe kernel decides it's time to have a fit and hard-lock?01:24
bluefoxicy(i.e. apparently mplayer caused kernel memory corruption)01:24
crimsunthat shouldn't be possible01:33
bluefoxicycrimsun:  ok, I think the ubuntu amd64 kernels in dapper need some nice looking at then.  Are you guys using any weird patches?01:36
crimsunheh, what do you call "weird?"01:37
bluefoxicyor anything aside from drivers that's experimental?01:37
bluefoxicycrimsun:  well, if it does something to the kernel's source tree, it's weird.01:37
crimsunwell by that classification, everything that's patched is done by something weird, which is some non-negligible amount of source01:38
bluefoxicythere's a specific reason why the linux mainline kernel is what it is.  Additional drivers are pop in and out; but modifications to the VM system, initialization routines, VFS subsystem, CPU schedulers, or the like that aren't backported bugfixes are DISTINCTLY odd01:38
bluefoxicycrimsun:  if it's a bug in something you added, I can't go to the LKML and report it; otherwise I can just bounce it at them01:39
crimsunthe kernel isn't precisely the first place I'd look for an oops caused by mplayer01:40
bluefoxicyIf I bring them something and say "Oh there's some odd patches in ubuntu's kernel like the hard-deadline-scheduler and the memory-split-merge-mapper and ingo molnar's realtime patches" they'll go "THEN DON'T ASK US!"  :(01:40
crimsundo you have ksymoops output?01:40
bluefoxicycrimsun:  it's not an oops.01:40
crimsunhow are you ascertaining it's not an oops if you get a hard lock?01:41
bluefoxicymplayer sits there fine; then when I send kill -9 at it, the box drops straight off network, the mouse stops working, sound stops playing, hard disk stops, the screen stays as is, keyboard won't work. . .01:41
bluefoxicycrimsun:  because an oops is a condition where the kernel says, "Oops," and keeps on going.01:41
bluefoxicyThe most kernel-aware activity this could be is a panic01:41
bluefoxicywhich is where the kernel says "HOLY SHIT" and stops01:42
crimsunthat doesn't mean you don't have an oops and then a panic01:42
crimsunin any case, can you reliably reproduce it?01:42
bluefoxicywell, I guess I could cause one and see01:42
bluefoxicybut I'm a little shakey01:42
bluefoxicyevery 2 or 3 hard-locks, gnome's settings reset.01:42
bluefoxicyapplet configurations go, background goes, xchat-gnome settings reset, gnome-terminal settings reset, startup programs reset, rhythmbox settings reset. .01:43
crimsunthe first thing I'd do is try with an ia32 kernel01:43
bluefoxicyanything stored in the ~/.* directories for the apps stays there01:43
=== bluefoxicy doesn't have IA32 ubuntu installed
bluefoxicyI had IA32 dapper installed, it was stable01:44
crimsunwhich kernel with ia32?01:44
bluefoxicythe x86-64 kernels are being a real pain01:44
bluefoxicyI had i686 up to 2.6.15-1401:44
bluefoxicythen i installed a 64-bit base.01:44
crimsunso do flight 2 amd64 or flight 3 amd64 have this issue?01:45
bluefoxicyno idea.01:45
bluefoxicyoh01:45
=== bluefoxicy facepalm
bluefoxicyI most likely know where the problem is anyway01:46
bluefoxicyI keep forgetting, I'm using the via driver in xorg01:47
bluefoxicyand it seems to be really bitchy01:47
bluefoxicybut I don't see how that could be linked to killing mplayer. . .01:47
bluefoxicyFeb 23 14:30:05 localhost kernel: [ 8564.581410]  RIP: 0010:[_end+134114922/2132357120]  <ffffffff88453e6a>{:via:via_mmFreeMem+10}01:47
bluefoxicyThis is where every single oops I've had has happened.01:48
bluefoxicylike ever01:48
bluefoxicyso I'm assuming there's a bigger bug around there that's causing a panic or hard-lock01:48
bluefoxicycrimsun:  I can't make the logical link between "killall -9 gmplayer" and "Hard lock," but that's a starting point.  There's no logs of kernel panics (for a specific reason-- the kernel halts immediately)01:49
bluefoxicyfor now I'm getting off the via driver.01:50
=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #ubuntu-kernel
bluefoxicyok my test data to reproduce it is gone now damn.01:53
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== j_ack [n=nico@p508D938E.dip0.t-ipconnect.de] has joined #ubuntu-kernel
=== TheMuso [n=luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel
=== crimsun [n=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-kernel
mjg59infinity: It's supposed to - we should probably work out what's up (swsusp)10:54
=== CataEnry [n=cataenry@host92-11.pool8261.interbusiness.it] has joined #ubuntu-kernel
=== TheMuso [n=luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel
=== TheMuso [n=luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel
=== jane_ [n=JaneW@dsl-146-161-84.telkomadsl.co.za] has joined #ubuntu-kernel
=== TheMuso [n=luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel
infinitymjg59: Well, check recent threads on ubuntu-users.  Several users claim that adding RAM to their machine breaks swsusp (and removing it again to drop below 1GB fixes it)12:26
=== smurf [n=smurf@run.smurf.noris.de] has joined #ubuntu-kernel
=== doko [n=doko@dslb-084-059-116-248.pools.arcor-ip.net] has joined #ubuntu-kernel
makxthere swap might be to small03:49
bluefoxicyswsusp could be better designed though04:46
bluefoxicyhalt programs, flush disk buffers (so file system is consistent), check how much swap is free vs how much memory is used04:47
bluefoxicyif there's not enough swap, see if there's enough space on / for the rest, if yes then create a swsusp file there and make note of it in the swap partition04:48
bluefoxicyflush to swap, flush remaining to the new inode on /, flush disk buffers, and halt04:48
bluefoxicywhen coming back up, look for something that claims there's an inode holding a swsusp file.  If there's one there, load that entirely into RAM and unlink the inode04:48
bluefoxicya little less lazy, but it would be possible.04:49
bluefoxicybut that's out of scope.04:49
bluefoxicymakx is probably right, they probably get like a gig and a half of application memory used and have a gig of swap.04:49
bluefoxicySHIT.  I can't run apt.04:53
bluefoxicygotta reboot I guess.04:53
mjg59infinity: Hnngh.05:16
=== desrt [n=desrt@dhcp-0-20-af-d2-7c-3.cpe.mountaincable.net] has joined #ubuntu-kernel
=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #ubuntu-kernel
bluefoxicyI can say with 95% certainty at this point that the bug was in the via dri code in the kernel.09:48
bluefoxicyif I stay up for another day, I'll promote that to 99%09:48
bluefoxicyI've had no oopses since boot and no crashes09:49
=== ispiked [n=ispiked@unaffiliated/ispiked] has joined #ubuntu-kernel
desrtoh where oh where is benc10:19
=== netzmeister [n=netzmeis@p549FA3B8.dip0.t-ipconnect.de] has joined #ubuntu-kernel
=== TheMuso [n=luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== desrt tackles BenC
=== BenC doges and runs for the touchdown
=== crimsun [n=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-kernel

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