1 |
2010/10/6 Olaf Krause <gentoo_ac@××××.de>: |
2 |
>>> Hello, |
3 |
>>> |
4 |
>>> first: where should I ask the following question? |
5 |
>>> |
6 |
>>> We successfully operate some HP Proliant DL380 G3, using Gentoo |
7 |
>>> Xen-kernels |
8 |
>>> as Dom0 and DomU. |
9 |
>>> Now i tried to upgrade to Generation 4 and 6: |
10 |
>>> * HP Proliant DL380 G4 |
11 |
>>> * HP Proliant DL380 G6 |
12 |
>>> |
13 |
>>> Grub works fine. After selecting a kernel to boot, it is loaded and |
14 |
>>> starts |
15 |
>>> operating and fails some lines later with a kernel panic. The kernel |
16 |
>>> seems |
17 |
>>> not to find the HP SCSI controller (/dev/cciss/...). |
18 |
>>> |
19 |
>>> I made sure, that the kernel has build in the needed drivers as described |
20 |
>>> here: |
21 |
>>> http://en.gentoo-wiki.com/wiki/HP_ProLiant_DL380_G5 |
22 |
>>> |
23 |
>>> Funny is, that the Gentoo boot images do work, for example |
24 |
>>> install-x86-minimal-20100216.iso. |
25 |
>>> |
26 |
>>> I use the iso images to boot the system initially, initialize the SCSI |
27 |
>>> disks |
28 |
>>> with fdsik and mkfs... and then mount the SCSI drives (/dev/cciss/...), |
29 |
>>> copy |
30 |
>>> a working tarball-image, populate the filsystem and then use the grub |
31 |
>>> shell |
32 |
>>> make it bootable. |
33 |
>>> |
34 |
>>> Attached is a screen shot with the error message. |
35 |
>>> |
36 |
>> |
37 |
>> Is this screenshot from a domU or dom0 ? If it's from a domU then I |
38 |
>> think that in Xen you have a different driver than cciss for the |
39 |
>> disks. |
40 |
>> |
41 |
>> If it's from a dom0, are you sure that you have the cciss driver |
42 |
>> built-in instead of a module ? From the screenshot it seems that it's |
43 |
>> not present at the point the kernel is booting. |
44 |
> |
45 |
> It is the screenshot of the Dom0. And yes - also for me the driver seems not |
46 |
> to be available during boot time. But i am sure to have it build in. And on |
47 |
> older hardware (G3 - generation 3 HP hardware) the same kernel seems to |
48 |
> work, mounting the cciss devices. |
49 |
> |
50 |
> Here is what mount says in the same kernel on a G3 hardware (sorry for the |
51 |
> linebreaks): |
52 |
> ---- |
53 |
> orion ~ # mount |
54 |
> /dev/cciss/c0d0p1 on / type ext3 (rw,noatime) |
55 |
> proc on /proc type proc (rw,nosuid,nodev,noexec) |
56 |
> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec) |
57 |
> udev on /dev type tmpfs (rw,nosuid,size=10240k,mode=755) |
58 |
> devpts on /dev/pts type devpts (rw,nosuid,noexec,gid=5,mode=620) |
59 |
> /dev/cciss/c0d1p1 on /mnt/xen2 type ext3 (rw,noatime) |
60 |
> shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev) |
61 |
> usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85) |
62 |
> --- |
63 |
> |
64 |
|
65 |
Maybe the cciss driver doesn't have your controller on the PCI devices |
66 |
list. This is unlikely but would give the symptoms you are describing. |
67 |
Please post the output of 'lspci -k' and 'lspci -n' commands. Which |
68 |
kernel version are you trying to run ? |
69 |
|
70 |
-- |
71 |
Maciej Grela |