mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Komuro <komurojun-mbn@nifty.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-pcmcia <linux-pcmcia@lists.infradead.org>,
	linux-kernel@vger.kernel.org,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-ide@vger.kernel.org,
	Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	jgarzik@redhat.com, rjw@sisk.pl
Subject: Re: [KERNEL 2.6.26-rc4]  bugreport : pata_pcmcia with Sandisk Extreme III 8GB
Date: Mon, 7 Jul 2008 21:42:53 +0900	[thread overview]
Message-ID: <20080707214253.2406f81a.komurojun-mbn@nifty.com> (raw)
In-Reply-To: <4870D46C.7000604@gmail.com>


Hi,

> How come ap->lock can get set to bogus address?  Can you please printk
> &host->lock and ap->lock after ata_host_alloc() without the patch?

Here is the output of printk.
Strangely, without the patch, the pata_pcmcia problem happens again.


ata_piix 0000:00:1f.1: version 2.12
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
&host->lock = d6c288b4
ap->lock = d6c288b4
ap->lock = d6c288b4
PCI: Setting latency timer of device 0000:00:1f.1 to 64
scsi0 : ata_piix
scsi1 : ata_piix
....

pcmcia: registering new device pcmcia1.0
&host->lock = d70ee534
ap->lock = d70ee534
scsi2 : pata_pcmcia


	host = devres_alloc(ata_host_release, sz, GFP_KERNEL);
	if (!host)
		goto err_out;

	devres_add(dev, host);
	dev_set_drvdata(dev, host);

	spin_lock_init(&host->lock);
	printk("&host->lock = %x\n", &host->lock);
	host->dev = dev;
	host->n_ports = max_ports;

	/* allocate ports bound to this host */
	for (i = 0; i < max_ports; i++) {
		struct ata_port *ap;

		ap = ata_port_alloc(host);
		if (!ap)
			goto err_out;

		ap->port_no = i;
		/*
		ap->lock = &ap->__lock;
		spin_lock_init(ap->lock);
		*/
		printk("ap->lock = %x\n", ap->lock);
		host->ports[i] = ap;
	}

Best Regards
Komuro


  reply	other threads:[~2008-07-07 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080528225049.9a134e0d.Kristoffer.Ericson@Gmail.com>
     [not found] ` <20080528222740.GB20893@isilmar.linta.de>
     [not found]   ` <20080530135728.be02d3dc.Kristoffer.Ericson@Gmail.com>
2008-06-07 13:37     ` Komuro
2008-06-11  7:20       ` Dominik Brodowski
2008-06-14  3:00         ` Komuro
2008-06-14  7:20           ` Jeff Garzik
2008-06-14 12:36             ` Komuro
2008-06-16  3:07               ` Tejun Heo
2008-06-16 13:11                 ` Komuro
2008-06-16 13:24                   ` Tejun Heo
2008-06-17 12:23                     ` Komuro
2008-06-17 14:09                       ` Tejun Heo
2008-06-17 14:15                         ` Dominik Brodowski
2008-06-18 12:23                         ` Komuro
2008-07-06  1:37                       ` Komuro
2008-07-06 14:19                         ` Tejun Heo
2008-07-07 12:42                           ` Komuro [this message]
2008-07-09  4:10                             ` Tejun Heo
2008-07-12  2:39                               ` Komuro
2008-06-22  1:07                 ` Komuro

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=20080707214253.2406f81a.komurojun-mbn@nifty.com \
    --to=komurojun-mbn@nifty.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jgarzik@redhat.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@dominikbrodowski.net \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®