From owner-freebsd-current Sun Aug 1 22:26: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles505.castles.com [208.214.165.69]) by hub.freebsd.org (Postfix) with ESMTP id B1F6714EFE; Sun, 1 Aug 1999 22:25:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01521; Sun, 1 Aug 1999 22:20:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908020520.WAA01521@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: current@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Sat, 31 Jul 1999 01:32:57 +0300." <37A22819.DD36695B@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 22:20:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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. Also after panic cu on notebook is hanging, so I have to kill it. > Following is the log, bit if you think that it is not sufficien and I could > do something more to shade light on this proble please do not hesitate to > contact me. > > -Maxim > > > Script started on Sat Jul 31 00:56:04 1999 > sh-2.03# cu -l '/dev/cuaa0' > Connected. > Console: serial port > BIOS drive A: is disk0 > BIOS drive C: is disk1 > > FreeBSD/i386 bootstrap loader, Revision 0.7 640/64448kB > (root@home, Sun Jul 25 04:04:09 EEST 1999) > Booting [kernel]... > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Sat Jul 31 00:29:40 EEST 1999 > root@home:/usr/src/sys/compile/MBSD > Timecounter "i8254" frequency 1193027 Hz > CPU: AMD-K6(tm) 3D processor (300.64-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 67043328 (65472K bytes) > avail memory = 62607360 (61140K bytes) > Preloaded elf kernel "kernel" at 0xc0265000. > Probing for PnP devices: > CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1013c276 Comp ID: PNP0600 > [0x0006d041] > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: APM BIOS version 0102 > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > apm: CS_limit=0x0, DS_limit=0x0 These limits look pretty suspect, although the code segment below looks OK. > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x48:0x8034 > stack pointer = 0x10:0xc0279e98 > frame pointer = 0x10:0x67890000 > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 0 > processor eflags = interrupt enabled, resume, IOPL = 0 Why is IOPL zero? I've also noted that making a bios16 call also results in IOPL being zero (I have more that I want to take up with you on that at some stage, since it's got me stumped, but one thing at a time). Do I need to tweak something in the segment descriptors to change IOPL? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message