Project

General

Profile

Actions

Bug #1637

closed

HP DL360G4 Smart Array 6i issue

Added by Graaf_van_Vlaanderen about 14 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

During USB boot DragonFly BSD 2.4.1 AMD64 hangs on a HP DL360 G4 with the
following (last) message:

"ciss0:<HP Smart Array 6i> port 0x4000-0x40ff mem 0xfdf80000-0xfdfbfff,
0xfdff0000-0xfdff1fff irq5 at device 1.0 on pci2"

This is the SCSI version of the HP DL360 G4 series.

I have currently three of these machines and they all run without issues on
FreeBSD 8.0 AMD64

If you need any log files from FreeBSD operation, contact me.


Files

sysctl_DFBSD_Latest_AMD64 (24.3 KB) sysctl_DFBSD_Latest_AMD64 Graaf_van_Vlaanderen, 01/10/2010 03:33 PM
dmesg_DFBSD_Latest (10.2 KB) dmesg_DFBSD_Latest Graaf_van_Vlaanderen, 01/10/2010 03:35 PM
camcontrol_out (380 Bytes) camcontrol_out Graaf_van_Vlaanderen, 01/10/2010 03:35 PM
Actions #1

Updated by tuxillo about 14 years ago

Hi,

Can you please provided a verbose boot for that machine? This can be achieved by
selecting option 5 on the dragonfly menu options.

Thanks,
Antonio

Actions #2

Updated by tuxillo about 14 years ago

Hi again,

Could you please also try to boot with the lastest AMD64 ISO image. You can grab
it here:
http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/x86_64/LATEST-x86_64-master.iso.bz2

Cheers,
Antonio Huete

Actions #3

Updated by Graaf_van_Vlaanderen about 14 years ago

I just tested the latest version and it works now.
However I can not start the 'installer' because of a read only issue:
"/usr/sbin/installer cannot create /tmp/ps.txt read only file system."
For the same reason I cannot bring up the Broadcom NICs and cannot create
network connections, hence I needed to mount a USB stick to transfer the info
too.

I attached a couple of files that might be helpful for you:

dmesg -a; sysctl -a and camcontrol devlist

To summarize: the machine is a HP DL360 G4 with 8GB and two 3GHz 1MB cache HT
CPU's. If you need more info feel free to ask.

Actions #4

Updated by swildner about 14 years ago

It's because you are using a USB image and the file system somehow got dirty
(see dmesg).

I think you can do several things:

1) Just dd the img once more and try again (maybe set write protection on the
USB stick).

2) Login as root and do fsck /dev/da8s1a. When it's finished, reboot cleanly
using "shutdown -r now".

Regards,
Sascha

Actions #5

Updated by swildner about 14 years ago

About the bge, can you try setting it to polling mode? bge(4) supports that
AFAICS. Try logging in as root on some vty and do:

ifconfig bge0 polling

and see if that improves matters.

Regards,
Sascha

Actions #6

Updated by swildner about 14 years ago

It turned out that our USB images don't run fsck but / is mounted read/write.

I've committed a fix for that:

http://leaf.dragonflybsd.org/mailarchive/commits/2010-01/msg00038.html

Sascha

Actions #7

Updated by Graaf_van_Vlaanderen about 14 years ago

I took another USB-stick (which didn't want to boot), cleared (newfs) it and
moved the image to it.
Then I booted the stick and saw the same type of errors as with the other stick.
Then I performed what was recommmended: fsck /dev/da8s1 and rebooted with
  1. shutdown -r now
    I could run the installer and successfully installed (with HammerFS) on the
    second drive.

Currently the main issue is trying to make a network connection. This fails
completely. Polling doesn't help. In FreeBSD this machine works fine with both
interfaces in laggproto. Here bge0 gives 'no carrier', while bge1 is so called
'active'. In no cases I can reach the default router in other words the outer
world. Enabling DHCP creates a time out. I guess something is wrong with the
drivers of these NICs.

Actions #8

Updated by swildner about 14 years ago

Hmm just to rule that out:

Can you try booting a i386 (not x86_64) image and see if it works there?

Sascha

Actions #9

Updated by Graaf_van_Vlaanderen about 14 years ago

I just tried this morning with the 32-bit version but with little success.
The same behavior and errors appear.
I will also try on a HP DL320 G5, since the Broadcom NICs are different (at
least 200Mb/s faster than those in HP DL360G4)
Additionally I will try to add a PCI NIC in the DL360 G4.
By the way how can I see multiple CPUs in 'top'? The '-M' option doesn't seem to
work.

Actions #10

Updated by Graaf_van_Vlaanderen about 14 years ago

Some extra feedback:

HP DL360 G4:

Adding another NIC failed and made the system hang. I think this is a hardware
issue. The NIC is a D-Link 528T PCI gigabit ethernet adapter which I inserted
into a PCI-X slot.

HP DL320 G5:

I couldn't test those Broadcom NICs, since I ran into the well known 'mountroot'
issue.

Actions #11

Updated by tuxillo about 14 years ago

Hi

Did you have the mountroot issue in i386 also?

Cheers,
Antonio

Actions #12

Updated by Graaf_van_Vlaanderen about 14 years ago

Yes, I have seen this issue for both i86 and amd64, this on the HP DL320 G5
which uses SATA as HDs.

I used to see this issue also with CD-ROM boot of DragonFly 2.4.1. on the HP
DL360 G4 (SCSI). I did not see this issue when booting through USB-stick with
the snap shots of last week.

Actions #13

Updated by elekktretterr about 14 years ago

Emmanuel De Paepe <> added the comment:

Yes, I have seen this issue for both i86 and amd64, this on the HP DL320
G5
which uses SATA as HDs.

I had a similar/same issue with where boot froze while initializing ciss.
I saw this problem on x86_64 but I believe it was fixed a month ago or so
in this commit:

http://leaf.dragonflybsd.org/mailarchive/commits/2009-12/msg00130.html

Petr

Actions #14

Updated by ftigeot about 12 years ago

  • Status changed from New to Resolved

Closing due to lack of recent feedback.

Actions #15

Updated by ftigeot about 12 years ago

  • Status changed from Resolved to Closed

Resolved, closing.

Actions

Also available in: Atom PDF