Re: [S.u.S.E. Linux] General Protection error
Hi! Trying to kill the keyboard, laszlo@idt.net produced:
On Sun, 31 May 1998, Wolfgang Weisselberg wrote:
Trying to kill the keyboard, laszlo@idt.net produced:
I'm getting a very regular General Protection error, on the following system ( set up to be a mail and www server runing X ). [...] After every few hours, the system gets semi locked. It responds to <alt><Function key> commands, but not to <cntrl><alt><del>. <enter> at any screen, except login prompt gives the following.
general protection error: 0000 cpu : 0 eip : 0010:[<00124c207>]
Are the numbers the same every time or do they cange? Did you compile this kernel?
Well, did you compile the kernel? If yes, did you apply any patches, which ones? Do the numbers change? Which kernel is it, if you didn't compile it yourself (uname -a)? Does the machine have a constant internet or intranet connection, if not, did it die while connected or while stand-alone? Is it connected now? (I am thinking of an attack, maybe via nestea or so)
What does /var/log/messages say about the crashes?
What do the logs say?
The case is located directly in the path of the air conditioner. And the system crashed repeated at night. There seems to enough air circulation since I had a secondary cooling fan installed on the system.
All fans working, actually the power supply vents are the coolest of any or the many systems running here.
Crashes at night ... all fans working ... hmmm ... Does someone probably switch of A/C at night? (There are people who think A/C is for the comfort of humans ... let's save some energy and fry the computers :-/ )
I will run it with an open case, Since installing the network card, prior to the OS. The case has been on.
Are you 110ure your memory chip(s) is/are OK (no, works under Win does
Machine never had windows on it, but the memory seems fine running the debian distributuion. It has been up for almost 20 hours now.
Thow it a couple (like 20) kernel compilations, see if it still stands. If yes, the memory should be OK. What kernel is the Debian distri running (uname -r)? -Wolfgang -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Laszlo On Tue, 2 Jun 1998, Wolfgang Weisselberg wrote:
Hi!
Trying to kill the keyboard, laszlo@idt.net produced:
On Sun, 31 May 1998, Wolfgang Weisselberg wrote:
Trying to kill the keyboard, laszlo@idt.net produced:
I'm getting a very regular General Protection error, on the following system ( set up to be a mail and www server runing X ). [...] After every few hours, the system gets semi locked. It responds to <alt><Function key> commands, but not to <cntrl><alt><del>. <enter> at any screen, except login prompt gives the following.
general protection error: 0000 cpu : 0 eip : 0010:[<00124c207>]
Are the numbers the same every time or do they cange? Did you compile this kernel?
Well, did you compile the kernel? If yes, did you apply any patches, which ones? Do the numbers change?
Which kernel is it, if you didn't compile it yourself (uname -a)? Does the machine have a constant internet or intranet connection, if not, did it die while connected or while stand-alone? Is it connected now? (I am thinking of an attack, maybe via nestea or so)
I compiled the ethernet support for the 'tulip' chip into the kernel v 2.0.33. Debian was running a much older kernel, 2.0.2? There is a constant internet connection over a T1 line, but doubt that the failures was due to attacks. I think that it may just be a heat issue. Without the case cover, it's been up for 10 hours. I find it difficult to accept, there was no noticable head buildup. And I had taken all precautions on providing air conditining and ventilation on specially installed racks. Oh well. I hope that it was a heat issues, as the solutions are the easiest to implement. Thanks, Laszlo -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi! Trying to kill the keyboard, laszlo@idt.net produced:
I compiled the ethernet support for the 'tulip' chip into the kernel v 2.0.33. Debian was running a much older kernel, 2.0.2? There is a constant internet connection over a T1 line, but doubt that the failures was due to attacks.
Well, I remember there is an attack against unpatched 2.0.33 kernels that result in exactly that failure mode ... but I'll have to look into the bugtraq archives (and I am offline, so that'll take some time). I _think_ it was nestea, however: <A HREF="ftp://ftp.suse.com/pub/suse_update/kernel/ipfragment-2.0.33"><A HREF="ftp://ftp.suse.com/pub/suse_update/kernel/ipfragment-2.0.33</A">ftp://ftp.suse.com/pub/suse_update/kernel/ipfragment-2.0.33</A</A>> (Patch against the "nestea" attack), explanation is in <A HREF="http://www.suse.de/safety/nestea.html"><A HREF="http://www.suse.de/safety/nestea.html</A">http://www.suse.de/safety/nestea.html</A</A>> I'll translate the main gist (since it's in German) An error in the TCP/IP code of the kernel was found that allows anyone to crash the computer. Similar to the "Teardrop"-bug (fixed in 2.0.32) a specially crafted fragmented packet overwrites the memory, leading to a crash or reboot. Name: "syndrop" or "nestea". Another DoS-Attack (Denial of Service) exploits the fact that oversized IP-Packets get logged, bombarding a computer with these leads to it doing nothing else than logging them. [and filling up /var/log] Thanks to the usual swift reaction of the Linux-community a patch is already aviable for both problems. You are strongly urged to use it on all computers directly reachable from the internet. The patch is aviable from our FTP-site. [and other places, of course]
I think that it may just be a heat issue. Without the case cover, it's been up for 10 hours. I find it difficult to accept, there was no noticable head buildup. And I had taken all precautions on providing air conditining and ventilation on specially installed racks.
I know that my HD gets just over handwarm in the case, but not noticably warm at all all open-cased. Ok, the air circulation may not be perfect, but it is there.
Oh well. I hope that it was a heat issues, as the solutions are the easiest to implement.
Do patch in the patch, as well - or, if possible, sever the T1-connection while debugging. -Wolfgang -- PGP 2 welcome: Mail me, subject "send PGP-key". If you've nothing at all to hide, you must be boring. Unsolicited Bulk E-Mails: *You* pay for ads you never wanted. Is our economy _so_ weak we have to tolerate SPAMMERS? I guess not. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Anyone? Kernel.org is well..., slow. (no surprise since the new stable kernel has been released) but how about a fast ftp site? ;-) Dana -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
ftp.funet.fi Dana J. Laude wrote:
Anyone? Kernel.org is well..., slow. (no surprise since the new stable kernel has been released) but how about a fast ftp site? ;-)
Dana
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dana J. Laude wrote:
Anyone? Kernel.org is well..., slow. (no surprise since the new stable kernel has been released) but how about a fast ftp site? ;-)
Never mind, found a good link off linuxhq.com. Dana -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
dana＠ntd.net -
laszlo＠idt.net -
satan＠nfinity.com -
weissel＠jupiter.ph-cip.uni-koeln.de