From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Tejun Heo <htejun@gmail.com>
Cc: Komuro <komurojun-mbn@nifty.com>, Jeff Garzik <jeff@garzik.org>,
jgarzik@redhat.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-pcmcia <linux-pcmcia@lists.infradead.org>,
Kristoffer Ericson <kristoffer.ericson@gmail.com>
Subject: Re: [KERNEL 2.6.26-rc4] bugreport : pata_pcmcia with Sandisk Extreme III 8GB
Date: Tue, 17 Jun 2008 16:15:50 +0200 [thread overview]
Message-ID: <20080617141549.GA490@isilmar.linta.de> (raw)
In-Reply-To: <4857C590.6050002@gmail.com>
On Tue, Jun 17, 2008 at 11:09:20PM +0900, Tejun Heo wrote:
> Okay. The exit is from CS_CHECK macro on GetNextTuple, missed that
> macro. It means it failed to request IO resource somewhere. Can you
> please try the attached patch? It will show us where it failed.
>
> This part of code hasn't changed at all in pata_pcmcia && I don't really
> understand the tuple business. We need pcmcia people to pitch in.
The strange thing is that neither the PCMCIA side nor pata_pcmcia changed
between the working 2.6.26-rc4 and the non-working 2.6.26-rc3... that's why
I am at least as surprised as you are ;)
Thanks,
Dominik
next prev parent reply other threads:[~2008-06-17 14:16 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 [this message]
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
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=20080617141549.GA490@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jgarzik@redhat.com \
--cc=komurojun-mbn@nifty.com \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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
all inboxes | Powered by JetHome®