I wonder if this may be what I am seeing with the Si3124 on my Alpha
based setup.
I'm not sure if Alpha meets all the criteria, but the thing refuses to
recognize any drivers when they are connected and I see what are
supposed pci parity failures.
maybe not ...
...tom
Mark Mason wrote:
No like with only a drive attached and no PMP. The driver is still
unable to IDENTIFY the connected disk:
failed to IDENTIFY (I/O error, err_mask=0x20)
On Jan 28, 2008 1:51 AM, Thomas Evans [EMAIL PROTECTED] wrote:
On 1/27/08, Tejun Heo [EMAIL PROTECTED] wrote:
Hmmm... That's strange
I've tried it in various slots on both PCI hoses - no difference.
...tom
Tejun Heo wrote:
Thomas Evans wrote:
No like with only a drive attached and no PMP. The driver is still
unable to IDENTIFY the connected disk:
failed to IDENTIFY (I/O error, err_mask=0x20)
So, the problem
I hate blasting the the list with every minute detail.
On 1/27/08, Tejun Heo [EMAIL PROTECTED] wrote:
Hmmm... That's strange. If PERR makes a difference, it means PCI bus
side is contributing to the problem but only when PMP is attached while
directly attached drive works just fine?
I need
added some more printk's based on what I saw -
maybe some issue with the dma port?
...tom
Thomas Evans wrote:
Tejun (and all) -
I've attached a log from my machine marked up with a few extra printk's.
I did add the ssleep() you suggested off line - made no difference.
I'll be happy to add
max UDMA/100 host [EMAIL PROTECTED] port 0x9aa6000 irq 31
I don't think the output is being truncated?
Is there some issue with the address?
...tom
Thomas Evans wrote:
added some more printk's based on what I saw -
maybe some issue with the dma port?
...tom
-
To unsubscribe from this list
I will work on getting that log - is there anything non-kernel that
may have changed that could cause this? udev changes or something
like that? Just so odd for it to start failing after having worked
for so long.
...tom
On Jan 23, 2008 10:52 PM, Tejun Heo [EMAIL PROTECTED] wrote:
Thomas
That's what I thought - is there another chip that support the 4726
PMP that you think I could try?
...tom
On Jan 24, 2008 10:11 AM, Tejun Heo [EMAIL PROTECTED] wrote:
Thomas Evans wrote:
I will work on getting that log - is there anything non-kernel that
may have changed that could cause
Um, I can, but it's not all that different than the others - is there
something I am missing that would collect more info in the logs?
Thanks,
...tom
On Jan 23, 2008 9:32 PM, Tejun Heo [EMAIL PROTECTED] wrote:
Thomas Evans wrote:
I hadn't tried that until just now - I have 2 3124 cards, 1
On 1/21/08, Tejun Heo [EMAIL PROTECTED] wrote:
Hello, Thomas.
Hi -
Can you install linux on a x86 machine and see whether anything is
different?
Did that today - it mostly works. There is some sort of conflict with
the card on the PC I am using. During POST I sometimes get a Plug
and Play
I should have mentioned that in 1 of the failing logs, it finds the PMP
device, that is rare, it usually doesn't even see it.
That happened this morning and I was hopeful that somehow it was more
meaningful than the usual case where it doesn't even notice the PMP.
...tom
Thomas Evans wrote
I stopped seeing this message when I started using rc4.
I upgraded to rc7 with your patch - the dmesg is attached.
The link speed seems limited to 1.5Gbps now though, which hasn't been
the case in rc3-rc6.
...tom
-Original Message-
From: Tejun Heo [mailto:[EMAIL PROTECTED]
Sent:
Applied this patch to my 2.22.1 installation (alpha w/pcix 3124 card. The patch
made a huge difference whenprobing devices at start. No 10 second retries
followed by resets.
...tom
-Original Message-
From: Tejun Heo [EMAIL PROTECTED]
Sent: Friday, September 21, 2007 6:55 AM
To: Jon
13 matches
Mail list logo