Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, Yes I have seen and I know that the module that don't loads correctly it's from vmware. The problem with the module it's that it complains about it's license. Vmware configure script try to load the module when configuring it and and it says it loads OK, but kernel complains about license. I'm just remembering now, that centos crew they recently change kmod-drbd package politics, before they had one rpm for each kernel they sent out. Now the same rpm it's for all the kernels. Can that be the problem? About modules i think it's all, everything else it's normal and it's distributed with the kernel itself. Thanks, Lars Marowsky-Bree wrote: > On 2009-01-28T10:49:25, Igor Neves <igor at 3gnt.net> wrote: > > >> Pid: 8329, comm: drbd0_receiver >> EIP: 0060:[<c0608e1b>] CPU: 3 >> EIP is at _spin_lock_irqsave+0x13/0x27 >> EFLAGS: 00000282 Tainted: GF (2.6.18-92.1.22.el5PAE #1) >> > > The tainted F flag means that a module was forced into the kernel, > despite its symbol type checksums indicating that they do not match the > running kernel. > > Basically, when that happens, all bets are completely off. That can and > will cause data corruption, which can manifest itself in random ways, > and in places seemingly unrelated to the module loaded. > > Any reputable Linux vendor in the world will throw up their hands and > say "No way", or increase your bill tenfold ;-) > > Can you retest this with a clean system? > > > Regards, > Lars > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090129/294c7847/attachment.htm>