linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com, axboe@suse.de,
	chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: Tue, 3 Jan 2006 09:08:47 -0800	[thread overview]
Message-ID: <20060103090847.43c2a00d.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <87vex7rnfn.fsf@marrow.phys.tohoku.ac.jp>

On 30 Dec 2005 17:36:44 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:

> I tested kernel 2.6.15-rc7 with your patch applied on my ThinkPad X41.
> While booting, it locks up after printing
> 
>     ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1810 irq 14
>     ata1: dev 0 ATA-6, max UDMA/100, 117210240 sectors: LBA
>     ata1(0): applying bridge limits
>     ata1: dev 0 configured for UDMA/100
> 
> If I select CONFIG_SCSI_SATA_AHCI, then the kernel emits an oops and
> panics during boot.

Hi,

Can you capture the kernel oops & panic messages?

Please send me your .config also.

Is this on your Fujitsu notebook with some kind of hybrid
PATA/SATA?

> By the way, I found that kernel 2.6.15-rc7 with the following patches
> work with or without the snd_intel8x0m module.

I don't understand this part.  What does the intel sound
driver have to do with this?

>     git-libata-all.patch
>     libata_resume_fix.patch
>     libata_suspend-fix.patch
>     libata_suspend.patch
>     from http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm3/broken-out/

Thanks,
---
~Randy

  reply	other threads:[~2006-01-03 17:08 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 [this message]
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
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=20060103090847.43c2a00d.randy_d_dunlap@linux.intel.com \
    --to=randy_d_dunlap@linux.intel.com \
    --cc=axboe@suse.de \
    --cc=chris@powerblogs.com \
    --cc=jgarzik@pobox.com \
    --cc=jhpark@tuhep.phys.tohoku.ac.jp \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).