Bug#286467: sparcstation lx install 20041218 image -- kernel oops at end
Package: installation-reports
INSTALL REPORT
Debian-installer-version: 20041218
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/sparc/20041219/sarge-sparc-netinst.iso
uname -a: Linux blast 2.4.27-1-sparc32 #1 Tue Aug 24 01:05:41 PDT 2004 sparc GNU/Linux
Date: 2004-12-19 22:00
Method: How did you install? netboot cd
What did you boot off? netboot cd
Machine: sparcstation LX
Processor: sparc32 / sun4m
Memory: 96 MB
Root Device:
Root Size/partition table:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 3822840 210112 3418536 6% /
tmpfs 45084 0 45084 0% /dev/shm
/dev/sda1 92725 7953 79825 10% /boot
Output of lspci and lspci -n:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
fsbe and sunvideo sbus bords installed, not in use.
serial console.
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: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
****
Comments/Problems:
The image I downloaded appears to have been overwritten by a newer one
in the same directory.
Install went fine (other than the long pauses) until stage 2 was
exiting. When I should have gotten the login prompt, instead an error
repeated (batch of a couple dozen, pause, repeat) until I hit control
C and got a kernel oops:
zs_open tts/%d0, tty overwrite.
zs_open tts/%d0, tty overwrite.
zs_open tts/%d0, tty overwrite.
zs_open tts/%d0, tty overwrite.
Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 0000002a
tsk->{mm,active_mm}->pgd = fc00c000
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
swapper(0): Oops
PSR: 41401fc6 PC: f00e1c40 NPC: f00e1bf8 Y: 00000000 Not tainted
g0: f057dc78 g1: 00000000 g2: 00000000 g3: 00000000 g4: f01df634 g5: fffffc18 g6: f000e000 g7: 00000001
o0: 00000003 o1: 00000001 o2: 00000001 o3: f0199000 o4: f01994b4 o5: f000e000 sp: f000fc70 o7: f00e1a28
l0: 00000007 l1: f3266000 l2: 00000003 l3: 00000001 l4: f01e704c l5: 00000000 l6: 00000000 l7: f0052a84
i0: f021f060 i1: f000fe08 i2: 000000e4 i3: 00000000 i4: 00029461 i5: 74000000 fp: f000fcd8 i7: f00e1eec
Caller[f00e1eec]
Caller[f0014e44]
Caller[f0012668]
Caller[f0012668]
Caller[f00161a4]
Caller[f01b4eec]
Caller[f01b4790]
Caller[00000000]
Instruction DUMP: 10bffff0 84102002 10bfffef <c0284000> 7ffce52d 81e80000 7fffff1b 81e80000 7ffff9ad
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
Press L1-A to return to the boot prom
Machine was usable after power cycling it.
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: