The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unable to handle kernel NULL pointer / tty / 2.6.31-vanilla/ still persists
Date: Tue, 15 Sep 2009 08:04:55 -0700	[thread overview]
Message-ID: <20090915150455.GA22282@suse.de> (raw)
In-Reply-To: <200909151032.53683.denys@visp.net.lb>

On Tue, Sep 15, 2009 at 10:32:53AM +0300, Denys Fedoryschenko wrote:
> Kernel 2.6.31-rc7
> x86 , 32-bit
> gcc 4.4.1
> 
> Happened on heavy network load, looks like as previous one, seems problem 
> still persists.
> It is hyperthreading Xeon, as i heard on such CPU's SMP bugs most easy to 
> trigger. But for me triggered after few days of operation.
> 
> Here is oops:

Ugh.

What are you doing at the time of this happening?  What kind of load is
on the system?

thanks,

greg k-h

  reply	other threads:[~2009-09-15 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  7:32 unable to handle kernel NULL pointer / tty / 2.6.31-vanilla/ still persists Denys Fedoryschenko
2009-09-15 15:04 ` Greg KH [this message]
2009-09-15 16:06   ` Denys Fedoryschenko
2009-09-17  9:35 ` Frederic Weisbecker
2009-09-17  9:58   ` Denys Fedoryschenko

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=20090915150455.GA22282@suse.de \
    --to=gregkh@suse.de \
    --cc=denys@visp.net.lb \
    --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