Bug 713732 - [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Summary: [abrt] kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d9a269026c379c8ee319106af77...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 12:20 UTC by Brian G. Anderson
Modified: 2011-10-12 12:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-11 22:18:12 UTC
Type: ---


Attachments (Terms of Use)

Description Brian G. Anderson 2011-06-16 12:20:21 UTC
abrt version: 2.0.1
architecture:   i686
cmdline:        ro root=/dev/mapper/vg_mimzy-lv_root rd_LVM_LV=vg_mimzy/lv_root rd_LVM_LV=vg_mimzy/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        I wasn't doing anything in particular when this crash poped up.  The only notable process running was VirtualBox emulating Windows 7.
component:      kernel
kernel:         2.6.38.8-32.fc15.i686.PAE
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: unable to handle kernel NULL pointer dereference at   (null)
time:           Thu Jun 16 05:17:08 2011

backtrace:
:BUG: unable to handle kernel NULL pointer dereference at   (null)
:IP: [<fac4ee13>] 0xfac4ee13
:*pdpt = 000000002b817001 *pde = 000000011b825067 
:Oops: 0000 [#1] SMP 
:last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0/voltage_now
:Modules linked in: vboxnetadp vboxnetflt vboxdrv fuse sunrpc cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm arc4 iwlagn iwlcore mac80211 snd_timer snd cfg80211 soundcore ppdev btusb e1000e i2c_i801 iTCO_wdt bluetooth snd_page_alloc iTCO_vendor_support intel_ips dell_wmi parport_pc sparse_keymap dell_laptop rfkill parport wmi dcdbas microcode ipv6 sdhci_pci sdhci firewire_ohci firewire_core mmc_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
:Pid: 5471, comm: VirtualBox Not tainted 2.6.38.8-32.fc15.i686.PAE #1 Dell Inc. Latitude E6410/0667CC
:EIP: 0060:[<fac4ee13>] EFLAGS: 00210246 CPU: 3
:EIP is at 0xfac4ee13
:EAX: 00000000 EBX: eca6dd98 ECX: fad6c000 EDX: 00000000
:ESI: 0000280a EDI: fad6c000 EBP: eca6dd78 ESP: eca6dd50
: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
:Process VirtualBox (pid: 5471, ti=eca6c000 task=edfbcb60 task.ti=eca6c000)
:Stack:
: fad6c000 eca6dd6c eb95d9d0 fad51000 fad6c000 fad51000 eca6ddb8 00000000
: fad51000 00000001 eca6ddb8 fac287d6 eca6dd98 fad6c000 00000000 00000000
: f6df2810 000a0000 00000000 00000000 00000000 fad51000 f21bd57c 00000000
:Call Trace:
: [<c059bbc6>] ? avc_has_perm_noaudit+0x8e/0x346
: [<c059cef5>] ? inode_has_perm+0x6e/0x87
: [<c0435b3a>] ? __might_sleep+0x29/0xe4
: [<c04e0fc2>] ? kfree+0xab/0xb3
: [<fa309cc4>] ? supdrvIOCtlFast+0x69/0x72 [vboxdrv]
: [<fa307230>] ? VBoxDrvLinuxIOCtl+0x0/0x1a4 [vboxdrv]
: [<fa30726f>] ? VBoxDrvLinuxIOCtl+0x3f/0x1a4 [vboxdrv]
: [<fa307230>] ? VBoxDrvLinuxIOCtl+0x0/0x1a4 [vboxdrv]
: [<c04f9f11>] ? do_vfs_ioctl+0x451/0x482
: [<c059d219>] ? selinux_file_ioctl+0x39/0x3c
: [<c04f9f8a>] ? sys_ioctl+0x48/0x6a
: [<c040969f>] ? sysenter_do_call+0x12/0x28
: [<c07e0000>] ? __cpuid+0x11/0x12
:Code: 00 8d bc 27 00 00 00 00 55 89 e5 53 83 ec 24 8b 55 0c 8b 5d 08 8b 82 dc 36 00 00 85 c0 89 45 f4 74 1d 8b 55 10 83 e2 03 8d 14 d0 <8b> 02 8b 52 04 89 03 89 d8 89 53 04 83 c4 24 5b 5d c2 04 00 8d

Comment 1 Dave Jones 2011-07-11 22:18:12 UTC
virtualbox bug.

Comment 2 Frank Mehnert 2011-10-12 09:52:46 UTC
Brian, which version of VirtualBox was installed?

Comment 3 Brian G. Anderson 2011-10-12 12:43:33 UTC
I was running 4.1.2, but the problem seems to have gone away with 4.1.4.


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