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. If
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 is not specific to PMP support. That makes more sense.
Does moving the controller to different slot
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 is
Thomas Evans wrote:
Tejun and all -
I have a new log - I got somewhat further by setting this bit when
init'd via HOST_CTRL:
Bit [28]: PERR Rpt Dsbl (R/W) – PERR Report Disable. This bit, when set
to one, disables reporting of PCI bus
parity errors to the Command Execution State Machine
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
Saw something that caught my attention might be nothing ...
When initialized, the port address is a 64 bit address:
sil24_init_one init_one: port:FD00:09AA
sil24_init_one init_one: port:FD00:09AA2000
sil24_init_one init_one: port:FD00:09AA4000
sil24_init_one init_one:
Thomas Evans wrote:
Saw something that caught my attention might be nothing ...
When initialized, the port address is a 64 bit address:
sil24_init_one init_one: port:FD00:09AA
sil24_init_one init_one: port:FD00:09AA2000
sil24_init_one init_one: port:FD00:09AA4000
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
Thomas Evans wrote:
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.
Nope, this is way before userland has any say in it. The
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
Thomas Evans wrote:
That's what I thought - is there another chip that support the 4726
PMP that you think I could try?
JMicron SATA controllers are ahci and support PMP.
--
tejun
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL
Thomas Evans wrote:
Hi All -
If I forget and get the Plug and Play error, disconnecting the
drives and resetting isn't enough, nor is power cycling *or*
unplugging the machine. I have to physically remove the card and
restart without it, power down and then re-insert it. I could only
plug
Thomas Evans wrote:
I hadn't tried that until just now - I have 2 3124 cards, 1 without
internal connections.
Just tried the 1 with internal sata ports - it fails in the same way on
a single drive.
There are cable which have SATA connector on one side and e-SATA on the
other. You can connect
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
Thomas Evans wrote:
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?
Well, at times, small differences can tell us more information. The
best we can do here is to gather as much information as possible. Even
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
Hello,
Thomas Evans wrote:
On 1/21/08, Tejun Heo [EMAIL PROTECTED] wrote:
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
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:
Hello, Thomas.
Thomas Evans wrote:
What do you mean by eSata PMP enclosure? Is it a different PMP device?
It is an external PMP box, 5 drive bays - it is the exact same
manufacturer and is based on the same PMP:
0x1095:0x4726 r31, 7 ports, feat 0x1/0x9
Okay.
I can hook the card and
20 matches
Mail list logo
