<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Fatal trap 12: page fault while in kernel mode in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/150001#M9564</link>
    <description>&lt;P&gt;The issue was resolved after replacing multiple parts, SAS Card, Mother Board, IOXM, Chassis and NVRAM&lt;/P&gt;</description>
    <pubDate>Sat, 03 Aug 2019 01:37:46 GMT</pubDate>
    <dc:creator>ashwin</dc:creator>
    <dc:date>2019-08-03T01:37:46Z</dc:date>
    <item>
      <title>Fatal trap 12: page fault while in kernel mode</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148829#M9482</link>
      <description>&lt;P&gt;FAS6250 unable to bbot after multiple parts replacement&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Starting AUTOBOOT press Ctrl-C to abort...&lt;BR /&gt;Loading X86_64/freebsd/image1/kernel:0x100000/9574160 0xa21710/4044936 Entry at 0x8016e4a0&lt;BR /&gt;Loading X86_64/freebsd/image1/platform.ko:0xdfd000/785704 0xf9ad68/724104 0xebcd40/45064 0x104b9f0/49728 0xec7d48/110175 0xee2ba7/80605 0xef66a0/172160 0x1057c30/195312 0xf20720/16 0xf20730/2448 0x1087720/7344 0xf21100/0 0xf21100/344 0x10893d0/1032 0xf21258/1952 0x10897d8/5856 0xf219f8/1648 0x108aeb8/4944 0xf22068/240 0x108c208/720 0xf22160/448 0xf5d860/14942 0xf9ac6b/253 0xf612c0/136560 0xf82830/99387 &lt;BR /&gt;Starting program at 0x8016e4a0&lt;BR /&gt;NetApp Data ONTAP 8.2.3P1 7-Mode&lt;/P&gt;
&lt;P&gt;Copyright (C) 1992-2015 NetApp.&lt;BR /&gt;All rights reserved.&lt;BR /&gt;Checking boot device filesystem&lt;BR /&gt;** /dev/da0s1&lt;BR /&gt;** Phase 1 - Read and Compare FATs&lt;BR /&gt;** Phase 2 - Check Cluster Chains&lt;BR /&gt;** Phase 3 - Checking Directories&lt;BR /&gt;** Phase 4 - Checking for Lost Files&lt;BR /&gt;65 files, 1259328 free (39354 clusters)&lt;BR /&gt;MARK FILE SYSTEM CLEAN? yes&lt;BR /&gt;MARKING FILE SYSTEM CLEAN&lt;BR /&gt;Retry #1 of 5: /sbin/fsck_msdosfs /dev/da0s1&lt;BR /&gt;Retry #2 of 5: /sbin/fsck_msdosfs /dev/da0s1&lt;BR /&gt;Repaired boot device filesystem&lt;BR /&gt;md1.uzip: 39168 x 16384 blocks&lt;BR /&gt;md2.uzip: 15360 x 16384 blocks&lt;BR /&gt;*******************************&lt;BR /&gt;* *&lt;BR /&gt;* Press Ctrl-C for Boot Menu. *&lt;BR /&gt;* *&lt;BR /&gt;*******************************&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Fatal trap 12: page fault while in kernel mode&lt;BR /&gt;cpuid = 5; apic id = 12&lt;BR /&gt;fault virtual address = 0x0&lt;BR /&gt;fault code = supervisor read data, page not present&lt;BR /&gt;instruction pointer = 0x20:0xffffffff80e1bb6d&lt;BR /&gt;stack pointer = 0x28:0xffffff805bd48b30&lt;BR /&gt;frame pointer = 0x28:0xffffff805bd48b90&lt;BR /&gt;code segment = base 0x0, limit 0xfffff, type 0x1b&lt;BR /&gt;= DPL 0, pres 1, long 1, def32 0, gran 1&lt;BR /&gt;processor eflags = interrupt enabled, resume, IOPL = 0&lt;BR /&gt;current process = 5 (g_down)&lt;BR /&gt;trap number = 12&lt;BR /&gt;PANIC : page fault (supervisor read, page not present) on VA 0 cs:rip = 0x20:0xffffffff80e1bb6d rflags = 0x10286&lt;BR /&gt;version: 8.2.3P1: Mon Feb 2 07:45:33 PST 2015&lt;BR /&gt;conf : x86_64&lt;BR /&gt;cpuid = 5&lt;BR /&gt;Uptime: 19s&lt;BR /&gt;coredump: primary dumper unavailable.&lt;BR /&gt;coredump: trying secondary dumper...&lt;BR /&gt;no tftp server ip specified &lt;BR /&gt;netdump: no targets available to dump&lt;BR /&gt;coredump: secondary dumper failed -1.&lt;BR /&gt;System halting...&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:28:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148829#M9482</guid>
      <dc:creator>ashwin</dc:creator>
      <dc:date>2025-06-04T12:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: Fatal trap 12: page fault while in kernel mode</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148863#M9483</link>
      <description>&lt;P&gt;I would upload the core file if you can get it off. It sounds like a software panic to me. If you don't have a support case open go ahead and open one.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 13:02:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148863#M9483</guid>
      <dc:creator>paul_stejskal</dc:creator>
      <dc:date>2019-06-13T13:02:02Z</dc:date>
    </item>
    <item>
      <title>Re: Fatal trap 12: page fault while in kernel mode</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148865#M9484</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Try to pull and re-seat the FAS6250 controller module if you have not already done so&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2019 13:33:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/148865#M9484</guid>
      <dc:creator>COMITSUPPORT</dc:creator>
      <dc:date>2019-06-13T13:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Fatal trap 12: page fault while in kernel mode</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/150001#M9564</link>
      <description>&lt;P&gt;The issue was resolved after replacing multiple parts, SAS Card, Mother Board, IOXM, Chassis and NVRAM&lt;/P&gt;</description>
      <pubDate>Sat, 03 Aug 2019 01:37:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Fatal-trap-12-page-fault-while-in-kernel-mode/m-p/150001#M9564</guid>
      <dc:creator>ashwin</dc:creator>
      <dc:date>2019-08-03T01:37:46Z</dc:date>
    </item>
  </channel>
</rss>

