Bug 728531
| Summary: | [abrt] kernel: BUG: Bad page state in process systemd-readahe pfn:37ac5: TAINTED -----B | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:355164e2e25b7ff6f36073c644556c4f54524597 EFI32 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-07-10 21:40:39 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mads Kiilerich
2011-08-05 12:39:51 UTC
Created attachment 516891 [details]
dmesg
There are plenty of other bad page state messages - I guess they have the same root cause
The 3.2.10 update being pushed into updates-testing right now has some extra debug checks enabled in the VM code. If you could run that for a while, and report back anything that looks unusual, that might help. thanks. Created attachment 570704 [details]
dmesg with 3.2.10-1.fc16.i686.debug
interesting, thanks. This machine passes a memtest run ok ? That it happens so early in boot is very suspicious. memtest86+ do apparently not support EFI. "memtester 700" do not show any problems, and the machine do in general work fine both under OS/X and Linux. Are the other options for memtest? I guess this mainly is a problem of 32 bit EFI being less supported than 64 bit, perhaps because the older Apple firmware is more broken and grub+kernel doesn't have the necessary workarounds? it's feasible that the EFI memory map is either broken, or being mis-parsed. For the 32bit mini's, you're probably better off with bootcamp tbh. With "bootcamp" you mean the "CSM" bios emulation? That do unfortunately not work for booting from USB and is thus not an option for my use case. Despite these error messages the systems seem to work OK in EFI, something I wouldn't expect if the memory map really was mis-parsed. I now see a different kind of BUGs - all with i915 in the call stack. I don't know if that is a coincidence. [ 2.967284] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [ 2.989704] dracut: Starting plymouth daemon [ 3.133666] usb 5-2: New USB device found, idVendor=05ac, idProduct=8240 [ 3.133671] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.133674] usb 5-2: Product: IR Receiver [ 3.133677] usb 5-2: Manufacturer: Apple Computer, Inc. [ 3.142775] generic-usb 0003:05AC:8240.0005: hiddev0,hidraw4: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-0000:00:1d.3-2/input0 [ 3.703694] BUG: Bad page state in process plymouthd pfn:37e2a [ 3.703759] page:f5e4a540 count:0 mapcount:0 mapping: (null) index:0x0 [ 3.703812] page flags: 0x80400000(uncached) [ 3.703857] Modules linked in: i915 drm_kms_helper drm i2c_algo_bit i2c_core video [ 3.703869] Pid: 194, comm: plymouthd Not tainted 3.3.7-1.fc16.i686.PAE #1 [ 3.703872] Call Trace: [ 3.703884] [<c10fe6b7>] bad_page+0xa7/0xf0 [ 3.703888] [<c10ff85c>] get_page_from_freelist+0x46c/0x520 [ 3.703894] [<c1214c42>] ? cred_has_capability+0xb2/0x120 [ 3.703898] [<c10ffb7b>] __alloc_pages_nodemask+0x10b/0x740 [ 3.703903] [<c1215117>] ? selinux_vm_enough_memory+0x47/0x60 [ 3.703907] [<c110d37e>] shmem_getpage_gfp+0x23e/0x5f0 [ 3.703911] [<c110d764>] shmem_read_mapping_page_gfp+0x34/0x50 [ 3.703934] [<f8951dcc>] i915_gem_object_bind_to_gtt+0x19c/0x590 [i915] [ 3.703949] [<f8954fbc>] i915_gem_object_pin+0x12c/0x190 [i915] [ 3.703963] [<f895508e>] i915_gem_object_pin_to_display_plane+0x6e/0x180 [i915] [ 3.703969] [<c12692d5>] ? put_dec+0x85/0x90 [ 3.703973] [<c1269dc1>] ? string+0x31/0xb0 [ 3.703989] [<f89644a9>] intel_pin_and_fence_fb_obj+0x59/0x100 [i915] [ 3.703994] [<c126aa7d>] ? vsnprintf+0x9d/0x370 [ 3.704008] [<f8964bb1>] intel_pipe_set_base+0x81/0x270 [i915] [ 3.704074] [<f880fc55>] ? drm_get_connector_name+0x45/0x50 [drm] [ 3.704082] [<f874e93d>] drm_crtc_helper_set_config+0x63d/0xa20 [drm_kms_helper] [ 3.704095] [<f8812235>] drm_mode_setcrtc+0xe5/0x410 [drm] [ 3.704105] [<f8804e18>] drm_ioctl+0x378/0x480 [drm] [ 3.704115] [<f8812150>] ? drm_mode_setplane+0x3b0/0x3b0 [drm] [ 3.704125] [<f8804aa0>] ? drm_copy_field+0x80/0x80 [drm] [ 3.704132] [<c1156542>] do_vfs_ioctl+0x82/0x5a0 [ 3.704137] [<c1217867>] ? selinux_file_ioctl+0x47/0xe0 [ 3.704140] [<c1156acf>] sys_ioctl+0x6f/0x80 [ 3.704147] [<c102e909>] ? smp_apic_timer_interrupt+0x59/0x90 [ 3.704156] [<c155225f>] sysenter_do_call+0x12/0x28 [ 3.704159] Disabling lock debugging due to kernel taint 32bit EFI is pretty much unsupported, so it's unlikely this is going to improve any time soon. You might get lucky reporting it upstream, but honestly I'm not optimistic. |