mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Professor Berkley Shands <berkley@seas.wustl.edu>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.0.18 tcsetattr on fd 0 when detached freezes system (RCU timeouts) (Centos 6.1 x86_64)
Date: Thu, 02 Feb 2012 16:09:40 -0600	[thread overview]
Message-ID: <4F2B09A4.7040005@seas.wustl.edu> (raw)
In-Reply-To: <4F2A4B22.7020909@msgid.tls.msk.ru>

I built my .config from the redhat .config provided in 2.6.32-131 using 
make oldconfig.
that failed miserably. I then used one based on 2.6.39.4, which actually 
booted, but I get these
lockup errors, RCU timeouts, ...

The system died right away on the tcsetattr(), (which also did not 
return any error).
And my simple test case crashed all the time. Looked rather suspicous...
Now after a week, *ALL* my 3.0.18 boxes lock up (other than sitting 
IDLE, any load eventually
causes the system to stop scheduling). That is 32 core 6282's, 3.46GHz 
Nehalems, 2.3 GHz 2374's...
I have to assume the tcsetattr() is an artifact at this point.
Without building all the kernels in between 2.6.32.55 and 3.0.18, I 
needed a starting point
for the .config that works. Usually it is something unnoticed that 
needed to be updated
that make oldconfig didn't point out. Things do change that I can't keep 
current on. :-)

So it appears that it has to be my configuration. Hence the request for 
a .config I can compare against to see
what is wrong / misconfigured / not configured etc.

Berkley


      reply	other threads:[~2012-02-02 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28  0:43 Professor Berkley Shands
2012-01-28  6:55 ` Michael Tokarev
     [not found]   ` <4F283B40.1070200@seas.wustl.edu>
2012-02-02  8:36     ` Michael Tokarev
2012-02-02 22:09       ` Professor Berkley Shands [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=4F2B09A4.7040005@seas.wustl.edu \
    --to=berkley@seas.wustl.edu \
    --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®