Hardy and Intrepid freeze with kernel error: "Eeek! page_mapcount(page) went negative! (-1)"

Bug #252977 reported by Richard Corner
116
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned

Bug Description

In Xubuntu 8.04.1 my system keeps completely freezing, apparently randomly, leaving apparently no information except a message like the following in the syslog:

Jul 25 23:44:21 blackbox kernel: [ 1566.411452] Eeek! page_mapcount(page) went negative! (-1)

SYSTEM INFO:

Pentium 4 HT on an Asus P4P800 Deluxe motherboard with an ATI Radeon 9500 AGP graphics card and the restricted ATI driver installed via Envy_NG. I have 3 IDE drives (two attached via the main IDE controllers and one on the VIA VT1640 controller) and an eSATA drive (on one of the onboard SATA controllers), with a mixture of software RAID1 and RAID5 and non-RAID EXT3 and NTFS partitions.

Output of uname -a:

Linux blackbox 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

Here's a sysinfo report:

System information report, generated by Sysinfo: 26/07/2008 12:43:26 AM
http://sourceforge.net/projects/gsysinfo

SYSTEM INFORMATION
 Running Ubuntu Linux, the Ubuntu 8.04 (hardy) release.
 GNOME: unknown (unknown)
 Kernel version: 2.6.24-19-generic (#1 SMP Fri Jul 11 23:41:49 UTC 2008)
 GCC: 4.2.3 (i486-linux-gnu)
 Xorg: unknown (13 June 2008 01:08:21AM)
 Hostname: blackbox
 Uptime: 0 days 0 h 33 min

CPU INFORMATION
 GenuineIntel, Intel(R) Pentium(R) 4 CPU 2.40GHz
 Number of CPUs: 2
 CPU clock currently at 2398.911 MHz with 512 KB cache
 Numbering: family(15) model(2) stepping(9)
 Bogomips: 4802.06
 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts sync_rdtsc cid xtpr

MEMORY INFORMATION
 Total memory: 3042 MB
 Total swap: 5530 MB

STORAGE INFORMATION
 SCSI device - scsi0
  Vendor: ATA
  Model: WDC WD2000JB-00D
 SCSI device - scsi1
  Vendor: ATA
  Model: ST3200822A
 SCSI device - scsi1
  Vendor: HL-DT-ST
  Model: DVDRAM GSA-4160B
 SCSI device - scsi2
  Vendor: ATA
  Model: WDC WD2500KS-00M

HARDWARE INFORMATION
MOTHERBOARD
 Host bridge
  Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
  Subsystem: ASUSTeK Computer Inc. P4P800/P5P800 series motherboard
 PCI bridge(s)
  Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801 PCI Bridge (rev c2) (prog-if 00 [Normal decode])
 USB controller(s)
  Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
 ISA bridge
  Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
 IDE interface
  Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
  Subsystem: ASUSTeK Computer Inc. P4P800 series motherboard

GRAPHIC CARD
 VGA controller
  ATI Technologies Inc RV350 AS [Radeon 9550] (prog-if 00 [VGA controller])
  Subsystem: PC Partner Limited Unknown device 0200

SOUND CARD
 Multimedia controller
  Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
  Subsystem: ASUSTeK Computer Inc. P4P800 Mainboard

NETWORK
 Ethernet controller
  3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
  Subsystem: ASUSTeK Computer Inc. A7V600/P4P800/K8V motherboard

Tags: cft-2.6.27
Richard Corner (rcorner)
description: updated
Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
matjan (matty-janssen) wrote :
Download full text (3.2 KiB)

It looks like my box is suffering from the same bug, although in Ubuntu 8.04.1 (2.6.24-19). My system also freezes at random apparently, most of the time leaving no messages in the logs whatsoever. However, I found a same 'Eeek' message in the logs very recently:

Aug 12 11:32:30 quadpc kernel: [101268.516775] Eeek! page_mapcount(page) went negative! (-1)

Please see below for some additional information (and messages attached).

uname -a: Linux quadpc 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

Sysinfo output:

System information report, generated by Sysinfo: 13/08/2008 10:14:25 PM
http://sourceforge.net/projects/gsysinfo

SYSTEM INFORMATION
 Running Ubuntu Linux, the Ubuntu 8.04 (hardy) release.
 GNOME: 2.22.3 (Ubuntu 2008-07-09)
 Kernel version: 2.6.24-19-generic (#1 SMP Fri Jul 11 23:41:49 UTC 2008)
 GCC: 4.2.3 (i486-linux-gnu)
 Xorg: unknown (13 June 2008 01:08:21AM) (13 June 2008 01:08:21AM)
 Hostname: quadpc
 Uptime: 0 days 2 h 9 min

CPU INFORMATION
 GenuineIntel, Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
 Number of CPUs: 4
 CPU clock currently at 1596.000 MHz with 4096 KB cache
 Numbering: family(6) model(15) stepping(11)
 Bogomips: 4814.38
 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm

MEMORY INFORMATION
 Total memory: 2026 MB
 Total swap: 4769 MB

STORAGE INFORMATION
 SCSI device - scsi0
  Vendor: ATA
  Model: WDC WD3200AAKS-0
 SCSI device - scsi7
  Vendor: HL-DT-ST
  Model: DVD-RAM GSA-H55L
 SCSI device - scsi7
  Vendor: ATA
  Model: SAMSUNG SP1203N
 SCSI device - scsi4
  Vendor: ST350063
  Model: 0A

HARDWARE INFORMATION
MOTHERBOARD
 Host bridge
  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02)
  Subsystem: ASUSTeK Computer Inc. Unknown device 8276
 PCI bridge(s)
  Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) (prog-if 00 [Normal decode])
 USB controller(s)
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])

