Re: [FYI] linux 2.6 still not working with PReP (ppc32)
On Tue, Jan 04, 2005 at 11:46:37AM -0800, J. William Campbell wrote:
> Hi Sven,
> I don't know if this will help you any but I have similar results
> with both a MCP750 and an MVME3604. I have attached a copy of my install
> reports below. They
> both hang at exactly the same point as reported by Ulrich Teichert
> <krypton@ulrich-teichert.org> in Re: 43p-140 install issues on Mon, 3
> Jan 2005 20:32:12 +0100 (MET). If I can do any testing for you with
> these boards, I would be glad to help. Thank you!
Cool. Any help is welcome, i am not fully sure i grasp fully the kernel
support side of those various prep boxes. I have a fix that works on the
powerstack, but other prep hardware is rather new to me, so any help is
welcome. I will be making a new debian kernel upload nextly, and hope to fix
as much as possible as far as prep support goes, but would be glad to have
help from anyone with the hardware, or knowledgeable in prep kernel issues.
Mmm, CCing debian-boot, altough even if there is a kernel issue, the place it
hangs is in the initrd, if i am not wrong, and maybe someone on debian-boot
may have an insight.
> Best Regards,
> J. William Campbell
>
> Package: installation-reports
>
> Debian-installer-version: vmlinuz-prep.initrd from
> people.debian.org/~luther/d-i/images/daily/powerpc/netboot/vmlinuz-prep.initrd <http://people.debian.org/%7Eluther/d-i/images/daily/powerpc/netboot/vmlinuz-prep.initrd>
> uname -a: never got this far
> Date: 18-December-2004, all day long more or less
> Method: TFTP of local copy of vmlinuz-prep.initrd
> transfered from a local i386 linux system
>
> Machine: Motorola MCP750
> Processor:
> Memory:
> Root Device: /dev/hdc1 if I had got far enough
> Root Size/partition table:
> Output of lspci and lspci -n:
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot worked: [E]
Oh well.
> Configure network HW: [ ]
> Config network: [ ]
> Detect CD: [ ]
> Load installer modules: [ ]
> Detect hard drives: [ ]
> Partition hard drives: [ ]
> Create file systems: [ ]
> Mount partitions: [ ]
> Install base system: [ ]
> Install boot loader: [ ]
> Reboot: [ ]
>
> Comments/Problems:
>
> Please find attached two attempts to start a sarge install, first on a
> MCP750 and second on a
> MVME3604-5. I used the build of 18 December 2004, but I get the same result
> with the "testing" build of 18 November 2004 on sarge-powerepc-1.iso
> install/powerpc/vmlinuz-prep.initrd. First note that one must specify a
> memory size on boot, probably because the "residual data" is stored in high
> memory and will be written over if not protected
Ah, ... Is this anything that can be automated ? I guess not, maybe it would
be better to have some kind of mention of this in the documentation ? Could
you write some kind of instruction so it can be added in the installation
manual ?
> some way. The version 2.4 prep.initrd does not work at all on these
> systems. I think I heard somewhere that there were patches
> for the prep build that were not present in 2.4 but were present in 2.6???
Ah, well, no great loose, if we can get ride of 2.4, so much the better. The
powerpc debian port actually defaults on a 2.6 kernel, and has the 2.4 kernel
only there as a backup in case of incompatibility or whatnot. All the other
arches still default to 2.4 though, too bad for them :)
> I never was able to get Woody to work with either
> of these boards. The version 2.2 boot-mcp750.bin produced by Eric Valette
> DOES completely work on my MCP750.
Ah, we certainly don't want to have a 2.2 kernel in sarge, no way. Let's see
if those issues can be fixed in 2.6, or if they are patches around which fix
it.
> I think the problems I am having here are not really install problems, but
> rather kernel configuration problems. It also seems
> that the Debian support for the Motorola PPC boards (MVME
> 2600/2700/3600/4600) and MCP750 has not worked in some time????
> I have two MCP750s, a 3604-5, and a 2604 that I can use to help debug these
> problems. I can also borrow a 2700 and a 5100 if
> desired. Is there anyone in the Debian developers group working on these
I think not. I think nobody did prep until i got kindly donated the powerstack
machine.
> boards? If so, I don't want to be in the way, but if
> not I will gladly try to help debug these problems. If anyone can enlighten
> me, please do so. Thanks!
First order of business is getting the kernel working correctly. Can you
compile a kernel yourself, and try to boot it ? Maybe we need a modification
of the .config or something, or a fixed mkinitrd, don't know.
Also, i know nothing about mvme boards, but i guess these don't use pci or
something ? would that be a problem with discover/hotplug based device
detection ?
Ok, let's look the kernel messages :
> **************************************************************************************
>
> Copyright Motorola Inc. 1988 - 1998, All Rights Reserved
>
> PPC1 Debugger/Diagnostics Release Version 4.1 - 10/12/98 RM01
> COLD Start
>
> Local Memory Found =08000000 (&134217728)
>
> MPU Clock Speed =367Mhz
>
> BUS Clock Speed =67Mhz
>
>
> WARNING: Keyboard Not Connected
>
> Reset Vector Location : ROM Bank B
> Mezzanine Configuration: Single-MPU
> Current 60X-Bus Master : MPU0
> Idle MPU(s) : NONE
>
> Initializing System Memory (DRAM)...
>
> System Memory: 128MB, ECC Enabled (ECC-Memory Detected)
> L2Cache: 1024KB, 147Mhz
>
>
> PPC1-Bug>nbo
> Network Booting from: DEC21140, Controller 0, Device 0
> Device Name: /pci@80000000/pci1011,9@e,0:0,0
> Loading: vmlinuz-prep.initrd
>
> Client IP Address = 192.168.1.129
> Server IP Address = 192.168.1.102
> Gateway IP Address = 192.168.1.1
> Subnet IP Address Mask = 255.255.255.0
> Boot File Name = vmlinuz-prep.initrd
> Argument File Name =
>
> Network Boot File load in progress... To abort hit <BREAK>
>
> Bytes Received =&5513751, Bytes Loaded =&5513751
> Bytes/Second =&1378437, Elapsed Time =4 Second(s)
>
> Residual-Data Located at: $07F88000
> loaded at: 00005400 0054EFF4
>
> relocated to: 00800000 00D49BF4
>
> zimage at: 0080A94C 0093E3DC
>
> initrd at: 0093F000 00D3FAC7
>
> avail ram: 00400000 00800000
>
>
> Linux/PPC load: console=ttyS0,9600 console=tty0 mem=127M
>
> Uncompressing Linux...done.
>
> Now booting the kernel
>
> Total memory = 127MB; using 256kB for hash table (at c0300000)
>
> Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian
> 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
>
> PReP architecture
>
> Built 1 zonelists
>
> Kernel command line: console=ttyS0,9600 console=tty0 mem=127M
>
> OpenPIC Version 1.3 (2 CPUs and 16 IRQ sources) at effde000
>
> OpenPIC timer frequency is 8.333519 MHz
>
> PID hash table entries: 512 (order 9: 4096 bytes)
>
> time_init: decrementer frequency = 16.667038 MHz
>
> Console: colour dummy device 80x25
>
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
>
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
>
> Memory: 121380k available (1732k kernel code, 1060k data, 164k init, 0k
> highmem)
>
> Calibrating delay loop... 731.13 BogoMIPS
>
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
>
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
>
> Freeing initrd memory: 4098k freed
>
> NET: Registered protocol family 16
>
> PCI: Probing PCI hardware
>
> PCI: Unable to handle 64-bit address space for <------- Not sure
> what this error means.
Seems strange indeed. Maybe the board has 64bit pci slots, but the kernel
doesn't know how to handle the upper 32 bits ?
> Setting PCI interrupts for a "Mesquite cPCI (MCP750)" <------- Correct
> ident
>
> PCI: Cannot allocate resource region 0 of device 0000:00:0e.0
Well, this seems like a missing irq, not sure what pci device is attached to
that pci id ?
> Thermal assist unit using timers, shrink_timer: 2000 jiffies
>
> audit: initializing netlink socket (disabled)
>
> audit(1103438127.996:0): initialized
>
> devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
>
> devfs: boot_options: 0x0
>
> Initializing Cryptographic API
>
> Activating ISA DMA hang workarounds.
>
> Generic RTC Driver v1.07
>
> Macintosh non-volatile memory driver v1.1
>
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
>
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
>
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>
> input: Macintosh mouse button emulation
>
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>
> mice: PS/2 mouse device common for all mice
>
> NET: Registered protocol family 2
>
> IP: routing cache hash table of 512 buckets, 4Kbytes
>
> TCP: Hash tables configured (established 8192 bind 16384)
>
> RAMDISK: Compressed image found at block 0
>
> VFS: Mounted root (cramfs filesystem) readonly.
>
> Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware
>
> NET: Registered protocol family 1
>
> <!!!!HANGS HERE FOREVER UNTIL RESET IS PRESSED>
Mmm, ... i wonder why. you are over a serial console, aren't you ? At this
point, the kernel has uncompressed the initrd, mounted it, and if i am not
wrong, is starting to execute it. Need to check what it does here.
> Copyright Motorola Inc. 1988 - 1998, All Rights Reserved
>
> PPC1 Debugger/Diagnostics Release Version 4.1 - 10/12/98 RM01
> COLD Start
>
> Local Memory Found =08000000 (&134217728)
>
> MPU Clock Speed =367Mhz
>
> BUS Clock Speed =67Mhz
>
>
> WARNING: Keyboard Not Connected
>
> Reset Vector Location : ROM Bank B
> Mezzanine Configuration: Single-MPU
> Current 60X-Bus Master : MPU0
> Idle MPU(s) : NONE
>
> Initializing System Memory (DRAM)...
>
> System Memory: 128MB, ECC Enabled (ECC-Memory Detected)
> L2Cache: 1024KB, 147Mhz
>
>
> PPC1-Bug>
>
>
> ***********************************************************************************************************
>
> Copyright Motorola Inc. 1988 - 1999, All Rights Reserved
>
> PPC1 Debugger/Diagnostics Release Version 4.3 - 01/20/99 RM01
> COLD Start
>
> Local Memory Found =04000000 (&67108864)
>
> MPU Clock Speed =300Mhz
>
> BUS Clock Speed =67Mhz
>
>
> WARNING: Keyboard Not Connected
>
> Reset Vector Location : ROM Bank A
> Mezzanine Configuration: Single-MPU
> Current 60X-Bus Master : MPU0
> Idle MPU(s) : NONE
>
> Initializing System Memory (DRAM)...
>
> System Memory: 64MB, ECC Enabled (ECC-Memory Detected)
> L2Cache: 512KB
>
>
> SelfTest/Boots about to Begin... Press <BREAK> at anytime to Abort ALL
>
> SelfTest about to Begin... Press <ESC> to Bypass, <SPC> to Continue
>
> PPC1-Diag>niot
> Controller LUN =00?
> Device LUN =00?
> Node Control Memory Address =03F9E000?
> Client IP Address =192.168.1.75?
> Server IP Address =192.168.1.102?
> Subnet IP Address Mask =255.255.255.0?
> Broadcast IP Address =192.168.1.255?
> Gateway IP Address =192.168.1.1?
> Boot File Name ("NULL" for None) =vmlinuz-prep.initrd?
> Argument File Name ("NULL" for None) =?
> Boot File Load Address =001F0000?
> Boot File Execution Address =001F0000? .
>
> PPC1-Diag>ioi
> I/O Inquiry Status:
> CLUN DLUN CNTRL-TYPE DADDR DTYPE RM Inquiry-Data
> 0 0 NCR53C825 0 $00 N MICROP 2112 4024
> 0 40 NCR53C825 4 $01 Y ARCHIVE Python 04687-XXX 6580
> 1 0 PC8477 0 $00 Y <None>
> PPC1-Diag>niot ;H
> Network Controllers/Nodes Available
> CLUN DLUN Name Address P-Address/H-Address
> 0 0 DEC21140 $00007000 192.168.1.75/08003E2F220E
> 10 0 DEC21140 $00008000 0.0.0.0/0000003002AF
> 13 0 DEC21140 $00009800 0.0.0.0/08003E2D6E46
>
> PPC1-Diag>nbo
> Network Booting from: DEC21140, Controller 0, Device 0
> Device Name: /pci@80000000/pci1011,9@e,0:0,0
> Loading: vmlinuz-prep.initrd
>
> Client IP Address = 192.168.1.75
> Server IP Address = 192.168.1.102
> Gateway IP Address = 192.168.1.1
> Subnet IP Address Mask = 255.255.255.0
> Boot File Name = vmlinuz-prep.initrd
> Argument File Name =
>
> Network Boot File load in progress... To abort hit <BREAK>
>
> Bytes Received =&5513751, Bytes Loaded =&5513751
> Bytes/Second =&367583, Elapsed Time =15 Second(s)
>
> Residual-Data Located at: $03EE8000
> loaded at: 00005400 0054EFF4
>
> relocated to: 00800000 00D49BF4
>
> zimage at: 0080A94C 0093E3DC
>
> initrd at: 0093F000 00D3FAC7
>
> avail ram: 00400000 00800000
>
>
> Linux/PPC load: console=ttyS0,9600 console=tty0 mem=63M
>
> Uncompressing Linux...done.
>
> Now booting the kernel
>
> Total memory = 63MB; using 128kB for hash table (at c0300000)
>
> Linux version 2.6.8-powerpc (sven@pegasos2) (version gcc 3.3.5 (Debian
> 1:3.3.5-2)) #1 Thu Dec 9 10:27:54 CET 2004
>
> PReP architecture
>
> Built 1 zonelists
>
> Kernel command line: console=ttyS0,9600 console=tty0 mem=63M
>
> OpenPIC Version 1.3 (2 CPUs and 16 IRQ sources) at effde000
>
> OpenPIC timer frequency is 8.333674 MHz
>
> PID hash table entries: 256 (order 8: 2048 bytes)
>
> time_init: decrementer frequency = 16.667731 MHz
>
> Console: colour dummy device 80x25
>
> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>
> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>
> Memory: 56652k available (1732k kernel code, 1060k data, 164k init, 0k
> highmem)
>
> Calibrating delay loop... 299.00 BogoMIPS
>
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
>
> checking if image is initramfs...it isn't (no cpio magic); looks like an
> initrd
>
> Freeing initrd memory: 4098k freed
>
> NET: Registered protocol family 16
>
> PCI: Probing PCI hardware
>
> Setting PCI interrupts for a "MVME 3600 with MVME761" <-----------
> correct ident
>
> PCI: Cannot allocate resource region 0 of device 0000:00:0b.1 <------
> probably not good
>
> PCI: Cannot allocate resource region 1 of device 0000:00:0b.1
>
> PCI: Cannot allocate resource region 2 of device 0000:00:0b.1
>
> PCI: Cannot allocate resource region 3 of device 0000:00:0b.1
>
> PCI: Cannot allocate resource region 4 of device 0000:00:0b.1
>
> PCI: Cannot allocate resource region 5 of device 0000:00:0b.1
>
> PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
>
> PCI: Cannot allocate resource region 1 of device 0000:00:0d.0
>
> PCI: Cannot allocate resource region 0 of device 0000:00:0e.0
>
> PCI: Cannot allocate resource region 0 of device 0000:00:10.0
>
> PCI: Cannot allocate resource region 0 of device 0000:00:12.0
>
> PCI: Cannot allocate resource region 0 of device 0000:00:13.0
Sounds like a bunch of bad pci irqs. can you check if that is the case, or
someone knowledgeable check about this ?
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> PCI: I/O Region 0000:00:0d.0/-1 too large (4096 bytes)
>
> Thermal assist unit not available
>
> audit: initializing netlink socket (disabled)
>
> audit(1103492432.571:0): initialized
>
> devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
>
> devfs: boot_options: 0x0
>
> Initializing Cryptographic API
>
> Generic RTC Driver v1.07
>
> Macintosh non-volatile memory driver v1.1
>
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
>
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh@kernel.crashing.org>)
>
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>
> input: Macintosh mouse button emulation
>
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>
> mice: PS/2 mouse device common for all mice
>
> NET: Registered protocol family 2
>
> IP: routing cache hash table of 512 buckets, 4Kbytes
>
> TCP: Hash tables configured (established 4096 bind 8192)
>
> RAMDISK: Compressed image found at block 0
>
> VFS: Mounted root (cramfs filesystem) readonly.
>
> Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware
>
> NET: Registered protocol family 1
>
> <!!!!!! HANGS HERE FOREVER UNTIL RESET PRESSED>
Same problem then.
Friendly,
Sven Luther
Reply to: