All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Scarpa <m.scarpa@mondonet.net>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Gabriel Ricard <g_ricard@yahoo.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Lombard hard freeze (still there)
Date: Wed, 03 May 2000 12:22:11 +0200	[thread overview]
Message-ID: <390FFDD3.410A690C@mondonet.net> (raw)
In-Reply-To: Pine.LNX.4.10.10005022156240.13541-100000@opal.biophys.uni-duesseldorf.de


Michael Schmitz wrote:
>
> > 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.
>
> It's a bit tough to debug kernel stuff on a machine like the Lombard if it
> has no serial port to attach a console terminal or even a kernel debugger
> to. It's even harder to remote debug such a machine over a mailing list
> :-)

Indeed ;-)

Here's my setup: Lombard with 6GB HD and 64MB RAM (just like yours
I guess); my probs started with USB support compiled in the kernel:
even if it does not lead to a total freeze so often (would say very
seldom indeed), I still get mouse freeze under X when heavy network
activity is being made (last time 5 mins ago getting a big attachment).
Some other times I get a kernel panic during the boot when initializing
the serial interfaces (no, I have NOT support for standard serial
but only MAC serial compiled into the kernel).
This is why I was thinking about some USB/serial code problem but I
agree we need some debug output to work on.

Using Debian 2.2 and XF86_FBDev with kernel 2.2.15pre20 from Paul's
tree.

Thinking about the debug way you suggest, it comes to my mind another
question not so related to the prob: is there a USB->serial converter
around ? Is there one of this devices supported by Linux ? On PPC ?

Ciao,

--
Mario Scarpa

Mondonet NOC
Phone: +39 06 52.47.37.02

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

  reply	other threads:[~2000-05-03 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-02 19:13 Lombard hard freeze (still there) Gabriel Ricard
2000-05-02 20:20 ` Michael Schmitz
2000-05-03 10:22   ` Mario Scarpa [this message]
  -- 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=390FFDD3.410A690C@mondonet.net \
    --to=m.scarpa@mondonet.net \
    --cc=g_ricard@yahoo.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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.