GRAPHIC CARD

SOUND CARD
 Multimedia controller
  Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
  Subsystem: ASUSTeK Computer Inc. Unknown device 829f

NETWORK

NVIDIA GRAPHIC CARD INFORMATION
 Model name: GeForce 8600 GTS
 Card Type: PCI-E
 Video RAM: unknown
 GPU Frequency: unknown
 Driver version: NVIDIA...

Read more...

Revision history for this message
Luka Čehovin (lukacu) wrote :

My experience is rather similar: the computer freezes at random ... one time it took a few hours, then three days. No log of the event is produced. However I cannot find the "Eeek!" message in the syslog ...

Sysinfo says:

SYSTEM INFORMATION
 Running Ubuntu Linux, the Ubuntu 8.04 (hardy) release.
 GNOME: 2.22.3 (Ubuntu 2008-07-09)
 Kernel version: 2.6.24-19-generic (#1 SMP Fri Jul 11 23:41:49 UTC 2008)
 GCC: 4.2.3 (i486-linux-gnu)
 Xorg: unknown (13 June 2008 01:08:21AM) (13 June 2008 01:08:21AM)
 Hostname: plasma
 Uptime: 0 days 9 h 45 min

CPU INFORMATION
 GenuineIntel, Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
 Number of CPUs: 4
 CPU clock currently at 2400.044 MHz with 4096 KB cache
 Numbering: family(6) model(15) stepping(11)
 Bogomips: 4803.52
 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm

MEMORY INFORMATION
 Total memory: 3545 MB
 Total swap: 9538 MB

STORAGE INFORMATION
 SCSI device - scsi0
  Vendor: ATA
  Model: Hitachi HDS72161
 SCSI device - scsi0
  Vendor: TSSTcorp
  Model: CDDVDW SH-S203D
 SCSI device - scsi1
  Vendor: ATA
  Model: Hitachi HDS72161

HARDWARE INFORMATION
MOTHERBOARD
 Host bridge
  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02)
  Subsystem: Giga-byte Technology Unknown device 5000
 PCI bridge(s)
  Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) (prog-if 00 [Normal decode])
  Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) (prog-if 00 [Normal decode])
 USB controller(s)
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) (prog-if 00 [UHCI])
  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI])
  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])

GRAPHIC CARD

SOUND CARD
 Multimedia controller
  Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
  Subsystem: Giga-byte Technology Unknown device a022

NETWORK

NVIDIA GRAPHIC CARD INFORMATION
 Model name: GeForce 8600 GT
 Card Type: PCI-E
 Video RAM: unknown
 GPU Frequency: unknown
 Driver version: NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008

Revision history for this message
Richard Corner (rcorner) wrote :

Attaching another syslog - see Aug 24 22:00:19 for the Eeek! message.

Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
Richard Corner (rcorner) wrote :

Looking back at the syslogs I have posted, I notice that the following message often occurs shortly before the Eeek! message:

NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..

Is this a clue?

When I first installed the OS there was a wireless card in a PCI slot on the machine. During my early attempts to figure out what was making this machine unstable I removed the wireless card. Perhaps there is something lingering as a result of this?

The label on the (now removed) wireless card says:

TP-LINK TL-WN651G
108M Wireless PCI Adapter
Super-G (TM) and eXtended Range (TM)
108Mbps
2.4GHz - 802.11g/b
FCC ID: TE7WN65XG

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Richard Corner (rcorner) wrote :

Thank you for the suggestion that I try 2.6.27. I have installed the following:

Linux blackbox 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux

I'll let you know how this goes.

Revision history for this message
Richard Corner (rcorner) wrote :

I am running the Intrepid alpha now, with the open-source ATI driver instead of the proprietary one I was running under Hardy, and still the problem occurs. See the attached syslog.

Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
Richard Corner (rcorner) wrote :
Revision history for this message
Richard Corner (rcorner) wrote :

Today something slightly different happened. See the attached syslog (syslog-2009-09-12.txt). It includes the Eeek! message but this happened much closer to startup than usual, and the OS continued to run for a minute or two after it, with various other error messages.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in linux:
status: New → Confirmed
Revision history for this message
JP Courtney (jpc386) wrote :

Are you Crazy!? If this was Debian, the entire team would have stopped to concentrate on this very serious bug. One volunteer ain't enough. I too have been suffering from this bug through hardy AND intrepid, and I cannot supply my syslog because I've been forced to distro-hop since this bug destroyed half of my homework. Ubuntu is great, it really is, but I think I'll stick with Debian testing because at least Debian has the sense to concentrate on stability first.

Again, EVERYONE needs to work on this together. After all, Average Joe's mother knows nothing about system logs, but she hates it when her computer freezes while writing an email or IM to the grandkids. If Ubuntu wants to be truly user friendly, then this needs to take priority.

