Koozali.org: home of the SME Server

7.0pre3 installation - kernel panic on new hardware

jaykay

7.0pre3 installation - kernel panic on new hardware
« on: February 21, 2006, 12:05:00 PM »
I'm running an AMD 64bit processor with 1GB of RAM, and 2 WD SATA 80GB HDDs with a hardware RAID connection, and an LG DVD/CD -RW.

I initially tried installing v6.0.1 but it refused to recognise the HDD.  After a bit of research I realised I needed v7.0 to work with the disks.  The first time I tried installing everything went well, but there was a GRUB error 2 when it tried to load.  I then tried doing a fresh installation, and made it 96% of the way.  On the 3rd attempt it crashed at 47%.  There doesn't seem to be anything wrong with the installation disk - the checksum on the ISO file was OK, and the check of the installation media doesn't reveal any abnormalities.

The error shown on the last two attempts is:
Kernel panic - not syncing: drivers/scsi/scsi_lib.c:343: spin_lock (drivers/scsi/libata-core.c:f7a9d300) already locked by drivers/scsi/libata-core.c/3573

This seems a little different to the kernel panics that others have experienced.  Is this a problem with v7.0pre3 that needs to be reported to bugzilla, or is there a more mundane explanation?

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: 7.0pre3 installation - kernel panic on new hardware
« Reply #1 on: February 22, 2006, 02:35:53 AM »
Quote from: "jaykay"
I'm running an AMD 64bit processor with 1GB of RAM, and 2 WD SATA 80GB HDDs with a hardware RAID connection, and an LG DVD/CD -RW.

Real hardware RAID (i.e. appears as a single disk), or BIOS assist RAID? If the latter, I'd disable it - you may have the kernel and RAID card fighting. You should also try the same install with CentOS 4.2 to compare. This may also be an x86_64 issue.
Quote from: "jaykay"

This seems a little different to the kernel panics that others have experienced.  Is this a problem with v7.0pre3 that needs to be reported to bugzilla, or is there a more mundane explanation?

Anything you do not expect should be reported to the bug tracker, with what you expected to happen and what you saw. Thanks.
............