Peter Wemm wrote:
> Terry Lambert wrote:
> > Compile "hints" into your kernel if you are going to be using an
> > abbreviated loader (e.g. to load into VMWare or via netboot).
>
> Uhh, Terry.. This has absolutely nothing to do with the problem.
Yes, this was already pointed out.
I've seen trap
Terry Lambert wrote:
> Julian Elischer wrote:
> >
> > Using $PIR table, 12 entries at 0xc00f2f70
> > npx0: on motherboard
> > npx0: INT 16 interface
> > acpi0: on motherboard
> >
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0x735f6e72
> > fault code
On 27-Jun-2002 Terry Lambert wrote:
> Julian Elischer wrote:
>>
>> Using $PIR table, 12 entries at 0xc00f2f70
>> npx0: on motherboard
>> npx0: INT 16 interface
>> acpi0: on motherboard
>>
>> Fatal trap 12: page fault while in kernel mode
>> fault virtual address = 0x735f6e72
>> fault code
Ignore this..
pilot error. mismatched acpi module.
On Thu, 27 Jun 2002, Julian Elischer wrote:
> Using $PIR table, 12 entries at 0xc00f2f70
> npx0: on motherboard
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 27-Jun-2002 Julian Elischer wrote:
> Using $PIR table, 12 entries at 0xc00f2f70
> npx0: on motherboard
> npx0: INT 16 interface
> acpi0: on motherboard
>
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x735f6e72
This is the string "rn_s".
> fault code
Julian Elischer wrote:
>
> Using $PIR table, 12 entries at 0xc00f2f70
> npx0: on motherboard
> npx0: INT 16 interface
> acpi0: on motherboard
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x735f6e72
> fault code = supervisor read, page not present