Changed in linux:
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Medium → High
Revision history for this message
Richard Corner (rcorner) wrote :

OK, since the early releases of Intrepid I have not had this particular problem. Though there have been a lot of freezeups during boot on this particular machine I have not seen the "Eeek!" message or the freezeups while using the desktop.

But today I upgraded to the following:

Linux blackbox 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

and the error is back! Xubuntu booted fine then, as before with Hardy, suddenly froze while I was using Firefox at the desktop.

See the attached syslog:

Nov 27 23:57:32 blackbox kernel: [ 174.153965] Eeek! page_mapcount(page) went negative! (-1)
Nov 27 23:57:32 blackbox kernel: [ 174.153981] page pfn = a6ff3
Nov 27 23:57:32 blackbox kernel: [ 174.153986] page->flags = 80000068
Nov 27 23:57:32 blackbox kernel: [ 174.153993] page->count = 1
Nov 27 23:57:32 blackbox kernel: [ 174.153997] page->mapping = f33734e1
Nov 27 23:57:32 blackbox kernel: [ 174.154038] vma->vm_ops = 0x0

Revision history for this message
Richard Corner (rcorner) wrote :

And again - see attached syslog (overlaps a bit with the one previously posted):

Nov 28 00:17:26 blackbox kernel: [ 1158.042009] Eeek! page_mapcount(page) went negative! (-1)
Nov 28 00:17:26 blackbox kernel: [ 1158.042024] page pfn = a8d4b
Nov 28 00:17:26 blackbox kernel: [ 1158.042029] page->flags = 80000068
Nov 28 00:17:26 blackbox kernel: [ 1158.042035] page->count = 1
Nov 28 00:17:26 blackbox kernel: [ 1158.042040] page->mapping = f2155d31
Nov 28 00:17:26 blackbox kernel: [ 1158.042072] vma->vm_ops = 0x0

Revision history for this message
Richard Corner (rcorner) wrote :

And again - this time while scrolling a window in Opera:

Nov 28 00:27:57 blackbox kernel: [ 596.612527] Eeek! page_mapcount(page) went negative! (-1)
Nov 28 00:27:57 blackbox kernel: [ 596.612543] page pfn = a5793
Nov 28 00:27:57 blackbox kernel: [ 596.612548] page->flags = 80000068
Nov 28 00:27:57 blackbox kernel: [ 596.612554] page->count = 1
Nov 28 00:27:57 blackbox kernel: [ 596.612559] page->mapping = f2b74d21
Nov 28 00:27:57 blackbox kernel: [ 596.612591] vma->vm_ops = 0x0

Revision history for this message
Andy Whitcroft (apw) wrote : Re: [Bug 252977] Re: Hardy and Intrepid freeze with kernel error: "Eeek! page_mapcount(page) went negative! (-1)"

On Fri, Nov 28, 2008 at 05:12:49AM -0000, Richard Corner wrote:

> OK, since the early releases of Intrepid I have not had this particular
> problem. Though there have been a lot of freezeups during boot on this
> particular machine I have not seen the "Eeek!" message or the freezeups
> while using the desktop.
>
> But today I upgraded to the following:
>
> Linux blackbox 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
> GNU/Linux
>
> and the error is back! Xubuntu booted fine then, as before with Hardy,
> suddenly froze while I was using Firefox at the desktop.
>
> See the attached syslog:
>
> Nov 27 23:57:32 blackbox kernel: [ 174.153965] Eeek! page_mapcount(page) went negative! (-1)
> Nov 27 23:57:32 blackbox kernel: [ 174.153981] page pfn = a6ff3
> Nov 27 23:57:32 blackbox kernel: [ 174.153986] page->flags = 80000068
> Nov 27 23:57:32 blackbox kernel: [ 174.153993] page->count = 1
> Nov 27 23:57:32 blackbox kernel: [ 174.153997] page->mapping = f33734e1
> Nov 27 23:57:32 blackbox kernel: [ 174.154038] vma->vm_ops = 0x0

It seems that you have a relativly reproducible one here. As its so
easy to trigger for you would you be able to try the newer kernel in
-proposed, currently 2.6.27-10.20 and confirm if it is there too?

Revision history for this message
Richard Corner (rcorner) wrote :

Andy, thanks for your attention to this bug. I am installing the updates from intrepid-proposed and will let you know whether the problem continues.

Revision history for this message
Richard Corner (rcorner) wrote :

It has only been a day, but I have not had any freezes with the new kernel:

richard@blackbox:~$ uname -a
Linux blackbox 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux

Revision history for this message
Andy Whitcroft (apw) wrote :

@Richard Corner -- that sounds encouraging. I will mark this as Fix Committed as it seems the fix is in the -proposed kernel. If you find this reproduces on the -proposed kernel you should move this bug back to New. Thanks for testing.

Changed in linux:
assignee: ubuntu-kernel-team → apw
status: Triaged → In Progress
status: In Progress → Fix Committed
Revision history for this message
Richard Corner (rcorner) wrote :

Just to confirm: the kernel 2.6.27-10 does seem more stable, and I have not seen the Eeek! message since installing it.

