Bug 772738 - system crash
Summary: system crash
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-09 20:28 UTC by Randy
Modified: 2012-03-01 17:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 17:35:53 UTC
Type: ---


Attachments (Terms of Use)

Description Randy 2012-01-09 20:28:18 UTC
Description of problem:

system crashes

Version-Release number of selected component (if applicable):

All kernel versions for Fedora 16

VMware Player 4.0.1-528992


How reproducible:

Easy

Steps to Reproduce:

Only happens when running a guest VM and the system accesses an encrypted volume added to the system after install, /media/backup. 

Start a guest VM

Do any file operation on /media/backup 

Usually needs to be big like copy or delete allot of data


Actual results:

System crashes


Expected results:

Data copied or deleted


Additional info:


[root@ajax ~]# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Wed Nov 30 13:18:53 2011
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/luks-0d9a1667-5987-4228-8a53-aff0b243e3bb /                       ext4    defaults        1 1
UUID=5f2a00ed-2354-4997-af11-aec0b279c274 /boot                   ext4    defaults        1 2
UUID=671c8c82-d8ce-4ce3-9511-bf5abf1630a4 swap                    swap    defaults        0 0
/dev/mapper/backup /media/backup           ext4    defaults        1 1

[root@ajax etc]# cat crypttab
luks-0d9a1667-5987-4228-8a53-aff0b243e3bb UUID=0d9a1667-5987-4228-8a53-aff0b243e3bb none 
backup UUID=1df44b3a-1d80-4ae8-82b2-ac3b4b1f7b3c none 
[root@ajax etc]#

Comment 1 Josh Boyer 2012-01-09 20:38:41 UTC
We'll need to see the backtrace before anything can really be done.

It might be a problem in VMWare itself (plausible even).

Comment 2 Randy 2012-02-12 01:38:55 UTC

How should I generate the backtrace?

The system is crashing regularly now


Feb 11 19:20:48 ajax kernel: [   60.592800] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Feb 11 19:21:28 ajax kernel: [   97.629409] /dev/vmmon[2469]: PTSC: initialized at 3701000000 Hz using TSC, TSCs are synchronized.
Feb 11 19:21:28 ajax kernel: [   97.821767] /dev/vmmon[2469]: Monitor IPI vector: 0
Feb 11 19:21:29 ajax kernel: [   98.626227] /dev/vmnet: open called by PID 2542 (vmx-vcpu-0)
Feb 11 19:21:29 ajax kernel: [   98.626244] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:21:29 ajax kernel: [   98.626255] /dev/vmnet: open called by PID 2542 (vmx-vcpu-0)
Feb 11 19:21:29 ajax kernel: [   98.626262] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:22:12 ajax kernel: [  138.285599] NET: Registered protocol family 39
Feb 11 19:22:12 ajax kernel: [  138.285881] [2542]: VMCI: IOCTL_VMCI_QUEUEPAIR_ALLOC (cid=4141045350,result=4).
Feb 11 19:22:54 ajax kernel: [  178.457157] /dev/vmnet: open called by PID 3478 (vmx-vcpu-0)
Feb 11 19:22:54 ajax kernel: [  178.457167] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:22:54 ajax kernel: [  178.457173] /dev/vmnet: open called by PID 3478 (vmx-vcpu-0)
Feb 11 19:22:54 ajax kernel: [  178.457176] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:23:27 ajax kernel: [  210.929376] /dev/vmnet: open called by PID 3825 (vmx-vcpu-0)
Feb 11 19:23:27 ajax kernel: [  210.929386] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:23:27 ajax kernel: [  210.929392] /dev/vmnet: open called by PID 3825 (vmx-vcpu-0)
Feb 11 19:23:27 ajax kernel: [  210.929395] /dev/vmnet: port on hub 8 successfully opened
Feb 11 19:24:36 ajax kernel: [  280.041312] [3825]: VMCI: IOCTL_VMCI_QUEUEPAIR_ALLOC (cid=4141045349,result=4).
Feb 11 19:25:49 ajax kernel: [  352.992660] TCP lp registered
Feb 11 19:31:23 ajax kernel: [  686.123836] BUG: unable to handle kernel paging request at ffff8803fd8cd000
Feb 11 19:31:23 ajax kernel: [  686.123841] IP: [<ffffffff81499e1a>] implement+0x6a/0x110
Feb 11 19:31:23 ajax kernel: [  686.123846] PGD 1a06063 PUD df7a9067 PMD 3fc7a9063 PTE 80000003fd8cd161
Feb 11 19:31:23 ajax kernel: [  686.123850] Oops: 0003 [#1] SMP 
Feb 11 19:31:23 ajax kernel: [  686.123853] CPU 0 
Feb 11 19:31:23 ajax kernel: [  686.123854] Modules linked in: tcp_lp hidp lockd vmnet(O) ppdev parport_pc parport rfcomm fuse vsock(O) vmci(O) vmmon(O) bnep nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables sha256_generic nvidia(P) snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_seq btusb bluetooth snd_seq_device iTCO_wdt i2c_i801 r8169 snd_hwdep snd_pcm mii snd_timer snd hid_logitech_dj soundcore joydev i2c_core snd_page_alloc iTCO_vendor_support rfkill serio_raw microcode uinput sunrpc xts gf128mul dm_crypt raid0 mxm_wmi usb_storage firewire_ohci firewire_core crc_itu_t wmi [last unloaded: scsi_wait_scan]
Feb 11 19:31:23 ajax kernel: [  686.123885] 
Feb 11 19:31:23 ajax kernel: [  686.123888] Pid: 1526, comm: Xorg Tainted: P           O 3.2.5-3.fc16.x86_64 #1 Gigabyte Technology Co., Ltd. Z68X-UD7-B3/Z68X-UD7-B3
Feb 11 19:31:23 ajax kernel: [  686.123891] RIP: 0010:[<ffffffff81499e1a>]  [<ffffffff81499e1a>] implement+0x6a/0x110
Feb 11 19:31:23 ajax kernel: [  686.123894] RSP: 0018:ffff8803e54d5c58  EFLAGS: 00010006
Feb 11 19:31:23 ajax kernel: [  686.123896] RAX: 5500000000000000 RBX: 5500000000000000 RCX: 0000000000000000
Feb 11 19:31:23 ajax kernel: [  686.123897] RDX: 0000000000000040 RSI: ffff8803fd8ccff1 RDI: ffff8803ffce4000
Feb 11 19:31:23 ajax kernel: [  686.123899] RBP: ffff8803e54d5c88 R08: 0000000000000000 R09: ffff8803fd8ccff1
Feb 11 19:31:23 ajax kernel: [  686.123900] R10: 000000000000000a R11: 0000000000000004 R12: 0000000000000000
Feb 11 19:31:23 ajax kernel: [  686.123902] R13: 0000000000000040 R14: ffff8803fd8ccff9 R15: ffff8803ffce4000
Feb 11 19:31:23 ajax kernel: [  686.123904] FS:  00007f366f708880(0000) GS:ffff88041f400000(0000) knlGS:0000000000000000
Feb 11 19:31:23 ajax kernel: [  686.123906] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 11 19:31:23 ajax kernel: [  686.123907] CR2: ffff8803fd8cd000 CR3: 00000003e38ce000 CR4: 00000000000406f0
Feb 11 19:31:23 ajax kernel: [  686.123909] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 11 19:31:23 ajax kernel: [  686.123910] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 11 19:31:23 ajax kernel: [  686.123912] Process Xorg (pid: 1526, threadinfo ffff8803e54d4000, task ffff8803fd9d1720)
Feb 11 19:31:23 ajax kernel: [  686.123913] Stack:
Feb 11 19:31:23 ajax kernel: [  686.123915]  0000000000000001 0000000000000024 0000000000000048 ffff880403f26200
Feb 11 19:31:23 ajax kernel: [  686.123918]  0000000000000008 ffff8803ffce4000 ffff8803e54d5d08 ffffffff8149a33d
Feb 11 19:31:23 ajax kernel: [  686.123921]  0000000000000082 ffff880401a49800 ffff880401a49818 00000000811646f3
Feb 11 19:31:23 ajax kernel: [  686.123924] Call Trace:
Feb 11 19:31:23 ajax kernel: [  686.123927]  [<ffffffff8149a33d>] hid_output_report+0xed/0x160
Feb 11 19:31:23 ajax kernel: [  686.123931]  [<ffffffff814a76b8>] usbhid_submit_report+0xe8/0x340
Feb 11 19:31:23 ajax kernel: [  686.123936]  [<ffffffffa00de8bb>] logi_dj_ll_input_event+0x10b/0x180Feb 11 19:34:58 ajax kernel: imklog 5.8.7, log source = /proc/kmsg started.

Comment 3 Josh Boyer 2012-03-01 17:35:53 UTC
If you can recreate this without the vmware and nvidia modules loaded, please let us know.


Note You need to log in before you can comment on or make changes to this bug.