When I use kernel-2.4.0-test10,I got this problem on my server.

When I use kernel-2.4.0-test10,I got this problem on my server.

[cnchun]

The boot messages is below:
.....
megaraid:v107 (december 22.1999)
megaraid:found 0x8086:0x1960:in 03:0b.1
megaraid:board configure for I2O .ignoring this card.reconfigure the card
megaraid:in the bios for "mass storage" to use it with the driver.
linux pcmcia card services 3.1.22
	options:[pci][cardbus][pw]
i2o_scsi.c:version 0.0.1
chain_pool:0bytes@f7be0b60
(512 byte buffers X4 can_querue X0 i2o controllers)
net4:linux tcp/ip 1.0 for net4.0
ip protocols:icmp,udp,tcp,igmp
ip:routing cache hash table of 16384 buckets. 128Kbytes
tcp:hash tables configured (establiched 131072 bind 65536)
net4:unix domain socket 1.0/smp for linux net4.
kmen_create:forcing size word alignment.nfs_fh
ds:no socket drivers locaded!
vfs:cannot open root device "801" or 08:01
Please append a correct "root=" boot option
...........
kernel panic....

The kernel-2.2.18 can run on my server very well.My server is DELL 6450/550 with 4G MEM and 4 CPU,I also have 2 Raid-5(DELL
Powervault 210s) with 1.6 TG storage.


please help me!







                             

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: When I use kernel-2.4.0-test10,I got this problem on my server.

[Alan Cox]

> The kernel-2.2.18 can run on my server very well.My server is DELL 6450/550 with 4G MEM and 4 CPU,I also have 2 Raid-5(DELL
> Powervault 210s) with 1.6 TG storage.

My fault. 2.4test contains a forward port of some 2.2 experimenting that
was backed out

Try


--- drivers/scsi/megaraid.c~	Tue Oct 31 20:32:01 2000
+++ drivers/scsi/megaraid.c	Wed Nov  8 09:26:17 2000
@@ -1491,21 +1491,6 @@
 	    pciDev,
 	    pdev->slot_name);
 
-    /*
-     *	Dont crash on boot with AMI cards configured for I2O. 
-     *  (our I2O code will find them then they will fail oddly until
-     *   we figure why they upset our I2O code). This driver will die
-     *   if it tries to boot an I2O mode board and we dont stop it now.
-     *     - Alan Cox , Red Hat Software, Jan 2000
-     */
-     	    
-    if((pdev->class >> 8) == PCI_CLASS_INTELLIGENT_I2O)
-    {
-    	printk( KERN_INFO "megaraid: Board configured for I2O, ignoring this card. Reconfigure the card\n"
-		KERN_INFO "megaraid: in the BIOS for \"mass storage\" to use it with this driver.\n");
-	continue;
-    }		
-
     /* Read the base port and IRQ from PCI */
     megaBase = pci_resource_start (pdev, 0);
     megaIrq  = pdev->irq;
@@ -1545,12 +1530,11 @@
     megaCtlrs[numCtlrs++] = megaCfg; 
     if (flag != BOARD_QUARTZ) {
       /* Request our IO Range */
-      if (check_region (megaBase, 16)) {
+      if (request_region (megaBase, 16, "megaraid")) {
 	printk (KERN_WARNING "megaraid: Couldn't register I/O range!" CRLFSTR);
 	scsi_unregister (host);
 	continue;
       }
-      request_region (megaBase, 16, "megaraid");
     }
 
     /* Request our IRQ */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/