Revision history for this message
Richard Corner (rcorner) wrote :

Happened again. See attached syslog for three new occurrences.

Linux blackbox 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux

Revision history for this message
Richard Corner (rcorner) wrote :

Resetting status because the problem happened again on the proposed kernel.

Changed in linux:
status: Fix Committed → New
Revision history for this message
Erektium (meizinteizi) wrote :

I always have the freeze when I'm browsing ubuntu forums. It's really annoying.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Richard,

Can you also post your dmesg output which captures this error. The reason I ask is because there should be a corresponding stack trace included in the dmesg output that would be useful to see. Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Andy,

I'm also attaching information from a similar (likely duplicate) bug report, bug 311545, from Matt Zimmerman. When he saw this he was preparing to debug bug 311254, which included:

1. Installing xserver-xorg-core-dbg
2. Plugging in a USB remote control
3. Opening an ssh session into the system
4. Running screen
5. Running 'ps aux |grep X' to get the PID for the X server

at this point he noticed that the ps command hung partway through, and examining dmesg, found the errors. Many operations would block at this point, and so he had to reboot.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I forgot to mention Matt was running the newer 2.6.28-3 Jaunty kernel.

Revision history for this message
Richard Corner (rcorner) wrote :

Leann,

Attached: some syslog and dmesg files as requested. As far as I can tell from the date stamps these go together. Let me know if they don't contain what you need.

My current kernel: Linux blackbox 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:52 UTC 2008 i686 GNU/Linux

Andy Whitcroft (apw)
Changed in linux:
status: New → In Progress
Revision history for this message
Andy Whitcroft (apw) wrote :
Download full text (10.4 KiB)

Looking through the various instances reported here, we have a couple which have a real stack trace attached:

    Aug 12 11:32:30 quadpc kernel: [101268.516775] Eeek! page_mapcount(page) went negative! (-1)
    Aug 12 11:32:30 quadpc kernel: [101268.516785] page pfn = 30b48
    Aug 12 11:32:30 quadpc kernel: [101268.516787] page->flags = 40080014
    Aug 12 11:32:30 quadpc kernel: [101268.516789] page->count = 0
    Aug 12 11:32:30 quadpc kernel: [101268.516790] page->mapping = 00000000
    Aug 12 11:32:30 quadpc kernel: [101268.516818] vma->vm_ops = 0x0
    Aug 12 11:32:30 quadpc kernel: [101268.516836] ------------[ cut here ]------------
    Aug 12 11:32:30 quadpc kernel: [101268.516842] kernel BUG at /build/buildd/linux-2.6.24/mm/rmap.c:631!
    Aug 12 11:32:30 quadpc kernel: [101268.516846] invalid opcode: 0000 [#2] SMP
    Aug 12 11:32:30 quadpc kernel: [101268.516852] Modules linked in: vmnet(P) vmmon(P) rfcomm l2cap bluetooth parport_pc ppdev ipv6 acpi_cpufreq cpufreq_userspace cpufreq_ondemand cpufreq_powersave cpufreq_conservative cpufreq_stats freq_table sbs sbshc video output container dock battery xt_limit xt_tcpudp iptable_mangle ipt_LOG ipt_MASQUERADE nf_nat ipt_TOS ipt_REJECT nf_conntrack_irc nf_conntrack_ftp nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables nls_iso8859_1 nls_cp437 vfat fat ac coretemp w83627ehf hwmon_vid sbp2 lp parport loop snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep snd_seq_dummy snd_seq_oss ov511 sr_mod videodev snd_seq_midi nvidia(P) cdrom v4l2_common snd_rawmidi atl1 i2c_core v4l1_compat snd_seq_midi_event snd_seq snd_timer snd_seq_device intel_agp iTCO_wdt button snd shpchp pci_hotplug agpgart iTCO_vendor_support soundcore pcspkr evdev usbhid hid usb_storage ext3 jbd mbcache sg sd_mod libusual pata_jmicron pata_acpi ata_generic ata_piix ahci oh
    Aug 12 11:32:30 quadpc kernel: i1394 libata scsi_mod ieee1394 via_rhine mii uhci_hcd ehci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
    Aug 12 11:32:30 quadpc kernel: [101268.517058]
    Aug 12 11:32:30 quadpc kernel: [101268.517063] Pid: 11524, comm: hadam3_um_5.03_ Tainted: P B D (2.6.24-19-generic #1)
    Aug 12 11:32:30 quadpc kernel: [101268.517067] EIP: 0060:[page_remove_rmap+0xf9/0x110] EFLAGS: 00010246 CPU: 2
    Aug 12 11:32:30 quadpc kernel: [101268.517074] EIP is at page_remove_rmap+0xf9/0x110
    Aug 12 11:32:30 quadpc kernel: [101268.517079] EAX: 00000000 EBX: c1616900 ECX: 00000046 EDX: 00000000
    Aug 12 11:32:30 quadpc kernel: [101268.517083] ESI: e4059dc0 EDI: 78d41000 EBP: dcd381c0 ESP: cb4e9ec8
    Aug 12 11:32:30 quadpc kernel: [101268.517088] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    Aug 12 11:32:30 quadpc kernel: [101268.517092] Process hadam3_um_5.03_ (pid: 11524, ti=cb4e8000 task=e35c05c0 task.ti=cb4e8000)
    Aug 12 11:32:30 quadpc kernel: [101268.517097] Stack: c03b377a 00000000 00000020 fff98504 c017c398 00000000 30b48067 c1f99080
    Aug 12 11:32:30 quadpc kernel: [101268.517112] c04782a0 c20202b0 79084fff 74bed000 e4059dc0 cb4e9f60 00000000 002ab000
    Aug 12 11:32:30 quadpc kernel: [101268.517126] 000...

Revision history for this message
Andy Whitcroft (apw) wrote :

Those of you who are seeing this regularly, if you are able to test the 2.6.28 based kernel as from Jaunty and confirm that the issue is still there. This kernel can be found here:

    32bit: http://gb.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.28-4-virtual_2.6.28-4.5_i386.deb
    64bit: http://gb.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.28-4-generic_2.6.28-4.5_amd64.deb

Revision history for this message
Matt Zimmerman (mdz) wrote :

@Andy: I've seen this, or something like it, *only* on Jaunty (see bug 311545)

Revision history for this message
Richard Corner (rcorner) wrote :

Andy, the 2.6.28.4 kernel did not fix the problem. See the attached archive, containing two dmesg files and one syslog.

Revision history for this message
Richard Corner (rcorner) wrote :

I don't know whether this is relevant, but today I got a different kind of hang - the symptoms on screen were the same, with the whole system becoming unresponsive to mouse or keyboard, and unavailable over the network, shortly after I logged in to the (XFCE) desktop. But in the logs this looks quite different, with many segfaults in udevd earlier during bootup. I find it curious that the point where I was forced to restart the system resembles the point where the Eeek! error tends to occur (see syslog in the attached archive).

I am going to run memtest on this machine again just to be sure, though previous runs have not turned up any RAM errors.

Revision history for this message
Richard Corner (rcorner) wrote :

Ran several passes of memtest on the machine - no RAM errors.

Revision history for this message
Richard Corner (rcorner) wrote :

I finally got around to hooking up a serial console so that I could record the error messages that flash by on the console. I attach the output from one "Eeek!" incident.

What happened here was: I booted the computer and logged in as usual, but instead of my usual XFCE desktop with icons and wallpaper I saw just a grey desktop with the XFCE panels top and bottom. I clicked the Quit icon on the top panel and chose "Log out" and the result was what you see in the attachment.

There are two files in the attached archive. Between these two I stupidly pressed CTRL-ALT-DEL on the wrong machine by accident (I pressed it on the machine I was logging from, not the machine with the problem), so I missed some of the error messages that were continually flashing by on screen while the machine running minicom rebooted. The second file is what I managed to capture after it rebooted.

Revision history for this message
Richard Corner (rcorner) wrote :

Oddly, the syslog has started including some trace information since I redirected tty0 output to the serial port. I don't know why this would be, but attached is the console output and corresponding syslog for another Eeek! incident. This happened when I wasn't doing anything directly on the machine, but had the desktop and (I think) Thunar file manager open. Unlike the previous incident the desktop was displaying correctly, and the desktop only froze about a minute after I saw the errors appearing on the minicom terminal.

Revision history for this message
Andy Whitcroft (apw) wrote :

@Richard -- yeah i am not supprised. The slowness (relativly) of the serial console would keep the machine alive a little longer, seemingly long enough to allow syslog to get the info out of the kernel and onto the disk. Thanks for the additional logs.

Revision history for this message
Andy Whitcroft (apw) wrote :

After some digging it seems that there have been a couple of clusters of Eeek! panics. Those since 2.6.21 seem to have always appeared on systems with Nvidia graphics. Looking through the numerous panics reported here (with full stacks) I see that at least one of you is using a proprietory driver, perhaps Nvidia.

So could those of you who are hitting this issue indicate whether you have Nvidia or other proprietory drivers installed. If so could you report the output of the 'dkms status' command. Also if you are able could you try running with the OSS 'nv' X driver for a while to see if that eliminates the issue.

Changed in linux:
status: In Progress → Incomplete
Revision history for this message
SrdjanTodorovic (todorovic-s) wrote :

@Andy
At least one of the traces had proprietary ATI drivers.
But one thing that's interesting, is of all the reports I've seen (not that many I guess), the machines are running SMP kernels on multi-core CPUs.

I had one of these Eeek! messages just the other week... after a long long period of no Eeek!s.
Memtest (even after 15 hours run-time overnight) always gives good results.

Interestingly, I've never had these Eeek messages on my Slackware box. This Kubuntu box has apps segfaulting at times.

As for running the nv driver - the hangs happen at unpredictable times, usually you have to wait many days/weeks before the next crash. This makes running nv driver for long periods a bit impractical.

Revision history for this message
Richard Corner (rcorner) wrote :

@Andy,

I have proprietary ATI drivers enabled. I will try it for a while without, though on this machine I tried that before and still experienced random hangs. Not sure whether they were the same hangs though - so I'll give it a go.

Output of "dkms status" is:

vboxdrv, 2.0.6, 2.6.28-4-generic, i686: installed
vboxdrv, 2.0.6, 2.6.27-10-generic, i686: installed
vboxdrv, 2.0.6, 2.6.27-7-generic, i686: installed
vboxdrv, 2.0.6, 2.6.27-11-generic, i686: installed
vboxdrv, 2.0.6, 2.6.27-9-generic, i686: installed
fglrx, 8.552, 2.6.28-4-generic, i686: installed (WARNING! Diff between built and installed module!)
fglrx, 8.552, 2.6.27-10-generic, i686: installed
fglrx, 8.552, 2.6.27-11-generic, i686: installed
fglrx, 8.552, 2.6.27-9-generic, i686: installed

Revision history for this message
Charles Perreault (muganor) wrote : Re: [Bug 252977] Re: Hardy and Intrepid freeze with kernel error: "Eeek! page_mapcount(page) went negative! (-1)"

I had the "Eeek! page_mapcount = -1" kernel panics on AMD servers using only
1 cpu, with perfect RAM. All those servers are CLI only, not any X drivers
whatsoever. You should search somewhere else.

--------------------------------------------------
From: "SrdjanTodorovic" <email address hidden>
Sent: Monday, January 26, 2009 9:35 AM
To: "Charles Perreault" <email address hidden>
Subject: [Bug 252977] Re: Hardy and Intrepid freeze with kernel error:
"Eeek! page_mapcount(page) went negative! (-1)"

> @Andy
> At least one of the traces had proprietary ATI drivers.
> But one thing that's interesting, is of all the reports I've seen (not
> that many I guess), the machines are running SMP kernels on multi-core
> CPUs.
>
> I had one of these Eeek! messages just the other week... after a long long
> period of no Eeek!s.
> Memtest (even after 15 hours run-time overnight) always gives good
> results.
>
> Interestingly, I've never had these Eeek messages on my Slackware box.
> This Kubuntu box has apps segfaulting at times.
>
> As for running the nv driver - the hangs happen at unpredictable times,
> usually you have to wait many days/weeks before the next crash. This
> makes running nv driver for long periods a bit impractical.
>
> --
> Hardy and Intrepid freeze with kernel error: "Eeek! page_mapcount(page)
> went negative! (-1)"
> https://bugs.launchpad.net/bugs/252977
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Revision history for this message
Richard Corner (rcorner) wrote :

@Andy,

I disabled the ATI proprietary driver and still get the Eeek! message. See the attached logs.

Revision history for this message
georg wiltschek (georg-wiltschek) wrote :

Same issues here with Kubuntu 8.04.2 (Linux yeheyuan 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 GNU/Linux). Installed new RAM a couple of days ago, but memtest says it's fine. As of today the machine crashes frequently, sometimes shutting down X, sometimes garbling the screen...

Here are some lines from the syslog from the last 3 crashes:

Feb 16 12:30:53 yeheyuan kdm[5190]: X server terminated: [0, 0, 0]
Feb 16 12:30:53 yeheyuan kdm[5190]: X server for display :0 terminated unexpectedly
Feb 16 12:30:53 yeheyuan kdm[5190]: StartServerSucces
Feb 16 12:30:55 yeheyuan kernel: [ 4334.151334] [fglrx] PCIe has already been initialized. Reinitializing ...
Feb 16 12:30:55 yeheyuan kernel: [ 4334.169728] [fglrx] Reserve Block - 0 offset = 0X3ff0000 length = 0X10000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.169734] [fglrx] Reserve Block - 1 offset = 0X3fef000 length = 0X1000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.169737] [fglrx] Reserve Block - 2 offset = 0X3fee000 length = 0X1000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.169739] [fglrx] Reserve Block - 3 offset = 0X0 length = 0X40000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.169742] [fglrx] Reserve Block - 4 offset = 0X3fae000 length = 0X40000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.280421] [fglrx] interrupt source 20008000 successfully enabled
Feb 16 12:30:55 yeheyuan kernel: [ 4334.280429] [fglrx] enable ID = 0x00000004
Feb 16 12:30:55 yeheyuan kernel: [ 4334.280766] [fglrx] Receive enable interrupt message with irqEnableMask: 20008000
Feb 16 12:30:55 yeheyuan kernel: [ 4334.280961] [fglrx] interrupt source 10000000 successfully enabled
Feb 16 12:30:55 yeheyuan kernel: [ 4334.280964] [fglrx] enable ID = 0x00000005
Feb 16 12:30:55 yeheyuan kernel: [ 4334.281171] [fglrx] Receive enable interrupt message with irqEnableMask: 10000000
Feb 16 12:30:57 yeheyuan kernel: [ 4334.457430] Eeek! page_mapcount(page) went negative! (-14391805)

Feb 16 12:33:50 yeheyuan kernel: [ 41.720154] amarokapp[6117]: segfault at 37a2b568 eip b7feb16c esp bf8dafcc error 4
Feb 16 12:33:50 yeheyuan kernel: [ 90.985337] lesspipe[6126]: segfault at 0000000b eip b7e7f386 esp bf9ddf3c error 4
Feb 16 12:33:50 yeheyuan kernel: [ 90.985751] Eeek! page_mapcount(page) went negative! (-5181311)

Feb 16 12:40:29 yeheyuan kernel: [ 122.277204] tg3: eth0: Link is up at 10 Mbps, half duplex.
Feb 16 12:40:29 yeheyuan kernel: [ 122.277214] tg3: eth0: Flow control is off for TX and off for RX.
Feb 16 12:40:29 yeheyuan kernel: [ 122.280024] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 16 12:40:30 yeheyuan avahi-daemon[5225]: Registering new address record for fe80::2c0:9fff:fe77:9e1a on eth0.*.
Feb 16 12:40:37 yeheyuan ntpdate[4118]: step time server 131.130.1.11 offset 0.606196 sec
Feb 16 12:40:39 yeheyuan kernel: [ 126.686119] eth0: no IPv6 routers present
Feb 16 12:43:39 yeheyuan kernel: [ 165.848051] drkonqi[6625]: segfault at 36ecd616 eip 36ecd616 esp bfb7159c error 4
Feb 16 12:43:41 yeheyuan kernel: [ 103.805536] kicker[6666]: segfault at 00000194 eip b7fdce31 esp bf8cd168 error 4
Feb 16 12:43:41 yeheyuan kernel: [ 103.806053] Eeek! page_mapcount(page) went negative! (-538976289)

Revision history for this message
georg wiltschek (georg-wiltschek) wrote :

i tried to boot with noapic and nolapic boot options and it ran well for a while, then ktorrent, firefox, pidgin crashed within a couple of minutes and the system went down.

switched back to my old RAM now, will see if that helps.

another thing i wonder about (even if i think it's just coincidence) is this post from one of the dupes of this bug:

"ChrisLees wrote on 2008-02-18: (permalink)
I have run Memtest86 for 5 passes. The RAM (which is new, anyway) passes. I have a Core 2 Duo. The problem has only happened twice - once on the 14th of Feb, the other time on the 16th. I have had this computer unaltered since the beginning of the year."

had a strange crash two days ago and it got really bad today... any chance that this is somehow related to the date?

Revision history for this message
Richard Corner (rcorner) wrote :

I'm still on Intrepid but using the Jaunty kernel 2.6.28-9-generic. The problem still occurs. I attach another capture from the serial console, showing the error happening on shutdown.

Revision history for this message
Thomas S. (tstuetz) wrote :

same bug, different hw and kernel 2.6.24-23-generic.
if more information on my system is needed please say what you need.

br
thomas

Revision history for this message
Andy Whitcroft (apw) wrote :

It is most bizarre how easily those of you who are affected seem to be able to trigger it and yet how hard the rest of us can push our systems without triggering it at all. You must be doing something/have something we do not do/have.

Looking the logs it looks like @Richard and @mdz are both using virtualisation, one with virtual-box and the other with kvm. I wonder if there is correlation there? Could the rest of you confirm whether you are using one of these?

Revision history for this message
Andy Whitcroft (apw) wrote :

@Thomas -- could you attach your dmesg output when this occurs please.

Revision history for this message
mukesh agrawal (launchpad-net-mukesh) wrote :

Just saw the same symptom on a Pentium Dual E2140 with ATI Radeon HD 2400 XT, using the radeonhd X driver.

/var/log/kern.log attached

Revision history for this message
mukesh agrawal (launchpad-net-mukesh) wrote :

@Andy: Forgot to mention that I'm not using virtualization here.

Revision history for this message
randallw (rwayth) wrote :

Hi,

Not sure if this is helpful, but I got this crash today when logging out of gnome. The machine hung at exactly the point where normally gdm would restart. I was using the "nv" driver and was about to install the proprietary nvidia driver. The only thing that I can think of that might be relevant (following from posts above) is that the video card I'm using is quite new (a GTS250), so maybe causes bugs in nv. (maybe...)

Syslog is attached below. System is a fairly fresh install of Hardy. No virtualization or other funny business.
Linux curta 2.6.24-24-generic #1 SMP Wed Apr 15 15:11:35 UTC 2009 x86_64 GNU/Linux
The hardware is an Asus P5Q-E mobo. CPU is Core(TM)2 Quad CPU Q9400.
I can supply more info if required.

attached goodies:
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce GTS 250] (rev a2)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b1)
05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 14)
05:03.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70)

Revision history for this message
randallw (rwayth) wrote :

Apologies. Please ignore what I have posted above. It seems that I had a bad memory stick in my workstation. All has been well after I removed it.

Revision history for this message
Andres Mujica (andres.mujica) wrote :

digging around i've found this:

- it could be hw related.
http://lkml.indiana.edu/hypermail/linux/kernel/0812.3/01426.html
http://www.flickr.com/photos/kernelslacker/251807263/in/set-72157594298237090/

- it could be triggered by a proprietary module (including vbox)
http://bugs.gentoo.org/138366
http://lkml.indiana.edu/hypermail/linux/kernel/0607.0/0136.html

- it seems to be present since 2.6.18
http://lkml.org/lkml/2006/12/12/177

- a patch to get more debugging output is available but it never went upstream (as far as i could check)
http://lkml.org/lkml/2006/12/19/30

Probably testing with Mainline kernel we can rule out the modules

https://wiki.ubuntu.com/KernelMainlineBuilds

(i've marked some dupes including mdz's one, the mm/rmap.c:xxx line is the only one missing)

Revision history for this message
Andres Mujica (andres.mujica) wrote :
Revision history for this message
Jason B (jasonb) wrote :

I am able to reliably reproduce this issue though it is triggered by a bit of custom code I do not have access to.

What I believe to be relevant details.

The Host: ubuntu 8.04.3 LTS
kernel 2.6.24-24-xen
Xen 3.2

The issue manifests while running under the -xen kernel but does not occur when running under kernel 2.6.24-24-server

[ 27.667553] Eeek! page_mapcount(page) went negative! (-1)
[ 27.667646] page pfn = ffffffffffffffff
[ 27.667728] page->flags = 15d
[ 27.667804] page->count = 9460
[ 27.667882] page->mapping = 00000000000033f2
[ 27.667974] vma->vm_ops = 0x0
[ 27.668054] vma->vm_file->f_op->mmap = xen_mmap_mem+0x0/0x40
[ 27.668145] ------------[ cut here ]------------
[ 27.668226] kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/mm/rmap.c:631!
[ 27.668325] invalid opcode: 0000 [1] SMP
[ 27.668530] CPU 1
[ 27.668670] Modules linked in: bridge sbs container battery sbshc
dock ac iptable_filter ip_tables x_tables af_packet parport_pc lp
[ 27.672687] Pid: 5320, comm: espd Not tainted 2.6.24-24-xen #1
[ 27.672767] RIP: e030:[<ffffffff8028e7eb>] [<ffffffff8028e7eb>]
page_remove_rmap+0x12b/0x140
[ 27.672927] RSP: e02b:ffff8800ef4e1d88 EFLAGS: 00010292
[ 27.673007] RAX: 0000000000000045 RBX: ffff880002a24fc8 RCX: ffffffffff5f7000
[ 27.673089] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8058ce64
[ 27.673170] RBP: ffff8800f20c1f00 R08: 0000000000000000 R09: ffffffffff5b1760
[ 27.673252] R10: 0000000000000000 R11: ffffffff80359a10 R12: 00007f5855b3d000
[ 27.673333] R13: 0000000000000020 R14: ffff880002a24fc8 R15: 00007f5855b3d000
[ 27.673418] FS: 00007f93434a96e0(0063) GS:ffffffff805c7080(0000)
knlGS:0000000000000000
[ 27.673511] CS: e033 DS: 0000 ES: 0000
[ 27.673591] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 27.673673] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 27.673755] Process espd (pid: 5320, threadinfo ffff8800ef4e0000,
task ffff8800f2b9e040)
[ 27.673850] Stack: 00000000000000c0 ffff8800f166b970
00007f5855b2e000 ffffffff80283e8c
[ 27.674257] ffffffff8061a420 ffff880001ac9438 00007f5855b3cfff
0000000000000000
[ 27.674603] ffff8800ef4e1eb0 00007f5855b3d000 00007f5855b2d000
ffff8800f20c1f00
[ 27.674874] Call Trace:
[ 27.675024] [<ffffffff80283e8c>] unmap_vmas+0x69c/0xb30
[ 27.675112] [<ffffffff80289e08>] unmap_region+0xc8/0x160
[ 27.675196] [<ffffffff8028ad2a>] do_munmap+0x22a/0x2f0
[ 27.675280] [<ffffffff80471f92>] __down_write_nested+0x12/0x100
[ 27.675364] [<ffffffff8028ae3d>] sys_munmap+0x4d/0x80
[ 27.675447] [<ffffffff8020c698>] system_call+0x68/0x6d
[ 27.675529] [<ffffffff8020c630>] system_call+0x0/0x6d
[ 27.675612]
[ 27.675687]
[ 27.675688] Code: 0f 0b eb fe 48 8b 53 10 e9 65 ff ff ff 0f 1f 84
00 00 00 00
[ 27.677170] RIP [<ffffffff8028e7eb>] page_remove_rmap+0x12b/0x140
[ 27.677314] RSP <ffff8800ef4e1d88>
[ 27.677395] ---[ end trace 480ff852f0bf3e83 ]---

Revision history for this message
Richard Corner (rcorner) wrote :

It has been a while since I followed up on this bug report. I removed Ubuntu from the machine in question and tried Debian instead, and neither the stable nor the testing builds were 100% stable on this machine. Just as a test I replaced Debian with Windows 7. This has not proved 100% reliable either on the machine, with occasional blue screen errors. At this point I suspect there is a hardware fault somewhere in the CPU or motherboard of this machine. I have not seen this bug on any of my other Ubuntu machines.

Andy Whitcroft (apw)
Changed in linux (Ubuntu):
assignee: Andy Whitcroft (apw) → nobody
Revision history for this message
nutznboltz (nutznboltz-deactivatedaccount) wrote :

If this is a hardware problem then explain why so many people with different hardware experience it?

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

For at least two of these reporters, it appears to be a hardware issue. That does not mean the bug is not present for others, and it does not eliminate hardware for others.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Given the original reporters impression that this is faulty hardware related, I will be closing this bug. Those of you who seem to be experiencing this: please file a new bug for your individual hardware so that we can narrow the causes. You can use 'ubuntu-bug linux' from the terminal window or run apport interactively.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.