Re: ????: Re: [parisc-linux] "I/O MMU is out of mapping resources" while a base install into HP C200
On Tue, Feb 07, 2006 at 06:43:39PM +0900, yong Jung wrote:
> I tried installation with testing image.
> Because you told me it was corrected in a newer
> version.
> You are right, it was corrected, I/O MMU....
> We succeeded base installation, but failed PALO
> installation step as the below.
> And we tried booting without PALO installation, but we
> failed to boot as the below.
> Could you please check the below what I did if you
> don't mind ?
> .
> Thanks a million,
> Kiyong
> ...........
>
> Trying install with testing image after successful
> base installation.
> ====================================================================
> ----------------+ [!!] Debian installer main menu
> +----------------+
>
> | Installation step failed
> |
>
> | An installation step failed. You can try to run
> the failing item |
>
> | again from the menu, or skip it and choose
> something else. The |
>
> | failing step is: Install PALO on a hard disk
> |
> -----------------+ [!] Continue without boot loader
> +------------------+
> | No boot loader installed
> |
> | No boot loader has been installed, either because
> you chose not to or |
> | because your specific architecture doesn't
> support a boot loader yet. |
> |
> |
> | You will need to boot manually with the /vmlinux
> kernel on partition |
> | /dev/sda2 and root=/dev/sda5 passed as a kernel
> argument. |
> |
> ......
> We tried booting after skipping PALO install step as
> the below.
> .......
> .......
> ramdisk_size=32765
> Current command line:
> /dev/sda2/vmlinux root=/dev/sda5 initrd=0/ramdisk
> ramdisk_size=32765 init=/linux
> rc console=ttyS0 TERM=vt102
> 0: /dev/sda2/vmlinux
parameter "0:" looks very wrong to me.
It should be 0/vmlinux since initrd is pointing at 0/ramdisk.
grant
> 1: root=/dev/sda5
> 2: initrd=0/ramdisk
> 3: ramdisk_size=32765
> 4: init=/linuxrc
> 5: console=ttyS0
> 6: TERM=vt102
>
> <#> edit the numbered field
> 'b' boot with this command line
> 'r' restore command line
> 'l' list dir
> ? b
>
> Command line for kernel: 'root=/dev/sda5
> ramdisk_size=32765 init=/linuxrc consol
> e=ttyS0 TERM=vt102 palo_kernel=0/dev/sda2/vmlinux'
> Selected kernel: /dev/sda2/vmlinux from partition 0
> Selected ramdisk: /ramdisk from partition 0
> Warning: kernel name doesn't end with 32 or 64 --
> Guessing... Choosing 32-bit ke
> rnelELF32 executable
> Entry 00100000 first 00100000 n 2
> Segment 0 load 00100000 size 3005696 mediaptr 0x1000
> Segment 1 load 003e0000 size 385158 mediaptr 0x2df000
> Loading ramdisk 3259565 bytes @ 07cd3000...
> Branching to kernel entry point 0x00100000. If this
> is the last
> message you see, you may need to switch your console.
> This is
> a common symptom -- search the FAQ and mailing list at
> parisc-linux.org
>
> Linux version 2.6.12-1-parisc (buildd@sarti) (gcc
> version 4.0.2 (Debian 4.0.1-9)
> ) #1 Tue Sep 27 10:16:14 UTC 2005
> FP[0] enabled: Rev 0 Model 14
> The 32-bit Kernel has started...
> Initialized PDC Console for debugging.
> Determining PDC firmware type: System Map.
> model 000059d0 00000481 00000000 00000002 77647a2b
> 100000f0 00000008 000000b2 00
> 0000b2
> vers 00000501
> CPUID vers 14 rev 23 (0x000001d7)
> capabilities 0x2
> model 9000/782/C200+
> Total Memory: 128 MB
> initrd: 17cd3000-17feecad
> initrd: reserving 07cd3000-07feecad (mem_max 08000000)
> LED display at f0190001 registered
> Built 1 zonelists
> Kernel command line: root=/dev/sda5 ramdisk_size=32765
> init=/linuxrc console=tty
> S0 TERM=vt102 palo_kernel=0/dev/sda2/vmlinux
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Console: colour dummy device 160x64
> Dentry cache hash table entries: 32768 (order: 5,
> 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536
> bytes)
> Memory: 131072k available
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> Mount-cache hash table entries: 512
> checking if image is initramfs...it isn't (no cpio
> magic); looks like an initrd
> NET: Registered protocol family 16
> EISA bus registered
> Searching for devices...
> Found devices:
> 1. U2-IOA BC Runway Port at 0xfff88000 [8] { 12, 0xf,
> 0x580, 0x0000b }
> 2. Dino PCI Bridge at 0xf2000000 [8/0] { 13, 0x3,
> 0x680, 0x0000a }, additional
> addresses: 0xf2800000
> 3. Raven U/L2 Dino RS-232 at 0xf2003000 [8/0/63] { 10,
> 0x0, 0x006, 0x0008c }
> 4. Raven+ w SE FWSCSI Core BA at 0xffd00000 [8/16] {
> 11, 0x0, 0x056, 0x00081 },
> additional addresses: 0xffd0c000 0xffc00000
> 5. Raven+ w SE FWSCSI Core RS-232 at 0xffd05000
> [8/16/4] { 10, 0x0, 0x056, 0x000
> 8c }
> 6. Raven+ w SE FWSCSI Core SCSI at 0xffd06000 [8/16/5]
> { 10, 0x0, 0x056, 0x00082
> }
> 7. Raven+ w SE FWSCSI Core Centronics at 0xffd02000
> [8/16/0] { 10, 0x0, 0x056, 0
> x00074 }, additional addresses: 0xffd01000 0xffd03000
> 8. Raven+ w SE FWSCSI Core Audio at 0xffd04000
> [8/16/1] { 10, 0x4, 0x056, 0x0007
> b }
> 9. Raven+ w SE FWSCSI Core PS/2 Port at 0xffd08000
> [8/16/7] { 10, 0x0, 0x056, 0x
> 00084 }
> 10. Raven+ w SE FWSCSI Core PS/2 Port at 0xffd08100
> [8/16/8] { 10, 0x0, 0x056, 0
> x00084 }
> 11. U2-IOA BC GSC+ Port at 0xf203f000 [8/63] { 7, 0x1,
> ?x501, 0x0000c }
> 12. Raven U/L2 Dino PS/2 Port at 0xf2001000 [8/1] {
> 10, 0x0, 0x006, 0x00096 }
> 13. U2-IOA BC Runway Port at 0xfff8a000 [10] { 12,
> 0xf, 0x580, 0x0000b }
> 14. Coral SGC Graphics at 0xf6000000 [10/12] { 10,
> 0x0, 0x004, 0x00077 }
> 15. U2-IOA BC GSC+ Port at 0xf103f000 [10/63] { 7,
> 0x1, 0x501, 0x0000c }
> 16. Cujo PCI Bridge at 0xf1000000 [10/0] { 13, 0x1,
> 0x682, 0x0000a }
> 17. Dino RS-232 at 0xf1003000 [10/3] { 10, 0x0, 0x007,
> 0x0008c }
> 18. Raven U 200 (9000/780/C200) at 0xfffa0000 [32] {
> 0, 0x0, 0x59d, 0x00004 }
> 19. Memory at 0xfffb1000 [49] { 1, 0x0, 0x05d, 0x00009
> }
> CPU(s): 1 x PA8200 (PCX-U+) at 200.000000 MHz
> Setting cache flush threshold to 20 (1 CPUs online)
> Found U2 at 0xfff88000
> Found U2 at 0xfff8a000
> Lasi version 0 at 0xffd00000 found.
> Dino version 3.1 found at 0xf2000000
> Cujo version 2.0 found at 0xf1000000
> Enabling Cujo 2.0 bug workaround
> Cujo: No PCI devices enabled.
> SCSI subsystem initialized
> TC classifier action (bugs to netdev@vger.kernel.org
> cc hadi@cyberus.ca)
> unwind_init: start = 0x1033aaa0, end = 0x1035a120,
> entries = 8040
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096
> bytes)
> devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
> devfs: boot_options: 0x0
> Initializing Cryptographic API
> PDC Stable Storage facility v0.09
> Soft power switch enabled, polling @ 0xf0140000.
> STI GSC/PCI core graphics driver Version 0.9a
> id 2d08c0a7-9a02587, conforms to spec rev. 8.07
> graphics card name: HPA4450AX1280
> sticon: Initializing STI text console.
> Console: switching to colour STI console 160x64
> Console: switching to colour frame buffer device
> 160x64
> fb0: stifb 1280x1024-8 frame buffer device,
> HPA4450AX1280, id: 2d08c0a7, mmio: 0
> xf6100000
> Generic RTC Driver v1.07
> serio: GSC PS/2 keyboard port at 0xffd08000 irq 20 @
> 8:16:7
> serio: GSC PS/2 mouse port at 0xffd08100 irq 20 @
> 8:16:8
> Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports,
> IRQ sharing enabled
> ttyS0 at MMIO 0xffd05800 (irq = 16) is a 16550A
> ttyS1 at MMIO 0xf2003800 (irq = 21) is a 16550A
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 32765K
> size 1024 blocksize
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP established hash table entries: 8192 (order: 4,
> 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768
> bytes)
> TCP: Hash tables configured (established 8192 bind
> 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "sda5" or
> unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(2,0)
> ............
>
>
>
>
>
>
>
>
>
>
>
>
> --- Grant Grundler <grundler@parisc-linux.org>
> ????????:
>
> > On Sat, Feb 04, 2006 at 06:52:47PM +0900, yong Jung
> > wrote:
> > > Hellow debian lovers,
> > > .
> > > Could you give me a favor to check my install
> > problem
> > > on C200 machine ?
> >
> > Hi Yong.
> > You are the 3rd person in the past week or so to
> > report this problem. :)
> > It was fixed here:
> > | revision 1.18
> > | date: 2005/03/06 23:48:39; author: grundler;
> > state: Exp; lines: +34 -32
> > | branches: 1.18.2; 1.18.4;
> > |
> > | 2.6.11-pa2 - ditch ccio_mem_ratio. "Ported" from
> > similar change to sba driver.
> >
> > I'm told debian-31r1a-hppa-netinst.iso uses 2.6.8.1.
> >
> > Workaround is to reduce the number of outstanding
> > scsi commands
> > and thus reduce the amount of total I/O "in flight".
> >
> > You can do this by setting "queue_depth" to 1.
> > Offhand I only know about /sys entries:
> > find /sys -name queue_depth
> >
> > and then "echo 1 > /sys/devices/...../queue_depth"
> >
> > Or can someone remind me how to globally do that
> > from the command line?
> > google isn't finding it for me today.
> >
> > grant
> >
>
>
>
>
> ________________________________________________________
> ????! ?????? - ???????? ???? ???? ????! ?????? ????!???????? ????????
> http://kr.mobile.yahoo.com
Reply to: