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

Bug#351738: marked as done (sun blade 2000 / 2006.02.06 netinst ISO)

Your message dated Wed, 08 Sep 2010 03:58:10 +0000
with message-id <E1OtBnW-00054E-AM@ravel.debian.org>
and subject line Closing old installation report #351738
has caused the Debian Bug report #351738,
regarding sun blade 2000 / 2006.02.06 netinst ISO
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.)


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

Boot method: CD
Image version: 2006.02.06 http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/sparc/iso-cd/debian-testing-sparc-netinst.iso
Date: Mon, 06 Feb 2006 18:44:22 -0700

Machine: Sun Blade 2000
Processor: 2 X UltraSPARC-III+
Memory: 6144 MB
Partitions: <df -Tl will do; the raw partition table is preferred>
 dannf> Not easy to obtain; but I don't think this caused any problems
Output of lspci and lspci -n:
~ # lspci
0000:00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module
0000:00:04.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05)
0001:00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module
0001:00:01.0 Display controller: 3DLabs Sun XVR-500 Graphics Accelerator (rev 01)
0001:00:01.1 Display controller: 3DLabs Sun XVR-500 Graphics Accelerator (rev 01)
0001:00:05.0 Bridge: Sun Microsystems Computer Corp. RIO EBUS (rev 01)
0001:00:05.1 Ethernet controller: Sun Microsystems Computer Corp. RIO GEM (rev 01)
0001:00:05.2 FireWire (IEEE 1394): Sun Microsystems Computer Corp. RIO 1394 (rev 01)
0001:00:05.3 USB Controller: Sun Microsystems Computer Corp. RIO USB (rev 01)
0001:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37)
0001:00:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37)
 dannf> didn't grab lspci -n output, sorry

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

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [E]
Load installer modules: [O]
Detect hard drives:     [E]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [E]
Install boot loader:    [E]
Reboot:                 [E]

Comments/Problems:

I tried a VGA/keyboard install first, but the installer came up
monochrome, making it impossible to see what line was highlighted, etc.
So, I setup serial console instead.

The system hangs hung for a very long time while loading the via82cxxx
IDE driver (~100 seconds).  I thought the system was hung, but it
eventually returned. My system has no devices that require the via82cxxx
driver.

My system has a fibre channel controller that requires the qla2200
driver.  Though this driver is in our 2.6.15 kernel images, it is not in
the linux-kernel-di-sparc-2.6 scsi packages.  I used wget to fetch and
load this driver by hand.

I have a sym53c8xx card in my system, but it has no disks attached to
it.  This driver is constantly going through the scsi ABORT/DEVICE
RESET/SCSI BUS reset path while loaded.

The partitioner has ugly ascii boxes after the partition listings.

An install of testing fails because it tries and fails to install a
2.6.12 kernel, but that's probably expected.  I got further with sid.

When it tries to pull packages off the cdrom, I get an error that it
couldn't fine a Release file on the cdrom.  I dropped to a shell &
unmounted the cdrom so that the installation would try the network
instead.

The sid kernel fails to install because yaird fails.  I worked around
this[1] at the shell by using initramfs-tools instead.

Probably due to the above, silo installer failed to install.  I did this
by hand.

When the system came back up, I got a bunch of udev messages[2] on the
console, and then a panic because init died.  But, I guess I can't blame
d-i - this was because I used initramfs-tools instead of yaird.

[1]
BusyBox v1.01 (Debian 1:1.01-4) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # ls
bin          etc          initrd       proc         target       var
cdrom        floppy       lib          sbin         tmp
dev          init         preseed.cfg  sys          usr
~ # cd /target
/target # ls
bin         etc         lost+found  proc        sys
boot        home        media       root        tmp
cdrom       initrd      mnt         sbin        usr
dev         lib         opt         srv         var
/target # chroot . bash
root@sparc:/# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up linux-image-2.6.15-1-sparc64-smp (2.6.15-4) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: can't open /proc/bus/input/devices (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.15-1-sparc64-smp (--configure):
 subprocess post-installation script returned error exit status 9
dpkg: dependency problems prevent configuration of linux-image-2.6-sparc64-smp:
 linux-image-2.6-sparc64-smp depends on linux-image-2.6.15-1-sparc64-smp (= 2.6.15-4); however:
  Package linux-image-2.6.15-1-sparc64-smp is not configured yet.
dpkg: error processing linux-image-2.6-sparc64-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.15-1-sparc64-smp
 linux-image-2.6-sparc64-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@sparc:/# ls /proc/
root@sparc:/# mount proc /proc -t proc
root@sparc:/# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up linux-image-2.6.15-1-sparc64-smp (2.6.15-4) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: can't open directory /sys/block (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.15-1-sparc64-smp (--configure):
 subprocess post-installation script returned error exit status 9
dpkg: dependency problems prevent configuration of linux-image-2.6-sparc64-smp:
 linux-image-2.6-sparc64-smp depends on linux-image-2.6.15-1-sparc64-smp (= 2.6.15-4); however:
  Package linux-image-2.6.15-1-sparc64-smp is not configured yet.
dpkg: error processing linux-image-2.6-sparc64-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.15-1-sparc64-smp
 linux-image-2.6-sparc64-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@sparc:/# ls /sys
root@sparc:/# mount sys /sys -t sys
mount: unknown filesystem type 'sys'
root@sparc:/# cat /proc/filesystems
nodev   sysfs
nodev   rootfs
nodev   bdev
nodev   proc
nodev   sockfs
nodev   securityfs
nodev   usbfs
nodev   pipefs
nodev   futexfs
nodev   tmpfs
nodev   inotifyfs
nodev   eventpollfs
nodev   devpts
        ext2
        cramfs
nodev   ramfs
nodev   mqueue
        iso9660
        vfat
        ext3
        jfs
        reiserfs
        xfs
root@sparc:/# mount sysfs /sys -t sysfs
root@sparc:/# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up linux-image-2.6.15-1-sparc64-smp (2.6.15-4) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: unrecognised device: /sys/devices/pci0000:00/0000:00:04.0/host2/rport-2:0-0
yaird error: there were errors in this run, aborting now without output (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.15-1-sparc64-smp (--configure):
 subprocess post-installation script returned error exit status 9
dpkg: dependency problems prevent configuration of linux-image-2.6-sparc64-smp:
 linux-image-2.6-sparc64-smp depends on linux-image-2.6.15-1-sparc64-smp (= 2.6.15-4); however:
  Package linux-image-2.6.15-1-sparc64-smp is not configured yet.
dpkg: error processing linux-image-2.6-sparc64-smp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-2.6.15-1-sparc64-smp
 linux-image-2.6-sparc64-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@sparc:/# apt-get install initramfs-tools
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  busybox klibc-utils libklibc udev
The following NEW packages will be installed:
  busybox initramfs-tools klibc-utils libklibc udev
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 779kB of archives.
After unpacking 2437kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://debian-mirror.fc.hp.com sid/main libklibc 1.2.1-3 [19.3kB]
Get:2 http://debian-mirror.fc.hp.com sid/main klibc-utils 1.2.1-3 [142kB]
Get:3 http://debian-mirror.fc.hp.com sid/main busybox 1:1.01-4 [312kB]
Get:4 http://debian-mirror.fc.hp.com sid/main udev 0.084-2 [268kB]
Get:5 http://debian-mirror.fc.hp.com sid/main initramfs-tools 0.51 [36.9kB]
Fetched 779kB in 0s (2310kB/s)
Selecting previously deselected package libklibc.
(Reading database ... 10008 files and directories currently installed.)
Unpacking libklibc (from .../libklibc_1.2.1-3_sparc.deb) ...
Selecting previously deselected package klibc-utils.
Unpacking klibc-utils (from .../klibc-utils_1.2.1-3_sparc.deb) ...
Selecting previously deselected package busybox.
Unpacking busybox (from .../busybox_1%3a1.01-4_sparc.deb) ...
Selecting previously deselected package udev.
Unpacking udev (from .../udev_0.084-2_sparc.deb) ...
Selecting previously deselected package initramfs-tools.
Unpacking initramfs-tools (from .../initramfs-tools_0.51_all.deb) ...
Setting up libklibc (1.2.1-3) ...
Setting up klibc-utils (1.2.1-3) ...
Setting up busybox (1.01-4) ...
Setting up udev (0.084-2) ...
A chroot environment has been detected, udev not started.
FATAL: Could not load /lib/modules/2.6.15-1-sparc64/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.15-1-sparc64/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.15-1-sparc64/modules.dep: No such file or directory
Waiting for /dev to be fully populated...
Populating the new /dev filesystem temporarily mounted on /tmp/udev.8yjsr9/...
udevd-event[20892]: unlink_secure: chown(/tmp/udev.8yjsr9/.tmp-11-0, 0, 0) failed: No such file or directory

[2]
...
scsi1 : sym-2.2.1
vent[801]: runqla2200 0000:00:04.0: LIP occured (f8e8).
_qla2200 0000:00:04.0: LOOP UP detected (1 Gbps).
qla2200 0000:00:04.0: Topology - (Loop), Host Loop address 0x0
pscsi0 : qla2xxx
qla2200 0000:00:04.0:
 QLogic Fibre Channel HBA Driver: 8.01.03-k
  QLogic QLA22xx -
  ISP2200: PCI (66 MHz) @ 0000:00:04.0 hdma-, host#=0, fw=2.02.08 TP
rogram: exec of program '/lib/udev/udeinput: HID 0430:0005 as /class/input/input0
input: USB HID v1.00 Keyboard [HID 0430:0005] on usb-0001:00:05.3-2
v_run_devd' failed
udevd-event[805]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[806]: run_program: exec of program '/lib/udev/udev_run_devd' failed
udevd-event[809]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
...
udevd-event[3460]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3464]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3466]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3468]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3518]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3517]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3470]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3519]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3514]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3520]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3521]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3522]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3534]: run_program: exec of program '/lib/udev/usb_id' failed
udevd-event[3535]: run_program: exec of program '/lib/udev/scsi_id' failed
udevd-event[3536]: run_program: exec of program '/lib/udev/scsi_id' failed
udevd-event[3537]: run_program: exec of program '/lib/udev/edd_id' failed
udevd-event[3538]: run_program: exec of program '/lib/udev/vol_id' failed
udevd-event[3539]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3540]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3545]: run_program: exec of program '/lib/udev/vol_id' failed
udevd-event[3546]: run_program: exec of program '/lib/udev/vol_id' failed
udevd-event[3549]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3547]: run_program: exec of program '/lib/udev/vol_id' failed
udevd-event[3548]: run_program: exec of program '/lib/udev/vol_id' failed
udevd-event[3550]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3568]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3567]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3552]: run_program: exec of program '/lib/udev/usb_id' failed
udevd-event[3569]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3571]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3553]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3570]: run_program: exec of program '/lib/udev/udkjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
ev_run_hotplugd' failed
udevd-event[3573]: run_program: exec of program '/lib/udev/udev_run_devd' failedudevd-event[3554]: run_program: exec of program '/lib/udev/udev_run_hotplugd' failed
udevd-event[3572]: run_program:Kernel panic - not syncing: Attempted to kill init!
 <0>Press Stop-A (L1-A) to return to the boot prom
 exec of program '/lib/udev/scsi_id' failed
udevd-event[3575]: run_program: exec of program '/lib/udev/scsi_id' failed
udevd-event[3576]: run_program: exec of program '/lib/udev/edd_id' failed

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: