linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: ppc32 lockups with 2.6
Date: Thu, 06 Nov 2003 22:34:26 +0100	[thread overview]
Message-ID: <3FAABE62.4090804@g-house.de> (raw)
In-Reply-To: <3FA5698A.9000905@g-house.de>


as nobody seems to answer,

yes, i know, if the problem does not occur to other people, it's not
worth fixing it. and PReP machines seem to be some kind of "exotic"
(read: outdated) anyways. but i don't have the skills fixing it :-(

so, if at least someone could point me to something i might have
forgotten to look at, or how to get an oops message out of this here.
would be nice if it turns out to be a user-error only.

i also filed a bug in bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=1494

Thanks for reading,
Christian.

--
BOFH excuse #128:

Power Company having EMP problems with their reactor


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

  reply	other threads:[~2003-11-06 21:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 20:31 ppc32 lockups with 2.6 Christian Kujau
2003-11-06 21:34 ` Christian [this message]
2003-11-10 18:50   ` linas
2003-11-10 20:32     ` Tom Rini
2003-11-10 22:39     ` Christian
2003-11-10 23:57       ` linas
2003-11-11  0:25         ` Christian
2003-11-11 15:36           ` Tom Rini
2003-11-13  0:59             ` Christian Kujau
2003-11-13 17:47               ` Tom Rini
2003-11-13 23:56                 ` Christian Kujau
2003-11-14 15:57                   ` Tom Rini
2003-11-18 12:33                   ` Christian Kujau
2003-11-18 14:14                     ` Christian Kujau
2003-11-21 15:25                       ` Christian Kujau
2003-11-21 17:54                         ` Tom Rini

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=3FAABE62.4090804@g-house.de \
    --to=evil@g-house.de \
    --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).