yenta_socket and Machine check in kernel mode

[DaNiMoTh]

Hi,

The error message "Caused by (from SRR1=214b030): Transfer error ack signal"
is everywhere in my (PowerBook G4) messages.log. I checked, and the module 
that cause it is yenta_socket.

That's the messages.log after a rmmod && modprobe (the [...] as for hundred 
and hundred line of the same messages:

Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: CardBus bridge found [0000:0000]
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: Using CSCINT to route CSC interrupts to PCI
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: Routing CardBus interrupts to PCI
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: TI: mfunc 0x00001002, devctl 0x60
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: ISA IRQ mask 0x0000, PCI irq 53
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: Socket status: 30000007
Nov 12 21:41:09 localhost kernel: yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge window: [io  0x0000-0x7fffff]
Nov 12 21:41:09 localhost kernel: pcmcia_socket pcmcia_socket0: cs: IO port probe 0x0-0x7fffff:Machine check in kernel mode.
Nov 12 21:41:09 localhost kernel: Caused by (from SRR1=214b030): Transfer error ack signal
Nov 12 21:41:09 localhost kernel: Machine check in kernel mode.
[...]
Nov 12 21:43:47 localhost kernel: Machine check in kernel mode.
Nov 12 21:43:47 localhost kernel: Caused by (from SRR1=214b030): Transfer error ack signal
Nov 12 21:43:47 localhost kernel: Machine check in kernel mode.
Nov 12 21:43:47 localhost kernel: Caused by (from SRR1=214b030): Transfer error ack signal
Nov 12 21:43:47 localhost kernel:
Nov 12 21:43:47 localhost kernel: yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge window: [mem 0xf3000000-0xf3ffffff]
Nov 12 21:43:47 localhost kernel: pcmcia_socket pcmcia_socket0: cs: memory probe 0xf3000000-0xf3ffffff: clean.
Nov 12 21:43:47 localhost kernel: yenta_cardbus 0001:10:13.0: pcmcia: parent PCI bridge window: [mem 0x80000000-0xafffffff]
Nov 12 21:43:47 localhost kernel: pcmcia_socket pcmcia_socket0: cs: memory probe 0x80000000-0xafffffff: excluding 0x80000000-0x807fffff 0x84000000-0x8bffffff 0xa0000000-0xa07fffff


I'm using the git 3.2.0-rc1 kernel, but I have the same problem with the 2.6.38.
There's something I can do (apart from blacklisting it, and don't use PCMCIA)?

Thanks

PS: Maybe related:

[1] http://lkml.indiana.edu/hypermail/linux/kernel/1104.3/01793.html
(Using pci=cbmemsize=8M doesn't help.. messages are still here)
[2] https://lists.linux-foundation.org/pipermail/bugme-new/2011-January/026377.html
(No hint if that is fixed or not)


-- 
Stay open, be free.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20111113/e3c8c05a/attachment.pgp>