All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Laures <GoM@Taygeta.gom.dorm.org.cybercable.fr>
To: GoM@Taygeta.gom.dorm.org.cybercable.fr
Cc: mlan@cpu.lu, linux-pmac@samba.anu.edu.au,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: [ANNC] New release of PlanB
Date: Mon, 5 Apr 1999 21:26:16 +0000 (Local time zone must be set--see zic manual page)	[thread overview]
Message-ID: <199904052126.VAA00422@Taygeta.gom.dorm.org> (raw)
In-Reply-To: <199904042337.XAA00413@Taygeta.gom.dorm.org>


On  4 Avr, Guillaume Laures wrote:
>
> 
> Anyway I must report that I had several crashes recently (actually 3 in
> a week, which is definitely much for linux) since I upgraded to 2.2.5,
> with the planb as well. I have only controlfb in the kernel on a
> 8600/250 and use the XFB, and i get hard locks when switching quickly
> beetwen X and console.
> Don't know to what it could be related to. Can other people comment on
> this ?

I might add that I run Login.app as X starter, and it is not really
reliable (sometimes X is frozen, Login.app takes 90% of CPU and all I
can do is telnet from another machine, su and kill it).
This may more likely be my problem.


BTW, for people looking into raid, I can provide a patch for 2.2.5. I
don't send it right now cause it includes planB as well...

-- 
---
Guillaume Laurès laures@esiea.fr


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-04-05 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-04 20:44 [ANNC] New release of PlanB Michel Lanners
1999-04-04 23:37 ` Guillaume Laures
1999-04-05 21:26   ` Guillaume Laures [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=199904052126.VAA00422@Taygeta.gom.dorm.org \
    --to=gom@taygeta.gom.dorm.org.cybercable.fr \
    --cc=linux-pmac@samba.anu.edu.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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.