From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: randy_dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.6.13-rc3 Kernel Panic...
Date: Fri, 22 Jul 2005 23:01:09 +0200 [thread overview]
Message-ID: <42E15E95.70904@tzi.de> (raw)
In-Reply-To: <20050722102446.05daf2ae.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
> The common ways are:
> - use a serial console
My laptop dosen'T have a serial port..., or is there a way to use USB
for that ?
> - use netconsole (kernel config option + netcat on another system)
it's an ACPI bug, it happens before the networkcard is even initalized
> - use a smaller console font
I hacked the Kernel oops mesage, so I could see what was the last
message before the oops:
Executing all Device _STA and _INI methodes
after this commes a big trace, here a few lines...
default_wake_function
acpi_ex_exit_interpreter
__down_failed
.text.lock.ec
acpi_ec_space_handler
acpi_ec_space_handler
acpi_ev_address_space_dispatch
If anybody is interested in the full stack trace, say it, then I will
type it all in by hand...
Janosch
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-22 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 21:50 2.6.13-rc3 Kernel Panic Janosch Machowinski
[not found] ` <42DEC727.6050108-cGBD8117FJM@public.gmane.org>
2005-07-22 17:24 ` randy_dunlap
[not found] ` <20050722102446.05daf2ae.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2005-07-22 21:01 ` Janosch Machowinski [this message]
[not found] ` <42E15E95.70904-cGBD8117FJM@public.gmane.org>
2005-07-23 4:29 ` Pavel Troller
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=42E15E95.70904@tzi.de \
--to=scotch-cgbd8117fjm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@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