On Sat, 24 Feb 2007 20:45:18 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> 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.
I insert some
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
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
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
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
On Sat, 24 Feb 2007 20:45:18 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
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.
I insert some printk().
I
Alan <[EMAIL PROTECTED]> wrote:
The oops is fixed. Thanks!
But when I repeat insertion/rejection of the device,
ataX.00 is incremented.
Is this correct?
>pccard: PCMCIA card inserted into slot 1
>pccard: card ejected from slot 1
>ata1.00: disabled
>
>pccard: PCMCIA card inserted into slot 1
Alan [EMAIL PROTECTED] wrote:
The oops is fixed. Thanks!
But when I repeat insertion/rejection of the device,
ataX.00 is incremented.
Is this correct?
pccard: PCMCIA card inserted into slot 1
pccard: card ejected from slot 1
ata1.00: disabled
pccard: PCMCIA card inserted into slot 1
pccard:
On Wed, Feb 21, 2007 at 03:37:29PM +, Alan wrote:
> Does this fix the oops ?
>
> Alan
>
>
> diff -u --new-file --recursive --exclude-from /usr/src/exclude
> linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
> linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
> ---
Does this fix the oops ?
Alan
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
--- linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c 2007-02-20
13:37:58.0 +
+++
Does this fix the oops ?
Alan
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
--- linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c 2007-02-20
13:37:58.0 +
+++
On Wed, Feb 21, 2007 at 03:37:29PM +, Alan wrote:
Does this fix the oops ?
Alan
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
---
Hi,
I tried the kernel 2.6.20-git14,
the pata_pcmcia drive works properly.Thanks!
But I do the "pccardctl eject"
NULL-pointer-dereference error happens.
[dmesg]
pcmcia: registering new device pcmcia1.0
SCSI subsystem initialized
libata version 2.10 loaded.
ata1: PATA max PIO0 cmd 0x0001d100
Hi,
I tried the kernel 2.6.20-git14,
the pata_pcmcia drive works properly.Thanks!
But I do the pccardctl eject
NULL-pointer-dereference error happens.
[dmesg]
pcmcia: registering new device pcmcia1.0
SCSI subsystem initialized
libata version 2.10 loaded.
ata1: PATA max PIO0 cmd 0x0001d100 ctl
On 2/11/07, Alan <[EMAIL PROTECTED]> wrote:
> [pata_pcmcia dmesg]
> ata1.00: CFA, max PIO0, 20480 sectors: LBA
> ata1.00: ata1: dev 0 multi count 0
> ata1.01: CFA, max PIO0, 20480 sectors: LBA
> ata1.01: ata1: dev 1 multi count 0
Do you have two cards here ?
I've seen this as well, on an
On 2/11/07, Alan [EMAIL PROTECTED] wrote:
[pata_pcmcia dmesg]
ata1.00: CFA, max PIO0, 20480 sectors: LBA
ata1.00: ata1: dev 0 multi count 0
ata1.01: CFA, max PIO0, 20480 sectors: LBA
ata1.01: ata1: dev 1 multi count 0
Do you have two cards here ?
I've seen this as well, on an ancient 4MB
>> [pata_pcmcia dmesg]
>> ata1.00: CFA, max PIO0, 20480 sectors: LBA
>> ata1.00: ata1: dev 0 multi count 0
>> ata1.01: CFA, max PIO0, 20480 sectors: LBA
>> ata1.01: ata1: dev 1 multi count 0
>Do you have two cards here ?
No. one card.
I am not sure why two devices are detected.
Actually,
> The PATA_PCMCIA driver does not work.
> The kernel version is 2.6.20.
> Does anyone test this driver?
Yes it gets regularly tested and works reliably on my test harware. I am
however using standards compliant hardware.
> [pata_pcmcia dmesg]
> ata1.00: CFA, max PIO0, 20480 sectors: LBA
>
The PATA_PCMCIA driver does not work.
The kernel version is 2.6.20.
Does anyone test this driver?
Yes it gets regularly tested and works reliably on my test harware. I am
however using standards compliant hardware.
[pata_pcmcia dmesg]
ata1.00: CFA, max PIO0, 20480 sectors: LBA
ata1.00:
[pata_pcmcia dmesg]
ata1.00: CFA, max PIO0, 20480 sectors: LBA
ata1.00: ata1: dev 0 multi count 0
ata1.01: CFA, max PIO0, 20480 sectors: LBA
ata1.01: ata1: dev 1 multi count 0
Do you have two cards here ?
No. one card.
I am not sure why two devices are detected.
Actually, this card
20 matches
Mail list logo
