From: Elyse Grasso <emgrasso@data-raptors.com>
To: linux-kernel@vger.kernel.org
Subject: apm gpf on Inspiron2500 with 2.4.9
Date: Wed, 19 Dec 2001 17:02:00 -0700 [thread overview]
Message-ID: <20011220000357Z285654-18284+4575@vger.kernel.org> (raw)
Please copy me on any comments, I am not subscribed to the list.
Attempts to interract with apm on Inspiron 2500 laptops produce results like
the following (KRUD/RedHat 7.2, but also occurs with 7.1).
kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
general protection fault: e998
CPU: 0
EIP: 0050:[<00002ffb>] Not tainted
EFLAGS: 00010046
eax: 00000292 ebx: 00000001 ecx: 00000000 edx: 00000000
esi: c023149a edi: 00000014 ebp: c9f6de80 esp: c9f6de78
ds: 0058 es: 0000 ss: 0018
Process apmd (pid 781, stackpage c9f6d000)
Stack: 5319519e 0000de80 00000058 149a0292 de940050 00000001 530a0000
00000016
00485369 00000000 c9f6def8 c01109b3 00000010 c9f6def8 00000292 ffff0018
00000018 cbe50000 c0120000 c9f6df32 c023149a ffffffff c9f5c000 c0110bbf
Call Trace: [<c01109b3>] apm_bios_call [kernel] 0x43
[<c0120000>] force_sig [kernel] 0x0
[<c023149a>] .rodaata.str1.1 [kernel] 0x5c35
[<c0110bbf>] apm_get_power_status [kernel] 0x3f
[<c0126c24>] do_munmap [kernel] 0x64
[<c0111886>] apm_get_info [kernel] 0x46
[<c0153704>] proc_file_read [kernel] 0x94
[<c0106f3b>] sys_read [kernel] 0x96
[<c0106f3b>] system_call [kernel] 0x33
Please let me know if there is other information that would be helpful...
it's been about 15 years since I did device driver work on 8086 based
machines, but I can probably figure out how to get you the information you
ask for.
Thanks
Elyse Grasso
next reply other threads:[~2001-12-20 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 0:02 Elyse Grasso [this message]
2001-12-20 0:19 ` Dave Jones
2001-12-20 22:13 ` Elyse Grasso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011220000357Z285654-18284+4575@vger.kernel.org \
--to=emgrasso@data-raptors.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®