John Baldwin [EMAIL PROTECTED] writes:
This is where it faulted for some reason or another. It was running
a registered interrupt handler. Do you have any kernel modules in this
system?
Not that were loaded at the time of the panic.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To
On 10-Dec-2002 Dag-Erling Smorgrav wrote:
John Baldwin [EMAIL PROTECTED] writes:
This is where it faulted for some reason or another. It was running
a registered interrupt handler. Do you have any kernel modules in this
system?
Not that were loaded at the time of the panic.
Had you
This is 100% reproducible with a top-of-tree kernel, but didn't happen
with Wednesday's sources:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc01e8d
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc045dc80
stack
On Wed, 11 Dec 2002, Mitsuru IWASAKI wrote:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc01e8d
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc045dc80
stack pointer = 0x10:0xd536dce4
frame pointer
John Baldwin [EMAIL PROTECTED] writes:
On 10-Dec-2002 Dag-Erling Smorgrav wrote:
John Baldwin [EMAIL PROTECTED] writes:
This is where it faulted for some reason or another. It was running
a registered interrupt handler. Do you have any kernel modules in this
system?
Not that were
On 10-Dec-2002 Dag-Erling Smorgrav wrote:
John Baldwin [EMAIL PROTECTED] writes:
On 10-Dec-2002 Dag-Erling Smorgrav wrote:
John Baldwin [EMAIL PROTECTED] writes:
This is where it faulted for some reason or another. It was running
a registered interrupt handler. Do you have any kernel
On 08-Dec-2002 Dag-Erling Smorgrav wrote:
This is 100% reproducible with a top-of-tree kernel, but didn't happen
with Wednesday's sources:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc01e8d
fault code = supervisor write, page not present
