bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #52629] ieee1275 for 64-bit PowerPC (big endian): Invalid memory ac


From: A. Wilcox
Subject: [bug #52629] ieee1275 for 64-bit PowerPC (big endian): Invalid memory access on Power Mac G5
Date: Sat, 9 Dec 2017 00:23:52 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

URL:
  <http://savannah.gnu.org/bugs/?52629>

                 Summary: ieee1275 for 64-bit PowerPC (big endian): Invalid
memory access on Power Mac G5
                 Project: GNU GRUB
            Submitted by: awilfox
            Submitted on: Sat 09 Dec 2017 05:23:51 AM UTC
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: Hardware-specific
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: 2.02
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

I'm the ppc64 maintainer for the Adélie Linux distribution.  We're trying to
craft a bootable CD for the Power Mac G5 and IBM pSeries.  We don't have the
pSeries here yet for testing, but we do have a Power Mac G5 (dual 2.0 GHz,
PCI-X).

I'm seeing the following on-screen when booting either from OF (boot
cd:,\boot\grubcore.img) or letting the machine boot from CD "normally" using
the "C" key (tbxi):


Welcome to GRUB!

/
Invalid memory access at  %SRR0: 00000000.00000f20  %SRR1: 90000000.00810000
 ok
0 >


This happens very early on.  The 32-bit PowerPC build that we have of grub
2.02 boots fine on the same hardware, so it seems specific to the 64-bit
port.

I added "set debug=all" to the embedded image "early" config file, and
rebooted.  I received the exact same output.  Please let me know if there is
another (possibly undocumented?) method of causing GRUB to print more debug
information.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52629>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]