public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Fw: epoll oops on 2.6.x
Date: Fri, 14 May 2004 01:58:00 +0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0405131844560.12980@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <40A3EAF6.1000902@cs.uwaterloo.ca>

On Thu, 13 May 2004, Randy.Dunlap wrote:

> 
> Davide,
> >From the linux-ia64 mailing list, in case you didn't see it.....
> 
> Begin forwarded message:
> 
> Date: Thu, 13 May 2004 17:39:02 -0400
> From: Louay Gammo <lgammo@cs.uwaterloo.ca>
> To: linux-ia64@vger.kernel.org
> Subject: epoll oops on 2.6.x
> 
> 
> Hi,
> 
> I keep getting these oopses and kernel panics when I overload my 
> Itanium-2 box with http requests. I had these
> oopses in 2.6.1 through 2.6.5 and it is consistently happening while 
> using epoll, but not select. Also, these oopses
> happen only on IA-64.
> 
> I am including some of these oopses as attachements. I am not sure what 
> the 'normal' bug reporting mechanism is
> for IA-64 kernels.

I'm getting this from Randy, since I was not subscribed to linux-ia64. Now 
I am. I took a quick look at it and so far the clue is completely missing. 
Only one of the oops actually happen inside epoll, even if the other ones 
comes typically from __wake_up_common() (others from vfs_read(), that is 
quite unrelated), that let me think that it might be epoll related (epoll 
has a wait queue item dropped in). Can you try a few experiments?

1) Disable pre-emption (if enabled)
2) Load the server thru loopback
3) #define DEBUG_EPOLL 10

(Your machine does not look too much in shape looking at INIT messages 
though)



- Davide


  reply	other threads:[~2004-05-14  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 21:39 epoll oops on 2.6.x Louay Gammo
2004-05-14  1:58 ` Davide Libenzi [this message]
2004-05-14 22:23 ` Fw: " Louay Gammo
2004-05-15  0:49 ` Davide Libenzi
2004-05-17 16:06 ` Louay Gammo
2004-05-17 16:27 ` Davide Libenzi

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=Pine.LNX.4.58.0405131844560.12980@bigblue.dev.mdolabs.com \
    --to=davidel@xmailserver.org \
    --cc=linux-ia64@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