> We have i2o on one of our testnodes: Adaptec Zero channel RAID 2010S
> integrated
> on MSI MS-9136 motherboard and I don't have access to another i2o hardware.
> Also I don't have any ideas how to detect buggy i2o node. As far as I
> understand
> Markus is right, and i2o hardware couldn't handl
On Tue, May 15, 2007 at 04:59:49PM +0400, Vasily Averin wrote:
> I would add:
> I've reported about this issue some time ago to [EMAIL PROTECTED]
> How this lockup can be reproduced:
> - boot the kernel,
> - load i2o_proc module
> - login as user and read all entries in /proc/i2o/ directory
>
> My
Alan Cox wrote:
> On Tue, 15 May 2007 16:47:05 +0400
> Vasily Averin <[EMAIL PROTECTED]> wrote:
>
>> Reading from some i2o related proc files can lead to the i2o controller hang
>> due
>> unknown reasons. As a workaround this patch changes the permission of these
>> files to root-only accessible.
On Tue, 15 May 2007 16:47:05 +0400
Vasily Averin <[EMAIL PROTECTED]> wrote:
> Reading from some i2o related proc files can lead to the i2o controller hang
> due
> unknown reasons. As a workaround this patch changes the permission of these
> files to root-only accessible.
I guess you have a crap
I would add:
I've reported about this issue some time ago to [EMAIL PROTECTED]
How this lockup can be reproduced:
- boot the kernel,
- load i2o_proc module
- login as user and read all entries in /proc/i2o/ directory
My testnode hangs when I try to read any file from /proc/i2o/iop0/030/
directory:
Reading from some i2o related proc files can lead to the i2o controller hang due
unknown reasons. As a workaround this patch changes the permission of these
files to root-only accessible.
Signed-off-by: Vasily Averin <[EMAIL PROTECTED]>
--- lk2.6/drivers/message/i2o/i2o_proc.c
+++ lk2.6/drivers/m
6 matches
Mail list logo
