FC12: Null pointer dereference

james.primrose · #1 3rd December 2009, 04:01 PM

2.6.31.6-145.fc12.x86_64

Sometimes I can get logged in, other times it hangs.

Ideas?

Quote:

Dec 3 09:35:47 variable kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Dec 3 09:35:47 variable kernel: IP: [<ffffffffa00756c1>] intel_tv_mode_set+0x231/0x7c4 [i915]
Dec 3 09:35:47 variable kernel: PGD 119417067 PUD 1185e0067 PMD 0
Dec 3 09:35:47 variable kernel: Oops: 0000 [#1] SMP
Dec 3 09:35:47 variable kernel: last sysfs file: /sys/devices/virtual/sound/timer/uevent
Dec 3 09:35:47 variable kernel: CPU 1
Dec 3 09:35:47 variable kernel: Modules linked in: sunrpc ipv6 cpufreq_ondemand acpi_cpufreq freq_table dm_multipath uinput arc4 ecb snd_hda_codec_intelhdmi iwlagn snd_hda_codec_idt iwlcore snd_hda_intel mmc_block snd_hda_codec snd_hwdep snd_seq snd_seq_device sdhci_pci mac80211 firewire_ohci sdhci snd_pcm tg3 firewire_core snd_timer mmc_core dell_laptop ricoh_mmc i2c_i801 snd cfg80211 iTCO_wdt soundcore joydev snd_page_alloc dcdbas iTCO_vendor_support crc_itu_t wmi rfkill yenta_socket rsrc_nonstatic i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: microcode]
Dec 3 09:35:47 variable kernel: Pid: 1416, comm: Xorg Not tainted 2.6.31.6-145.fc12.x86_64 #1 Latitude E5500
Dec 3 09:35:47 variable kernel: RIP: 0010:[<ffffffffa00756c1>] [<ffffffffa00756c1>] intel_tv_mode_set+0x231/0x7c4 [i915]
Dec 3 09:35:47 variable kernel: RSP: 0018:ffff8801169778a8 EFLAGS: 00010246
Dec 3 09:35:47 variable kernel: RAX: 0000000000000000 RBX: ffff880117837000 RCX: 0000000000000000
Dec 3 09:35:47 variable kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000000c
Dec 3 09:35:47 variable kernel: RBP: ffff880116977948 R08: 00000000000001df R09: 0000000000000000
Dec 3 09:35:47 variable kernel: R10: 0000000000000040 R11: 0000000000000000 R12: ffff88011798b800
Dec 3 09:35:47 variable kernel: R13: ffff88011798fbd8 R14: ffffffffa007c630 R15: 00000000000200c0
Dec 3 09:35:47 variable kernel: FS: 00007fa1a34fa7e0(0000) GS:ffff88002803c000(0000) knlGS:0000000000000000
Dec 3 09:35:47 variable kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Dec 3 09:35:47 variable kernel: CR2: 0000000000000008 CR3: 000000011854e000 CR4: 00000000000406e0
Dec 3 09:35:47 variable kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 3 09:35:47 variable kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 3 09:35:47 variable kernel: Process Xorg (pid: 1416, threadinfo ffff880116976000, task ffff880119594680)
Dec 3 09:35:47 variable kernel: Stack:
Dec 3 09:35:47 variable kernel: 0000034a1798c000 0000000c0000002c 0000000000000000 0000000000000000
Dec 3 09:35:47 variable kernel: <0> 0000000000000000 ffff880100000000 0000002c0000000c ffff88011798c000
Dec 3 09:35:47 variable kernel: <0> 0000007a16977948 0000000000000000 ffff880100000000 ffff880100000000
Dec 3 09:35:47 variable kernel: Call Trace:
Dec 3 09:35:47 variable kernel: [<ffffffffa00521f4>] drm_crtc_helper_set_mode+0x287/0x34e [drm_kms_helper]
Dec 3 09:35:47 variable kernel: [<ffffffffa006ceda>] intel_get_load_detect_pipe+0x101/0x14a [i915]
Dec 3 09:35:47 variable kernel: [<ffffffffa00764a6>] intel_tv_detect+0x8d/0x14d [i915]
Dec 3 09:35:47 variable kernel: [<ffffffffa0052b8b>] drm_helper_probe_single_connector_modes+0xba/0x282 [drm_kms_helper]
Dec 3 09:35:47 variable kernel: [<ffffffffa002fac8>] drm_mode_getconnector+0xf5/0x39a [drm]
Dec 3 09:35:47 variable kernel: [<ffffffffa00691ee>] ? intel_mark_busy+0xa9/0xca [i915]
Dec 3 09:35:47 variable kernel: [<ffffffffa002f9d3>] ? drm_mode_getconnector+0x0/0x39a [drm]
Dec 3 09:35:47 variable kernel: [<ffffffffa002521f>] drm_ioctl+0x237/0x2f4 [drm]
Dec 3 09:35:47 variable kernel: [<ffffffff81108b29>] vfs_ioctl+0x6f/0x87
Dec 3 09:35:47 variable kernel: [<ffffffff81109038>] do_vfs_ioctl+0x47b/0x4c1
Dec 3 09:35:47 variable kernel: [<ffffffff811090d4>] sys_ioctl+0x56/0x79
Dec 3 09:35:47 variable kernel: [<ffffffff81011cf2>] system_call_fastpath+0x16/0x1b
Dec 3 09:35:47 variable kernel: Code: 0f 45 d3 45 8b 9e 8c 00 00 00 44 89 5d 88 41 89 d3 41 81 cb 00 00 00 20 83 7d 88 00 41 0f 45 d3 45 8b 9e 90 00 00 00 44 89 5d c8 <45> 8b 59 08 44 89 5d 8c 45 8b 5e 7c 44 89 5d bc 45 8b 9e 80 00
Dec 3 09:35:47 variable kernel: RIP [<ffffffffa00756c1>] intel_tv_mode_set+0x231/0x7c4 [i915]
Dec 3 09:35:47 variable kernel: RSP <ffff8801169778a8>
Dec 3 09:35:47 variable kernel: CR2: 0000000000000008
Dec 3 09:35:47 variable kernel: ---[ end trace f039f0dacbfa2091 ]---
Dec 3 09:35:58 variable gnome-session[1510]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
Dec 3 09:36:02 variable init: tty4 main process (1381) killed by TERM signal
Dec 3 09:36:02 variable init: tty5 main process (1382) killed by TERM signal
Dec 3 09:36:02 variable init: tty2 main process (1383) killed by TERM signal
Dec 3 09:36:02 variable init: tty3 main process (1384) killed by TERM signal
Dec 3 09:36:02 variable init: tty6 main process (1385) killed by TERM signal
Dec 3 09:36:02 variable avahi-daemon[1029]: Got SIGTERM, quitting.
Dec 3 09:36:03 variable gnome-keyring-daemon[1503]: dbus failure unregistering from session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 3 09:36:03 variable acpid: exiting
Dec 3 09:36:03 variable pcscd: pcscdaemon.c:581:signal_trap() Preparing for suicide
Dec 3 09:36:04 variable pcscd: readerfactory.c:1242:RFCleanupReaders() entering cleaning function
Dec 3 09:36:04 variable pcscd: pcscdaemon.c:531:at_exit() cleaning /var/run
Dec 3 09:36:04 variable rpc.statd[1238]: Caught signal 15, un-registering and exiting.
Dec 3 09:36:05 variable NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Dec 3 09:36:05 variable NetworkManager: <info> (wlan0): taking down device.
Dec 3 09:36:05 variable NetworkManager: <info> (eth0): cleaning up...
Dec 3 09:36:05 variable NetworkManager: <info> (eth0): taking down device.
Dec 3 09:36:06 variable kernel: tg3 0000:09:00.0: PME# enabled
Dec 3 09:36:06 variable NetworkManager: <info> exiting (success)
Dec 3 09:36:06 variable rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Dec 3 09:36:06 variable cpuspeed: Disabling ondemand cpu frequency scaling governor
Dec 3 09:36:07 variable init: prefdm main process (1380) killed by KILL signal
Dec 3 09:36:07 variable kernel: Kernel logging (proc) stopped.

Replicant10000 · #2 3rd December 2009, 07:31 PM

Um.

I may just be firing out of my ass here, but don't you think you should report that to RedHat Bugzilla as a security issue in Fedora?

http://bugzilla.redhat.com

james.primrose · #3 3rd December 2009, 11:03 PM

Quote:

you should report that to RedHat Bugzilla as a security issue in Fedora

It's a security issue?

Is my data safe?

Can they hack into my hard data across the intranet????

regulatre · #4 4th December 2009, 01:26 AM

Looked to me like xorg crapped the bed in the above crahsdump. I'm guessing your GUI failed to load? Does it always crapp-out at the same point? Does it ever crapp-out while you're in the GUI? This doesn't look like a kernel problem to me.

What changes have you made from default, in regard to your video/display setup? Consider backing out those changes. Also consider running #yum update to get all your packages up to date, including xorg.