[Bug 251483] after upgrading from 12.1 to 12.2 the mfi driver crashes during boot
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 30 15:01:16 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251483
Bug ID: 251483
Summary: after upgrading from 12.1 to 12.2 the mfi driver
crashes during boot
Product: Base System
Version: 12.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: cstamas+fbsdbz at digitus.itk.ppke.hu
Hi,
I have a Dell R740 server with PERC H330 Mini card in HBA mode.
The install was done using 12.1 and today I upgraded to 12.2 with
freebsd-update.
The kernel crashes now during boot. (I attached the captured serial logs
below.)
Following the recommendation from the friendly folks on #freebsdhelp I was able
to boot up
the system by setting hw.mfi.mrsas_enable="1" in the bootloader. This is not
ideal at the moment
as ZFS complains about difference in configured vs. native blocksizes.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
lo0: bpf attached
vlan: initialized, using hash tables with chaining
tcp_init: net.inet.tcp.tcbhashsize auto tuned to 1048576
IPsec: Initialized Security Association Processing.
hptnr: no controller detected.
hptrr: no controller detected.
hpt27xx: no controller detected.
ahcich0: AHCI reset...
ugen0.1: <0x8086 XHCI root HUB> at usbus0
mfisyspd0 numa-domain 0 on mfi0
mfisyspd0: 7630885MB (15628053168 sectors) SYSPD volume (deviceid: 0)
mfisyspd0: SYSPD volume attached
GEOM: new disk mfisyspd0
ahcich0: SATA connect timeout time=10000us status=00000000
ahcich0: AHCI reset: device not found
ahcich1: AHCI reset...
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ahcich1: SATA connect timeout time=10000us status=00000000
ahcich1: AHCI reset: device not found
mfisyspd1 numa-domain 0 on mfi0
ahcich2: AHCI reset...
mfi0: DJA NA XXX SYSPDIO
Fatal trap 12: page fault while in kernel mode
cpuid = 14; apic id = 14
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff806d040b
stack pointer = 0x28:0xfffffe00faad61c0
frame pointer = 0x28:0xfffffe00faad61f0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 13 (g_down)
trap number = 12
panic: page fault
cpuid = 14
time = 1
KDB: stack backtrace:
#0 0xffffffff80c0a8f5 at kdb_backtrace+0x65
#1 0xffffffff80bbeb1b at vpanic+0x17b
#2 0xffffffff80bbe993 at panic+0x43
#3 0xffffffff8108f911 at trap_fatal+0x391
#4 0xffffffff8108f96f at trap_pfault+0x4f
#5 0xffffffff8108efb6 at trap+0x286
#6 0xffffffff81066f38 at calltrap+0x8
#7 0xffffffff806c92b8 at mfi_send_frame+0x28
#8 0xffffffff806c91a9 at mfi_data_cb+0x359
#9 0xffffffff80c00382 at bus_dmamap_load_bio+0xb2
#10 0xffffffff806c8cce at mfi_mapcmd+0xae
#11 0xffffffff806c802b at mfi_startio+0xdb
#12 0xffffffff806ce3d9 at mfi_syspd_strategy+0x99
#13 0xffffffff80b07d85 at g_disk_start+0x325
#14 0xffffffff80b0bd49 at g_io_schedule_down+0x169
#15 0xffffffff80b0c57c at g_down_procbody+0x6c
#16 0xffffffff80b8044e at fork_exit+0x7e
#17 0xffffffff81067f6e at fork_trampoline+0xe
Uptime: 1s
these kernels work fine:
Jul 27 12:55:31 backup20vh kernel: FreeBSD 12.1-RELEASE r354233 GENERIC amd64
Sep 2 15:56:28 backup20vh kernel: FreeBSD 12.1-RELEASE-p8 GENERIC amd64
Nov 30 14:49:50 backup20vh kernel: FreeBSD 12.1-RELEASE-p10 GENERIC amd64
Nov 30 15:03:10 backup20vh kernel: FreeBSD 12.1-RELEASE-p10 GENERIC amd64
this is the one with the issue:
Nov 30 14:29:59 backup20vh kernel: FreeBSD 12.2-RELEASE r366954 GENERIC amd64
Regards,
cstamas
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list