From: Jeff Garzik <jeff@garzik.org>
To: Komuro <komurojun-mbn@nifty.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] PATA_PCMCIA does not work
Date: Sat, 24 Feb 2007 20:45:18 -0500 [thread overview]
Message-ID: <45E0EA2E.5050004@garzik.org> (raw)
In-Reply-To: <20070225081407.8ebce421.komurojun-mbn@nifty.com>
Komuro wrote:
> Hi,
>
> The pata_pcmcia problem is fixed. Thanks!
> (I tested it on kernel 2.6.20-git14)
>
> But kernel 2.6.20-mm2 introduced new oops
> when I insert the pata_pcmcia device.
>
>
> pcmcia: registering new device pcmcia1.0
> SCSI subsystem initialized
> libata version 2.10 loaded.
> ata1: PATA max PIO0 cmd 0x0001d100 ctl 0x0001d10e bmdma 0x00000000 irq 3
> scsi0 : pata_pcmcia
> BUG: unable to handle kernel NULL pointer dereference at virtual address 0000004d
> printing eip:
> d8a1b10e
> *pde = 00000000
> Oops: 0000 [#1]
> last sysfs file: /block/hda/size
> Modules linked in: pata_pcmcia libata scsi_mod dm_mirror dm_multipath dm_mod pcmcia yenta_socket rsrc_nonstatic pcmcia_core
> CPU: 0
> EIP: 0060:[<d8a1b10e>] Not tainted VLI
> EFLAGS: 00010296 (2.6.20-mm2 #1)
> EIP is at ata_acpi_exec_tfs+0x157/0x8ad [libata]
> eax: 00000001 ebx: 00000000 ecx: d6d43c84 edx: d6d43c84
> esi: d51f4514 edi: 00000000 ebp: d51f438c esp: d6f2bcdc
> ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
> Process scsi_eh_0 (pid: 1647, ti=d6f2a000 task=c13c9a70 task.ti=d6f2a000)
> Stack: d51f6190 00000246 00000246 00000000 d8a130b7 00000000 00000000 00000000
> 00000000 d6f2bd48 d6f2bdf0 d51f4514 ec000000 d51f6190 00000000 00000000
> 00000000 00000246 d6d43c84 00000000 00000000 00000000 00000000 ffffffff
> Call Trace:
> [<d8a130b7>] ata_exec_internal_sg+0x3ae/0x3b8 [libata]
> [<d8a125f8>] ata_dev_configure+0xc1/0x7d2 [libata]
> [<d8a10e87>] ata_dev_select+0xce/0x11a [libata]
Any chance you could insert some printk() calls into ata_apci_exec_tfs?
ata_exec_internal_sg() never calls that function, so I'm curious if
something corrupted memory a bit, or what happened.
In any case, I'm surprised that ACPI would be executing taskfiles on
PCMCIA anyway.
Jeff
next prev parent reply other threads:[~2007-02-25 1:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 12:27 [BUG KERNEL 2.6.20-rc1] ftp: get or put stops during file-transfer Komuro
2006-12-17 4:02 ` Al Viro
2006-12-17 14:23 ` Komuro
2006-12-18 3:01 ` Adrian Bunk
2006-12-18 20:55 ` Komuro
2006-12-23 11:17 ` Komuro
2006-12-30 9:50 ` Komuro
2006-12-30 1:23 ` YOSHIFUJI Hideaki / 吉藤英明
2006-12-30 11:59 ` Komuro
2006-12-30 14:19 ` YOSHIFUJI Hideaki / 吉藤英明
2006-12-31 9:42 ` Komuro
2007-01-01 17:18 ` Komuro
2007-01-04 20:45 ` Komuro
2007-01-04 12:23 ` Craig Schlenter
2007-01-09 1:24 ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09 5:11 ` [PATCH] " Craig Schlenter
2007-01-09 5:22 ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09 8:11 ` David Miller
2007-01-09 22:01 ` Komuro
[not found] ` <20070211101537.e40fa309.komurojun-mbn@nifty.com>
2007-02-11 1:56 ` [BUG] PATA_PCMCIA does not work Alan
2007-02-11 10:32 ` Haavard Skinnemoen
2007-02-11 2:40 ` Komuro
2007-02-18 2:09 ` Komuro
2007-02-21 15:37 ` Alan
2007-02-21 15:24 ` Manuel Lauss
2007-02-24 2:06 ` Komuro
2007-02-24 23:14 ` Komuro
2007-02-25 1:45 ` Jeff Garzik [this message]
2007-02-25 2:43 ` Komuro
2007-03-21 1:56 ` [PATCH]: pcmcia - spot slave decode flaws (for testing) Komuro
2007-03-17 13:00 ` [BUG] PATA_PCMCIA cmd port Komuro
2007-03-17 15:43 ` libata reports bogus addresses for everything (was PATA_PCMCIA cmd port) Alan Cox
2007-03-18 5:48 ` Tejun Heo
2007-03-17 16:10 ` [BUG] PATA_PCMCIA cmd port Jeff Garzik
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=45E0EA2E.5050004@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=komurojun-mbn@nifty.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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