mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alejandro Riveira Fernández" <alejandro.riveira@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Various OOps with 2.6.27-rc5
Date: Tue, 09 Sep 2008 00:21:45 +0200	[thread overview]
Message-ID: <1220912505.17965.0.camel@Varda> (raw)
In-Reply-To: <20080908135736.5d0c3ef8.randy.dunlap@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

El lun, 08-09-2008 a las 13:57 -0700, Randy Dunlap escribió:
> On Mon, 08 Sep 2008 22:36:22 +0200 Alejandro Riveira Fernández wrote:
> 
> > El lun, 08-09-2008 a las 12:46 -0700, Randy Dunlap escribió:
> > 
> > [ ... ]
> > > > The dmesg including oopses
> > > 
> > > Actually they are INFO: messages with getnstimeofday() being stuck,
> > > similar to a few other reports on lkml.
> > 
> >  So is it useful to report them or i just do:
> >  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> >  And forget about it ??
> 
> I'm not sure.  I haven't followed the other problem reports very
> closely.  AFAIK, it represents a real bug, but if your system is
> running OK, you could just ignore it...
 
 Ok; thank you for your time
 Cheers


> 
> 
> ---
> ~Randy
> Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
> http://linuxplumbersconf.org/

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-09-08 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 19:21 Alejandro Riveira Fernández
2008-09-08 19:46 ` Randy Dunlap
2008-09-08 20:36   ` Alejandro Riveira Fernández
2008-09-08 20:57     ` Randy Dunlap
2008-09-08 22:21       ` Alejandro Riveira Fernández [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=1220912505.17965.0.camel@Varda \
    --to=alejandro.riveira@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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

Powered by JetHome