Hello:

I am working on a Fedora Core 6 box, and have the same issue.
Currently running 2.6.18-1.2849. When I try to compile the patch, of course, it breaks horribly:

make -C /lib/modules/2.6.18-1.2849.fc6/build SUBDIRS=/usr/src/fusion clean
make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
make -C /lib/modules/2.6.18-1.2849.fc6/build SUBDIRS=/usr/src/fusion modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
CC [M] /usr/src/fusion/mptbase.o
/usr/src/fusion/mptbase.c:50:26: error: linux/config.h: No such file or directory
In file included from /usr/src/fusion/mptbase.c:71:
/usr/src/fusion/mptbase.h:1088:28: error: linux/diskdump.h: No such file or directory
/usr/src/fusion/mptbase.c: In function âmpt_suspendâ:
/usr/src/fusion/mptbase.c:1646: error: switch quantity not an integer
/usr/src/fusion/mptbase.c: In function âMakeIocReadyâ:
/usr/src/fusion/mptbase.c:2510: error: implicit declaration of function âcrashdump_modeâ
/usr/src/fusion/mptbase.c:2510: error: implicit declaration of function âdiskdump_mdelayâ
make[2]: *** [/usr/src/fusion/mptbase.o] Error 1
make[1]: *** [_module_/usr/src/fusion] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2849.fc6-i686'
make: *** [default] Error 2

Any patches for this kernel?

Thanks,

-- Juan

You should be able to look at the source and make the appropriate change as the code in FC6 is not significantly different in this particular area but I think the file is called mptscsih.c in the newer kernels.

I don't have the FC6 source handy, but basically, if you simply simply take the FC6 source and look in drivers/message/fusion there should be a file called mptscsih.c Open this file and do a search for DID_BUS_BUSY. Approximately the third hit from the top of the file should be a line that looks like this:

sc->result = (DID_BUS_BUSY << 16) | scsi_status;

Simply change the DID_BUS_BUSY to DID_OK so that the line looks like this:

sc->result = (DID_OK << 16) | scsi_status;

And then remcompile and you should be good. If you can't get this to work I can try to put some more specific instructions together in another day or so, perhaps even a download, I just don't have time at the moment.

Later,
Tom

Hello, have the same problem. Thanks to your comments, we found a solution.

Many thanks to all of you who got involved in this thread, this has been really really helpful.
You rule!

is this solution useful for my problem???
http://www.vmware.com/community/thread.jspa?threadID=67781&tstart=0

thanks, I really need your help 'cause it's a critical machine and I have just one more day to find a solution...

I'm seeing this behavior (Linux guest goes read-only suddenly) on a guest OS that is running on _local_ storage. (I.e., not on a SAN, and not on iSCSI.) Has anyone seen this?

-Rick