Jump to content

My whole system closes down [solved]


Kieth
 Share

Recommended Posts

Well, I thought the problem might have been Firefox and Thunderbird running together, but not this time. I had Opera 9.5 and Thunderbird 2.0.0.16 on, along with BibleTime 1.6.5, OpenOffice 2.4.1, and KMahjongg. Without a warning, my system just turned off.

 

Is there a log that I can get to that will list what happened, or will at least give me some information? Any other ideas that might be creating this? It all started about 2 weeks ago after I did a normal upgrade. I do not remember what was upgraded, but I think it had to do with sound and/or video. This problem of turning off unexpectedly is sporadic.

 

$ uname -a

Linux Alice 2.6.24.7-desktop-1mnb #1 SMP Mon Jul 28 15:12:10 EDT 2008 i686 AMD Athlon 64 Processor 3000+ GNU/Linux

 

I'm using Mandriva 2008, the latest issue. If there's a command that will list my system, if you'll tell me, then I'll get more information.

 

Thanks,

Kieth

 

 

[moved from Everything Linux by spinynorman]

Link to comment
Share on other sites

  • Replies 44
  • Created
  • Last Reply

Top Posters In This Topic

I tried to look in that file the other day, but it was blank. I tried again today, and it was blank. Then I opened kwrite in root, opened the file, and . . . Well, it wasn't blank after all!! While I was looking at it, the system crashed again. Following is part of the file, the part when the system crashed. Does it make sense to anyone? It doesn't to me!!

 

Last night it rained and cooled everything down. Today, it's quit nice, not really hot, just warm.

 

Thanks,

Kieth

 

Aug 28 17:25:09 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.74.125 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=64430 DF PROTO=TCP SPT=2324 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0

Aug 28 17:25:12 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.74.125 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=65178 DF PROTO=TCP SPT=2324 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0

Aug 28 17:25:37 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.148.88 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=3373 DF PROTO=TCP SPT=3817 DPT=135 WINDOW=64800 RES=0x00 SYN URGP=0

Aug 28 17:27:21 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.231.74 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=21991 DF PROTO=TCP SPT=20395 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:28:26 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=43646 DF PROTO=TCP SPT=4851 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:28:29 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=43699 DF PROTO=TCP SPT=4851 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:28:35 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=43765 DF PROTO=TCP SPT=4851 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:29:22 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.43.138 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=58 ID=35571 DF PROTO=TCP SPT=24073 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:31:15 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=45712 DF PROTO=TCP SPT=4951 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:31:18 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=45753 DF PROTO=TCP SPT=4951 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:31:24 Alice kernel: IN=ppp0 OUT= MAC= SRC=79.18.246.111 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=45898 DF PROTO=TCP SPT=4951 DPT=41361 WINDOW=64240 RES=0x00 SYN URGP=0

Aug 28 17:31:49 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.43.138 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=58 ID=47040 DF PROTO=TCP SPT=31403 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:32:25 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.43.138 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=58 ID=49832 DF PROTO=TCP SPT=33234 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:32:46 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.157.184 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=39941 DF PROTO=TCP SPT=39410 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:32:49 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.157.184 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=40407 DF PROTO=TCP SPT=39410 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:33:57 Alice kernel: IN=ppp0 OUT= MAC= SRC=92.62.101.21 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=112 ID=43616 PROTO=TCP SPT=33772 DPT=1080 WINDOW=65535 RES=0x00 SYN URGP=0

Aug 28 17:34:31 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.40.60 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=122 ID=42175 DF PROTO=TCP SPT=4904 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0

Aug 28 17:34:34 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.40.60 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=122 ID=42507 DF PROTO=TCP SPT=4904 DPT=445 WINDOW=16384 RES=0x00 SYN URGP=0

Aug 28 17:34:41 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.231.74 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=20016 DF PROTO=TCP SPT=9405 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:34:59 Alice kernel: IN=ppp0 OUT= MAC= SRC=82.106.16.134 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18040 PROTO=TCP SPT=32767 DPT=61012 WINDOW=65535 RES=0x00 SYN URGP=0

Aug 28 17:35:02 Alice kernel: IN=ppp0 OUT= MAC= SRC=82.106.16.134 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18045 PROTO=TCP SPT=32767 DPT=61012 WINDOW=65535 RES=0x00 SYN URGP=0

Aug 28 17:35:08 Alice kernel: IN=ppp0 OUT= MAC= SRC=82.106.16.134 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18047 PROTO=TCP SPT=32767 DPT=61012 WINDOW=65535 RES=0x00 SYN URGP=0

Aug 28 17:36:05 Alice kernel: rarian-sk-get-c[13487]: segfault at 00000000 eip b7cd18a3 esp bfd27dec error 4

Aug 28 17:37:18 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.157.184 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=27495 DF PROTO=TCP SPT=6854 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Aug 28 17:40:24 Alice syslogd 1.4.2: restart.

Aug 28 17:40:24 Alice klogd: klogd 1.4.2, log source = /proc/kmsg started.

Aug 28 17:40:25 Alice kernel: Linux version 2.6.24.7-desktop-1mnb (qateam@titan.mandriva.com) (gcc version 4.2.3 (4.2.3-6mnb1)) #1 SMP Mon Jul 28 15:12:10 EDT 2008

Aug 28 17:40:25 Alice kernel: BIOS-provided physical RAM map:

Link to comment
Share on other sites

Aug 28 17:35:08 Alice kernel: IN=ppp0 OUT= MAC= SRC=82.106.16.134 DST=87.16.190.124 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=18047 PROTO=TCP SPT=32767 DPT=61012 WINDOW=65535 RES=0x00 SYN URGP=0

Aug 28 17:36:05 Alice kernel: rarian-sk-get-c[13487]: segfault at 00000000 eip b7cd18a3 esp bfd27dec error 4

Aug 28 17:37:18 Alice kernel: IN=ppp0 OUT= MAC= SRC=87.16.157.184 DST=87.16.190.124 LEN=52 TOS=0x00 PREC=0x00 TTL=57 ID=27495 DF PROTO=TCP SPT=6854 DPT=135 WINDOW=60352 RES=0x00 SYN URGP=0

Do you see the segfault!

I think that will be why the system is rebooting. What's causing it I don't know, but going by your first post I would suggest it is something you have installed during your update. Maybe someone can offer more help from there.

Link to comment
Share on other sites

OK, I downloaded are ran Ultimate Boot CD. I didn't understand much, though. :P The one thing I did understand, though, was all the red writing stating that it found almost 9,000 errors. It was with Memtest86+ v1.70. On test 5 (block move, 64 moves), it came up with all the errors. Does it mean anything to anyone? Do I need to run it again and try and write down some more information?

 

After dan wrote his first answer, it came to mind another problem. Every once in a while, though rarely, my BIOS boot sequence and setup is changed. I was also having problems with the BIOS reading my usb connector (the added external one that has 4 usb ports in it). I do not know if these things are related to my present problem.

 

Thanks,

Kieth

Edited by Kieth
Link to comment
Share on other sites

The only way to know which ram stick is causing the trouble is to remove a stick and repeat the test until the culprit is located.

 

It is possible that it is your motherboard that is defective and not the ram itself. I believe the first thing I would try is to clear the CMOS. This effectively resets the bios and returns everything to factory defaults. There should be a clear CMOS jumper on your motherboard. If you are unable to locate this jumper, you can also remove the motherboard battery for 5 minutes or so. This will also clear the CMOS.

Link to comment
Share on other sites

I had a false memory problem once - so if your bios has an option to choose the optimised defaults, select this and run the test again. My bios was configured wrong for the memory, and so I got memory errors. Only Linux noticed it, Windows worked fine for years with the odd crash here or there :)

 

I'd check this first, if the problems continue, start removing memory and test and see where it is as daniewicz said.

Link to comment
Share on other sites

OK, this is what I've done so far, and what I've found out. I really appreciate the help. Last night while in bed, I got to thinking about what SilverSurfer said, that it's probably an up-dated program/file that's causing the problem. About a month ago (I think), I tried once again to get my Canon LBP 2900 laser printer to work, but w/o success. Doing that though, I installed the 2 drivers it needed: cndrvcups-common and cndrvcups-capt. Since I thought I would try to get the printer working another day, I decided to leave the files installed on my system. By the way, I mentioned earlier that my BIOS wasn't reading the usb hub (the external plugin type). Well, on the hub, I had this printer attached. After removing the files, I then plugged the hub back in, plugged the printer into it, and started up my system. The BIOS (which I had re-set by taking out the battery - as I couldn't find the CMOS reset plug), "saw" the hub and started up w/o a problem.

 

I checked the BIOS, and I couldn't find an optimized default option. Of course I do not really know where to look, but I read all the options I could find.

 

Also, I checked the memory, using the Ultimate Boot CD. I have 2 - 512 memory sticks. After taking them in and out, switching them from left to right, checking them together and individually, I found the problem. When both of them are in, I have a memory problem, when I have one or the other in, either in the left or right slot, there is no problem. I hoped it was just a dirty pin, so I took the memory sticks in a out a few times. In fact, the amount of errors changed drastically. Instead of thousands, it was 'just' hundreds.

 

Any ideas as to what I should do now?

 

Thanks,

Kieth

Link to comment
Share on other sites

Check that both memory sticks are the correct speed. Use something to clean the contacts on the memory sticks and put them back in again. I don't know what to suggest to clean them with though.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...