Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Jan 2004 15:20:06 -0600 (CST)
From:      "Paul Seniura" <pdseniura@techie.com>
To:        freebsd-current@freebsd.org
Cc:        Paul Seniura <pdseniura@techie.com>
Subject:   Fatal trap 9 GPF while in kernel mode, even with today's CTM bucket
Message-ID:  <20040130212006.4C4D25C34@techpc04.okladot.state.ok.us>
In-Reply-To: <20040128171448.D9EA85C34@techpc04.okladot.state.ok.us>
References:  <20040128171448.D9EA85C34@techpc04.okladot.state.ok.us>

next in thread | previous in thread | raw e-mail | index | archive | help
This is related to previous e-mail referred to in the header of this msg.
The previous msg contains my custom kernel and dmesg editted to show where the hang is.
I think this problem started showing up after Monday eve's CTM bucket before it went south, and it crashed again today after catching up with CTMs and doing makes on world & kernel.
It is with the 4BSD scheduler (ULE is broken for me as ref'd in another msg to this list).
The trap seems to spring when the system gets busy; with me it pops sometime during a 'make'.
I am having to use a kernel I built last week until this is fixed (thankful for backups, and yes the older kernel is what I must use to finish making these newer things ;) .
At the point of the crash, I hand-copied the following:


kernel trap 9 with interrupts disabled


Fatal trap 9: general protection fault while in kernel mode
instruction pointer     = 0x8:0xc07a6c7d
stack pointer           = 0x10:0xd2797bce
frame pointer           = 0x10:0xd2797bea
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 0
current process         = 28 (swi8: tty:sio clock)
kernel: type 9 trap, code=0
Stopped at      atpic_handle_intr+0x4d: cmpl    $0,0x4(%edi)
db> trace
atpic_handle_intr(8) at Xatpic_intr8+0x27
--- interrupt, eip = 0x26c4, esp = 0xd2797c36, ebp = 0xc09c2626 ---
(null)(6b00646e,73637274,62690077,5f327363,70726770) at 0x26c4
db>


Again, if someone could help or give me a tip or two, I'd appreciate it.
I will need to continue this next Monday (I don't have any li'l-endians at home ;) .

Thank you,

  --  Paul Seniura
      System Specialist
      State of Okla. D.O.T.



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