From: Simon Braunschmidt <braunschmidt@corscience.de>
To: zergio <zergio@isma.kharkov.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.27 suddenly hangs
Date: Mon, 15 Nov 2004 12:11:40 +0100 [thread overview]
Message-ID: <41988EEC.3040708@corscience.de> (raw)
In-Reply-To: <419886CE.2030304@isma.kharkov.ua>
I have a similar problem at the moment, i have setup my box with gentoo
and now i get hardlocks from time to time (time < 1.5 days), happens
with and without x, kernel 2.4.27 untainted, with apic on and off, acpi
on and off, apm on and off...
@zergio: Can you tell me if it only happened with 2.4.27?
The system is really stuck when it crashes. My wireless keyboard has a
led to indicate traffic, an when system hangs, not even the led would
blink, it just stays in either on or off state (its normaly off). No
disk activity, mouse is locked, display remains unchanged (x.org nv or
plain (non-fbdev) console). Havent tried so far to reach the box over
network, but is suspect it will not work.
@developers:
Maybe thats a hint, could it be that a broken keyboard induces such
behaviour?
Im going to change kernel to 2.4.24 (had uptimes > 14 days with it) and
see if it helps.
As far as i can see, nothing was written to the logs, no messages, it
just peacefully dies...
zergio schrieb:
> Hello, all!
> I‘m not sure that the below problem is kernel related, however, I think,
> this mailing list is the best place to start. I've got 2x1.8 Xeon on
> Intel SE7500CW2 motherboard with Intel SCSI RAID (GDT driver). The
> system powered by Red Hat Linux 7.3 with custom kernel version 2.4.27.
> Occasionally, the system just hangs, without giving any error messages
how long is occasionaly?
> to syslog or any panic-like messages to the screen. No response to ping.
> Usually it happens on weekends in early hours, but not at particular
> time and day, when users’ activity is minimal. Couple of times the last
> few messages before, the hang had strange timestamps. It seems like the
> system time entered a TIME LOOP within a period of 1 second.
> Nov 6 05:37:31 service dhcpd: Message...
> Nov 6 05:37:32 service named: Message...
> Nov 6 05:37:31 service named: Message...
> Almost all the time last messages came from different services, except
> three times, when mgetty was the last. I'd updated mgetty, pppd, kernel
> (from 2.4.20), BIOS, dhcpd etc., however, the problem remains.
> Can anyone tell me, how I can detect, what application or hardware cause
> such a problem.
> Any ideas would be appreciated.
> Thank you in advance
>
> These are services being run on the server:
> gpm
> named
> iptables
> crond
> ldap
> smb
> xinetd (swat amanda)
> autofs
> nfs
> qmail
> sqwebmail
> dhcpd
> ups
> sshd
> firebird
> ntpd
> httpd
> arpwatch
> drwebd
> mgetty
> pppd
> postgresql
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-11-15 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 10:37 2.4.27 suddenly hangs zergio
2004-11-15 11:11 ` Simon Braunschmidt [this message]
2004-11-15 11:54 ` zergio
2004-11-15 14:22 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41988EEC.3040708@corscience.de \
--to=braunschmidt@corscience.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zergio@isma.kharkov.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox