Bug#692196: Debian installer 7.0 beta 3 on sparc Ultra 2 fails
Package: installation-reports
Boot method: boot cdrom with net install version of ISO for installer 7, beta 3, sparc
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/sparc/iso-cd/debian-wheezy-DI-b3-sparc-netinst.iso
Date: Nov 2, 2012
Machine: Sun Ultra 2
Processor: 2 x 400 Mhz
Memory: 1 GB
Partitions: 2 internal SCSI disks, left 10 MB free at disk start. RAID 1 partitions for
/boot 90 MB
/ 30 GB
/tmp 2 GB
non-RAID swap partition with remaining space on each disk.
Each file system was set as ext3.
Output of lspci -knn (or lspci -nn): non-working, cannot produce
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [E]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems: System hung during package installs for Desktop Environment, SSH services
and basic system package sets. System hang was reproducible at same spot.
Watched VT screen of F4 and there was no kernel dump or error.
The system became unresponsive. Pressing numlock or caps lock
had no effect on LED for same. One first attempt, used apt repo at Dal.ca. On second
attempt used apt repo at uwaterloo.ca Computer Science club. No difference.
Sorry I don't have the final line of the package that was being downloaded
at the time the system stopped responding. I can tell you it did download
perhaps 100 to 300 packages before it seized. It gave no error. It behaved
as if it was taking a long time to download or whatever, except
that when I checked after 30 minutes or so of no progress, I saw the keyboard
wasn't responding with the standard numlock/capslock LED test of system health.
Control-Alt F1, etc. were also attempted to see what another VT might show.
Finally, a Stop-A was done, which should cause the PROM to pop us out to a ok >
prompt, and it did nothing.
This failure was observed twice, once with the progress bar view,
and once with the details view from F4 virtual terminal.
System seemed healthy prior to install attempt - it had been running Solaris 10 with ZFS
mirrored RAID on same disks for a few years and no hardware problems.
--Donald Teed
Reply to: