From: Trent Lloyd <lathiat@bur.st>
To: linux-kernel@vger.kernel.org
Subject: Re: Server suddenly freezes but awakes upon SysRq!?
Date: Thu, 4 Mar 2004 21:43:44 +0800 [thread overview]
Message-ID: <20040304134343.GA15402@thump.bur.st> (raw)
In-Reply-To: <20040304131915.GA15713@westend.com>
I've seen similar problems where the machines userspace seems to die but
it still pings etc and requires a reboot
This was on just P1/PPRO hardware, never figured it out. havent seen it
for quite some time
Haven't tried SQSRQ, if I see it again I'll try that.
Cheers,
Trent
Sixlabs
> Hello
>
> We have some problems with a server that started to suddenly freeze
> every now and then which means that it does react to ping and tcp
> connects but does not allow a login nor returns the shell or does syslog
> write anything to disc or network.
>
> Funnily it always immediately awakes when we presses 'AltGr+SysGr+h'
> although a login on the console did not work before.
>
> What could be the cause of this "sleep" mode if a sysrq ends it?
> We noticed that at least 1-2 freezes occured right after accessing the
> external usb2.0 backup harddrive.
>
> The server is a dual-p3 with a 3ware ide-scsi RAID and very low load as
> postfix+apache server.
>
> bye,
>
> -christian-
>
> Some bits of the configuration:
>
> ...
> CONFIG_MPENTIUMIII=y
> ...
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> CONFIG_HIGHIO=y
> # CONFIG_MATH_EMULATION is not set
> CONFIG_MTRR=y
> CONFIG_SMP=y
> CONFIG_NR_CPUS=32
> # CONFIG_X86_NUMA is not set
> # CONFIG_X86_TSC_DISABLE is not set
> CONFIG_X86_TSC=y
> CONFIG_HAVE_DEC_LOCK=y
> #
> # General setup
> #
> CONFIG_NET=y
> CONFIG_X86_IO_APIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_PCI=y
> # CONFIG_PCI_GOBIOS is not set
> # CONFIG_PCI_GODIRECT is not set
> CONFIG_PCI_GOANY=y
> CONFIG_PCI_BIOS=y
> CONFIG_PCI_DIRECT=y
> CONFIG_ISA=y
> CONFIG_PCI_NAMES=y
> # CONFIG_EISA is not set
> # CONFIG_MCA is not set
> CONFIG_HOTPLUG=y
> ...
> # CONFIG_ACPI is not set
> CONFIG_ACPI_BOOT=y
> ...
> CONFIG_PNP=y
> CONFIG_ISAPNP=m
> ...
> CONFIG_DEBUG_STACKOVERFLOW=y
> # CONFIG_DEBUG_HIGHMEM is not set
> # CONFIG_DEBUG_SLAB is not set
> # CONFIG_DEBUG_IOVIRT is not set
> CONFIG_MAGIC_SYSRQ=y
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_FRAME_POINTER is not set
> CONFIG_LOG_BUF_SHIFT=0
>
> --
> Christian Hammers WESTEND GmbH | Internet-Business-Provider
> Technik CISCO Systems Partner - Authorized Reseller
> L?tticher Stra?e 10 Tel 0241/701333-11
> ch@westend.com D-52064 Aachen Fax 0241/911879
>
> -
> 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/
--
[ Trent "Lathiat" Lloyd lathi@sixlabs.org ]/ "You sure as hell shouldn't be \
[ tlhIngan Hol Dajatlh'e www.sixlabs.org ]| fingering my toaster" -Linus |
[ GPG Key Id: 0x04AB3C5D www.bur.st ]| Torvalds, LCA2003 Speakers dinner|
[ IPv6 Conference http://conf.sixlabs.org ]\ talking about ipv6 with me /
prev parent reply other threads:[~2004-03-04 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 13:19 Christian Hammers
2004-03-04 13:43 ` Trent Lloyd [this message]
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=20040304134343.GA15402@thump.bur.st \
--to=lathiat@bur.st \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®