Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Nov 2019 13:13:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 241735] kernel panic while booting on Intel Server Board S2600WF (wolfpass) when Installing intel Volume management Driver(VMD) and enabling VMD in Bios
Message-ID:  <bug-241735-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241735

            Bug ID: 241735
           Summary: kernel panic while booting on Intel Server Board
                    S2600WF (wolfpass) when Installing intel Volume
                    management Driver(VMD) and enabling VMD in Bios
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: surya.prakashx.jagatha@intel.com

Created attachment 208878
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D208878&action=
=3Dedit
kernel panic while booting on Intel Server Board S2600WF (wolfpass) when
Installing intel Volume management Driver(VMD) and enabling VMD in Bios

Product: Intel=C2=AE Server Board S2600WF Family

Code Name:  Products formerly Wolf Pass
Intel=C2=AE Xeon=C2=AE Scalable Processors
Supports Volume management : Yes

1) Enabled "Volume Management Device (VMD)" in BIOS.
2) Downloaded source/patch for Volume Management Device Source from
(https://github.com/freebsd/freebsd/commit/235ed49b64e7294cfe26e8c619c13717=
d7e44683)
3) installed Volume Management Device (VMD) on S2600WF (Wolfpass )=20
4) issued reboot
5) During Boot time kernel panic due to VMD (volume management Device)

please find the attached screenshot for the same.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241735-227>