Re: [PATCH 0/5] SATA/ACPI suspend/resume support

[Randy Dunlap <randy_d_dunlap@linux.intel.com>]

On 05 Jan 2006 23:08:12 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:

> Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> >
> > Does your system work without using the AHCI driver?
> > or is it required?
> 
> I tested turning off AHCI with 2.6.15-rc7 + git-libata-all.patch +
> libata_resume_fix.patch + libata_suspend-fix.patch +
> libata_suspend.patch.  The system runs okay, and ACPI suspend/resume
> and suspend2 work, without AHCI.
> 
> > Of course, even if the AHCI driver is not needed,
> > it shouldn't be oopsing like this.
> > 
> > It looks like the ata_piix driver is the one that is
> > actually being used, from what I can see here.
> > 
> > Please send your /proc/interrupts, /proc/iomem, /proc/ioports,
> > and 'lspci -v'.
> 
> They are enclosed below.
> 
> > If you are up to it, please enable libata verbose debugging
> > and then boot & cause this bug again and send me as much
> > output as you can collect.
> > Patch is below.
> 
> Let me remind you that I used kernel 2.6.15-rc7 +
> http://www.xenotime.net/linux/SATA/2.6.15-rc7/libata-combine.patch +
> libata verbose debug patch.  libata-combine-2615.patch does not cause
> kernel panic.

Thanks for that clarification.
So enabling ATA debugging via:
-#undef ATA_VERBOSE_DEBUG	/* yet more debugging output */
+#define ATA_DEBUG		/* debugging output */
+#define ATA_VERBOSE_DEBUG	/* yet more debugging output */

is causing this particular Oops.  Hmph.


> I copied boot up messages below for cases with CONFIG_SCSI_SATA_AHCI
> turned off and on.  After turning on verbose debugging messages, the
> call trace has changed, and the kernel panics for
> CONFIG_SCSI_SATA_AHCI=n as well.

To clarify more (for me):
Without the libata verbose debugging patch, do you (still)
have a problem with the AHCI driver causing an Oops?

Thanks,
---
~Randy