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: 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: Wed, 4 Jan 2006 10:57:05 -0800	[thread overview]
Message-ID: <20060104105705.0afa3e0e.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <87ek3o22z8.fsf@marrow.phys.tohoku.ac.jp>

On 04 Jan 2006 10:31:23 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:

> Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> 
> > On 04 Jan 2006 07:40:00 +0900
> > Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:
> > > Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> > > > On Tue, 3 Jan 2006 20:03:47 +0100
> > > > Jens Axboe <axboe@suse.de> wrote:
> > > > > 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.
> > > 
> > > My laptop is ThinkPad X41 Tablet, which has the same SATA controller
> > > as 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.
> > 
> > This certainly isn't the same failure that Jens saw.
> > 
> > Could there be any informative & helpful messages missing
> > before these messages, e.g., an assert() failure?
> 
> Let me copy as far as I can setting the video mode to 80x60.
> Scrolling back does not work after kernel panic.
> 
> highmem bounce pool size: 64 pages
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> acpi_bus-0201 [27] bus_set_power         : Device is not power manageable
> ahci: probe of 0000:00:1f.2 failed with error -12
> 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
> do_drive_set_taskfiles: unexpected GTF length (-1040297340)
> scsi0: ata_piix
>   Vendor: ATA       Model: HTC426060G9AT00   Rev: 00P3
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15
> ata2: disabling port
> scsi1 : ata_piix
> SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
> SCSI device sda: drive cache: write back
> SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
> SCSI device sda: drive cache: write back
>  sda:<1>Unable to handle kernel NULL pointer dereference at virtual address 00000172
>  ...
> 
> > I don't quite understand what CONFIG_SCSI_SATA_AHCI has to do
> > with this.  I see ata_interrupt() [from libata-core.c],
> > but ahci.c contains ahci_interrupt(), which isn't in this
> > stack dump.  Nevertheless, it looks like complete() is
> > being passed a NULL struct completion...  Maybe I'm misusing
> > the completion API and don't know it (?).

Jae-hyeon,

Does your system work without using the AHCI driver?
or is it required?
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'.

Thanks,
---
~Randy

  parent reply	other threads:[~2006-01-04 18:56 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 [this message]
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=20060104105705.0afa3e0e.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).