From: "Randy.Dunlap" <rddunlap-3NddpPZAyC0@public.gmane.org>
To: Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: bperkins-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Plea for help
Date: Fri, 19 Dec 2003 16:09:47 -0800 [thread overview]
Message-ID: <20031219160947.79c3fcdf.rddunlap@osdl.org> (raw)
In-Reply-To: <3FE39231.4040003-Wuw85uim5zDR7s880joybQ@public.gmane.org>
On Fri, 19 Dec 2003 18:05:05 -0600 Ian Pilcher <i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.org> wrote:
| Brian Perkins wrote:
| > First of all, what's the panic like?
| > Does it give a function?
| > You do have all of the kernel hacking options on, don't you?
| >
|
| You can see the panic at
|
| http://home.comcast.net/~i.pilcher/panics/1/panic.txt
|
| The config used to produce it is at
|
| http://home.comcast.net/~i.pilcher/panics/1/config
|
| Unfortunately, if I turn CONFIG_FRAME_POINTER on I don't get the panic,
| just the hang at
|
| http://home.comcast.net/~i.pilcher/panics/2/hang.txt
|
| Config at
|
| http://home.comcast.net/~i.pilcher/panics/2/config
|
| And as I previously mentioned, turning CONFIG_DEBUG_SLAB on prevents
| the panic entirely.
Can you also put the System.map file for that kernel on your website
so that we can correlate kernel memory addresses?
--
~Randy
MOTD: Always include version info.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-20 0:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 5:41 Plea for help Ian Pilcher
[not found] ` <3FE28F79.601-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-19 14:28 ` Micha Feigin
2003-12-21 1:45 ` Micha Feigin
[not found] ` <3FE33B69.1010606@netspace.org>
[not found] ` <3FE33B69.1010606-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org>
2003-12-20 0:05 ` Ian Pilcher
[not found] ` <3FE39231.4040003-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-20 0:09 ` Randy.Dunlap [this message]
[not found] ` <20031219160947.79c3fcdf.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-20 1:09 ` Ian Pilcher
[not found] ` <3FE3A142.90407-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-20 2:40 ` Randy.Dunlap
[not found] ` <20031219184043.3983572d.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-20 19:47 ` Ian Pilcher
[not found] ` <3FE4A740.4080701-Wuw85uim5zDR7s880joybQ@public.gmane.org>
2003-12-21 2:08 ` Randy.Dunlap
[not found] ` <20031220180854.32e2f56d.rddunlap-3NddpPZAyC0@public.gmane.org>
2003-12-22 1:19 ` Ian Pilcher
-- strict thread matches above, loose matches on Subject: below --
2003-12-24 6:04 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C53-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-29 23:17 ` Ian Pilcher
2003-12-31 9:58 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C66-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-01 16:54 ` Ian Pilcher
2004-01-02 7:34 Yu, Luming
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=20031219160947.79c3fcdf.rddunlap@osdl.org \
--to=rddunlap-3nddppzayc0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bperkins-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org \
--cc=i.pilcher-Wuw85uim5zDR7s880joybQ@public.gmane.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