<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>152882</bug_id>
          
          <creation_ts>2006-10-26 08:24 0000</creation_ts>
          <short_desc>kernel &gt;= 2.6.14 won&apos;t boot on Netra X1</short_desc>
          <delta_ts>2006-12-26 07:02:22 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>Sparc64</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>UPSTREAM</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>max.gentoo.bugzilla@hacking.co.uk</reporter>
          <assigned_to>sparc@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>max.gentoo.bugzilla@hacking.co.uk</who>
            <bug_when>2006-10-26 08:24:44 0000</bug_when>
            <thetext>While attempting to install the latest stable (on SPARC) kernel (gentoo-sources-2.6.17-r8) on a Netra X1 I ran into the following problem.

Whenever I attempt to boot over the network I receive one of the error messages listed below:

IDPROM: Warning, unknown format type!
Illegal Instruction
Memory Address not Aligned
Data Access Exception
Fast Instruction Access MMU Miss

The error message can be changed by compiling a random kernel component in or out to change the size of the generated kernel.  All kernels I have tried have been less than 3MB, some less than 2.5MB.

I then tried installing every available version of gentoo-sources back to 2.6.14-r7 with the same result.  At this point I moved to testing vanilla-sources, unfortunately with no improvement.  

Kernel versions 2.6.13-r5 and earlier all boot fine.  This led me to believe that the issue was probably introduced in 2.6.14.  After scanning through the changelog for that version I have found the following commit:

commit bff06d552240ba7f5b49482a4865871d7bc03dc2
Author: David S. Miller
Date:   Thu Sep 22 20:11:33 2005 -0700

    [SPARC64]: Rewrite bootup sequence.
    
    Instead of all of this cpu-specific code to remap the kernel
    to the correct location, use portable firmware calls to do
    this instead.
    
    Signed-off-by: David S. Miller

Seems like more than a coincidence to me...  

After much searching of the web I have found that the following architectures are affected:

Sun Netra X1 (UltraSPARC-IIe 400MHz)
Sun Fire V240
Sun Blade 2500

Using OBP versions 4.0.5, 4.3.2, 4.5.9 and 4.17.1.

Should I file this directly with the kernel maintainers?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>max.gentoo.bugzilla@hacking.co.uk</who>
            <bug_when>2006-10-26 08:33:43 0000</bug_when>
            <thetext>Sorry, should have added that this is NOT related to the similar looking SILO bug.  This occurs when net-booting too.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>gustavoz@gentoo.org</who>
            <bug_when>2006-11-07 11:21:54 0000</bug_when>
            <thetext>One of the sparc devels has a V240 running with recent kernels just fine.
However this isn&apos;t related since the X1 is a completely different machine. And unfortunately we lack an X1 to help so it&apos;s best if you try upstream with the sparclinux mailing list.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>max.gentoo.bugzilla@hacking.co.uk</who>
            <bug_when>2006-12-22 02:58:25 0000</bug_when>
            <thetext>Resolved in kernel 2.6.19-r2.

I&apos;m happy to call this closed if you guys are.  :-)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>gustavoz@gentoo.org</who>
            <bug_when>2006-12-26 07:02:22 0000</bug_when>
            <thetext>We&apos;re happy if you&apos;re happy.
2.6.19-r2 won&apos;t go stable until we work around the qlogic firmware issue that 2.6.18+ got (removed firmware from the kernel, thus blade 1000/2000 machines can&apos;t boot from builtin disk).
Though it&apos;s a genkernel issue and completely unrelated.
</thetext>
          </long_desc>
      
    </bug>

</bugzilla>