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

Bug#619692: marked as done (IA64 wont boot Debian 6.0.1)

Your message dated Sat, 20 Jul 2013 17:22:32 +0200
with message-id <201307201723.03308.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #619692,
regarding IA64 wont boot Debian 6.0.1
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.)


-- 
619692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619692
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: HPVM using an ISO image mapped to DVD
Image version:
http://cdimage.debian.org/debian-cd/6.0.1a/ia64/iso-dvd/debian-6.0.1a-ia
64-DVD-1.iso
Date: 2011-03-26 1:00

Machine: HP rx2800 HOST OS: HP-UX 11.31 Sep 2010 - HPVM for Debian
Processor: IA64 (Tukwila)
Memory: 4 GB
Partitions: Entire disk

Output of lspci -knn (or lspci -nn): N/A

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [ ]
Configure network:      [ ]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [E]
Overall install:        [ ]

Comments/Problems: 

I have an HPVM with Net, Disk, and a DVD ISO on host mapped as a DVD
drive

GUI chooser comes up and asks Install, Install [Expert Mode], Recovery

Uncompressing Linux...Done
Loading file \initrd.gz...Done
<hangs here for long time>

6     SFW  0,0,0  2 0x4b00006300e00002 0x010000004d8d6653  BOOT_START
                                       Sat Mar 26 04:06:43 2011 
First Log Block as TEXT


Log Entry  5:    Sat Mar 26 04:06:43 2011
Alert Level 2:  Informational
Keyword: BOOT_START
CPU starting boot
SFW has started the boot process.
Logged by:  System Firmware cabinet 0, slot 0, cpu 0 Logged by:
Data:  0x5680006300e00001 000000000000000000
Time:  0x4b00006300e00002 0x010000004d8d6653

Log Entry  7:
Alert Level 0:  Minor Forward Progress
Keyword: MEMORY_ALLOCATION_START
Memory allocation has started
Guest memory allocation has started
Logged by:  Integrated Lights Out entity 0 Logged by:
Data:  0x160019c900e00000 0x0000000100000000


Last Log Block as Text

Log Entry  31:
Alert Level 0:  Minor Forward Progress
Keyword: BOOT_CELL_RELOCATE_EFI
Relocating EFI
SFW has relocated EFI
Logged by:  System Firmware cabinet 0, slot 0, cpu 0 Logged by:
Data:  0x3600001000e00000 000000000000000000

Log Entry  30:
Alert Level 0:  Minor Forward Progress
Keyword: BOOT_CELL_RELOCATE_EFI
Relocating EFI
SFW has relocated EFI
Logged by:  System Firmware cabinet 0, slot 0, cpu 0 Logged by:
Data:  0x3600001000e00000 000000000000000000

--- End Message ---
--- Begin Message --- 
reassign 609339 netcfg
tags 609339 + wontfix
reassign 604150 partman-partitioning
thanks

Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are quite old.

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: