Unless it stamps on things or overflows its stack or..
Memory corruption is probably the most probable one although nothing
suprises me as a driver bug any more.
> All tests has no error shown on analyzer.
Ok so your fibrechannel side is apparently behaving right.
> Could anyone help to:
> 1, provide some clue what could be wrong?
Check all the memory allocations you do. Also check you catch any NULL
returns. Also check use of the io_request lock - although I'd expect you
to find 'request list destroyed' messages if that was wrong.
It could be sd.c not doing checks so look at that too.
Another one to check is that your scatter gather limits are right. Does
the card blow up doing pure writes ?
> 2, If I use System2 as monitor to track system1 during the test so in case a
> lot of message shows up, I will be able to see the beginning of it with
> system2 X window. How do I set up these two system to do so?
Connect a serial port of system 1 to system 2, and boot system 1 with
the serial console options. All system messages then go down the serial
port
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/