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

Bug#275761: marked as done ([sparc][businesscard][20041009] Failure, Sun Ultra 10)

Your message dated Wed, 08 Sep 2010 03:57:42 +0000
with message-id <E1OtBn4-00049W-VL@ravel.debian.org>
and subject line Closing old installation report #275761
has caused the Debian Bug report #275761,
regarding [sparc][businesscard][20041009] Failure, Sun Ultra 10
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.)


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

INSTALL REPORT

Debian-installer-version:
 businesscard 20041009 from
 http://cdimage.debian.org/pub/cdimage-testing/daily/sparc/20041009/sarge-sparc-businesscard.iso (md5sum )

uname -a: 2.4.27
Date: 20040 10 10
Method:
  hit L1-A after openboot banner appears
  type 'boot cdrom'  in OpenBoot Prom 3.25
  type <return> to start installer


Machine: Sun Ultra 10 UPA/PCI OpenBoot 3.25
 same hardware as  Bug#275628

Processor: UltraSPARC-IIi 440MHz
Memory: 256Mb (50ns)
Root Device: IDE
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]
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:

Same hardware as bug Bug#275628. We get further, but not much.
Feel free to merge if appropriate.


Logs, or as much as I could transcribe:

....
Uniform Multi-platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes: override with idebus=xx
CMD646: IDE controller at PCI slot 01:03.0
CMD646: chipset revision 3
CMD646: chipset revision 0x03, MultiWord DMA Force Limited
   ide0: BM-DMA at 0x1fe02c00020-0x1fe02c00027, BIOS settings: hda:pio, hdb:pio
   ide1: BM-DMA at 0x1fe02c00028-0x1fe02c0002f, BIOS settings: hdc:pio, hdd:pio
CMD646: 100% native mode on irq4,7e0
hda: ST39111A, ATA Disk drive
ide: Assuming 33MHz system bus speed for PIO modes: override with idebus=xx
hdc: CRD-8322B, ATAPI CD/DVD-ROM drive
ide0 at 0x1fe02c00007,0x1fe02c0000a on irq 4,7e8
ide1 at 0x1fe02c00017,0x1fe02c0001a on irq 4,7e0 (shared with ide0)
Partion check:
  hda:end_request: I/O error, dev 03:00 (hda) sector 0
end_request: I/0 error, dev 03:00 (hda), sector 2
end_request: I/0 error, dev 03:00 (hda), sector 4
end_request: I/0 error, dev 03:00 (hda), sector 6
end_request: I/0 error, dev 03:00 (hda), sector 8
end_request: I/0 error, dev 03:00 (hda), sector 10
end_request: I/0 error, dev 03:00 (hda), sector 12
end_request: I/0 error, dev 03:00 (hda), sector 14
end_request: I/0 error, dev 03:00 (hda), sector 2
end_request: I/0 error, dev 03:00 (hda), sector 4
end_request: I/0 error, dev 03:00 (hda), sector 6
end_request: I/0 error, dev 03:00 (hda), sector 8
end_request: I/0 error, dev 03:00 (hda), sector 10
end_request: I/0 error, dev 03:00 (hda), sector 12
end_request: I/0 error, dev 03:00 (hda), sector 14
 unable to read partition table
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver usbmouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb.c: registered new driver usbkbd
usbkbd.c: USB HID Boot Protocol keyboard driver
mice: PS/2 mouse device common for all mice
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tabels configured (established 32768 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
RAMDISK: couldn't find valid RAM disk image starting at 0
Freeing initrd memory: 2823k freed
VFS: Mounted root (ext2 filesystem)
Mounted devfs on /dev
Trying to moove old root to /initrd ... okay
VFS: Mounted root (ext2 filesystem)
Mounted devfs on /dev
Setting up filesystem, please wait ...
~Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Unimplemented SPARC system call 188
Starting system log daemon: syslogd, klogd.
insmod: usbkbd.o: no module by that name found
modprobe: failed to load module usbkbd
insmod: hid.o: no module by that name found
modprobe: failed to load module hid
insmod: keybdev.o: no module by that name found
modprobe: failed to load module keybdev
insmod: usbserial.o: no module by that name found
modprobe: failed to load module usbserial
(process:238): INFO: kbd-mode: setting console mode to Unicode (UTF-8)

Segmentation fault
                  Segmentation fault
                                    Segmentation fault

... endlessly
At the time the segfault messages start, the frame buffer turns
partially red.
In solaris there are two graphics devices listed,
ffb0, "Creator 3D series2 (FFB2+)", and
m64/0, "ATI PGX32 24-bit"

The keyboard still works, it is not a usb keyboard but the older
style (Sun  Type-5 US PC)

I also tried this boot line:
  boot: linux debian-installer/framebuffer=false

This was completely ignored, ie the installer turned on the
framebuffer display, and failed in the same way.
Perhaps my syntax is off? Not according to
  http://www.debian.org/devel/debian-installer/errata

--- 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: