FS#38821 - [linux] 3.12.7+ Bad page state/map in process

Attached to Project: Arch Linux
Opened by Dan Ziemba (zman0900) - Friday, 07 February 2014, 03:47 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 23 April 2014, 21:18 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Kernel versions greater than 3.12.6 cause bug traces to be printed to dmesg when starting certain processes, and sometimes completely freeze X. I'm not sure if its related, but this is happening while running as a Xen dom0. The most common time for this to happen for me is when starting firefox. Firefox will either crash after the windows appear but before webpages in the tabs have finished loading, or X will completely freeze. When X freezes, the system is still accessible through ssh, and any domU VMs still continue to work. In either case, crash or freeze, dmesg contains the same types of errors repeated many times. I have seen this problem with every kernel I've tried greater than 3.12.6, including 3.12.8, 3.12.9, and the current testing 3.13.2-1.

Tomorrow I may try building a vanilla kernel to see if this is an upstream or Arch problem. Let me know if there is any other info I can provide or debugging that would help.

Additional info:
* package version(s)
Working: linux-3.12.6-1
Not working: linux-3.12.8, linux-3.12.9-2, linux-3.13.2-1
Other package versions:
mesa, nouveau-dri: 10.0.3-1, 10.0.2-1
firefox: 26, 27
gnome-shell: 3.10.3-1
xen: 4.3.1

* config and/or log files etc.
bad-page-state-firefox-dmesg-kernel-3.13.2.txt:
This is what showed up in dmesg when firefox 27 was started and then crashed on kernel 3.13.2

bad-page-state-vim-dmesg-kernel-3.13.2.txt
This is what showed up in dmesg when I opened vim immediately after firefox crashed in order to paste the log into it.

Steps to reproduce:
- Upgrade kernel past 3.12.6
- Reboot
- Start GNOME 3 desktop
- Start Firefox
- observe crash or freeze within a minute or less
- view dmesg, through ssh if necessary
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Wednesday, 23 April 2014, 21:18 GMT
Reason for closing:  Fixed
Comment by Dan Ziemba (zman0900) - Friday, 07 February 2014, 03:51 GMT
Forgot to mention my computer's hardware:
Motherboard: ASRock Z77 Extreme 6, UEFI boot
CPU: Intel core i7 3770 ivy bridge
Mem: 16GB (dom0 has 9GB)
GPU: Nvidia GTX 260, nouveau

All filesystems are ext4 on top of lvm, except for the fat efi partition.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 07 February 2014, 04:15 GMT
Nothing to do here. Please report to upstream if not already reported. Thanks.
Comment by Dan Ziemba (zman0900) - Monday, 24 February 2014, 04:36 GMT
Turns out this was caused by change in the kernel involving NUMA interacting with Xen. The just released 3.13.5 includes the patch that fixes this, and I can confirm it works. More info here:

http://lists.xen.org/archives/html/xen-devel/2014-02/msg00199.html

Loading...