i386/147929: hptiop(4) (HighPoint RocketRAID 3xxx/4xxx driver)
broken on FreeBSD 8.1-PRERELEASE
Masayuki FUKUI
fukui.FreeBSD at fanet.net
Thu Jun 17 02:40:04 UTC 2010
>Number: 147929
>Category: i386
>Synopsis: hptiop(4) (HighPoint RocketRAID 3xxx/4xxx driver) broken on FreeBSD 8.1-PRERELEASE
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jun 17 02:40:03 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Masayuki FUKUI
>Release: FreeBSD 8.1-PRERELEASE amd64
>Organization:
>Environment:
System: FreeBSD master 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Sat Jun 5 11:07:11 JST 2010 root at master:/usr/src/sys/amd64/compile/master amd64
>Description:
Fails to boot FreeBSD 8.1-PRERELEASE from RAID volume under hptiop(4) (HighPoint RocketRAID 3xxx/4xxx RAID controller).
RAID controller seems to be detected normally as hptiop(4). However, RAID volume is not detected at all.
hptiop(4) had operated normally on FreeBSD 7.2-RELEASE.
dmesg:
...
<snip>
...
hptiop0: adapter at PCI 1:0:0, IRQ 16
hptiop0: <RocketRAID 3510 SATA Controller
> mem 0xfdf00000-0xfdffffff irq 16 at device 0.0 on pci1
hptiop0: 0 RocketRAID 3xxx/4xxx controller driver v1.3 (010208)
xpt_dev_async_default called
hptiop0: [GIANT-LOCKED]
hptiop0: [ITHREAD]
...
<snip>
...
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Trying to mount root from ufs:/dev/da0p2
ROOT MOUNT ERROR:
If you have invalid mount options, reboot, and first try the following from
the loader prompt:
set vfs.root.mountfrom.options=rw
and then remove invalid mount options from /etc/fstab.
Loader variables:
vfs.root.mountfrom=ufs:/dev/da0p2
vfs.root.mountfrom.options=rw,noatime
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
...
<snip>
...
mountroot>
>How-To-Repeat:
Try to boot FreeBSD 8.1-PRERELEASE with RAID volume under HighPoint RocketRAID 3xxx/4xxx.
>Fix:
I do not understand the cause though I am debugging.
During boot FreeBSD 7.2-RELEASE, xpt_scan_lun() (in src/sys/cam/cam_xpt.c) seems to be called immediately after hptiop(4) is detected.
However, during boot FreeBSD 8.1-PRERELEASE, scsi_scan_lun() (in src/sys/cam/scsi/scsi_xpt.c) seems never to be called after hptiop(4) is detected.
Probing RAID volumes seems not to start at all.
I hope this problem solves by the time FreeBSD 8.1 is released.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-i386
mailing list