From: Karol Kozimor <sziwan@hell.org.pl>
To: "Hanno Böck" <mail@hboeck.de>
Cc: randy_dunlap <rdunlap@xenotime.net>,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
julien.lerouge@free.fr
Subject: Re: [ACPI] Re: Kernel oops with asus_acpi module
Date: Sat, 11 Jun 2005 14:19:23 +0200 [thread overview]
Message-ID: <20050611121923.GB20873@hell.org.pl> (raw)
In-Reply-To: <200506071946.20843.mail@hboeck.de>
Thus wrote Hanno Böck:
> Am Dienstag, 7. Juni 2005 00:21 schrieb Karol Kozimor:
> > Thanks. This might also help:
> Doesn't help (randys fix also didn't).
>
> > But I'd like to get the full oops with the matching asus_acpi.o file also
> > (might be off the list).
>
> Can you tell me what a full oops is, how I generate it? Then I can do so (I'm
> not a kernel-dev).
What I meant was the full log output (which, AFAIK, you did supply) and the
asus_acpi.o file from the kernel build that the specific oops report was
for, which only Randy received, I guess.
Anyway, I'll do a debug patch shortly.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan@hell.org.pl
prev parent reply other threads:[~2005-06-11 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 21:40 Kernel oops with asus_acpi module Hanno Böck
2005-06-06 16:50 ` randy_dunlap
[not found] ` <200506061929.24663.mail@hboeck.de>
[not found] ` <20050606114531.763eec37.rdunlap@xenotime.net>
[not found] ` <200506062050.42632.mail@hboeck.de>
2005-06-06 20:54 ` randy_dunlap
2005-06-06 21:32 ` Karol Kozimor
2005-06-06 21:47 ` Hanno Böck
2005-06-06 22:21 ` [ACPI] " Karol Kozimor
2005-06-07 17:46 ` Hanno Böck
2005-06-07 22:16 ` randy_dunlap
2005-06-11 12:17 ` Karol Kozimor
2005-10-11 9:01 ` Hanno Böck
2005-06-11 12:19 ` Karol Kozimor [this message]
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=20050611121923.GB20873@hell.org.pl \
--to=sziwan@hell.org.pl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=julien.lerouge@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@hboeck.de \
--cc=rdunlap@xenotime.net \
/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