linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: linuxppc-embedded@lists.linuxppc.org, all@cideas.com
Subject: Re: init is running (didn't trigger the wait queue panic)
Date: Tue, 13 Jun 2000 23:33:35 -0400	[thread overview]
Message-ID: <3946FD0F.7545C068@embeddededge.com> (raw)
In-Reply-To: m131qWd-001SyaC@bucks


diekema_jon wrote:

>         I tried running init again with Linux 2.4.0-test1-ac10
>         (through changeset 1.247.1.6 00/06/12 18:04:09-04:00
>         dmalek@geefour.netx4.com), and I was surprised to find that it
>         worked.  Previously, init was triggering a wait queue panic in the
>         scheduler.


I forget that if you are not on the BitKeeper mailing list you don't
see the updates people make.  Wolfgang sent me a stack backtrace that
pointed right to a problem in the uart driver with wait queues.  They
were not initialized properly (actually, not at all :-), so you would
get erratic behavior for any type of uart open/close.  This was fixed
a couple of days ago.

This affects both 8xx and 8260, so suck down the latest 2.4.0 sources
and give them a test.

Now, I will do some 8260 updates, hopefully to fix that irritating
Ethernet bug and the timer stuff you sent me.  I'll try to be better
about posting update message to this list (if people want that info).


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-06-14  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-13 13:14 init is running (didn't trigger the wait queue panic) diekema_jon
2000-06-14  3:33 ` Dan Malek [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=3946FD0F.7545C068@embeddededge.com \
    --to=dan@netx4.com \
    --cc=all@cideas.com \
    --cc=diekema@bucks.si.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).