Hello all:
I was getting a reproducible crash during an update of a xen system.
The problem went away after I set SELinux to permissive, but the fact
that it crashed was alarming (first one on a non-dev system that I've
had in over a year). I attempted the update earlier but it crashed at
the same point after attempting to update selinux. After verifying
hardware (all clean) I ran it again and crashed in the same location.
Third time failed again in same location. I rebooted, changed selinux,
then it completed after that. Unfortunately there are no dumps and I
had to put the system back into operation. Didn't see anything in
bugzilla either. Anyone else seen this?
Here's the console output:
Transaction Summary
===============================================================================Install
2 Package(s)
Update 17 Package(s)
Remove 2 Package(s)
Total size: 56 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : selinux-policy-targeted 1/38
general protection fault: 0000 [1] SMP
last sysfs file: /hypervisor/uuid
CPU 0
Modules linked in: autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth lockd sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state
ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp
ip6table_filter ip6_tables x_tables ipv6 xfrm_nalgo crypto_api
dm_multipath scsi_dh scsi_mod parport_pc lp parport xennet pcspkr
dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero
dm_mirror dm_log dm_mod xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 4269, comm: semodule Not tainted 2.6.18-164.10.1.el5xen #1
RIP: e030:[<ffffffff88037cb0>] [<ffffffff88037cb0>]
:jbd:journal_grab_journal_head+0x25/0x44
RSP: e02b:ffff88001ee5fb50 EFLAGS: 00010202
RAX: 0000000000304027 RBX: ffff88001d78e370 RCX: 0000000000000035
RDX: fffd88001d7939d0 RSI: ffff88001d78e310 RDI: ffff88001d78e370
RBP: 0000000000000001 R08: ffffffff804f8e00 R09: ffff88003e513600
R10: ffff88001d793a30 R11: ffffffff8804fc33 R12: ffff88001d793a30
R13: ffff88003e513600 R14: ffff88000194d908 R15: 0000000000000001
FS: 00002b85be90abc0(0000) GS:ffffffff805ca000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process semodule (pid: 4269, threadinfo ffff88001ee5e000, task ffff880032883820)
Stack: ffffffff88032257 0000000000000000 0000000000000000 ffff88001d78e3d0
00000c000194d8d0 ffff88001d78e2b0 ffff88000194d908 000000000000056e
0000000000000004 000000000000056e
Call Trace:
[<ffffffff88032257>] :jbd:journal_invalidatepage+0xdc/0x358
[<ffffffff8021d3dd>] truncate_complete_page+0x1b/0x5c
[<ffffffff8022b98f>] truncate_inode_pages_range+0x9b/0x290
[<ffffffff802c555b>] vmtruncate+0x4e/0xc9
[<ffffffff8024335e>] inode_setattr+0x22/0x104
[<ffffffff88050b2f>] :ext3:ext3_setattr+0x1bd/0x228
[<ffffffff8022ceab>] notify_change+0x145/0x2f3
[<ffffffff802d17af>] do_truncate+0x5e/0x79
[<ffffffff80212f1a>] may_open+0x1d3/0x22f
[<ffffffff8021b4ce>] open_namei+0x2c8/0x6ed
[<ffffffff80227a14>] do_filp_open+0x1c/0x38
[<ffffffff8021a1b8>] do_sys_open+0x44/0xbe
[<ffffffff802602f9>] tracesys+0xab/0xb6
Code: ff 42 08 8b 07 a9 00 00 20 00 75 0a 0f 0b 68 f5 97 03 88 c2
RIP [<ffffffff88037cb0>] :jbd:journal_grab_journal_head+0x25/0x44
RSP <ffff88001ee5fb50>
<0>Kernel panic - not syncing: Fatal exception
