-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, well, I have googled for this and it seems to be a problem with many kernels, but mostly the really old ones (One report is even about 1.something!?). Can´t find something helpful (for me) on the kernel-mailinglist, but this one here seems to run in a VMWare and I´ve found a possible fix in a Fedora-forum, where a user had exactly the same dmesg-errors.
On Fedora 2.6.22.9-91.fc7 it helped to change |scsi0.v||irtualDev |to| "lsilogic" |(so that there is |scsi0.virtualDev = "lsilogic|")| |in a *.vmx-file (I can´t say in which one because I never worked with VMWare and in this thread it´s not specialized, so I guess there is only one). Should I leave a comment at it and asking for "results" of this? The thread (see below) is in german, so if I should leave one, should I add the link at all? Sorry for asking so much, I will search the web for further information tomorrow because its really late here and I am kind of tired. Thanks, Sebastian Threadlink: http://www.fedoraforum.de/viewtopic.php?f=18&t=12936&p=71868&hilit=vmware+gel%C3%B6st#p71868 || -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBR7N3GrsPWF8MEmaqAQIe8xAA9rKGVEpdM+V5IIBY9K8plFDgozPq3i9t +HdYZrsvb4A9XY/IAqF0CeRKHVTMsgMSvGmIn/F34BJRjEEMwV3R7zi2f4wut9TM /SxnpwDqm7hDU7YXWGfqjbb2mldEU3wURRTcYUrgSE5NULAc39RmRJyUVH/VdMMF s+HCsg3GqrG5oSR3jNG0fPeMoAOPrilJkVbFxWlGruxspQi+Z7qYAQXzpBZQjIYv CegwZFn+RJBn6NMosBaSUGvEQIh5N60z6CdvB2yXhWyjzJPcuEVoRixWX184lDuh HTBjyNyHDt/x2xJDosjpfxk1JwckJb3XW43s5O1O4Tt/gIoamS9ddrb8hBfhOdKp ImZsjfYrgDWUPzyeMPXNyqeD5QIf+KwjTM1UFxVkzZzGKQBkmWD7WYU0B5FKg6V/ 5HP5ooWOuswCX0NqTu7DPMqCD/ch2UsgjCBppE6h7huk3tsb5848sBWxBiMvtZsE v5qHp1LXUZU2WxrVMUQYxy7EP9pmyms8u8Mw+ReiUzbygIWCPJA/AEoZ4p5AOuue O84jgqfMWOOGfystoitwI9XTba/5PXFR0VGHJ58+UB4HjaR4CneK5IYsy2p6gBy0 nPKu1oX4cKtsLQEX4RJIHS9YPMPDXAZoUEZhEDiDZkAklG7iSg/N5X558ff90iBJ TA0VTM33EnU= =Afxb -----END PGP SIGNATURE----- -- [email protected] mailing list
