linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Ricard <g_ricard@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Lombard hard freeze (still there)
Date: Tue, 2 May 2000 12:13:17 -0700 (PDT)	[thread overview]
Message-ID: <20000502191317.779.qmail@web1704.mail.yahoo.com> (raw)


I am wondering if any of the developers who do kernel
related work on LinuxPPC have any suggestions for us
on how to deal with this. If I knew how to do the
debugging work and trace the problem to its root I
would.

--- Bernhard Reiter <bernhard@intevation.de> wrote:
> On Tue, May 02, 2000 at 01:22:21PM +0200, Albrecht
> Dress wrote:
> > > my problems with the hard freezes still
> continue.
> > > I have not come to any idea what is causing it.
> > > Several methods of trying to encircle the
> problem area failed.
> >
> > Sorry, I am afraid I lost some messages of this
> thread.  Hope this is not
> > too outdated ;-)
>
> You can look it up in the webarchive.
>
http://lists.linuxppc.org/listarcs/linuxppc-dev/200004/threads.html
>
>
> > I _have_ a Lombard running without problems.  So
> just some ideas which
> > might give you some more information.  Maybe you
> should try to work from
> > the first virtual (text) console (ctrl-opt-F1).
> If the kernel panics
> > (which is does very likely) it will emit this
> information there, but you
> > will NEVER see it if you are in X, and it does not
> necessarily go into
> > /var/log/messages.
>
> The hard freeze's low temperature prohibits all
> output.
> Never got any error message.
>
> > Did you check the serial port drivers?  I rember
> there were some problems
> > if you use the serial.c under LinuxPPC.  You do
> not need it, the right one
> > is macserial.c.  I could trigger panics on the
> Lombard and on my old 7300
> > by just typing "cat /dev/ttyS0 > /dev/null".
>
> Yes I check the serial driver, built a kernel
> without usb and
> serial support at all. But the symptoms are still
> there.
>
> I have 192 MB of RAM though and a 10 Gb drive ,
> these are the only
> differences which I think my machine might have to
> other lombards.
>
> 	Bernhard
>
> --
> Professional Service around Free Software
>     (intevation.net)
> The FreeGIS Project				            (freegis.org)
> Association for a Free Informational Infrastructure
>           (ffii.org)
>

> ATTACHMENT part 2 application/pgp-signature


=====
Gabriel Ricard
g_ricard@yahoo.com

Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

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

             reply	other threads:[~2000-05-02 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-02 19:13 Gabriel Ricard [this message]
2000-05-02 20:20 ` Lombard hard freeze (still there) Michael Schmitz
2000-05-03 10:22   ` Mario Scarpa
  -- strict thread matches above, loose matches on Subject: below --
2000-05-03 17:51 Gabriel Ricard
2000-05-04 12:32 ` Mario Scarpa
2000-05-04 16:07   ` Michael Schmitz
2000-05-04 22:31     ` Mario Scarpa
2000-05-02  8:49 Bernhard Reiter
2000-05-02 11:22 ` Albrecht Dress
2000-05-02 11:40   ` Bernhard Reiter

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=20000502191317.779.qmail@web1704.mail.yahoo.com \
    --to=g_ricard@yahoo.com \
    --cc=linuxppc-dev@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).