For sure it'll be hard to find other platforms with same conditions. If
someone else has a kernel panic with another soft, it should help.
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
^M<3/8/2006 11:19:07 MEST>RIP: 0010:[<ffffffff8018cb4e>]
<ffffffff8018cb4e>{locks_remove_flock+201}
^M<3/8/2006 11:19:07 MEST>RSP: 0018:00000101abe2dcc8 EFLAGS: 00010246
^M<3/8/2006 11:19:07 MEST>RAX: 0000010227b8dce0 RBX: 00000101e9d7f2f8 RCX:
0000000000000000
^M<3/8/2006 11:19:07 MEST>RDX: 0000000000000000 RSI: 000000000000007c RDI:
ffffffff804d8880
^M<3/8/2006 11:19:07 MEST>RBP: 00000101e9d7f1e8 R08: 00000101e9d7f198 R09:
0000000300000000
^M<3/8/2006 11:19:07 MEST>R10: 0000000300000000 R11: ffffffff8015bc76 R12:
00000101f23807c0
^M<3/8/2006 11:19:07 MEST>R13: 00000101b3813e58 R14: 0000000000000000 R15:
0000000000000000
^M<3/8/2006 11:19:07 MEST>FS: 0000002a95584880(0000)
GS:ffffffff804d7c00(0000) knlGS:0000000000000000
^M<3/8/2006 11:19:07 MEST>CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
^M<3/8/2006 11:19:07 MEST>CR2: 000000375b72e728 CR3: 0000000000101000 CR4:
00000000000006e0
^M<3/8/2006 11:19:07 MEST>Process StartHostSoftFr (pid: 13436, threadinfo
00000101abe2c000, task 00000101b3414030)
^M<3/8/2006 11:19:07 MEST>Stack: 00000101e9d7f2f8 0000000000000000
0000000000000003 0000000000000000
^M<3/8/2006 11:19:07 MEST> 0000000000000000 ffffffff8018c9a1
0000000000071dc1 0000000044d1b3a7
^M<3/8/2006 11:19:07 MEST> 000000002b5ff548 0000000044d1bf8a
^M<3/8/2006 11:19:07 MEST>Call
Trace:<ffffffff8018c9a1>{locks_remove_posix+156}
<ffffffff80178835>{__fput+73}
^M<3/8/2006 11:19:07 MEST> <ffffffff80177460>{filp_close+103}
<ffffffffa024309c>{:vnode:mvop_linux_close_kernel+12}
^M<3/8/2006 11:19:08 MEST> <ffffffffa0243121>{:vnode:mvop_linux_close+122}
<ffffffffa02694fc>{:mvfs:mvfs_closev_ctx+409}
^M<3/8/2006 11:19:08 MEST>
<ffffffffa023fc5c>{:vnode:vnode_fop_release+124}
<ffffffff8017884f>{__fput+99}
^M<3/8/2006 11:19:08 MEST> <ffffffff80177460>{filp_close+103}
<ffffffff80138d7d>{put_files_struct+101}
^M<3/8/2006 11:19:08 MEST> <ffffffff801395a1>{do_exit+697}
<ffffffff80177afb>{vfs_read+207}
^M<3/8/2006 11:19:08 MEST> <ffffffff8013a03a>{sys_exit_group+0}
<ffffffff80110236>{system_call+126}
^M<3/8/2006 11:19:08 MEST>
^M<3/8/2006 11:19:08 MEST>
^M<3/8/2006 11:19:08 MEST>Code: 0f 0b 1e 38 32 80 ff ff ff ff 07 07 48 89
c3 48 8b 03 eb ba
^M<3/8/2006 11:19:08 MEST>RIP <ffffffff8018cb4e>{locks_remove_flock+201}
RSP <00000101abe2dcc8>
^M<3/8/2006 11:19:08 MEST> <0>Kernel panic - not syncing: Oops
^M<3/8/2006 11:19:08 MEST> ^@^@^[[H^[[J^MPress any key to enter the menu^M
TY
________________________________
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@xxxxxxxxxx>
Envoyé par : redhat-list-bounces@xxxxxxxxxx
04/08/2006 14:15
Veuillez répondre à
General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>
A
General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>
cc
Objet
Re: kernel-smp-2.6.9-34.0.2.EL
On Fri, 4 Aug 2006, pierre_stephane.baton@xxxxxxxxxxxxxxxxxxxxxx wrote:
> We have a big problem with 2 workstations here.
>
> Both are running kernel smp-2.6.9-22.0.2.EL with software Mentor
Graphics
> ModelSim SE. Yesterday we have updated to
> kernel-smp-2.6.9-34.0.2.EL.x86_64 with no problem until one of our
> engineer closed the simulation. At this point a kernel panic occured.
> Someone else had a similar problem?
Expecting to find any people that use the same software in the same
conditions resulting in the same (undefined) kernel panic is going to be
tremendously hard.
It would be really useful to send the information from the kernel panic.
Either from /var/log/messages (unlickely there's something useful in
there), by typing the stuff from screen (or the most relevant bits anyway)
or by installing something like crash to dump the kernel panic over the
network to another machine.
Kind regards,
-- dag wieers, dag@xxxxxxxxxx, 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@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
