> > > Fatal trap 9: general protection fault while in kernel mode
> > > instruction pointer = 0x48:0x8034
> > > stack pointer = 0x10:0xc0279e98
> > > frame pointer = 0x10:0x6789
> > > code segment = base 0xc00f, limit 0x, type 0x1b
> > >= DPL 0, pres 1, def32 1, gr
On Aug 08, 1999 at 09:57:10AM -0700, Mike Smith wrote:
> > > > Fatal trap 9: general protection fault while in kernel mode
> > > > instruction pointer = 0x48:0x8034
> > > > stack pointer = 0x10:0xc0279e98
> > > > frame pointer = 0x10:0x6789
> > > > code segment = base 0xc00f00
On Aug 08, 1999 at 10:20:38PM -0700, Mike Smith wrote:
>
> Jonathan; just some context, this is with your old 16-bit-protmode
> patches, spiffed up for -current, which I committed late last week.
Heh. I had just about forgotten about this patchset. I was somwehat
under the impression it wasn'
> # sorry to break the thread, I'm a digest reader...
Not a problem at all.
> > > apm0: on motherboard
> > > apm: APM BIOS version 0102
> > > apm: Code16 0xc00f, Data 0xc00fdfa0
> > > apm: Code entry 0x8010, Idling CPU enabled, Management enabled
> > > apm: CS_limit=0x0, DS_limit=0x0
>
> Hi!
>
> Thanks, seems your patch did the trick (panic gone). Following is dmesd:
Thanks for the confirmation; I've made an even more pessimistic patch
that should cover your situation. Please let me know if your next CTM
works correctly.
Thanks for the quick bug report too!
> apm_probe: A
Hi!
Thanks, seems your patch did the trick (panic gone). Following is dmesd:
apm_probe: APM bios gave zero len code16, pegged to 64K
apm_probe: APM bios gave zero len data, tentative 64K
apm0: on motherboard
apm: APM BIOS version 0102
apm: Code16 0xc00f, Data 0xc00fdfa0
apm: Code entry 0x00
# sorry to break the thread, I'm a digest reader...
Hi,
> > apm0: on motherboard
> > apm: APM BIOS version 0102
> > apm: Code16 0xc00f, Data 0xc00fdfa0
> > apm: Code entry 0x8010, Idling CPU enabled, Management enabled
> > apm: CS_limit=0x0, DS_limit=0x0
>
> These limits look pretty su
Jonathan; just some context, this is with your old 16-bit-protmode
patches, spiffed up for -current, which I committed late last week.
> Finally I back from my work, suped, builded kernel with APM_DEBUG and
> managed to get my computer booted using serial console, however due to
> unknown for
Finally I back from my work, suped, builded kernel with APM_DEBUG and
managed to get my computer booted using serial console, however due to
unknown for me problem it works only in one direction, i.e. I see boot
messages on my notebook, but when I press any key on it it has absolutely no
effect.
> Just suped and builded new kernel and discovered that it paniced when
> trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard
> + k6-II/300 CPU). Any ideas or recommendations about what should I do to
> make a more informative report?
Just the usual ones; full text of the pani
On Thu, 29 Jul 1999, Maxim Sobolev wrote:
> + k6-II/300 CPU). Any ideas or recommendations about what should I do to
> make a more informative report?
Maybe dmesg would be a good start...
Later,
--mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the b
Just suped and builded new kernel and discovered that it paniced when
trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard
+ k6-II/300 CPU). Any ideas or recommendations about what should I do to
make a more informative report?
Sincerely,
Maxim
To Unsubscribe: send mail to
12 matches
Mail list logo
