Hi lol!
I’m not really sure if my post belongs to this section but I need help urgently. I recently installed Mathematica 10.0.2 in my opensuse 13.2 system. Today, when I tried to open a “notebook” (Mathematica’s file) the system just froze and couldn’t do anything. I tryed several key-combos (ctrl+alt+supr; ctrl+alt+backspace; ctrl+alt+f2) and the lap-top just didn’t respond. I needed to hard-shutdown the system (pressing the on-off button until the lap shutdown). This happened about 4 or 5 times!
I know you know some magic commands to de-bug this. Please, help me 'cause I don’t know what to do or where to look:shame:
Thanks
Did you notice a lot of hard disk activity? Perhaps the program went out of control and tried to fill the system ram. If that happens, waiting a while usually the program will trigger the out of memory killer and the system will restablize.
If you notice the keyboard lights flashing, then the program caused a kernel panic.
Try running the application from a terminal and you can read the output when the freeze happens.
Thank you for your answer.
I didnot see lights flashing and waited several minutes and… nothing. Where can i check what happened?
I will try running it from terminallol!
Hi, 
I’m still having the “freezing” issue when I try to open a Mathematica’s file. I also noticed that the system is not updating with apper. Is there a connection? This bug is causing me much inconveniences. Can you help me? Thanks lol!
Probably not.
There’s a general problem at the moment with PackageKit hanging after accepting a license agreement:
https://bugzilla.opensuse.org/show_bug.cgi?id=908730
And at the moment there is yet another flash-player update, which requires a license agreement. So I’d guess that’s the reason for apper “not updating”.
You can run e.g. “pkcon get-updates” in a terminal window to make it continue, or run Apper additionally… If you interact with PackageKit in any way, it should wake up and continue the update.
or just user zypper up
You do have to kille packagekit since you can not have two program doing updates at the same time.
Thanks for your replies lol!
Could you guide me in the “freezing” thing?
I don’t have idea where to look.
Looking forward for your reply 
Well, you already got some suggestions.
So the freezes only happen with Mathematica?
As mentioned already, check that there’s enough RAM left (if the system runs out of RAM and is heavily swapping, it might seem to be frozen).
Run “top” in a terminal window. and watch the “Mem” and “Swap” statistics at the top when the freeze happens.
Other than that, such freezes normally point to a hardware (overheating?) or graphics driver problem.
So what graphics card/driver are you using?
Does it also happen when booting to “Recovery Mode”? (2nd entry in “Advanced Options” in the boot menu)
Also run “dmesg -w” in a terminal window and see whether new text appears when the system freezes.
Yes, only with Mathematica. I used the “monitors” of RAM and CPU usage and at the moment of “freezing” they where at 1GB (out of 4) and cpu less than 20%.
My graphics card:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)
IT seems that in “Recovery Mode” I don’t have the “freezing”
What else can I do?
Thanks lol!
Ok, I suppose we can rule out an overloaded system then…
But just to be clear: you do mean RAM (“Mem”) was at 1GB out of 4 (i.e. the 3rd line), not the Swap (the 4th line)?
And what about “dmesg -w”?
My graphics card:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)
IT seems that in “Recovery Mode” I don’t have the “freezing”
Well, it’s probably a graphics driver problem then. Apparently Mathematica is doing something that causes the (kernel) driver to crash (kernel panic), or something like that.
No idea, but you could probably try a newer kernel.
You can get the latest one from here: http://download.opensuse.org/repositories/Kernel:/stable/standard
OTOH, a kernel update (with some fixes to the intel driver among other things) for 13.2 is in progress, so maybe that would fix it too. (no idea when it will be released though, it might be in a few days, or a few weeks…)
It does seem to be a kernel problem at least, IMHO…
Hilol!
I really appreciate your support. It is a very strange behaviour what I found
Yes 1 GB used of a total of 4 GB of RAM memory.
Well, it’s probably a graphics driver problem then. Apparently Mathematica is doing something that causes the (kernel) driver to crash (kernel panic), or something like that.
I delayed a little to answer because I waited for the reply of the Mathematica team and they suggested me to re-install the program. I already did that and didn’t fix anything. Nonetheless, I will try once more to install it and see if the problem es corrected.
I will let you know the outcome
Thank yourotfl!
Hi again
I did what Mathematica people told me: uninstall and install back but nothing changed. In the very first file I tried to open with Mathematica 10 my system froze… (with all its inconveniences)
Could you, please, tell me where to look in this output? (it’s very long and got “lost”) What should I look for?
Thanks lol!
Nothing.
Just run it and ignore the output. It will continue running and print new log messages as they appear.
So reproduce the freeze then, and watch whether new messages appear in “dmesg -w”'s output (and if possible, post them).
To make things more obvious, you could also run “sudo dmesg -c” first, to clean the kernel log buffer. Then “dmesg -w” should not print anything at all at first.
Hi
iI had to unsintall Mathematica; re-install it and tried to open a fiLe to “reproduce” the freeze. At lLeast, I i succeded on this, my system froze. After restarting the system, iIran “sudo dmesg -c” and then “dmesg -w”. This is what i obtained:
# dmesg -w
4963.744347] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45879 PROTO=UDP SPT=1900 DPT=1900 LEN=44
4964.249269] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45880 PROTO=UDP SPT=1900 DPT=1900 LEN=44
4965.245490] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45881 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5007.568273] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:baee:65ff:feb3:8d8a DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
5083.331614] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45900 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5084.332303] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45901 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5085.333067] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45902 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5203.418673] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45921 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5204.419693] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45922 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5205.420325] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45923 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5323.507264] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45970 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5324.506693] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45971 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5325.507293] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45972 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5443.603117] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45991 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5444.604952] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45992 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5445.607394] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=45993 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5564.191124] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=46040 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5564.691523] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=46041 PROTO=UDP SPT=1900 DPT=1900 LEN=44
5565.712189] SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=b8:ee:65:b3:8d:8a:e8:94:f6:df:b2:89:08:00 SRC=192.168.1.1 DST=10.210.243.231 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=46042 PROTO=UDP SPT=1900 DPT=1900 LEN=44
and messages continued appearing on the console.
Will this help me?
I hope it willlol!
Thank you very much for your support
No, not at all.
Those are only messages by the firewall, unrelated to your freeze.
Also, you made a mistake.
dmesg is cleared at boot, if you reboot after the freeze, dmesg only prints the current messages.
You should instead post the messages that are visible on the screen at the moment that the system freezes.
Maybe take a picture and post that.
Good morning from México;)
I reproduced the “freezing” but I’m afraid that the photo I took won’t help much.
There appears the console and my file manager where you can see the Mathematica icon over a file and in the console appear messages from the firewall.
I leave you the link with the photo:
https://drive.google.com/file/d/0BzBoLoUQva9aUEQxYndrRTFlUXc/view?usp=sharing
https://drive.google.com/file/d/0BzBoLoUQva9aUEQxYndrRTFlUXc/view?usp=sharing
(how do I insert the image in the post? I tried “inset image” but didn’t work. Ha!..)
Thank you very much for giving me your support lol!
We keep in touch
Yeah, unfortunately that doesn’t help at all.
(how do I insert the image in the post? I tried “inset image” but didn’t work. Ha!..)
It does work, but you have to provide a direct URL to the image itself.
Regarding your problem, I don’t really have an idea at the moment.
There doesn’t seem to be a kernel crash, or it doesn’t even manage to show up in the Konsole any more. As you can’t even switch to the log console afterwards (Ctrl+Alt+F10), I doubt there’s a way to find out what happens. (you could try to login from a different system via the network if possible, but you’d have to enable the sshd service first and open the firewall)
As the problem does not happen in recovery mode, a likely reason is of course the graphics driver.
Can you try the same in a different desktop environment?
IceWM should be installed by default, you should be able to select it on the login screen (click on the icon in the bottom-left of the screen).
If it doesn’t happen in IceWM, the next step would probably be to disable desktop effects in KDE before you start mathematica, either in KDE’s settings or by pressing Shift+Alt+F12.
Does that help?
PS, as a side-note: googling for “mathematica freeze” gives quite a few hits, even for windows…
Hi, again:)
Today I was working and the system entered in panic…
https://drive.google.com/file/d/0BzBoLoUQva9ad2lBZkJtcGU2VjQ/view?usp=sharing
perhaps this is the problem ( I hope! )
Sorry for the photo 'cause I took it quickly before the system re-started (automatically)
Can you help me?
Thanks lol!
Well, at least it is a kernel crash (apparently related to interrupt handling), which should not happen.
I would suggest to try a newer kernel, to see whether this is maybe fixed already.
The latest one can be found here:
http://download.opensuse.org/repositories/Kernel:/stable/standard
E.g. type this to install it (I assume you are running a 64bit system):
sudo rpm -i http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/kernel-desktop-3.19.3-1.1.gf10e7fc.x86_64.rpm
If the new kernel is giving you problems, you should still be able to boot the old one via “Advanced Options” in the boot menu.
Or wait a few days until the currently running kernel update is released for 13.2, maybe this works better then…
If both kernels don’t help, you should file a bug report at http://bugzilla.opensuse.org/ (same username/password as here).
sudo rpm -i http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/kernel-desktop-3.19.3-1.1.gf10e7fc.x86_64.rpm
I followed what you suggested me and in the end asks me: **Update bootloader…
**Could you tell me how to do that?:shame:
Thanks