[Intel-gfx] Memory corruption on hibernate/thaw with KMS

Bojan Smojver bojan at rexursive.com
Mon Oct 10 12:05:18 CEST 2011


On Mon, 2011-10-10 at 19:18 +1100, Bojan Smojver wrote:
> I will try and let you know. From what I've seen at some other bugs,
> it helped some people, but not others. 

After about 20 cycles, got:
-----------------------------------------------
[  173.834896] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  173.837583] IP: [<ffffffff810f0c73>] shmem_evict_inode+0x8b/0xd5
[  173.840247] PGD 225d9f067 PUD 22c3ca067 PMD 0 
[  173.842880] Oops: 0000 [#1] SMP 
[  173.845474] CPU 1 
[  173.845491] Modules linked in: fuse ppdev parport_pc lp parport bnep bluetooth sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf arc4 iwlagn mac80211 snd_hda_codec_hdmi snd_hda_codec_conexant qcserial snd_hda_intel snd_hda_codec usb_wwan snd_hwdep snd_seq cfg80211 uvcvideo videodev snd_seq_device media snd_pcm thinkpad_acpi e1000e snd_timer mxm_wmi pcspkr v4l2_compat_ioctl32 rfkill iTCO_wdt iTCO_vendor_support snd i2c_i801 intel_ips joydev snd_page_alloc soundcore wmi microcode ipv6 sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
[  173.858814] 
[  173.861482] Pid: 4826, comm: rm Not tainted 3.1.0-rc9+ #105 LENOVO 4313CTO/4313CTO
[  173.864162] RIP: 0010:[<ffffffff810f0c73>]  [<ffffffff810f0c73>] shmem_evict_inode+0x8b/0xd5
[  173.866713] RSP: 0018:ffff88022c47de08  EFLAGS: 00010246
[  173.869182] RAX: 000000004e92c20b RBX: ffff880228765f10 RCX: 0000000000038478
[  173.871654] RDX: 0000000012e1ecfd RSI: ffffffffffffffff RDI: ffffffff81d64300
[  173.874125] RBP: ffff88022c47de28 R08: 000000000000000e R09: 0000000000000000
[  173.876540] R10: 0000000000000000 R11: ffffea0007afaf40 R12: 0000000000000000
[  173.878834] R13: ffffffff81613c70 R14: ffff880228765f00 R15: 0000000000000000
[  173.881140] FS:  00007fbef7ac4720(0000) GS:ffff88023bc80000(0000) knlGS:0000000000000000
[  173.883483] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  173.885822] CR2: 0000000000000000 CR3: 000000022c337000 CR4: 00000000000006e0
[  173.888202] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  173.890595] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  173.892968] Process rm (pid: 4826, threadinfo ffff88022c47c000, task ffff880229aadc80)
[  173.895369] Stack:
[  173.897756]  ffff880228765f10 ffff880228766010 ffffffff81613c70 00007fffdf431330
[  173.900193]  ffff88022c47de58 ffffffff8113b944 ffff880228766000 ffff880228765f10
[  173.902662]  ffff88022aae9c00 ffffffff81613c70 ffff88022c47de88 ffffffff8113bb74
[  173.905117] Call Trace:
[  173.907532]  [<ffffffff8113b944>] evict+0x93/0x149
[  173.909943]  [<ffffffff8113bb74>] iput+0x17a/0x182
[  173.912345]  [<ffffffff8113327d>] do_unlinkat+0x110/0x15f
[  173.914742]  [<ffffffff811309b6>] ? path_put+0x1f/0x23
[  173.917132]  [<ffffffff810a2328>] ? audit_syscall_entry+0x145/0x171
[  173.919509]  [<ffffffff811344d1>] sys_unlinkat+0x29/0x2b
[  173.921882]  [<ffffffff8149dd42>] system_call_fastpath+0x16/0x1b
[  173.924223] Code: 44 f1 15 00 4c 89 63 e0 4c 89 63 e8 48 c7 c7 80 55 a3 81 e8 92 5a 3a 00 eb 09 48 8b 7f c8 e8 47 67 02 00 4c 8b 63 f0 4c 8d 73 f0 <4d> 8b 2c 24 eb 19 49 8b 7c 24 10 e8 2f 67 02 00 4c 89 e7 4d 89 
[  173.929579] RIP  [<ffffffff810f0c73>] shmem_evict_inode+0x8b/0xd5
[  173.932226]  RSP <ffff88022c47de08>
[  173.934866] CR2: 0000000000000000
[  173.951595] ---[ end trace b2877a78c7f8d86f ]---
-----------------------------------------------

Which may or may not be corruption. Will have to test more.

-- 
Bojan




More information about the Intel-gfx mailing list