Bug 896441 - [abrt]: BUG: unable to handle kernel paging request at 000000008d5c60c9
Summary: [abrt]: BUG: unable to handle kernel paging request at 000000008d5c60c9
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1dca59c1e66e569101e15f5ab98...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 10:15 UTC by Alexey
Modified: 2013-04-16 14:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-16 14:18:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexey 2013-01-17 10:15:47 UTC
Additional info:
BUG: unable to handle kernel paging request at 000000008d5c60c9
IP: [<ffffffff8150ce3a>] sock_aio_read.part.9+0xca/0x170
PGD 0 
Oops: 0002 [#1] SMP 
Modules linked in: fuse ebtable_nat ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 bnep bluetooth iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_hda_codec_hdmi snd_hda_codec_idt arc4 snd_hda_intel snd_hda_codec ath9k_htc snd_hwdep ath9k_common ath9k_hw ath snd_seq mac80211 snd_seq_device snd_pcm snd_page_alloc snd_timer snd cfg80211 sp5100_tco soundcore atl1 edac_core i2c_piix4 edac_mce_amd ppdev rfkill joydev serio_raw k8temp mii parport_pc parport vhost_net tun macvtap macvlan kvm_amd kvm uinput dm_crypt ata_generic pata_acpi radeon pata_atiixp i2c_algo_bit drm_kms_helper ttm drm i2c_core
CPU 1 
Pid: 3061, comm: Chrome_ChildIOT Not tainted 3.7.2-201.fc18.x86_64 #1 ECS A740GM-M/A740GM-M
RIP: 0010:[<ffffffff8150ce3a>]  [<ffffffff8150ce3a>] sock_aio_read.part.9+0xca/0x170
RSP: 0018:ffff88004c74ddd0  EFLAGS: 00010a82
RAX: 000000008d5c6061 RBX: 0000000000001000 RCX: ffff88004c74ddf0
RDX: 0000000000001000 RSI: ffff88004c74dd58 RDI: ffff880032a50500
RBP: ffff88004c74ddd8 R08: 0000000000000001 R09: 0000000000000001
R10: 00000000ffffffff R11: 0000000000000000 R12: ffff88004c74de00
R13: ffff88004c74dd58 R14: ffff880032a50500 R15: 0000000000000802
FS:  00007fd9809cf700(0000) GS:ffff88007fc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000008d5c60c9 CR3: 0000000034db9000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process Chrome_ChildIOT (pid: 3061, threadinfo ffff88004c74c000, task ffff88003ad01720)
Stack:
 ffffffff8150cf09 ffff88004c74def8 ffffffff81194e37 0000000000000002
 00007fd99aa8c010 0000000000001000 0000000000000000 0000000000000000
 0000000000000000 ffffffff00000001 ffff88004377f900 0000000000000000
Call Trace:
 [<ffffffff8150cf09>] ? sock_aio_read+0x29/0x40
 [<ffffffff81194e37>] do_sync_read+0xa7/0xe0
 [<ffffffff8119563d>] vfs_read+0x15d/0x180
 [<ffffffff811956b2>] sys_read+0x52/0xa0
 [<ffffffff8163dad9>] system_call_fastpath+0x16/0x1b
Code: 00 00 48 c7 40 58 00 00 00 00 48 c7 40 60 00 00 00 00 4c 89 78 50 44 8b 7e 38 8b 95 4c ff ff ff 4c 89 ee 41 c1 ef 05 41 83 e7 40 <44> 89 78 68 44 89 f9 e8 fa c2 d7 ff 85 c0 74 16 48 98 48 81 c4 
RIP  [<ffffffff8150ce3a>] sock_aio_read.part.9+0xca/0x170
 RSP <ffff88004c74ddd0>
CR2: 000000008d5c60c9

Comment 1 Josh Boyer 2013-04-01 20:54:00 UTC
Is this still an issue with 3.8.x?

Comment 2 Josh Boyer 2013-04-16 14:18:33 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks.  If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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