linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Randy Dunlap <randy_d_dunlap@linux.intel.com>
Cc: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>,
	linux-ide@vger.kernel.org, jgarzik@pobox.com,
	chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: Tue, 3 Jan 2006 20:03:47 +0100	[thread overview]
Message-ID: <20060103190346.GY2772@suse.de> (raw)
In-Reply-To: <20060103172649.GV2772@suse.de>

On Tue, Jan 03 2006, Jens Axboe wrote:
> On Tue, Jan 03 2006, Randy Dunlap wrote:
> > 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?
> 
> I think I triggered the same oops on my T43, I'll try applying your sata
> acpi patches and see if it reproduces.

It's crashing here:

                acpi_os_free((void *)gtf_address);

in ata_acpi_exec_tfs(), looks like it's trying to free an uninitialized
gtf_address. Setting to 0 and doing:

        if (gtf_address)
                acpi_os_free((void *)gtf_address);

fixes it. Probably due to a nasty warning that it spews on boot:

ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x18C0 irq 14
ata1: dev 0 cfg 49:2f00 82:346b 83:7d09 84:6003 85:3469 86:3c09 87:6003
88:203f
ata1: dev 0 ATA-7, max UDMA/100, 156301488 sectors: LBA48
ata1(0): applying bridge limits
ata1: dev 0 configured for UDMA/100
ata_acpi_exec_tfs: call get_GTF, ix=0
ata_acpi_exec_tfs: call set_taskfiles, ix=0
do_drive_set_taskfiles: unexpected GTF length (-271707516)
scsi0 : ata_piix
  Vendor: ATA       Model: ST980825A         Rev: 3.04
  Type:   Direct-Access                      ANSI SCSI revision: 05

note the 'unexpected GTF length' message. Doing a suspend/resume cycle
doesn't trigger that error:

[...]
eth1: Coming out of suspend...
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 21 (level, low) -> IRQ 23
ata1: dev 0 configured for UDMA/100
ata_acpi_exec_tfs: call get_GTF, ix=0
ata_acpi_exec_tfs: call set_taskfiles, ix=0
Restarting tasks... done
[...]

-- 
Jens Axboe


  reply	other threads:[~2006-01-03 19:02 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 [this message]
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=20060103190346.GY2772@suse.de \
    --to=axboe@suse.de \
    --cc=chris@powerblogs.com \
    --cc=jgarzik@pobox.com \
    --cc=jhpark@tuhep.phys.tohoku.ac.jp \
    --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).