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

Bug#506280: marked as done (linux-image-2.6.26-1-versatile won't boot on AB926EJ-S)

Your message dated Tue, 12 Jan 2010 22:22:41 +0100
with message-id <20100112212241.GA4411@galadriel.inutil.org>
and subject line Re: Bug#506280: linux-image-2.6.26-1-versatile won't boot on AB926EJ-S
has caused the Debian Bug report #506280,
regarding linux-image-2.6.26-1-versatile won't boot on AB926EJ-S
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
506280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506280
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-1-versatile
Version: 2.6.26-8
Severity: critical

This kernel won't boot on the ARM Versatile/AB926EJ-S evaluation board.

Initially, we built an nfs-root system using a kernel and cramfs filesystem
from ARM.  (You can get this filesystem, kernel and the kernel config file
from http://www.arm.com/products/os/linux_download.html under the "RealView
Versatile PB926/AB926" line in the table of images on that page.) 

We then did a complete Debian/lenny install using the method described in
"Installing Debian GNU/Linux from a Unix/Linux System", at
http://www.debian.org/releases/stable/arm/apds03.html.en.  After a reboot,
the ARM kernel successfully runs using the Debian/lenny nfs-root filesystem.

We used then used aptitude running under this ARM-kernel/Debian-filesystem
to install the linux-image-2.6.26-1-versatile package.

The AB926EJ-S board uses U-Boot to load the kernel.  To set this up, we
first use mkimage from the package uboot-mkimage (running on an x86 desktop
machine) to create U-Boot images from the vmlinuz and initrd.img installed
into the nfs-root by the ARM system:

    # mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 \
      -n "vmlinuz-2.6.26-1-versatile" -d /tftpboot/debian/vmlinuz \
      /tftpboot/uImage

    # mkimage -A arm -O linux -T ramdisk -C gzip -a 0x800000 -e 0x800000 \
      -n "initrd.img-2.6.26-1-versatile" -d /tftpboot/debian/initrd.img \
      /tftpboot/uInitrd

(Addresses in the above are from linux/arch/arm/mach-versatile/Makefile.boot.)

U-Boot is configured as follows:

    VersatileAB # printenv
    bootdelay=2
    baudrate=38400
    bootfile="/tftpboot/uImage"
    ipaddr=192.168.1.7
    serverip=192.168.1.40
    bootargs=root=/dev/ram rw mem=128M console=ttyAMA0
    bootcmd=tftp 0x7fc0 uImage ; tftp 0x7fffc0 uInitrd ; bootm 0x7fc0 0x7fffc0
    stdin=serial
    stdout=serial
    stderr=serial
    verify=n

    Environment size: 272/8188 bytes
    VersatileAB #

(The tftp target addresses are chosen to place the payload of the U-Boot
images at their run addresses.  Loading to different addresses gives the
same results as described below.)

When booting from a hard reset, we see the following (CR's stripped for
clarity):

    Reading MCI 0
    No card found - Please insert memory card.


    ARM AB926EJ-S Boot Monitor
    Version:    V3.4.2
    Build Date: Nov  7 2006
    Endian:     Little
    %BootMonitor-Info, Creating new SYSTEM.DAT
    %BootMonitor-Error, Unable to open SYSTEM.DAT

    %Flash-Info, Creating new FLASH.DAT
    %Flash-Error, Unable to open FLASH.DAT

    > flash run u-boot


    U-Boot 1.1.5-g58f62f5e-dirty (Nov  2 2006 - 03:06:12)

    DRAM:   0 kB
    Flash: 64 MB
    In:    serial
    Out:   serial
    Err:   serial
    Hit any key to stop autoboot:  2  1  0 
    Using MAC Address 00:02:F7:00:18:54
    TFTP from server 192.168.1.40; our IP address is 192.168.1.7
    Filename 'uImage'.
    Load address: 0x7fc0
    Loading: *#################################################################
             #################################################################
             #################################################################
             #############################################################
    done
    Bytes transferred = 1308460 (13f72c hex)
    Using MAC Address 00:02:F7:00:18:54
    TFTP from server 192.168.1.40; our IP address is 192.168.1.7
    Filename 'uInitrd'.
    Load address: 0x7fffc0
    Loading: *#################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             #################################################################
             ############################################################
    done
    Bytes transferred = 4299935 (419c9f hex)
    ## Booting image at 00007fc0 ...
       Image Name:   vmlinuz-2.6.26-1-versatile
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1308396 Bytes =  1.2 MB
       Load Address: 00008000
       Entry Point:  00008000
    OK
    ## Loading Ramdisk Image at 007fffc0 ...
       Image Name:   initrd.img-2.6.26-1-versatile
       Image Type:   ARM Linux RAMDisk Image (gzip compressed)
       Data Size:    4299871 Bytes =  4.1 MB
       Load Address: 00800000
       Entry Point:  00800000

    Starting kernel ...

    Uncompressing Linux...................................................................................... done, booting the kernel.

Then nothing further from the kernel either on the console or on the
ethernet port.

One interesting thing of note:  CONFIG_VERSATILE is _not_ set in the config
file for this kernel, which seems contrary to expectations.

Any assistance with this problem would be greatly appreciated.  The hardware
can be made available for testing via ssh if that would be of help.

Regards,

David Querbach
Real-Time Systems Inc.

--- End Message ---
--- Begin Message --- 
On Tue, Sep 01, 2009 at 06:53:36PM +0200, Moritz Muehlenhoff wrote:
> On Fri, Dec 26, 2008 at 04:46:09PM +0100, Martin Michlmayr wrote:
> > David,
> > 
> > * David Querbach <querbach@realtime.bc.ca> [2008-11-19 22:40]:
> > > This kernel won't boot on the ARM Versatile/AB926EJ-S evaluation board.
> > 
> > What I forgot to mention in my last email was that nobody at Debian
> > actually has a Versatile board.  We only added the versatile flavour
> > for QEMU, but we don't have any actual hardware to test the kernel...
> > 
> > So I suggest you try the mainline kernel to see if that works.  If
> > that works, we can try to figure out why our kernel doesn't.
> 
> David, did you try the mainline kernel?

No further feedback, closing the bug.

Cheers,
        Moritz

--- End Message ---
Reply to: