From: kevin diggs <diggskevin38@gmail.com>
To: VAUGHAN Jay <jay.vaughan@thalesgroup.com>
Cc: Ian Lance Taylor <iant@google.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: hail marry (booting PowerMac 8600)
Date: Thu, 03 Feb 2011 21:10:00 -0000 [thread overview]
Message-ID: <AANLkTikVOFHcjtMtTUMHrEtqSipFnGOhieH_3fjvmYB7@mail.gmail.com> (raw)
In-Reply-To: <30863_1296722358_4D4A69B6_30863_16193_1_4D4A69B5.8090908@thalesgroup.com>
Hi,
There is also a thread (BootX) on linux power pc kernel list (see
linuxppc-dev mailing list on penguinppc.org). I find it very curious
that it can't even do simple device queries. I don't even think
inquiry works.
I think I'm gonna try to move the root disk to the 53c94 controller.
Or maybe I'll borrow the pci ide controller I have in another system
and move it to that. Debugging this will be ALOT easier if the mesh is
not required for 'operation' of the system.
kevin
On Thu, Feb 3, 2011 at 2:39 AM, VAUGHAN Jay <jay.vaughan@thalesgroup.com> wrote:
> On 02/03/2011 02:58 AM, Ian Lance Taylor wrote:
>> kevin diggs<diggskevin38@gmail.com> writes:
>> > Uh ... What does your gut tell you about whether this could be a
>> > compiler bug?
>> My gut tells me that it is very unlikely. However, compiler bugs have
>> been known to happen.
>
> I just want to encourage you guys to continue this discussion until some sort of
> meaningful conclusion can be made about what is going on with the differences;- such
> circumstances are precisely what some of us lurkers are here for.
>
> My gut feeling is that the narrowing-down process is going to lead to such a conclusion,
> eventually, and that this will be a Eureka! moment for a few of us working on PPC-related
> work with gcc .. I can't contribute much else, but I am definitely watching this thread
> with interest and from my end I'll be looking at mesh.c today ..
>
> (Not worth setting up gdb-kernel for this, to find out where exactly the hang is
> occurring? Doesn't linux-ppc have a sysreq-like inline debugger, somewhere?)
>
> --
> ; Thales Austria GmbH
> Jay Vaughan, Scheydgasse 41
> Software Developer 1210 Vienna AUSTRIA
> ============================================--------------------
>
prev parent reply other threads:[~2011-02-03 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 2:10 kevin diggs
2011-01-22 2:36 ` Ian Lance Taylor
2011-01-25 4:16 ` kevin diggs
2011-02-02 19:41 ` kevin diggs
2011-02-02 20:04 ` Jeff Kenton
2011-02-02 21:06 ` kevin diggs
2011-02-02 22:07 ` Ian Lance Taylor
2011-02-02 22:23 ` kevin diggs
2011-02-02 22:36 ` Ian Lance Taylor
2011-02-03 0:03 ` kevin diggs
2011-02-03 0:13 ` Ian Lance Taylor
2011-02-03 0:59 ` kevin diggs
2011-02-03 1:58 ` Ian Lance Taylor
2011-02-03 8:39 ` VAUGHAN Jay
2011-02-03 21:10 ` kevin diggs [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=AANLkTikVOFHcjtMtTUMHrEtqSipFnGOhieH_3fjvmYB7@mail.gmail.com \
--to=diggskevin38@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=jay.vaughan@thalesgroup.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).