diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-May/015768.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-May/015768.html | 231 |
1 files changed, 231 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-May/015768.html b/zarb-ml/mageia-dev/2012-May/015768.html new file mode 100644 index 000000000..c29e095a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015768.html @@ -0,0 +1,231 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Strange system stalls - neep a tip + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Strange%20system%20stalls%20-%20neep%20a%20tip&In-Reply-To=%3C201205220650.27989.dglent%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="015764.html"> + <LINK REL="Next" HREF="015760.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Strange system stalls - neep a tip</H1> + <B>Dimitrios Glentadakis</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Strange%20system%20stalls%20-%20neep%20a%20tip&In-Reply-To=%3C201205220650.27989.dglent%40gmail.com%3E" + TITLE="[Mageia-dev] Strange system stalls - neep a tip">dglent at gmail.com + </A><BR> + <I>Tue May 22 06:50:11 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="015764.html">[Mageia-dev] Strange system stalls - neep a tip +</A></li> + <LI>Next message: <A HREF="015760.html">[Mageia-dev] Strange system stalls - neep a tip +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#15768">[ date ]</a> + <a href="thread.html#15768">[ thread ]</a> + <a href="subject.html#15768">[ subject ]</a> + <a href="author.html#15768">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Στις 21/05/2012 23:17:05 Mahmut Bulut γράψατε: +><i> probably ntpd won't cause something like this, this is not a botnet +</I>><i> attack :) and also situation can't caused from cpu usage. I think it +</I>><i> can be (and your thought i appreciate) is kernel-related problem. +</I>><i> And use a c code something like that to panic; +</I>><i> +</I>><i> char *kernel_panic = NULL; +</I>><i> char message = *kernel_panic; +</I>><i> +</I>><i> and build a kernel extension after this use insmod to load kernel ext. +</I>><i> reboot and wait for panicking. +</I>><i> after panicking fall into terminal mode(if you can't, you can do it on +</I>><i> next reboot) +</I>><i> if you saw your system.map or where the log happens something like +</I>><i> "warn_slowpath_common+0x***" this can be caused by your eax and pc's +</I>><i> async work (program counter) your specific problem and it is not +</I>><i> caused by any distro but you can submit your trace to kernel +</I>><i> developers for debugging purposes and will be fixed. +</I>><i> +</I>><i> 2012/5/21, Robert Fox <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">list at foxconsult.net</A>>: +</I>><i> > On Mon, 2012-05-21 at 19:50 +0200, David Sjölin wrote: +</I>><i> >> On Mon, May 21, 2012 at 7:33 PM, AL13N <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote: +</I>><i> >> > perhaps check the logs (/var/log/messages) for information regarding +</I>><i> >> > those +</I>><i> >> > downtimes. +</I>><i> >> > +</I>><i> >> > see if the ping also delays +</I>><i> >> > +</I>><i> >> > perhaps try to monitor something via ssh or in tty, to see if it's only +</I>><i> >> > the graphic card. +</I>><i> >> > +</I>><i> >> > also, check ntpd settings, do they make big jumps? +</I>><i> >> > +</I>><i> >> > etc... +</I>><i> >> > +</I>><i> >> > +</I>><i> >> > in short: logging is always the key. +</I>><i> >> > +</I>><i> >> >> Hello All - +</I>><i> >> >> +</I>><i> >> >> I am experiencing a strange problem with a specific machine running +</I>><i> >> >> Cauldron. I am beginning to believe it is NOT a Mageia problem +</I>><i> >> >> because +</I>><i> >> >> when I boot into Ubuntu 12.04 the problem exists as well. I think it +</I>><i> >> >> may be hardware related but I can not find what is causing this issue. +</I>><i> >> >> +</I>><i> >> >> The machine is an Acer Aspire x3900 with a quad core ‎AMD Phenom(tm) +</I>><i> >> >> II +</I>><i> >> >> X4 925 Processor - 6GB memory. GeForce GT215 (GeForce 320) card. I am +</I>><i> >> >> running the x86_64 version of Cauldron. +</I>><i> >> >> +</I>><i> >> >> The problem occurs under both KDE and Gnome +</I>><i> >> >> +</I>><i> >> >> Basically, the system seems to freeze up (mouse moves) but nothing +</I>><i> >> >> else +</I>><i> >> >> - gkrellem freezes and no errors occur - it just seems to hang - but +</I>><i> >> >> magically wake up again after some time (many seconds at a time) +</I>><i> >> >> +</I>><i> >> >> I have checked various logs and can not find any problems - so I am +</I>><i> >> >> stumped how to find the source of the problem. I leave the machine +</I>><i> >> >> running 24x7, but don't think it is a thermal issue. +</I>><i> >> >> +</I>><i> >> >> When the system runs under Windows 7 (64bit) it appears to run fine. +</I>><i> >> >> +</I>><i> >> >> Any hints what I could check? +</I>><i> >> >> +</I>><i> >> +</I>><i> >> Hello! +</I>><i> >> +</I>><i> >> If you want to log cpuusage to see if some process has extra high cpu +</I>><i> >> usage during this freeze you could do something like: +</I>><i> >> +</I>><i> >> while true; do date >> testfilen.txt ; top -b -n1 >> testfilen.txt ; +</I>><i> >> sleep 1; done +</I>><i> >> +</I>><i> >> Then you will get top-output every second (sleep 1) or whatever time +</I>><i> >> you specify for sleep. I think there is a way to do this with top +</I>><i> >> only, without the delay but not sure which flags to use then (possibly +</I>><i> >> top -d 1 -b) +</I>><i> >> +</I>><i> >> The file testfilen.txt will of course grow quite large after a while, +</I>><i> >> so you can't keep this running 24/7 maybe, but maybe you could clear +</I>><i> >> out the file regularly until you get the error situation again and +</I>><i> >> then based on the date output you should be able to find cpu usage +</I>><i> >> around the time of the problem. +</I>><i> >> +</I>><i> >> Regards, +</I>><i> >> +</I>><i> >> David +</I>><i> > +</I>><i> > Thanks for the quick responses. I checked the cpu usage, but there +</I>><i> > doesn't appear to be a spike - and the load average in htop is real low: +</I>><i> > +</I>><i> > load average: 0.46, 0.67, 0.56 +</I>><i> > +</I>><i> > so if the X server or something else was maxing out the cpu, I'd see +</I>><i> > that. +</I>><i> > +</I>><i> > Also, if I use a console in KDE (like yakuake) - the stalls happen in +</I>><i> > there as well. At first I though this was Firefox related (like flash +</I>><i> > problem or something) because it was most noticeable when I surfed - +</I>><i> > firefox freezes off and on and it is really frustrating. +</I>><i> > +</I>><i> > This machine was working fine for at least a year - and I was suspecting +</I>><i> > something with the latest kernels and the AMD processor - but have no +</I>><i> > evidence. +</I>><i> > +</I>><i> > The search continues . . . +</I>><i> > +</I>><i> > Thanks again, +</I>><i> > R.Fox +</I>><i> > +</I>><i> > +</I>><i> > +</I>><i> > +</I>><i> +</I> +I have the same symptoms and some times with this message (in n: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:general protection fault: 0000 [#153] SMP + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:last sysfs file: /sys/devices/pci0000:00/0000:00:00.0/modalias + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Stack: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Call Trace: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Code: 00 e8 80 9c 29 00 48 8b 1c 24 4c 8b 64 24 08 c9 c3 eb 03 90 90 90 55 48 89 e5 53 48 83 ec 18 66 66 66 66 90 48 8b 47 60 48 89 fb <ff> 10 83 f8 00 7e 0a 48 89 d8 48 83 c4 18 5b c9 c3 75 18 48 89 + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:general protection fault: 0000 [#154] SMP + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:last sysfs file: /sys/devices/pci0000:00/0000:00:00.0/modalias + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Stack: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Call Trace: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Code: 00 e8 80 9c 29 00 48 8b 1c 24 4c 8b 64 24 08 c9 c3 eb 03 90 90 90 55 48 89 e5 53 48 83 ec 18 66 66 66 66 90 48 8b 47 60 48 89 fb <ff> 10 83 f8 00 7e 0a 48 89 d8 48 83 c4 18 5b c9 c3 75 18 48 89 + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:general protection fault: 0000 [#155] SMP + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:last sysfs file: /sys/devices/pci0000:00/0000:00:00.0/modalias + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Stack: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Call Trace: + +Message from <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">syslogd at localhost</A> at May 15 07:14:15 ... + kernel:Code: 00 e8 80 9c 29 00 48 8b 1c 24 4c 8b 64 24 08 c9 c3 eb 03 90 90 90 55 48 89 e5 53 48 83 ec 18 66 66 66 66 90 48 8b 47 60 48 89 fb <ff> 10 83 f8 00 7e 0a 48 89 d8 48 83 c4 18 5b c9 c3 75 18 48 89 + * Error: Unable to use "ps" to scan for gpg-agent processes + * Error: Please report to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">drobbins at funtoo.org</A> via <A HREF="http://bugs.gentoo.org">http://bugs.gentoo.org</A> + + +Yesterday morning happened always and i had to reboot the system every 10 minutes ... + +I have upload the output of /var/log/messages here: +<A HREF="http://pastebin.com/nNDYUbuu">http://pastebin.com/nNDYUbuu</A> + + + +-- +Dimitrios Glentadakis +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="015764.html">[Mageia-dev] Strange system stalls - neep a tip +</A></li> + <LI>Next message: <A HREF="015760.html">[Mageia-dev] Strange system stalls - neep a tip +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#15768">[ date ]</a> + <a href="thread.html#15768">[ thread ]</a> + <a href="subject.html#15768">[ subject ]</a> + <a href="author.html#15768">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |