All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny Cox <Danny.Cox@ECWeb.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-mm2 Surprises
Date: Wed, 31 Dec 2003 09:17:26 -0500	[thread overview]
Message-ID: <1072880245.1146.11.camel@vom> (raw)

I've found some surprises in my testing of 2.6.0-mm2 on my RH 9 box.

First, 'make menuconfig' doesn't work.  It paints the top 8 or so lines,
and freezes.  gnome-terminal begins using as much CPU as it's allowed. 
This is similar to bug 959 in bugme.osdl.org, but changing CHILD_PENALTY
from 90 to 130 didn't fix the problem.

Second, simply resizing gnome-terminal results in the same behavior. 
Certainly, this may be a gnome thing.

Third, 'rpm' cannot install packages.  It always exists with:

rpmdb: unable to join the environment
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db3 - Resource temporarily
unavailable (11)
error: cannot open Packages database in /var/lib/rpm

11 is EAGAIN, but an strace revealed little to the uninitiated (me).

rpm also fails in the same way with --rebuilddb.  /var/lib/rpm/__db.001
is zero length BTW.  That is almost certainly wrong.  Of course, these
both work fine with a 2.4.20 kernel.

Sorry if these (or some variant thereof) have already been reported
here.

Thanks for your time, and please note that I'm not subscribed to
linux-kernel.  If you need more info, please don't hesitate to ask.

-- 
Daniel S. Cox
Electronic Commerce Systems


             reply	other threads:[~2003-12-31 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 14:17 Danny Cox [this message]
2003-12-31 15:22 ` 2.6.0-mm2 Surprises Davide Libenzi
2003-12-31 15:27 ` Felipe Alfaro Solana

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=1072880245.1146.11.camel@vom \
    --to=danny.cox@ecweb.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.