From: Andrew Morton <akpm@osdl.org>
To: Yaoping Ruan <yruan@cs.princeton.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel hangs up - possible sendfile() epoll() bug?
Date: Fri, 15 Aug 2003 16:43:34 -0700 [thread overview]
Message-ID: <20030815164334.1e37b5b8.akpm@osdl.org> (raw)
In-Reply-To: <3F3D672D.1AF660B6@cs.princeton.edu>
Yaoping Ruan <yruan@cs.princeton.edu> wrote:
>
> Hi,
>
> Recently we updated a user space web server to use the sendfile() and
> epoll() interface, and tried to measure the performance with SpecWeb99
> benchmark. As the load increases, e.g a SpecWeb99's target score of 600
> connection, the kernel sometimes hangs up without any logging
> information, and the only way left is to push the reset button to
> reboot.
>
> We also made similar updates to use sendfile() and kevent() on FreeBSD
> and achieved a score of 1000 connections. Thus the possibility of
> application bug is low (also it is a user space server). Before the
> sendfile() and epoll() change, it was also fine but only could get a
> SpecWeb99 score of 500.
>
> The kernel we were using was 2.4.21 with the epoll patch applied. Since
> the epoll man pages mention the interface is stabilized in 2.5.66, we
> also tried 2.5.66 but didn't see anything better. The machine is a PIII
> Xeon processor-based Intel server motherboard, with 2 CPU support but
> only 1 is used, Maxtor Diamond IDE disk, Promise Ultra DMA 66
> controller, and a single Netgear GA621 gigabit ethernet network adapter.
>
Definitely a kernel bug.
Could you please test 2.6.0-test3? If that has the same problem then
some initial steps would be:
- Boot the kernel with the "nmi_watchdog=1" option on the kernel boot
command line. (It needs to be an SMP-compiled kernel for this to work.
Or one which has the local APIC enabled in config)
- Make sure that /proc/sys/kernel/sysrq was set to `1' after booting.
- Can you still ping the machine after it hangs up?
- Type ALT-SYSRQ-T and/pr ALT-SYSRQ-P on the keyboard, see if you get a trace.
- ALT-SYSRQ-M may be interesting too (memory stats)
If the nmi watchdog doesn't generate a trace then the sysrq keys should do
so.
If the above does not provide us with enough information to solve the bug
then the next step would be for you to provide sufficient material for a
kernel developer to reproduce the problem.
Thanks.
next prev parent reply other threads:[~2003-08-15 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 23:05 Yaoping Ruan
2003-08-15 23:43 ` Andrew Morton [this message]
2003-08-22 4:41 ` kernel hangs up running web server Yaoping Ruan
2003-08-22 5:19 ` Andrew Morton
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=20030815164334.1e37b5b8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yruan@cs.princeton.edu \
/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®