From: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>
To: Randy Dunlap <randy_d_dunlap@linux.intel.com>
Cc: axboe@suse.de, linux-ide@vger.kernel.org, jgarzik@pobox.com,
chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: 07 Jan 2006 22:11:00 +0900 [thread overview]
Message-ID: <87d5j418uz.fsf@marrow.phys.tohoku.ac.jp> (raw)
In-Reply-To: <20060106124310.10157732.randy_d_dunlap@linux.intel.com>
Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> To clarify more (for me):
> Without the libata verbose debugging patch, do you (still)
> have a problem with the AHCI driver causing an Oops?
I compiled six versions of kernels anew and tested again.
The results are as follows:
2.6.15-rc7 + libata-combine.patch AHCI=n
Kernel panics. Symbols in call trace are as in
http://marc.theaimsgroup.com/?l=linux-ide&m=113632815321896&w=2
2.6.15-rc7 + libata-combine.patch AHCI=y
Kernel panics. Symbols in call trace are as in
http://marc.theaimsgroup.com/?l=linux-ide&m=113632815321896&w=2
2.6.15-rc7 + libata-combine.patch + verbose patch AHCI=n
Kernel panics. Symbols in call trace are as in
http://marc.theaimsgroup.com/?l=linux-ide&m=113647020707839&w=2
2.6.15-rc7 + libata-combine.patch + verbose patch AHCI=y
Kernel panics. Symbols in call trace are as in
http://marc.theaimsgroup.com/?l=linux-ide&m=113647020707839&w=2
2.6.15 + libata-combine-2615.patch AHCI=n
Resume works if snd_intel8x0m has been loaded.
2.6.15 + libata-combine-2615.patch AHCI=y
Resume works if snd_intel8x0m has been loaded.
It turned out that kernel panic is independent of AHCI option. I made
a wrong statement in the bug report perhaps because I was compiling
too many kernels. I am sorry for the confusion.
Jae-hyeon
next prev parent reply other threads:[~2006-01-07 13:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 23:34 [PATCH 0/5] SATA/ACPI suspend/resume support Randy Dunlap
2005-12-30 8:36 ` Jae-hyeon Park
2006-01-03 17:08 ` Randy Dunlap
2006-01-03 17:26 ` Jens Axboe
2006-01-03 19:03 ` Jens Axboe
2006-01-03 19:06 ` Randy Dunlap
2006-01-03 19:57 ` Randy Dunlap
2006-01-03 20:06 ` Jens Axboe
2006-01-03 20:11 ` Randy Dunlap
2006-01-03 20:13 ` Jens Axboe
2006-01-03 21:00 ` Randy Dunlap
2006-01-03 21:16 ` Jens Axboe
2006-01-03 22:02 ` Randy Dunlap
2006-01-04 7:36 ` Jens Axboe
2006-01-03 22:40 ` Jae-hyeon Park
2006-01-04 0:40 ` Randy Dunlap
2006-01-04 1:31 ` Jae-hyeon Park
2006-01-04 18:13 ` Randy Dunlap
2006-01-04 18:57 ` Randy Dunlap
2006-01-04 19:42 ` Randy Dunlap
2006-01-05 14:08 ` Jae-hyeon Park
2006-01-05 18:36 ` Randy Dunlap
2006-01-06 1:02 ` Jae-hyeon Park
2006-01-06 1:10 ` Randy Dunlap
2006-01-06 20:43 ` Randy Dunlap
2006-01-07 13:11 ` Jae-hyeon Park [this message]
2006-01-07 16:55 ` Randy.Dunlap
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=87d5j418uz.fsf@marrow.phys.tohoku.ac.jp \
--to=jhpark@tuhep.phys.tohoku.ac.jp \
--cc=axboe@suse.de \
--cc=chris@powerblogs.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=randy_d_dunlap@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).