[Aurora-sparc-user] Re: Kernel panic when installing on SS10

[T. Ribbrock]

On Thu, Aug 03, 2006 at 05:11:23PM +0200, T. Ribbrock wrote:
> I still haven't succeeded in installing Aurora 2.0 on my SS10 - the
> install always fails in the same spot: right after installing
> glibc-common, the machine hangs and then produces a kernel panic (the
> last message is "Aiee, killing interrupt handler").
[...]

By now, I've succesfully installed Aurora 1.0 on that box[0]. The
install went without a hitch (contrary to 2.0...). The only thing I
noticed was in the dmesg when I booted the system for the first time:

[...]
VFS: Mounted root (ext2 filesystem).
esp0: IRQ 36 SCSI ID 7 Clk 40MHz CCYC=25000 CCF=8 TOut 167
NCR53C9XF(espfast)
ESP: Total of 1 ESP hosts found, 1 actually in use.
scsi0 : Sparc ESP100A-FAST
esp0: hoping for msgout
  Vendor: FUJITSU   Model: M2694ES-512       Rev: 8134
  Type:   Direct-Access                      ANSI SCSI revision: 02
  Vendor: CyberDrv  Model:  CD-ROM TW240S    Rev: 1.40
  Type:   CD-ROM                             ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 3, lun 0
SCSI device sda: 2117025 512-byte hdwr sectors (1084 MB)
Partition check:
 sda: sda1 sda2 sda3 sda4
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 308k freed
scsi : aborting command due to timeout : pid 104, scsi0, channel 0, id
3, lun 0 
Read (10) 00 00 17 e4 23 00 00 40 00 
esp0: Aborting command
esp0: dumping state
esp0: dma -- cond_reg<a6400310> addr<f01f4400>
esp0: SW [sreg<11> sstep<04> ireg<10>]
esp0: HW reread [sreg<01> sstep<44> ireg<00>]
esp0: current command [tgt<03> lun<00> pphase<CLUELESS> cphase<DATAIN>]
esp0: disconnected 
SCSI host 0 abort (pid 104) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
esp0: Resetting scsi bus
esp0: Gross error sreg=40
esp0: SCSI bus reset interrupt
esp0: hoping for msgout
Adding Swap: 164000k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,4), internal journal
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
scsi : aborting command due to timeout : pid 1201, scsi0, channel 0, id
3, lun 0
 Read (10) 00 00 10 c2 eb 00 00 18 00 
esp0: Aborting command
esp0: dumping state
esp0: dma -- cond_reg<a6400310> addr<f3d46800>
esp0: SW [sreg<11> sstep<04> ireg<10>]
esp0: HW reread [sreg<01> sstep<c4> ireg<00>]
esp0: current command [tgt<03> lun<00> pphase<CLUELESS> cphase<DATAIN>]
esp0: disconnected 
SCSI host 0 abort (pid 1201) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
esp0: Resetting scsi bus
esp0: Gross error sreg=40
esp0: SCSI bus reset interrupt
esp0: hoping for msgout

Anybody an idea whether this could have anything to do with Aurora 2.0
panicing during install?

Cheerio,

Thomas

[0] shocking, really - the installer is quite a bit faster than the
Aurora 2.0 one - and the minimum install is almost 300MB(!) smaller...
%-}
-- 
-----------------------------------------------------------------------------
                Thomas Ribbrock    http://www.ribbrock.org 
  "You have to live on the edge of reality - to make your dreams come true!"