From: Luyseyal <luyseyal@austin.cc.tx.us>
To: linuxppc-dev@lists.linuxppc.org
Subject: lockups in 129 on pmac 6500
Date: Mon, 07 Dec 1998 15:18:28 -0600 [thread overview]
Message-ID: <366C4624.84A1E42A@austin.cc.tx.us> (raw)
i have a pmac 6500/225 (603ev) running an almost stock linuxppc. 2.1.127
worked
fine (except the annoying speaker bug), but apparently the PPC update in
129 killed
something. regardless of configuration, it locks up right after it
parses the Open
Firmware device tree.
i'm not on this list, so please write me directly or CC.
also, i'm not a developer, so if you want a bug report you'll have to
explain how to generate one for a kernel (i've only used gdb on a few
minor prog's).
thanks,
-l
--
By the way, ALL software projects are done by iterative prototyping.
Some companies call their prototypes "releases", that's all.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT d- s+:- a-- C++$ UL(++++)>$ P L++ E--- W++ N-- !o !K w(---) !O M(--)
!V PS--(+++) PE Y+ PGP- t+* !5 X(-) R(*)
[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1998-12-07 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=366C4624.84A1E42A@austin.cc.tx.us \
--to=luyseyal@austin.cc.tx.us \
--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).