Bug 871571 - [abrt]: BUG: unable to handle kernel paging request at ffffeb88000359c0
[abrt]: BUG: unable to handle kernel paging request at ffffeb88000359c0
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
abrt_hash:b2be3af87be106ef47debbb0005...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-30 14:20 EDT by nplamondon
Modified: 2012-10-30 17:45 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-30 16:05:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description nplamondon 2012-10-30 14:20:44 EDT
Description of problem:
Installed USB bluetooth dongle. It worked for a few minutes before the system became unresponsive.

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
cmdline:        BOOT_IMAGE=/vmlinuz-3.3.4-5.fc17.x86_64 root=/dev/mapper/vg_nabu-lv_root ro KEYTABLE=dvorak rd.lvm.lv=vg_nabu/lv_swap rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_nabu/lv_root rd.luks.uuid=luks-30cbe6ac-5508-4edd-b43c-5518f04909af LANG=en_US.UTF-8 rhgb quiet
kernel:         3.3.4-5.fc17.x86_64

backtrace:
:BUG: unable to handle kernel paging request at ffffeb88000359c0
:IP: [<ffffffff81167843>] ksize+0x33/0xd0
:PGD 0 
:Oops: 0000 [#1] SMP 
:CPU 0 
:Modules linked in: rfcomm btusb lockd sunrpc bnep bluetooth ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ip6_tables snd_hda_codec_analog arc4 sierra microcode iTCO_wdt iTCO_vendor_support i2c_i801 iwl4965 iwlegacy mac80211 cfg80211 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer e1000e thinkpad_acpi snd soundcore rfkill uinput xts gf128mul dm_crypt firewire_ohci sdhci_pci sdhci mmc_core firewire_core crc_itu_t yenta_socket i915 video i2c_algo_bit drm_kms_helper drm i2c_core [last unloaded: scsi_wait_scan]
:Pid: 820, comm: X Not tainted 3.3.4-5.fc17.x86_64 #1 LENOVO 7764CTO/7764CTO
:RIP: 0010:[<ffffffff81167843>]  [<ffffffff81167843>] ksize+0x33/0xd0
:RSP: 0018:ffff880062e25a88  EFLAGS: 00010216
:RAX: 00000188000359c0 RBX: ffffeb88000359c0 RCX: 0000000000000800
:RDX: ffffea0000000000 RSI: 0000000000000000 RDI: ffffea0000d67cc0
:RBP: ffff880062e25a98 R08: ffff88007d416480 R09: 0000000000016480
:R10: 0000000000000000 R11: ffff88007a802c00 R12: ffffea0000d67cc0
:R13: 0000000000000000 R14: ffff88007a802900 R15: 00000000ffffffff
:FS:  00007fbd5fc628c0(0000) GS:ffff88007d400000(0000) knlGS:0000000000000000
:CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
:CR2: ffffeb88000359c0 CR3: 0000000063b09000 CR4: 00000000000006f0
:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
:Process X (pid: 820, threadinfo ffff880062e24000, task ffff880063aa5c80)
:Stack:
: ffff88007a802900 ffff88005492d100 ffff880062e25ae8 ffffffff814d302d
: ffff88007a802700 0000052000000000 ffff880060fb4560 ffff880063aa5c80
: ffff880063aa5c80 ffff880062e25b38 ffff88003e402700 0000000000000000
:Call Trace:
: [<ffffffff814d302d>] __alloc_skb+0x8d/0x230
: [<ffffffff814cc8c1>] sock_alloc_send_pskb+0x1a1/0x300
: [<ffffffff814cca35>] sock_alloc_send_skb+0x15/0x20
: [<ffffffff8157a3ef>] unix_stream_sendmsg+0x27f/0x440
: [<ffffffff814c82e7>] sock_aio_write+0x147/0x170
:[  73Oct 30 10:11:10 nabu kernel: imklog 5.8.10, log source = /proc/kmsg started.
Comment 1 Josh Boyer 2012-10-30 16:05:06 EDT
Please let us know if you can recreate with 3.6.x
Comment 2 nplamondon 2012-10-30 17:45:18 EDT
(In reply to comment #1)
> Please let us know if you can recreate with 3.6.x

Recreated with 3.6.3-1.fc17.x86_64. I'm not seeing crash notices, but the system freezes. I'm not sure where to get a trace like in the first post; Point me toward it, and I'll gladly share.

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