Bug#486168: Lenny Beta2 Kernel Panic - fails to re-boot on HP Netserver E60

[Chris Bell <chrisbell@overview.demon.co.uk>]

On Tuesday 17 June 2008 16:49, Frans Pop wrote:
> reassign 486168 linux-2.6 2.6.24-7
> thanks
>
> On Friday 13 June 2008, Chris Bell wrote:
> > Comments/Problems:
> > On re-boot the A channel is identified, but kernel panic while checking
> > the B channel.
> >
> > scsi 0 : adaptec AIC 7xxx EISA/VLB/PCI SCSI HBA Driver, Rev 7.0
> >             <Adaptec aic 7895 Ultra SCSI adapter>
> >             aic 7895C: UltraWide Channel A, SCSI Id=7, 32/253 SCBs
> > ACPI : PCI Interrpt 0000:00:05.1 [B] -> GSI 18 (level, low) -> IRQ 17
> > Kernel Panic - not syncing: HOST_MSG_LOOP with invalid SCB ff
>
> I would expect some more info about the kernel panic after this (register
> values and such). That info will be needed to follow up on this.
>
> As this is a kernel panic after the reboot after the installation is
> completed, this is not an installation issue, but a kernel issue. For
> that reason I'm reassigning the report to the kernel team.
>
> It is a bit strange though that you don't see the same panic during the
> installation. This indicates that the problem may be either that a
> slightly different kernel is used, or that the order in which modules are
> loaded and things get initialized makes a difference.
>
> Here are some things you can try and check.
>
> - Run the installer again, but start it in "rescue mode".
> - Check if your conroller gets detected again without problems.
> - If it is, start a chroot shell on your / partition, either as offered
>   by the installer or manually from VT2 or VT3; if needed mount any other
>   partitions.

Thanks for the reply.
Unfortunately I am even more confused now.
   I had left the computer with separate partitions auto-configured in LVM on 
the /sda, 686 kernel, and GRUB2. I decided to make it simple and re-install 
the base system with standard desktop, 686 kernel, and GRUB on a single / 
partition (tried before within the last few days but it gave the same kernel 
panic).
   It did re-boot first time, so I used ftp to dump a copy of all logs to 
another machine. I then tried another re-boot, and it has failed to boot with 
the same kernel panic every time for more than 10 attempts. The installer 
rescue system did boot, but I started to consider an obscure hardware fault.
   I am using cfdisc and mke2fs -c -c from Knoppix 5.1.1 to check the 
entire /sda (I have done it before, and no errors so far this time), and will 
then try another installation using the 486 kernel, and will keep you 
informed.  I have apt-proxy running on another Lenny box, so installation is 
relatively quick. 


>
> Cheers,
> FJP

-- 
Chris Bell