Bug#737335: general: Resets pulseaudio volume to 100% after pause
Package: general Severity: important Dear Maintainer, * What led up to the situation? use subtitle-composer with phonon. Set master level to a value 100, play video, pause video, press play. * What was the outcome of this action? Something resets the master volume to 100 upon resuming from pause. Very loud sound, pain in my ears. * What outcome did you expect instead? Painless enjoyment of nice, quiet videos. Note: i have phonon-backend-vlc version over 0.6.0-1 ! (debian-jessie latest) Also i use veromix as my mixer. Pulseaudio is set to use a single daemon! daemonize = yes system-instance = yes Let me know if you need more data, please. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140201200421.3397.74330.reportbug@moli-desktop
Bug#735927: general: X *always* crashes when ram is full
@Holger: I'm sorry, but I'm closing this bug as google-chrome is supported by Google, not by Debian. You _*REALLY*_ should read the whole ticket first. And other tickets in the future too. Please reopen this ticket. @Martijn: Or (recommended) just add a small swap partition (say 128MB) to allow the kernel to put unused memory pages on disk so the X server can use them instead. I'm sorry, i can not, i only have SSD in that machine. If i enable swap in a machine with only 1GB ram it would be in use all day long, every time. I will try your other recommendations through, please be patient and wait for my feedback. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140119163651.6bb3afa5@moli-desktop
Bug#735927: general: X *always* crashes when ram is full
You could change the OOM priority of the X server, this would cause some other process to be killed instead. Nice idea, i searched for this oom thing (btw it means: out of memory) and found OOM Killer. Some pages for future reference: http://linux-mm.org/OOM_Killer http://lwn.net/Articles/317814/ http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html Looks like nice priority is important when something has to be killed to free memory (unfortunatelly it's not that important as it does not take the nice LEVEL into the calculation, if it's -1 or -19, it's the same...), so i ran chrome by the following command: nice -19 /opt/google/chrome/google-chrome --password-store=gnome --disk-cache-size=1 --disk-cache-dir=/dev/null Then i ran the following command in a shell under root: while true ; do for i in $(pidof chrome) ; do pid=$(($i+0)) if [[ $pid -ne 0 ]] ; then echo -999 /proc/$i/oom_score_adj ; fi ; done ; sleep 1 ; done and opened some youtube videos, and the X crashed again. (Please check my commands, did i do everything right?) And no messages from oom_killer in /var/log/messages . So looks like it's not an oom killer thing happening. btw i ran the same tests on the same computer but with ubuntu 11.04 kernel 2.6.38 , no crashes!! Same shared video memory, same intel hardware, different kernel (drivers?). -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140119200443.5f8151db@moli-desktop
Bug#735927: general: X *always* crashes when ram is full
this next test was fast, sorry for the flood. You could disable memory overcommit, that would cause things to fall over sooner. Again, nice idea, thanks. For reference: http://serverfault.com/questions/485798/cent-os-how-do-i-turn-off-or-reduce-memory-overcommitment-and-is-it-safe-to-do Did the above, rebooted, started chrome, it ran but did not appear visually on the screen. The process ran and allocated the memory but probably it couldnt allocate enough to run onwards. Now when i tried to run anything, all failed with the message cannot allocate memory, and a few seconds later the X crashed again. No messages in /var/log from oom-killer (i mistyped its name in my previous email) so again it does not look like oom-killer WAS TAKING action. I'm emphasising this because i have an old message from oom-killer when it really worked: /var/log/kern.log.1:Jan 18 22:25:35 desktop kernel: [ 2027.606581] Xorg invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 /var/log/messages.1:Jan 18 22:25:35 desktop kernel: [ 2027.606581] Xorg invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 /var/log/syslog.1:Jan 18 22:25:35 desktop kernel: [ 2027.606581] Xorg invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 but not this time. (my clock is set) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140119204324.0d588343@moli-desktop
Bug#735927: general: xserver-xorg-video-intel crashes when shared dynamic video ram runs out
Thanks for your reply Andreas. What else do you expect after putting the system under extreme memory pressure I expect, intel driver bug-or-not ASIDE, the linux to kill the chrome and keep the X. tmpfs is another story, because there's nothing huge to kill except X. But again i expect the kernel to kill chrome first, X later. PS: and you would be perfectly fine if X wouldn't crash but would be killed by the oomkiller - with the same situation afterwards ? Now that you're asking it, yes! because that i could fix with Martijn's idea by setting chrome's oom_score_adj to a low value which would kill chrome first and enough memory would free up to keep the X. Compare the versions of xserver-xorg-core and xserver-xorg-video-intel between the Ubuntu version and the Debian version you used. Yes sir, xserver-xorg-video-intel debian: 2:2.19.0-6 ubuntu: 2:2.14.0-4 Could you try the vesa (xserver-xorg-video-vesa) driver instead and see what happens under extreme memory pressure? Excellent idea, dont know why i havent done this already. That's why i turned to you for help. btw this is my first time on debianbts, so i'm sorry if i do something out of etiquette - my bad english does not help either. I uninstalled xserver-xorg-video-intel as i'm dumb and dont know how to disable a driver (tried blacklist but dont know the module name, googled, nothing, so), i rebooted, tried to crash the system, opened 7 youtube videos, chrome got killed, X survived. Just like on my other systems and OSes. So it seems proven that the intel driver is the problem. Maybe because vesa driver doesnt use dynamic video memory only a fixed size small one? The ret value is not returned to the caller (X), so that does not know about the failure. Any chance to fix this? I don't think its running out of *video memory*. It's just running out of normal RAM. and To me this looks like the intel driver cannot do a task because it cannot allocate memory So it cannot allocate shared video memory ;) this does not neccessarily trigger the kernel's OOM killer Yes, because that's video memory, not system memory. The problem is exactly what you wrote: the oom-killer cannot step in to free memory before the intel driver crashes. Can i somehow allocate the video memory from the system memory fixed/permanently? And since I suspect xserver-xorg-video-intel, you might want try a newer version of that driver. Okay.. # echo 'APT::Default-release stable;' /etc/apt/apt.conf.d/00default # echo -e 'Package: *\nPin: release a=stable\nPin-Priority: 700\n\nPackage: *\nPin: release a=testing\nPin-Priority: 650\n\nPackage: *\nPin: release a=unstable\nPin-Priority: 600\n' /etc/apt/preferences.d/pinning # echo -e '\ndeb http://ftp.debian.org/debian/ jessie main contrib non-free\ndeb-src http://ftp.debian.org/debian/ jessie main contrib non-free\n' /etc/apt/sources.list # apt-get update # apt-get install xserver-xorg-video-intel/jessie but apt-pinning did not work, since it requires update of libc. So, i did: # apt-get install dpkg-dev # apt-get build-dep xserver-xorg-video-intel/jessie # apt-get -b source xserver-xorg-video-intel/jessie # dpkg -i xserver-xorg-video-intel_2.21.15-1_amd64.deb Guys, did i do this right? This building thing? I rebooted and ran the test, it did not crash. As i started to rejoice, i realized, i'm probably using the vesa driver, so still not knowing how to specify or even list the driver to use, i removed the xserver-xorg-video-vesa package and rebooted. It crashed just like with the old driver. You see my problem is in this current state the system is broken: it is wrong my grandma opens 10 browser tabs and the next thing she sees is the lightdm login screen - she doesnt know her password, she doesnt even know she HAS a username! (autologin) It would be totally fine if there would be only 1024-128=896 MB free ram to the system, hell i wouldnt even care if there would be 256 MB and she could just open 1 browser tab, but her aisleriot solitaire and mahjongg games should stay intact. Very important. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140120022011.5ec05ca3@moli-desktop
Bug#735927: general: X *always* crashes when 5 youtube video opened
Package: general Severity: important Dear Maintainer, * What led up to the situation? The hardware is an Intel D945GCLF2 motherboard with Intel 82945GC MCH and Intel Atom 330 processor and 1GB ram module. The bios settings: DVMT MODE: DVMT, IGD DVMT MEMORY: 32MB, IGD APERTURE SIZE: 128MB. There is no swap partition in the system. I installed debian 7.3 amd64 with alternative desktop environment xfce by graphical expert install using english language (because hungarian language fails at tasksel). After installation i purged a whole lot of packages so the number of installed packages came down to 800. Then i installed google-chrome- stable icedtea-6-plugin firmware-linux intel-microcode iucode-tool and rebooted. * What exactly did you do (or not do) that was effective (or ineffective)? I started chrome and opened 5 youtube 10 hour long videoes (i was planning to test my cooling solution). The processor load was at 80% (!! not 100%!), the ram was at ~90%. * What was the outcome of this action? In about 1 minute the X crashed. Reproducable any time. /var/log/Xorg.0.log.old: (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: No space left on device. * What outcome did you expect instead? X not to crash. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140118183730.3040.66017.reportbug@rozi-desktop
Bug#735927: i do have storage space
$ df -B1 Filesystem 1B-blocks Used Available Use% Mounted on rootfs 15761063936 2350039040 12610387968 16% / btw how do i concat a new message with reportbug? i do not want to use an email client, i dont want to install one just for this on that machine. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140118194407.2c5e6907@moli-desktop
Bug#735927: general: X *always* crashes when 5 youtube video opened
chrome. google-chrome-stable package from deb http://dl.google.com/linux/chrome/deb/ stable main To be clear, the list of all manually installed packages beside the base debian-xfce system: aisleriot (this is my grandma's computer who is using it for facebook mainly. that's why it is an atom and 1GB ram only and couldnt be more.) baobab curl desktop-profiles ez-ipupdate fail2ban firmware-linux firmware-linux-free firmware-linux-nonfree firmware-realtek gksu google-chrome-stable gtkorphan htop icedtea-6-plugin intel-microcode iucode-tool mahjongg mc menu-xdg molly-guard p7zip-full pv screen seahorse sqlite3 tree xdg-user-dirs-gtk xfce4-indicator-plugin xfce4-messenger-plugin xfonts-terminus xfonts-terminus-dos xfonts-terminus-oblique I can attach the list of purged packages if you need that, but that list is about 347 package long. chrome plugins: chrome pdf viewer icedtea-web plugin nativeclient widevine adobe flash player 12.0.0.41 chrome extensions: NONE chrome apps: NONE BUT i just disabled the adobeflash plugin so it would use pepper or html5, and ran the test again, it crashed ~40 seconds later. I dont have any knowledge in this area but i dont think this has anything to do with chrome, i think it's an intel graphics driver issue, it does not handle gracefully when the video memory is gone. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140118210834.6a62150f@moli-desktop
Bug#735927: general: X *always* crashes when ram is full
ok, another way to reproduce without chrome or flash or youtube: reboot to a clean system, dont run anything, only an X and a console # mkdir /tmp/foo # mount -t tmpfs none /tmp/foo -o size=900m # dd if=/dev/zero of=/tmp/foo/bar (a message comes with device full) (now you cannot give any new command in bash as there is no memory to start a new shell for you command: error message: bash: fork: cannot allocate memory) now wait a few seconds, move your mouse, etc, boom, the x crashes: /var/log/Xorg.0.log.old (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: No space left on device. note: this time i've set the bios parameters to the *MAXIMUM* values: DVMT MODE: FIXED IGD DVMT MEMORY: 128MB IGD APERTURE SIZE: 256MB so there should be plenty of video memory and note that i didnt run much program that needs video memory. Now testing this method on my desktop machine which has 12GB(!) ram and kdm+kde did not crash the X. The system suffered, lagged but did not crashed. After filling the tmpfs i opened some new chrome tabs (the only reason i'm using chrome is nothing else i use eats memory like it), waited for ~10 minutes, chrome did not respond but did not crash. Then i allocated some more ram again in the tmpfs, the system console had some messages it is killing the chrome to free ram, some chrome tabs crashed, but the X did not. After this i've logged out and logged in to my girlfriends account, she uses xfce. Did the same as above, X did not crash, so it's not looking like an xfce-bug. Note that my desktop machine has a video card with DEDICATED video ram. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140118235621.1522456b@moli-desktop
