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. - Install the -486 flavor of the 2.6.24-1 kernel for the installed system. That is the same kernel as the installer uses. Check if the installed system boots with that. - Save the output of dmesg and lsmod of the installer and compare that with what you see during a normal boot. It may provide clues. For example, do 'dmesg >/var/log/dmesg.txt' and then use the "Save debug logs" option in the main menu of the installer. - Check that the installer and the installed system actually load the same driver module for your disk (I expect they do). - Install the 2.6.25 kernel from unstable and see if that solves the problem. If using the -486 flavor of .24 solved the problem, try both flavors of .25! If the panic also occurs with 2.6.25, you can consider also filing a bug with the upstream kernel developers, but please keep this report updated about any progress if you do. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]