[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: kernel-smp-2.6.9-34.0.2.EL



I agree you about number of issues on this kernel : too much 8-D

For mvfs and vnode, those are used by IBM - Rational Clearcase, I'll look 
by there if they have more info as we have support.

Thank you for your help!

________________________________
Pierre-Stéphane BATON
DI - OI/IT
Consultant Trasys-OSI
Support informatique Unix/Linux
E01-H14-L44 - Tel :+32 (0)71 442797

Alcatel Alenia Space ETCA (DI/SYS)
Rue Chapelle BEAUSSART, 101
B-6032  Mont-sur-Marchienne



Dag Wieers <dag wieers com> 
Envoyé par : redhat-list-bounces redhat com
04/08/2006 15:02
Veuillez répondre à
General Red Hat Linux discussion list <redhat-list redhat com>


A
General Red Hat Linux discussion list <redhat-list redhat com>
cc

Objet
Re: kernel-smp-2.6.9-34.0.2.EL






If people with other software have kernel panics there is no way of 
knowing if it is related to the same issue. Unless you are convinced 
2.6.9-34.0.2.EL only has 1 issue and that issue bit you ? :)

 
> Nothing in /var/log/message, I checked there 1st. I can't experiment it 
> again, those WS are in prod, and the soft has to ru for hours to produce 

> results, so I can't crash it..
> 
> HeY I just asked my colleague, as he has put a cosole server, this is 
the 
> output! :
> 
> ^M<3/8/2006 11:19:06 MEST>Kernel BUG at locks:1799
> ^M<3/8/2006 11:19:06 MEST>invalid operand: 0000 [1] SMP
> ^M<3/8/2006 11:19:06 MEST>CPU 0
> ^M<3/8/2006 11:19:06 MEST>Modules linked in: mvfs(U) vnode(U) nfsd 
> exportfs md5 ipv6 parport_pc lp parport autofs4 i2c_dev i2c_core nfs 
lockd 
> nfs_acl sunrpc ds yenta_socket pcmcia_core dm_mirror dm_mod uhci_hcd 
> ehci_hcd e1000 floppy ext3 jbd raid1 ata_piix libata sd_mod scsi_mod
> ^M<3/8/2006 11:19:07 MEST>Pid: 13436, comm: StartHostSoftFr Tainted: PF 
> 2.6.9-34.0.2.ELsmp

Ok, this kernel is tainted. It has a non GPL-licensed module loaded and 
one of the modules has been force-loaded (which is an indication it may 
not have been build for your kernel).

Both mvfs and vnode modules are not part of the kernel and the kernel 
panic is obviously related to mvfs. I hope you have a 3rd party vendor to 
complain to.

Loading kernel modules that are not build against the kernel you are 
running is a high risk of messing up your system. You may have been lucky 
that you did not loose any data.

Kind regards,
--   dag wieers,  dag wieers com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]