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

Bug#406419: marked as done ([powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150)



Your message dated Sat, 8 Jun 2013 12:15:57 +0200
with message-id <20130608101556.GC4796@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #406419,
regarding [powerpc, CHRP] 2.6 kernel does not boot on IBM RS/6000 43p 150
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.)


-- 
406419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406419
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kernel-image-2.6-powerpc
Version: 2.6.18+5

during working on another bug, I tried to install the daily d-i build:

cdimage.d.o:/cdimage/daily-builds/sid_d-i/20070103-2/powerpc/iso-cd/debian-testing-powerpc-netinst.iso

on an IBM RS/6000 43p 150. This is a CHRP system, so I used the CHRP-initrd
image and tried to netboot it (serial console):

-----------------------server TFTP log---------------------------------
Jan  8 00:31:36 mosna dhcpd: BOOTREQUEST from 00:04:ac:97:14:87 via eth0
Jan  8 00:31:36 mosna dhcpd: BOOTREPLY for 192.168.22.58 to cholos (00:04:ac:97:14:87) via eth0
Jan  8 00:31:38 mosna in.tftpd[3649]: RRQ from 192.168.22.58 filename vmlinuz-chrp.initrd 
-----------------------server TFTP log---------------------------------

As you can see, the image is loaded just fine.

-----------------------client boot log---------------------------------
0 > boot net:192.168.22.51,vmlinuz-chrp.initrd,192.168.22.58 
LOAD: Waiting 60 seconds for Spanning Tree
BOOTP R = 1 BOOTP S = 1  
FILE: vmlinuz-chrp.initrd
Load Addr=0x4000 Max Size=0xbfc000 
FINAL Packet Count = 10753   Final File Size = 5505188 bytes.

zImage starting: loaded at 0x00400000 (sp: 0x00efffe0)
Allocating 0x36f658 bytes for kernel ...
OF version = 'IBM,TCP04195'
Allocating 0x3bb2ca bytes for initrd ...
initial ramdisk moving 0x1370000 <- 0x574000 (0x3bb2ca bytes)
initrd head: 0x1f8b0808
gunzipping (0x1000000 <- 0x407000:0x573abe)...done 0x33e654 bytes
OF stdout device is: /pci@80000000/isa@b/serial@i3f8
command line: console=ttyS0,9600 console=tty0
memory layout at init:
  alloc_bottom : 0172c000
  alloc_top    : 20000000
  alloc_top_hi : 20000000
  rmo_top      : 20000000
  ram_top      : 20000000
Looking for displays
found display   : /pci@80000000/display@16, opening ... done
instantiating rtas at 0x1ffe5000 ... done
copying OF device tree ...
Building dt strings...
Building dt structure...
Device tree strings 0x0172d000 -> 0x0172dd6d
Device tree struct  0x0172e000 -> 0x01732000
Calling quiesce ...
returning from prom_init
Using CHRP machine description
Total memory = 512MB; using 1024kB for hash table (at cff00000)
Linux version 2.6.18-3-powerpc (Debian 2.6.18-8) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 Sun Dec 10 17:59:01 CET 2006
Found initrd at 0xc1370000:0xc172b2ca
chrp type = 5
PCI buses 0..1 controlled by pci at 80000000
Built 1 zonelists.  Total pages: 131072
Kernel command line: console=ttyS0,9600 console=tty0
OpenPIC at f9e80000
OpenPIC irqs 0..15 in IDU
mpic: Setting up MPIC " MPIC    " version 1.0 at f9e80000, max 4 CPUs
mpic: ISU size: 16, shift: 4, mask: f
mpic: Initializing for 16 sources
i8259 legacy interrupt controller initialized
PID hash table entries: 4096 (order: 12, 16384 bytes)
-----------------------client boot log---------------------------------

Booting just stops here, nothing is displayed on the front LED.

As this box has a video card inside, I tried booting over the graphical
console, too. There it stops dead after the line:

coming back from prom_init

Booting from CD isn't working at all, stops with a front LED error display
of 185 - which can be anything.

Most likely, this bug can't be resolved before etch, but I thought I should
report it nonetheless,

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Single (Hushpuppies), Pay The Cobra
24539 Neumuenster, Germany|(The Bellrays), She's Got Standards (The Rifles)


--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---

Reply to: