Bug#558258: marked as done (linux-image-2.6-amd64: kernel BUG at mm/vmscan.c:725! when running under vmware ESXi 4)
Your message dated Sat, 1 Oct 2011 07:02:15 -0500
with message-id <20111001120215.GA17652@elie>
and subject line Re: kernel BUG at mm/vmscan.c:725! when running under vmware ESXi 4
has caused the Debian Bug report #558258,
regarding linux-image-2.6-amd64: kernel BUG at mm/vmscan.c:725! when running under vmware ESXi 4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
558258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558258
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-2.6-amd64: kernel BUG at mm/vmscan.c:725! when running under vmware ESXi 4
- From: peter neal <doabackflip@gmail.com>
- Date: Fri, 27 Nov 2009 13:23:58 +0000
- Message-id: <20091127132358.3517.65507.reportbug@x-client.adsl.dom>
Package: linux-image-2.6-amd64
Version: 2.6.26+17+lenny1
Severity: important
screenshot of kernel BUG to follow
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6-amd64 depends on:
ii linux-image-2.6.26-2-amd 2.6.26-19lenny2 Linux 2.6.26 image on AMD64
linux-image-2.6-amd64 recommends no packages.
linux-image-2.6-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Peter Neal wrote:
> It seems to have gone away, I haven't had the issue for ages now.
Thanks; closing. If you happen to remember whether it was a vmware
upgrade or a kernel upgrade (and in either case, which versions were
at the boundary that fixed it), that would be nice. I suppose the
current vmware and kernel versions you're using would be useful enough
as an upper bound for the next person stumbling on this.
--- End Message ---
Reply to: