From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Hanno Böck" <mail-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
Cc: randy_dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
julien.lerouge-GANU6spQydw@public.gmane.org
Subject: Re: 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-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
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-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
prev parent reply other threads:[~2005-06-11 12:19 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
[not found] ` <200506052340.41074.mail-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
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>
[not found] ` <200506062050.42632.mail-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
2005-06-06 20:54 ` randy_dunlap
[not found] ` <20050606135459.7ad699ae.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2005-06-06 21:32 ` Karol Kozimor
[not found] ` <20050606213248.GA22238-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-06-06 21:47 ` Hanno Böck
[not found] ` <200506062347.10582.mail-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
2005-06-06 22:21 ` Karol Kozimor
[not found] ` <20050606222151.GB65-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-06-07 17:46 ` Hanno Böck
[not found] ` <200506071946.20843.mail-60OJuG18Xr6zQB+pC5nmwQ@public.gmane.org>
2005-06-07 22:16 ` randy_dunlap
[not found] ` <20050607151649.4feaa50a.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2005-06-11 12:17 ` Karol Kozimor
[not found] ` <20050611121701.GA20873-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
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-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=julien.lerouge-GANU6spQydw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mail-60OJuG18Xr6zQB+pC5nmwQ@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